Xero + a modular WMS: how to architect the stack
Xero is the best accounting system most NZ businesses will ever use.
It is also the worst inventory system most of them will ever try to operate.
Xero is the best accounting system most NZ businesses will ever use.
It is also the worst inventory system most of them will ever try to operate.
Here is the stack that lets you keep one and fix the other.
The shape of the problem
Xero owns the ledger. The ledger owns the truth your accountant signs.
That truth is a number: count and cost. Two columns.
A warehouse runs on six: SKU, bin, batch, expiry, serial, location.
The four columns Xero does not have are the four that fail in production.
The wrong fix: rip out Xero
NetSuite reps will tell you the answer is one suite, one ledger, one login.
That is a $200,000 fix to a problem you can solve for NZ$1,500/month.
Migrating off Xero also costs you the relationship your bookkeeper has spent five years building.
That is six months of friction you do not need.
The right fix: layer operations above accounting
Two systems. One source of truth per concern.
- Xero owns finance: GST, invoices, AR, AP, bank reconciliation, payroll links.
- A WMS owns operations: bins, batches, picks, dispatch, receiving, cycle counts.
- A connector moves invoice headers from operations to Xero on dispatch. Payments flow back.
That is the architecture. Nothing else changes for your accountant.
What the WMS actually needs to do
- Multi-location, bin-level inventory with available, allocated, and on-order separated
- Batch, lot, serial, and expiry tracking, for FIFO enforcement and recall scope
- Pick, pack, and dispatch workflow your warehouse staff can run on a scanner
- Real-time stock against multi-channel orders so the website cannot oversell
- Carrier wired in (label, track, manifest) without bouncing to a separate console
Anything missing from that list is going to bite you within sixty days of go-live.
How OpsUI sits in this stack
OpsUI runs alongside Xero, not on top of it.
The Inventory Management module at /modules/inventory-management handles SKU, bin, batch, expiry, and serial.
The Receiving module at /modules/receiving-inbound and the Shipping module at /modules/shipping-outbound run the floor workflow.
The Finance & Accounting module carries the Xero sync, wired during rollout. See /integrations/xero for the sync detail.
Until the connector ships, OpsUI runs standalone next to your Xero account.
Once it ships, your stack stays the same: Xero for finance, OpsUI for operations.
Where this stack is the wrong call
Honest gaps:
- Multi-entity consolidation: if you run three subsidiaries with intercompany journals, you want NetSuite or Dynamics 365 BC, not a Xero+WMS pair.
- Inventory-only operators on a tight budget: if all you sell is twenty SKUs through one channel, Unleashed bolted to Xero may be all you need. See /compare/opsui-vs-unleashed.
- Multi-channel parcel sprawl with Shopify + Amazon + eBay all live: Cin7 Core handles that storefront fan-out more cleanly today. See /compare/opsui-vs-cin7.
The stack, in one line
Xero for the ledger.
OpsUI for the warehouse.
A connector in between.
Your accountant stays. Your warehouse runs on a system that was actually built for it.
Frequently asked
Why not just use Xero's built-in inventory module?
For under ~50 SKUs and a few hundred orders a month it is fine. Past that, Xero has no bins, no batches, no expiry, no picking workflow. Most NZ and AU operators outgrow Xero's inventory between 200 and 500 orders per month. Long before they outgrow Xero itself. See /blog/xero-inventory-gaps for the deeper breakdown.
Will I have to retrain my bookkeeper on a new accounting system?
No. That is the whole point of the layered architecture. Your bookkeeper continues to live in Xero, same GST flow, same AR, same AP, same bank reconciliation. The warehouse team learns OpsUI. The two systems talk via the connector.
When does the OpsUI Xero connector go live?
Bidirectional sync wired against your Xero tenant during rollout via the Finance & Accounting module. Customers, items, chart of accounts and tax codes flow from Xero; sales invoices, credit notes, payment status updates, and inventory adjustments flow back. See /integrations/xero for the full sync detail.
What about MYOB users, does the same stack work?
Yes. Same architecture: MYOB owns accounting, OpsUI owns operations. The MYOB sync is wired during rollout, same shape as the Xero sync, tuned for MYOB AccountRight and MYOB Business APIs. See /compare/beyond-myob for the AU operator's path.
How is this different from Cin7 or Unleashed?
Cin7 and Unleashed are inventory-first products that compete with both Xero's native inventory and a real WMS. OpsUI is a modular ERP. Inventory is one of 20 operational modules, and you can add warehouse, logistics, manufacturing, or finance modules as you need them. See /compare/opsui-vs-cin7 and /compare/opsui-vs-unleashed.
See how OpsUI approaches this differently.
No hidden fees. No six-month implementations. Just warehouse software that works.
Book a Consultation