Skip to content

Operations guide

WMS vs inventory management software: which do you actually need?

Work through the requirements and trade-offs before choosing a product or planning a change.

Go to the evaluation checklist →

Understand the decision

It is one of the most common questions we hear from growing ANZ wholesalers, distributors and manufacturers: do I need a warehouse management system, or is inventory management software enough? The two are often pitched as interchangeable, and plenty of buyers sign up for one when the problem they actually have calls for the other. The confusion is understandable, both deal with stock, but they solve genuinely different problems.

The cleanest way to think about it: inventory management software is quantity- and value-centric. It answers 'what stock do I own, how much of it, what did it cost, and what's it worth?' Tools like Cin7 Core, Unleashed, and the inventory add-ons that bolt onto Xero or MYOB track SKUs, stock-on-hand, reorder points, costing, batches and expiry. A warehouse management system (WMS) is location- and execution-centric. It answers 'where exactly is that stock, what's the fastest path to pick it, and did the right item actually go in the box?' That means bin and location tracking, directed putaway, wave and zone picking paths, RF/barcode scanning, slotting and cycle counts.

Confirm current subscription, allowances and implementation costs against an itemised proposal; the commercial structure is explained below. Many ANZ SMBs buy inventory software first, quite rightly, then hit a wall a year or two later when order volume climbs, mispicks creep up, and 'where is it?' becomes the daily fire drill. That wall is where a WMS earns its keep.

This guide explains the real difference, gives honest guidance on when a pure inventory tool is genuinely all you need (and cheaper and simpler for it), and shows where OpsUI sits, a modular ANZ platform that gives you both the inventory module and the warehouse execution modules in one system, so you can start with stock control and switch on real WMS depth the day the floor demands it, without ripping anything out.

OpsUI publishes this guide and is one of the options discussed. Use the operating guidance to frame your evaluation. Vendor-specific details without a checked primary source remain unverified; confirm them against the proposal you receive.

Requirements and options.

Conceptual illustration: Warehouse shelving and a picking tote connected by a short violet route.

Primary question it answers

OpsUI context
Where is the stock and how do we move it accurately? (location + physical execution)
Wider options and considerations
What stock do we own, how much, and what's it worth? (quantity + value)

Vendor-specific detail: confirm current scope and evidence.

Stock location granularity

OpsUI context
Down to bin/shelf/zone; every unit has a physical address and a movement history
Wider options and considerations
Typically warehouse- or location-level; bin-level varies by product and tier

Vendor-specific detail: confirm current scope and evidence.

Directed putaway

OpsUI context
System tells receivers exactly where to store incoming stock based on rules and capacity
Wider options and considerations
Usually manual, staff decide and record where it went, if at all

Vendor-specific detail: confirm current scope and evidence.

Picking method

OpsUI context
Wave and zone picking that cuts the walk between picks; batch and multi-order picking
Wider options and considerations
Pick lists by order; advanced path optimisation is limited or absent in lighter tools

Vendor-specific detail: confirm current scope and evidence.

RF / barcode scan-to-confirm

OpsUI context
Scan at putaway and at every pick to enforce accuracy on the floor in real time
Wider options and considerations
Barcode scanning available in stronger tools (e.g. Cin7 Core); depth varies by product

Vendor-specific detail: confirm current scope and evidence.

Slotting optimisation

OpsUI context
Re-slots fast-moving SKUs into accessible locations to cut pick travel time
Wider options and considerations
Not a core function of inventory-first tools

Vendor-specific detail: confirm current scope and evidence.

Cycle counting

OpsUI context
Rolling cycle counts by zone/velocity without a full stop-the-line stocktake
Wider options and considerations
Stocktake and basic count features; rolling location-based cycle counts vary

Vendor-specific detail: confirm current scope and evidence.

Costing, valuation & reorder points

OpsUI context
Handled by the OpsUI Inventory + Finance modules (FIFO/average cost, reorder logic)
Wider options and considerations
Core strength, rich costing, landed cost, valuation and reorder automation

Vendor-specific detail: confirm current scope and evidence.

Best fit

OpsUI context
Operations where pick accuracy, throughput and floor execution are the bottleneck
Wider options and considerations
Businesses where stock visibility, costing and ordering are the bottleneck

Vendor-specific detail: confirm current scope and evidence.

Implementation weight

OpsUI context
Heavier — locations, scan flows and pick logic to set up (OpsUI goes live module by module, in weeks)
Wider options and considerations
Lighter and faster to roll out; less operational disruption to get started

