MYOB inventory: where it works and where it breaks
MYOB AccountRight inventory is built for invoice-line tracking, not warehouse ops.
The split between MYOB Business and MYOB Advanced changes the answer.
MYOB AccountRight inventory is built for invoice-line tracking, not warehouse ops.
The split between MYOB Business and MYOB Advanced changes the answer.
When to extend MYOB with an ops layer and when MYOB has to go.
The MYOB product split
MYOB sells two stacks in ANZ. MYOB Business (cloud, accounting-led, SMB-shaped) and MYOB Advanced (Acumatica-powered, mid-market ERP). They are not the same product. The inventory story is different in each.
MYOB Business: lightweight inventory. SKUs, quantities on hand, average cost. No bin locations. No barcode scanning. No multi-warehouse separation worth running operations on.
MYOB Advanced: full inventory module. Multi-warehouse, bin locations, lot tracking, serial numbers, advanced costing. Closer to NetSuite than to MYOB Business.
When operators say “MYOB inventory is limited,” they usually mean MYOB Business. The Advanced shape is a different product entirely, and a different price.
Where MYOB Business inventory breaks
- More than one warehouse, or any internal stock-segregation requirement
- Barcode picking on the floor (no native pick-pack-ship workflow)
- Cycle counting on a schedule rather than annual stocktakes
- Real-time stock visibility for an ecommerce front-end
- Lot or batch tracking for compliance (food, pharma, electronics)
- Returns workflow with reasons, restocking, and credit-note linkage
If your operations need any of those, MYOB Business inventory is not the right system to run them on. You will hack a workaround with spreadsheets, the workaround will break at the worst possible time, and the cost of the workaround will exceed an ops layer subscription within months.
The default fix: extend MYOB with an ops layer
Same shape as the Xero-plus-ops-layer pattern. Keep MYOB Business for accounting (invoicing, payments, payroll, GST/BAS, P&L). Add an ops layer for the warehouse, picking, dispatch, cycle counts, and returns. Connect them with a bidirectional sync.
Your bookkeeper stays on MYOB. The warehouse gets the system they need. The two systems agree on what stock exists and where.
OpsUI ships bidirectional sync for both MYOB and Xero, wired against your accounting tenant during rollout via the Finance & Accounting module. The ops layer itself (warehouse modules, picking, dispatch, receiving, cycle counts) is in production today.
When MYOB Advanced or full ERP makes sense
MYOB Advanced is a real mid-market ERP. If you are evaluating it, the comparison set is NetSuite, Microsoft Dynamics 365 Business Central, SAP Business One, and Acumatica direct (since Advanced is Acumatica under the hood).
The trigger to leave MYOB Business for MYOB Advanced is usually one of:
- Multiple legal entities needing consolidated reporting
- Manufacturing complexity beyond light assembly
- A finance team larger than 3–4 people demanding workflow controls
- Audit-grade segregation of duties at a scale MYOB Business cannot evidence
If you are not in those triggers, the move from MYOB Business to MYOB Advanced is overkill. The ops-layer pattern keeps you on the cheaper accounting stack and solves the operational problem at the right cost.
The honest answer most operators need
Keep MYOB Business. Add an ops layer. Connect them. Get on with running the business.
The exit from MYOB only happens in the four cases above, the same shape as the Xero exit conversation, because the trigger is financial complexity, not operational complexity. Most operators have operational complexity. The right system for that is an ops layer, not a more expensive accounting platform.
Frequently asked
Does MYOB AccountRight handle multi-warehouse inventory?
MYOB Business AccountRight does not handle multi-warehouse inventory in a way most operations teams find usable. There is no bin location tracking, no warehouse-to-warehouse transfer workflow, and no native pick-pack-ship process. MYOB Advanced (the Acumatica-based mid-market product) does handle multi-warehouse properly but is a different product at a different price point.
Should I switch from MYOB to an ERP if my inventory is getting complex?
Usually no. The default move for ANZ operators outgrowing MYOB Business inventory is to add an ops layer alongside MYOB rather than migrate to a full ERP. Keep MYOB for accounting (invoicing, payroll, BAS/GST). Add an ops platform for warehouse, picking, dispatch, and cycle counting. Connect them with a bidirectional sync. Total cost is typically 10–20× lower than a NetSuite or MYOB Advanced migration.
When does MYOB Business actually have to go?
Four cases: multiple legal entities needing consolidated reporting; manufacturing complexity with multi-level BOMs and MRP; public-company audit-grade reporting; or a finance team large enough that workflow controls and segregation of duties have to be enforced at a level MYOB Business cannot evidence. None of those are triggered by warehouse complexity alone. That is solved by adding an ops layer.
Does OpsUI integrate with MYOB?
OpsUI ships bidirectional sync for MYOB via the Finance & Accounting module, wired against your MYOB tenant during rollout (same shape as the Xero sync, tuned for MYOB AccountRight and MYOB Business APIs). The ops layer itself, warehouse, picking, dispatch, receiving, cycle counts, returns, is in production today.
See how OpsUI approaches this differently.
No hidden fees. No six-month implementations. Just warehouse software that works.
Book a Consultation