WMS for MYOB users: keep the ledger, run the warehouse

Understand the decision

Search for "WMS that integrates with MYOB" and you are really asking two questions: how do I get warehouse and inventory capability without leaving MYOB, and how much system do I actually need? MYOB Business and AccountRight keep the books well, but they were not built for the warehouse. Native MYOB tracks one quantity per item and does not know whether that stock sits in one location or five; multi-location inventory is only available on the AccountRight Premier tier, not the lower AccountRight plans; there is no bin or zone tracking within a warehouse, and no barcode scanning or batch control out of the box. Once stock moves through more than one place, MYOB's own answer is to connect an inventory or warehouse system and let that system run the stock.

The field splits into three shapes. First, the MYOB-native specialist: Datapel Cloud.WMS, built in Sydney and trading for more than two decades, earned its name by sitting tightly against MYOB AccountRight (and later Xero) with two-way sync, giving stock-heavy wholesalers, distributors and manufacturers real warehouse control without forcing them off MYOB. Second, the inventory add-ons, Unleashed (NZ-founded, now MYOB-connected) and Cin7, which handle stock accuracy, purchasing and multichannel sales orders above your ledger, with mobile barcode apps for pick, pack and putaway; note that MYOB connection maturity varies by product, so confirm whether it is native or via a third-party connector. Third, operations platforms like OpsUI, where receiving and putaway, wave and zone picking, slotting optimisation, cycle counts, RF scanning and dispatch run as first-class modules on the same record set as orders, inventory and CRM.

This guide is written by OpsUI, so read it knowing that, but the honest version of the advice cuts more than one way. Datapel is the established MYOB-native option, and for a deep AccountRight install that wants a hardened, vendor-implemented warehouse fit, it is genuinely hard to beat; we say so plainly below. And plenty of MYOB businesses do not need a full WMS at all: if a small team can pick the day's orders from a list without falling behind, an inventory add-on is cheaper, faster to connect and entirely sufficient. The trigger for more is when the floor becomes the constraint, pick rates, walking distance, mispicks, missed dispatch cut-offs, because directed workflows are what fix those.

OpsUI's shape in this field: keep MYOB as the ledger and run operations, orders, inventory, warehouse, dispatch, shipping, CRM, in a modular platform of 20 operational modules plus 5 integration connectors, with bidirectional MYOB sync wired during rollout via the Finance & Accounting module so invoices, bills and contacts flow back to MYOB. To be precise, and we would rather you know it up front: that MYOB sync is configured with you during rollout, not a pre-built one-click MYOB marketplace app today. The bidirectional NetSuite sync is the one that runs live in production now.

Local operating considerations

Confirm production, backup and log locations for the proposed deployment. Regional domains or billing currencies do not establish data residency. That local centre of gravity matters in practice, GST and BAS handling on both sides of the Tasman is table stakes rather than an afterthought, and support hours match your shifts, because whichever system you choose, MYOB stays the system of record for GST and BAS and the operations layer feeds clean order, inventory and fulfilment data back to it. Two things still need checking on any shortlist. First, the MYOB connection itself: Datapel's two-way AccountRight sync is its hardened, long-standing strength, while OpsUI's MYOB sync is wired during rollout via the Finance & Accounting module rather than offered as a one-click marketplace app, and the inventory add-ons vary between native and third-party connectors, confirm exactly how each one talks to your MYOB file. Confirm production, backup and log locations for the proposed deployment. Regional domains or billing currencies do not establish data residency.

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

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.

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.

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 Datapel or a MYOB inventory add-on is the better fit

You run a deep, mature MYOB AccountRight install and want a warehouse system whose integration with it has been hardened over many years of real ANZ use. Datapel built its reputation on exactly that two-way MYOB sync, and for stock-heavy wholesalers and distributors that want a long-established local vendor with a 20-plus-year track record, it is a serious, proven option.

Your stock-control rules are highly specific and you want a traditional, vendor-led implementation configured tightly to them, rather than a faster modular switch-on. That configured depth is precisely what Datapel's engagement model is built to deliver.

Your pain is stock accuracy and channel sync, not floor workflow. If a small team can pick the day's orders from a printed or app list without falling behind, Unleashed or Cin7 solves the actual problem, reliable multichannel inventory above MYOB, with less cost and less change. (Confirm the MYOB connection is native or via a supported connector before you commit.)

You assemble or lightly manufacture. Unleashed and Cin7 Core both handle bills of materials and assembly natively, which suits food brands, fabricators and kit-builders that have outgrown MYOB's native stock but do not need warehouse-directed workflows. For heavy MRP and finite-capacity scheduling, look at a dedicated manufacturing system. That is not OpsUI's lane either.

You are a 3PL billing clients for storage and fulfilment. None of these lead there: purpose-built 3PL platforms like CartonCloud handle per-client billing and rate cards far better today.

When you need a real WMS beside MYOB

The bottleneck has moved from the spreadsheet to the floor. When pickers walk too far, mispicks creep up and dispatch cut-offs get missed, you need directed work — and you need it joined up. Where OpsUI goes deeper than the inventory add-ons is wave planning, velocity-based slotting optimisation and structured rolling cycle-count programmes, run as modules of the same platform as your orders, dispatch and CRM rather than a separate WMS app above your inventory system.

You want operations breadth without leaving MYOB or running a partner-led WMS build. Confirm current subscription, allowances and implementation costs against an itemised proposal; the commercial structure is explained below. All of it is published pricing.

Scope the required modules, users, data preparation and integrations before comparing delivery time or total cost. OpsUI was built from the floor, ships a public weekly changelog, and rolls out module by module, the bidirectional MYOB sync is wired during that rollout so the ledger keeps reconciling from day one. Be clear-eyed that this is a configured rollout step, not a one-click MYOB marketplace install today.

Confirm production, backup and log locations for the proposed deployment. Regional domains or billing currencies do not establish data residency.

Questions buyers ask.

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: MYOB / Acumatica, neutral guide

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

Continue your evaluation.

• Cloud WMS in New Zealand: OpsUI vs the NZ cloud warehouse field→
• WMS vs inventory management software: which do you actually need?→
• How much does a WMS cost in New Zealand? (2026)→
• WMS vs ERP: what's the difference and which do you need? (NZ, 2026)→
• How to choose a WMS in New Zealand: a 2026 buyer's framework→
• NetSuite WMS alternatives for NZ & AU operations→