MYOB inventory: the real limitations, and the fix that keeps MYOB

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.

MYOB inventory has real limitations, and almost all of them sit in MYOB Business (AccountRight and the cloud SMB product), not MYOB Advanced. MYOB Business tracks SKUs, quantity on hand and average cost, but it has no bin locations, no barcode pick-pack-ship workflow, no multi-warehouse separation you can run operations on, and no lot, batch or serial tracking for compliance. Cycle counting on a schedule and real-time stock for an ecommerce front-end are also missing. MYOB Advanced (the Acumatica-based mid-market product) does handle all of that, but it is a different product at a different price point. For most ANZ operators the fix is not to switch accounting systems: it is to keep MYOB for the ledger and add an operations layer for the warehouse.

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

Here is what that looks like on the floor. With no bin or shelf locations, a picker cannot be told where a SKU lives, so finding stock depends on who is rostered that day and how well they remember the racking. With no barcode scanning, every receipt and every pick is keyed by hand, which is both slow and the exact point where mispicks and miscounts enter. Multi-warehouse in MYOB Business is a label on a transaction, not a workflow: there is no guided transfer between sites, so per-location balances drift the first time someone forgets to key a movement.

MYOB Business also defaults to blocking a sale or adjustment that would push an item negative. That sounds prudent until goods physically ship before the replenishment receipt is keyed, at which point the despatch is blocked and the team either waits or invents a dummy receipt to get past it. Once dummy receipts become habit, stock valuation and cost of goods drift into fiction, and that fiction flows straight into your P&L and BAS.

Batch, lot and expiry tracking are absent, so first-expired-first-out picking is impossible and a supplier recall cannot be scoped to the customers who received the affected lot. For food, beverage, supplements, cosmetics and healthcare, that is a compliance gap, not an inconvenience. Cycle counting on an ABC cadence is off the table too, which leaves you with disruptive full stocktakes as the only way to true up the numbers.

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. For the full cost picture across four common shapes, see ERP implementation cost in NZ.

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). For a side-by-side on cost, timeline and risk against the ops-layer route, see OpsUI vs MYOB Acumatica.

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. Modular pricing is on the pricing page, and if you want your specific MYOB limits mapped to modules, book a consultation.