Vendor-specific detail: confirm current scope and evidence.

Local operating considerations

For ANZ businesses this distinction has a local twist. A lot of New Zealand and Australian SMBs run on Xero or MYOB and reach for an inventory add-on first, sensible, since those tools nail costing, GST-aware valuation and reorder logic that suit the local accounting stack. The category-leading inventory products have deep ANZ roots too: Cin7 was founded in Auckland, and Unleashed is a New Zealand-born tool, so it's no surprise local buyers start there. The wall tends to appear as e-commerce and wholesale orders scale and picking accuracy becomes the daily problem. Confirm current subscription, allowances and implementation costs against an itemised proposal; the commercial structure is explained below. You add inventory first and warehouse execution when you need it, no rip-and-replace.

Ask which carrier accounts, services and label formats are supported; how your accounting records move; and where production data, backups and logs are held. Record the answers for the exact deployment under consideration.

Compare the full operating cost.

Conceptual illustration: Operational work cells, a separate row of user markers and an optional connection bridge.

Separate subscription cost from user allowances, integrations, devices, data preparation and onboarding. Ask who owns configuration, training, cutover and support, and which items are recurring.

A starting subscription price is not an implementation quote. Compare the same workflows, team size and transaction volumes across proposals. Keep the original currency, tax treatment and billing period visible.

OpsUI’s published package structure

Essential

NZ$499

per month

2 users included

2 operational modules

Control

NZ$1,499

per month

5 users included

5 operational modules

Command

NZ$2,999

per month

15 users included

11 operational modules

Apex

NZ$11,990

per month

Unlimited users

20 operational modules

Published monthly subscriptions in NZD. Existing annual pricing and package allowances apply. Additional seats are NZ$99 per month beyond the applicable allowance; integration connectors are separate add-ons.

Review the full packages and configure pricing →

A checklist you can use in a demonstration.

Conceptual illustration: A tabletop warehouse plan and representative records with a magnifying lens at a handoff.

Bring representative records and ask each vendor to work through the same scenarios. Write down what was demonstrated, what needs configuration and what remains unverified.

  1. Receive a discrepancy. Use an expected delivery with a missing line and damaged stock. Follow the difference through recording, review and the stock decision.
  2. Allocate constrained stock. Use two orders competing for the same stock. Check reservations, priorities and what the service team sees.
  3. Resolve a short pick. Start with an empty pick location. Show the exception, reassignment or backorder, and who can approve the next step.
  4. Complete the dispatch handoff. Use your carrier, parcel mix and label format. Check tracking references, manifests and a rejected address.
  5. Recover from an interrupted sync. Reject a record or interrupt delivery. Show visibility, retry behaviour, duplicate prevention and reconciliation.
  6. Confirm access and reporting. Run the same scenario as an operator and supervisor. Check action permissions and the records available for investigation.

Fit and trade-offs

When inventory management software is genuinely enough

Be honest with yourself about volume and complexity, because a pure inventory tool is simpler, cheaper and faster to deploy, and for a large share of ANZ product businesses it is exactly the right call. If you ship modest daily order volumes, your SKU range is manageable, picking is straightforward (one person, a tidy room, items easy to find), and your real pain is knowing stock-on-hand, costing, landed cost and when to reorder, then a dedicated inventory tool like Cin7 Core, Unleashed or a well-chosen Xero/MYOB inventory add-on will serve you well without the setup overhead of a full WMS.

These tools are mature and deep at what they do. It's worth being precise: stronger inventory products are not 'WMS-less' — Cin7 Core, for example, documents mobile barcode scanning, guided pick paths and bin-level accuracy. The difference is one of depth and dedicated floor execution (directed putaway rules, wave/zone optimisation, slotting, location-based rolling cycle counts) rather than a clean presence-or-absence line. If you don't have the throughput to justify that execution depth, paying for it is money and complexity you don't need.

There are also fits OpsUI is candid about not chasing. If you run a dedicated 3PL with per-client carton/storage billing and TMS rating, CartonCloud is the stronger choice. If you need MPI E-cert, deep multi-entity financial consolidation, or heavy MRP production scheduling, those are specialist needs better served elsewhere. The smart sequence for many growing businesses is to start with inventory software, watch your pick accuracy and throughput metrics, and move to real WMS execution only when the floor, not the ledger, becomes the constraint. With OpsUI you can make that move inside one platform by switching on warehouse modules, rather than re-platforming from scratch.

