Understand the decision
Most WMS buying advice is a feature checklist, which is exactly backwards: every serious WMS does receiving, picking and dispatch, so the feature list rarely decides the outcome. What decides it is fit, against your data-residency obligations, your carriers, your finance system, your budget shape and your appetite for a long implementation.
This is a practical framework for NZ operators: seven decisions, in priority order, that determine whether a WMS will actually work for your warehouse, and the question to ask each vendor to pin down a real answer rather than a demo-day impression.
It's written to be vendor-neutral; OpsUI appears where it's genuinely the right answer and is left out where it isn't.
Requirements and options.
1. Data residency
- OpsUI context
- Confirm production, backup and log locations for the proposed deployment. Regional domains or billing currencies do not establish data residency.
- Wider options and considerations
- Ask: where exactly is production data hosted, can you guarantee an NZ region?
Vendor-specific detail: confirm current scope and evidence.
2. Carrier coverage
- OpsUI context
- NZ Couriers built in; NZ Post and Mainfreight in the same workflow
- Wider options and considerations
- Ask: which NZ carriers are native vs which need middleware?
Vendor-specific detail: confirm current scope and evidence.
3. Finance sync
- OpsUI context
- Bidirectional NetSuite live; Xero/MYOB wired during rollout
- Wider options and considerations
- Ask: is the sync bidirectional, and is it built-in or a third-party connector?
Vendor-specific detail: confirm current scope and evidence.
4. Pricing model
- OpsUI context
- Confirm current subscription, allowances and implementation costs against an itemised proposal; the commercial structure is explained below.
- Wider options and considerations
- Ask: per-user, per-transaction or flat? Is implementation a separate fee?
Vendor-specific detail: confirm current scope and evidence.
5. Rollout time
- OpsUI context
- Weeks for standard modules; scoped at the demo
- Wider options and considerations
- Ask: a realistic go-live for MY data — not a best case?
Vendor-specific detail: confirm current scope and evidence.
6. Scope beyond the warehouse
- OpsUI context
- Add orders, CRM, finance as modules when needed
- Wider options and considerations
- Ask: does it handle orders/CRM, or will I bolt on more tools?
Vendor-specific detail: confirm current scope and evidence.
7. Exit / lock-in
- OpsUI context
- Month-to-month, cancel a module anytime; export your data
- Wider options and considerations
- Ask: contract length, data-export format, off-boarding terms?
Vendor-specific detail: confirm current scope and evidence.
Local operating considerations
Confirm production, backup and log locations for the proposed deployment. Regional domains or billing currencies do not establish data residency. Model the three-year cost of your shortlist on erp cost calculator before you commit.
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.
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$499per month
2 users included
2 operational modules
Control
NZ$1,499per month
5 users included
5 operational modules
Command
NZ$2,999per month
15 users included
11 operational modules
Apex
NZ$11,990per 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.
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.
- Receive a discrepancy. Use an expected delivery with a missing line and damaged stock. Follow the difference through recording, review and the stock decision.
- Allocate constrained stock. Use two orders competing for the same stock. Check reservations, priorities and what the service team sees.
- Resolve a short pick. Start with an empty pick location. Show the exception, reassignment or backorder, and who can approve the next step.
- Complete the dispatch handoff. Use your carrier, parcel mix and label format. Check tracking references, manifests and a rejected address.
- Recover from an interrupted sync. Reject a record or interrupt delivery. Show visibility, retry behaviour, duplicate prevention and reconciliation.
- 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 a specialist or enterprise WMS is the right choice
If your operation is defined by a single specialised workflow, MPI E-cert export certification, pharmaceutical cold-chain compliance, or heavy automation integration, a vendor that has built exactly that is worth prioritising over breadth, even at a premium or a longer rollout.
If you run very high throughput or multi-site DCs with conveyors, pick-to-light or ASRS, an enterprise WMS's labour-management and optimisation depth earns its cost.
And if you're a pure 3PL whose product is per-client billing and rate cards, a purpose-built 3PL WMS (CartonCloud, Extensiv, Access Mintsoft) may fit the billing model more directly than a general platform.
When a modular cloud platform is the smart default
For most NZ SMB and mid-market warehouses, the seven decisions point the same way: you want in-region data, native NZ carriers, a finance system you keep, predictable pricing, a rollout measured in weeks, room to grow beyond the warehouse, and no lock-in. Scope the required modules, users, data preparation and integrations before comparing delivery time or total cost.
OpsUI is built around exactly that profile, start with the warehouse modules, add orders, CRM or finance when you need them, keep Xero/MYOB/NetSuite, and pay per module with the price on the page.
The framework also protects you from the two expensive mistakes: over-buying a monolithic ERP for a warehouse problem, and under-buying a standalone WMS you'll outgrow the moment orders or customers become the bottleneck.
Questions buyers ask.
What's the most important factor when choosing a WMS in NZ?
For most NZ operators it's the combination of data residency, native NZ carrier integration (NZ Couriers, NZ Post) and how the WMS syncs with your existing finance system (Xero, MYOB or NetSuite). Features matter less than fit, almost every WMS handles receiving, picking and dispatch, so the decision usually turns on these local factors plus pricing model and rollout time.
Should I choose a standalone WMS or an ERP with WMS modules?
If your only problem is inside the four walls and you're happy with your finance system, a standalone WMS (or WMS modules) can be enough. If you also struggle with orders, customers or reporting, choose a platform that can grow into those without a second implementation. Modular platforms like OpsUI let you start with the warehouse and add the rest later. See wms vs erp for the full distinction.
How long should a WMS take to implement?
It depends on scope, but be wary of vendors who quote a fixed timeline before scoping your data and integrations. Standard cloud-WMS rollouts run weeks, not months; heavy enterprise WMS projects with automation can run six to twelve months. Ask for a realistic go-live against your actual SKUs, carriers and finance sync, not a best-case demo timeline.
How much should a WMS cost in New Zealand?
Compare the required modules, users, order allowances, integration work and implementation responsibilities before comparing prices. OpsUI’s current package structure is shown on this page. Current competitor prices and terms need confirmation with the vendor; historical estimates are not a current quote.
What questions should I ask a WMS vendor?
Seven that cut through a demo: Where is my data hosted? Which NZ carriers are native? Is the finance sync bidirectional and built-in? Is pricing per-user, per-transaction or flat, and is implementation separate? What's a realistic go-live for my data? Can it handle orders and customers, or just the warehouse? And what are the contract length, data-export format and off-boarding terms?
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