How much does OpsUI cost?

OpsUI starter packs begin at A$1,499/month on opsui.au or NZ$1,499/month on opsui.co.nz (entry tier, five users included). Individual modules are from A$299/NZ$299 per month with five users included; additional users are A$99/NZ$99 per user per month. The full Enterprise tier — every module plus all integrations — is custom-quoted.

What is a modular ERP, WMS & CRM?

A modular ERP, WMS & CRM sells each operational capability — finance, HR, warehouse, logistics, customer management, analytics — as a separately-priced product instead of one monolithic suite. Buyers pick only the modules they need today and add more as they grow. OpsUI is modular by design: 20 operational modules covering ERP, WMS, and built-in customer management, plus 5 integration connectors (NetSuite live today; Xero, MYOB, Abel ERP and SAP Business One wired during rollout) — all individually priced.

Can OpsUI run alongside NetSuite?

Yes. OpsUI supports bidirectional NetSuite sync out of the box. Customers running NetSuite frequently buy specific OpsUI modules — Wave Picking, Slotting Optimisation, ML/AI Predictions — to upgrade operational areas without replacing the GL.

Is OpsUI suitable for Australian and New Zealand small businesses?

Yes. OpsUI is built for Australian and New Zealand operations. Australian customers use opsui.au with AUD pricing and AU-region data hosting; New Zealand customers use opsui.co.nz with NZD pricing and NZ-region data hosting.

Does OpsUI integrate with Xero or MYOB?

Yes. OpsUI ships bidirectional sync for both Xero and MYOB via the Finance & Accounting module — wired against your accounting tenant during rollout rather than installed from an app marketplace. Customers, items, chart of accounts and tax codes flow from your accounting system into OpsUI; sales invoices, credit notes, payment status updates and inventory adjustments flow back. Built on the Xero REST API + webhooks and MYOB's AccountRight Live + Business APIs. Full sync detail at opsui.co.nz/integrations/xero or opsui.au/integrations/xero. A documented REST API on every module is also available for custom integration.

Where is OpsUI customer data hosted?

New Zealand customer data is hosted in New Zealand. Australian customer data is hosted in Australia. Both regions are encrypted at rest with AES-256 and in transit with TLS 1.3, with role-based access control and full audit logging.

How long does an OpsUI rollout take?

Honest answer: it depends on your data, integrations, and team availability — every business is different. We don't quote a fixed timeline on the website because we'd be inventing a number. We scope your specific implementation during the demo. Enterprise rollouts use a stage plan: scope, configure, train, go-live — one module set at a time.

Is there a free trial?

OpsUI runs guided demos rather than self-serve trials, because most module value depends on real data being loaded. Demos are direct to a person via opsui.au/book-demo or opsui.co.nz/book-demo — no sales-development sequence.

Modules & pricing

Comparison · Choosing a warehouse management system in New Zealand

How to choose a WMS in New Zealand: a 2026 buyer's framework

The seven decisions that actually determine WMS fit for NZ warehouses — data residency, carriers, finance sync, pricing model, rollout, scope and exit — not the feature checklist vendors hand you.

In one line

Choosing a WMS in New Zealand comes down to seven decisions — NZ data residency, carrier coverage (NZ Couriers / NZ Post), finance-system sync (Xero / MYOB / NetSuite), pricing model, rollout time, how far beyond the four walls you need to go, and how easily you can leave — and getting those right matters far more than counting features.

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.

Side by side

How to choose a WMS in New Zealand: a 2026 buyer's framework, feature by feature.

	OpsUI	Choosing a WMS
1. Data residency	NZ data hosted in NZ (AU data in AU), separate domains	Ask: where exactly is production data hosted — can you guarantee an NZ region?
2. Carrier coverage	NZ Couriers built in; NZ Post and Mainfreight in the same workflow	Ask: which NZ carriers are native vs which need middleware?
3. Finance sync	Bidirectional NetSuite live; Xero/MYOB wired during rollout	Ask: is the sync bidirectional, and is it built-in or a third-party connector?
4. Pricing model	Public, flat, per-module from NZ$299/month — no per-transaction	Ask: per-user, per-transaction or flat? Is implementation a separate fee?
5. Rollout time	Weeks for standard modules; scoped at the demo	Ask: a realistic go-live for MY data — not a best case?
6. Scope beyond the warehouse	Add orders, CRM, finance as modules when needed	Ask: does it handle orders/CRM, or will I bolt on more tools?
7. Exit / lock-in	Month-to-month, cancel a module anytime; export your data	Ask: contract length, data-export format, off-boarding terms?

Honest pick

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.

Where OpsUI shines

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. A modular cloud platform hits all seven without a six-figure project.
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.

ANZ context

Two of the seven decisions are sharper in New Zealand specifically: data residency (Privacy Act expectations and customer/board comfort with NZ-hosted vs offshore data) and carrier coverage (NZ Couriers and NZ Post are table stakes; Mainfreight matters for freight). OpsUI hosts NZ data in NZ, builds NZ Couriers into the Shipping module, and runs bidirectional NetSuite sync today with Xero/MYOB wired during rollout. Model the three-year cost of your shortlist on /tools/erp-cost-calculator before you commit.

Common questions

What buyers ask before choosing.

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 /compare/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?

Bands run from ~NZ$15,000/year for SMB inventory-led platforms to NZ$200,000+/year for enterprise WMS, with implementation often 1.5–3× the annual licence. OpsUI publishes flat modular pricing from NZ$299/module/month. See /compare/wms-cost-nz for the full breakdown.

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?

Last updated 13 June 2026