Skip to content

Operations guide

Inventory management for MYOB (NZ & AU)

Work through the requirements and trade-offs before choosing a product or planning a change.

Go to the evaluation checklist →

Understand the decision

MYOB (AccountRight and Business) keeps the books for a large slice of ANZ SMBs, and its built-in inventory handles a modest catalogue of tracked items. But it was never built to run real stock operations, multi-location, bin/batch/serial tracking, scanner-driven receiving and picking, or high order volume, so growing product businesses add a dedicated inventory layer above MYOB.

The realistic options: an inventory-led platform built to sit on MYOB (Cin7, Unleashed), or a modular ERP/WMS like OpsUI that keeps MYOB as the financial system of record and adds the inventory and warehouse depth on top, synced bidirectionally.

This guide compares the approaches honestly, including when MYOB's native inventory, or a light add-on, is genuinely enough.

OpsUI publishes this guide and is one of the options discussed. Use the operating guidance to frame your evaluation. Vendor-specific details without a checked primary source remain unverified; confirm them against the proposal you receive.

Requirements and options.

Conceptual illustration: Retail, online and trade-order sources feeding one organised order tray and stock tote.

Multi-location stock

OpsUI context
Yes, multi-warehouse, transfers, per-location balances
Wider options and considerations
MYOB native is limited

Vendor-specific detail: confirm current scope and evidence.

Bin / batch / serial

OpsUI context
Yes, full lot and serial tracking
Wider options and considerations
Not in MYOB native

Vendor-specific detail: confirm current scope and evidence.

Barcode / RF scanning

OpsUI context
Mobile scanning for receiving, picking and counts
Wider options and considerations
Not in MYOB native

Vendor-specific detail: confirm current scope and evidence.

Relationship to MYOB

OpsUI context
Keeps MYOB as the ledger; bidirectional sync (AccountRight + Business APIs) wired during rollout
Wider options and considerations
MYOB IS the system; inventory is basic

Vendor-specific detail: confirm current scope and evidence.

Warehouse workflow

OpsUI context
Receiving, picking, dispatch as modules
Wider options and considerations
None in MYOB native

Vendor-specific detail: confirm current scope and evidence.

Pricing model

OpsUI context
Confirm current subscription, allowances and implementation costs against an itemised proposal; the commercial structure is explained below.
Wider options and considerations
MYOB plan; add-ons priced separately (often per-user)

Vendor-specific detail: confirm current scope and evidence.

When you outgrow it

OpsUI context
Add orders, CRM, finance modules on the same platform
Wider options and considerations
Add a separate inventory/WMS tool

Vendor-specific detail: confirm current scope and evidence.

Local operating considerations

OpsUI's MYOB connector is bidirectional, built on the AccountRight + Business APIs and wired against your MYOB tenant during rollout (NetSuite bidirectional sync is live today; Xero also supported), so master data flows from MYOB while sales, payments and inventory adjustments flow back. MYOB stays the system of record. Confirm current subscription, allowances and implementation costs against an itemised proposal; the commercial structure is explained below. See the inventory-vs-WMS line at wms vs inventory management, the Xero equivalent at inventory management for xero, and the upgrade-path view at beyond myob.

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.

Conceptual illustration: Operational work cells, a separate row of user markers and an optional connection bridge.

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

Essential

NZ$499

per month

2 users included

2 operational modules

Control

NZ$1,499

per month

5 users included

5 operational modules

Command

NZ$2,999

per month

15 users included

11 operational modules

Apex

NZ$11,990

per month

Unlimited users

20 operational modules

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.

Review the full packages and configure pricing →

A checklist you can use in a demonstration.

Conceptual illustration: A tabletop warehouse plan and representative records with a magnifying lens at a handoff.

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 MYOB's native inventory (or a light add-on) is enough

If you sell a small catalogue from one location, don't pick from bins, and your order volume is low, MYOB's built-in tracked inventory, or a lightweight add-on, may be all you need.

If your need is inventory plus light manufacturing on MYOB and you don't run a real warehouse, a focused MYOB/Xero-attached platform like Cin7 or Unleashed is mature and purpose-built for that lane.

Adding a modular ERP/WMS only pays off once stock accuracy depends on the floor — bins, scanners, multi-location, dispatch.

When OpsUI on top of MYOB is the better fit

When stock accuracy becomes a floor problem, bin locations, scanner-driven receiving and picking, multi-location transfers, cycle counts. You need WMS-grade inventory that MYOB's native tools and light add-ons don't provide. OpsUI adds exactly that while MYOB stays your ledger.

You keep the accounting system that works and add only the operations modules you need, at flat per-module pricing, rather than migrating your books or paying a per-user inventory tax as you add floor staff.

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

Questions buyers ask.

Does MYOB have inventory management?

MYOB (AccountRight and Business) has basic built-in inventory for tracked items, quantities, costs and simple stock-on-hand, which is fine for a small single-location catalogue. It isn't built for multi-location stock, bin/batch/serial tracking, or scanner-driven picking, so operators running a real warehouse add an inventory or WMS layer on top of MYOB.

What's the best inventory add-on for MYOB in NZ?

It depends on depth. Cin7 and Unleashed are mature inventory-and-light-manufacturing platforms that attach to MYOB; a modular ERP/WMS like OpsUI is the better fit when you need bin/batch/serial accuracy, barcode/RF scanning and the warehouse workflow around the stock, while keeping MYOB as the ledger. Match the tool to whether your stock problem is in the office or on the floor.

Does OpsUI replace MYOB?

No. OpsUI keeps MYOB as your financial system of record and adds the inventory, warehouse and order operations on top, with bidirectional sync wired during rollout so stock movements and valuations reconcile back to MYOB. If you'd rather consolidate later, OpsUI also has a Finance & Accounting module, but most operators keep MYOB.

How much does it cost to add proper inventory to MYOB?

Compare the required modules, users, order allowances, integration work and implementation responsibilities before comparing prices. OpsUI’s current package structure is shown on this page. Current competitor prices and terms need confirmation with the vendor; historical estimates are not a current quote.

Can I do barcode stocktakes with MYOB inventory?

Not with MYOB's native inventory. You need an inventory or WMS layer that supports mobile barcode/RF scanning. OpsUI runs scanning across receiving, picking and cycle counts while syncing valuations back to MYOB, so stocktakes are done on the floor rather than re-keyed into the ledger.

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.

    Your next step

    Put the checklist to work.

    Bring one process and the requirements behind it. Review where OpsUI fits and what still needs to be confirmed.