When you genuinely need a WMS (and OpsUI's warehouse modules fit)

You need a WMS when the problem has moved from the office to the floor. The tell-tale signs: mispicks and short-ships are creeping into your error rate, new staff take weeks to learn where things are, two people regularly hunt for the same SKU, and order volume has outgrown paper pick lists or a spreadsheet taped to the wall. At that point your inventory ledger can be perfectly accurate while your physical fulfilment quietly bleeds time and money, and no amount of better costing fixes a picker walking the long way round.

This is where OpsUI's warehouse modules do real work: directed receiving and putaway so stock lands in the right bin, wave and zone picking with optimised paths, RF/barcode scan-to-confirm at every pick to drive accuracy toward 99.9%+, slotting to keep fast movers within reach, and rolling cycle counts so you stop closing the warehouse for stocktakes. Confirm current subscription, allowances and implementation costs against an itemised proposal; the commercial structure is explained below.

The OpsUI advantage in this category is that the inventory and warehouse layers are the same platform. You aren't bolting a separate WMS onto a separate inventory tool and reconciling two sources of truth, the stock record and the pick instruction share one system, with NZ Couriers wired as the live carrier today (other AU/NZ carriers wired during rollout) and bidirectional NetSuite sync live now, with Xero and MYOB wired through the Finance module during rollout. Scope the required modules, users, data preparation and integrations before comparing delivery time or total cost.

Questions buyers ask.

What is the actual difference between a WMS and inventory management software?

Inventory management software is quantity- and value-centric: it tracks what stock you own, how much, what it cost and what it's worth (SKUs, stock-on-hand, costing, reorder points). A warehouse management system (WMS) is location- and execution-centric: it tracks where each item physically sits down to the bin, directs putaway, optimises wave/zone picking paths, enforces RF scan-to-confirm, and runs slotting and cycle counts. One is the ledger of stock; the other is the choreography of moving it accurately on the floor.

Do I need a WMS or is inventory software enough for my business?

If your order volume is modest, your SKU range is manageable, picking is simple and your main pain is stock visibility, costing and reordering, then inventory software is genuinely enough. It's simpler and cheaper. You need a WMS when the problem moves to the floor: rising mispicks, slow onboarding of warehouse staff, time lost hunting for stock, and throughput outgrowing paper pick lists. The trigger is pick accuracy and throughput, not your ledger.

Can't I just add barcode scanning to my inventory software instead of a WMS?

To a point, yes, stronger inventory tools like Cin7 Core include mobile barcode scanning and bin-level tracking, and that may be all you need. A dedicated WMS adds depth on top of scanning: directed putaway rules, wave and zone picking that cuts the walk between picks, slotting to keep fast movers close to dispatch, and rolling location-based cycle counts. If you don't have the throughput to justify that execution depth, you don't need it; if mispicks and pick travel time are hurting you, scanning alone usually isn't enough.

Does OpsUI replace my inventory software, or work alongside it?

OpsUI can do both. It includes an inventory module for stock control, costing and reorder logic plus dedicated warehouse modules for putaway, picking, slotting, cycle counts and dispatch, all in one platform, so the stock record and pick instruction share a single source of truth. If you'd rather keep your existing finance and inventory stack, OpsUI offers integrations: bidirectional NetSuite sync is live today, and Xero and MYOB are wired through the Finance module during rollout.

When is OpsUI not the right choice for warehouse or inventory needs?

OpsUI is candid about its boundaries. If you run a dedicated 3PL needing per-client carton/storage billing and TMS rating, CartonCloud is a better fit. If you need MPI E-cert, deep multi-entity financial consolidation, or heavy MRP production scheduling, those are specialist requirements better served by dedicated tools. And if a simple inventory tool already covers your stock visibility and costing and your floor isn't the bottleneck, a lighter dedicated inventory product may be all you need.

Sources and evidence

Checked facts apply only to the scope described next to each source. Other vendor details in the editorial analysis remain unverified for a current purchase decision. Confirm them with the vendor and record the applicable plan, version and proposal date.

    Current primary-source verification of this vendor’s detailed capabilities and prices is pending. An unknown is not a missing feature.

    Further reading: What is a WMS? Neutral explainer

    OpsUI integration delivery and scope · Security review information · Published OpsUI packages

    Continue your evaluation.

    Your next step

    Put the checklist to work.

    Bring one process and the requirements behind it. Review where OpsUI fits and what still needs to be confirmed.