Manufacturing ERP in Australia: the 2026 buyer's guide for SME manufacturers

If you make things in Australia, whether it is sauces and small-goods, kitchen cabinets, a contract job shop, or made-to-order industrial gear, you have probably hit the same wall. Your accounting system tracks money beautifully and knows nothing about your factory floor. Your spreadsheets track the factory floor and know nothing about your money. Somewhere in the gap, you are losing margin, missing delivery dates, and re-keying the same order three times.

A manufacturing ERP is meant to close that gap. But the term covers everything from a tiny cloud MRP app to a multi-month, six-figure enterprise platform, and the wrong choice can sink a small manufacturer for years. This guide is written for Australian SME makers weighing up a real decision in 2026. We will be specific about the sub-verticals, name the main vendors fairly, and be honest about where OpsUI is and is not the right answer.

What a manufacturing ERP has to do (and what it doesn't)

Strip away the jargon and a manufacturing ERP exists to answer four questions reliably, in real time: what can I make, what does it cost me, what have I promised, and what is actually happening on the floor right now.

To do that it needs a handful of capabilities your finance system was never built for:

• A bill of materials (BOM): the recipe or parts list for every product, ideally multi-level so a sub-assembly can be a component of a bigger build.
• Production orders or work orders: a way to commit materials and labour to a job, then track it through to a finished good.
• Material requirements planning (MRP): looking at demand, current stock and lead times, then telling you what to buy and when so you do not run out mid-run.
• Real inventory by location, lot and batch, with traceability, which matters enormously for food and beverage.
• Costing that rolls up materials, labour and overhead into a true unit cost you can quote against.

What it does not need to do is replace your general ledger, your BAS workpapers, or your payroll. Those are solved problems in Australia, and the temptation to rip them out and start again is where most failed ERP projects begin.

The four Australian SME manufacturing sub-verticals

Manufacturing ERP is not one market. The right fit depends heavily on how you actually make things, and the differences between these four archetypes are larger than most vendors admit.

Food and beverage processing

Think sauces, beverages, baked goods, dairy, small-goods. The defining requirements here are lot and batch traceability, expiry and shelf-life management, recall readiness, and recipe scaling with yield loss. You need to know which batch of raw material went into which finished pallet, and which customer received it, fast enough to satisfy a recall or an audit.

• Catch-weight and yield variance handling are common headaches.
• Allergen and ingredient declarations need to flow from the BOM.
• GS1 standards matter the moment you supply a major grocer: GTINs on products, GS1-128 carton labels, SSCC pallet labels, and ASN/Despatch Advice messages sent by EDI.

Cabinetmaking and joinery

Custom cabinets, shopfitting, joinery. Production is highly configured, often one job per customer, with cutting lists, sheet-stock optimisation and a heavy reliance on CAD/CAM nesting software at the machine. The ERP question here is less about long MRP runs and more about quoting accuracy, job costing, and not double-handling data between the design software and the back office.

• Configure-to-order quoting that does not take an hour per job.
• Job-level costing so you learn which jobs actually made money.
• Purchasing tied to the job, not to a forecast.

The job shop (make-to-order, mixed)

Engineering job shops, metal fabrication, sheet-metal, machining. Every job is a bit different, throughput is the constraint, and scheduling is the daily fire. These businesses live or die on shop-floor visibility: which jobs are on which machine, what is late, and where the bottleneck is today.

• Work-order routing through multiple work centres.
• Capacity and finite scheduling, at least at a rough-cut level.
• Time and materials capture on the floor, not on a clipboard transcribed on Friday.

Contract and made-to-order manufacturing

Contract manufacturers and MTO product businesses sit between the others. They often carry both repeat production runs and one-off builds, manage customer-owned materials, and have to hit committed delivery dates while juggling component lead times that blow out without warning. Demand visibility and accurate available-to-promise are the prize.

The Xero-has-no-BOM problem

This is the single most common starting point for Australian SME manufacturers, so it deserves its own section. Xero (and MYOB, and QuickBooks) are excellent small-business accounting systems. They handle invoicing, bank reconciliation, GST and BAS, and STP payroll reporting cleanly. That is exactly what they are for.

What they were never designed to do is manufacture. There is no real multi-level bill of materials, no production order that consumes components and yields a finished good at rolled-up cost, no MRP that nets demand against supply, and no shop-floor concept at all. Xero's inventory is a simple tracked-items list, not a manufacturing inventory engine.

So makers do one of three things:

• Run production on spreadsheets bolted to the side of Xero, which works until it quietly does not, usually around the point you cannot answer a recall or a margin question.
• Rip out Xero and migrate to a full manufacturing ERP with its own ledger, which is the expensive, disruptive, multi-month path, and which throws away an accounting setup your accountant and your team already trust.
• Keep the finance system and add a dedicated operations layer on top of it, syncing invoices, bills and inventory values back to the ledger.

That third option is the wedge most SME manufacturers should look at first, and it is the approach OpsUI is built around. Keep Xero, MYOB or NetSuite for the money; add the BOM, production and inventory layer for the making.

The vendor landscape, grouped by approach

There is no single best manufacturing ERP for Australia, only the right tool for your size, complexity and appetite for change. Here is a fair read on the main options SME makers actually shortlist, grouped by the approach they take. We have deliberately left out pricing figures because vendor pricing changes and is best confirmed directly, but we have flagged the pricing model where it matters.

Full mid-market ERP suites

These replace finance and operations in one platform. Powerful, broad, and the heaviest lift.

• Pronto Xi: an Australian-developed, long-established mid-market ERP with deep manufacturing and distribution modules. Strong fit for larger, more complex manufacturers who genuinely want one system of record and can resource a serious implementation.
• MYOB Acumatica (the rebranded MYOB Advanced, on the Acumatica platform): a cloud ERP with real manufacturing capability and Australian payroll/compliance grounding. A step up from MYOB Business, and a genuine ERP project in scope and effort.

These suites are the right call when you have outgrown everything else and accept a multi-month, five-figure-plus implementation as the cost of consolidation. They are usually overkill for a 10-person job shop.

Manufacturing-first systems that bolt onto your accounting

These focus on production and inventory and integrate with a separate ledger.

• Ostendo: a powerful, highly configurable operations and manufacturing add-on, popular in New Zealand and Australia, that sits on top of accounting systems like Xero and MYOB. Deep job costing and assembly capability; the flexibility comes with a learning curve and usually a specialist implementer.
• MRPeasy: a cloud MRP/ERP aimed squarely at small manufacturers, with BOM, production planning, stock and procurement in a tidy package. Per-user pricing that climbs as you add staff. Strong for a small make-to-stock or simple MTO shop that wants real MRP without a big project.

These are often the sweet spot for an SME maker who needs a true BOM and MRP but wants to keep their accounting where it is.

Inventory and light-manufacturing apps

These started as inventory or order tools and added assembly/manufacturing.

• Katana: a clean, visual manufacturing and inventory app that integrates tightly with Xero, QuickBooks and Shopify. Excellent for product businesses and light assembly; less suited to complex multi-level routing or heavy shop-floor scheduling.
• Cin7 Core (formerly Dear): inventory, order and light-manufacturing management with strong ecommerce and marketplace connections. Great for makers who also sell across Shopify, Amazon.com.au and eBay AU; manufacturing is capable but lighter than a dedicated MRP.

Pick these when inventory and omni-channel selling are the bigger problem and assembly is relatively simple.

The modular operations layer (where OpsUI sits)

OpsUI is not a finance ERP and does not pretend to be. It is a modular ERP, WMS and CRM that adds the operations layer (inventory, orders, receiving, shipping, warehouse and CRM) on top of the finance system you already run. You buy the modules you need and leave the rest. More on the fit below.

Modular versus monolithic: the real trade-off

The biggest architectural decision is not which vendor, it is whether you buy one big system or assemble a lean stack of focused tools.

A monolithic suite gives you one database, one login, and no integration to maintain. The cost is a large up-front implementation, a rigid feature set you pay for whether you use it or not, per-seat licensing that climbs with headcount, and a painful ledger migration that risks your clean accounting history. When it fits, it really fits; when it is oversold to a small shop, it becomes shelfware.

A modular approach keeps your finance system and adds focused operations modules a la carte. You go live faster, in weeks rather than quarters, you only pay for what you switch on, and you keep the accounting your accountant already signs off. The trade-off is that you are running an integration between your operations layer and your ledger, so that sync has to be solid.

This is exactly OpsUI's design: flat modular pricing from A$399/module/mo (full breakdown at /pricing), so you scale the cost to the modules you actually use instead of paying for a full suite on day one.

Implementation: where projects succeed or fail

More manufacturing ERP projects fail on implementation than on software features. A few hard-won principles for an Australian SME:

• Scope tight, then expand. Get one process live and clean (say, BOM plus production orders plus inventory) before you bolt on scheduling, quality and CRM. A phased go-live beats a big-bang every time.
• Get your data right first. A BOM full of wrong quantities or stale costs will produce confident, wrong answers. Clean item masters and accurate BOMs are the real project.
• Don't migrate your ledger unless you must. Every week spent re-implementing accounting you already had is a week not spent fixing the factory floor.
• Insist on a clear integration story. If the system bolts onto Xero, MYOB or NetSuite, know exactly which records sync, in which direction, and how conflicts resolve.
• Budget for change management. The cutting-list operator and the storeperson have to actually use it. Software no one trusts gets worked around.

GST, BAS, STP and Australian compliance

A practical note that trips up overseas-built tools. Your Australian compliance obligations, GST on sales and purchases, the quarterly or monthly BAS, and Single Touch Payroll reporting to the ATO, all live in your finance and payroll system. That is one more reason the keep-your-ledger approach is attractive: Xero, MYOB and NetSuite already handle GST coding, BAS preparation and STP natively and keep pace with ATO changes.

When you add an operations layer, what matters is that it feeds the finance system cleanly: sales orders that become correctly GST-coded invoices, supplier bills with the right tax treatment, and inventory valuations that reconcile. You should not be managing GST inside your warehouse tool; you should be handing the finance system clean, tax-correct transactions.

On eInvoicing, a quick myth-bust: Peppol eInvoicing in Australia is voluntary for businesses. The Business eInvoicing Right was never enforced, and the widely quoted 30%-by-1-July-2026 target applies to Commonwealth government agencies, not to private B2B trade. Treat eInvoicing as a useful capability, not a looming mandate.

How OpsUI fits

For an SME maker, OpsUI closes the gap between the ledger and the floor without replacing the ledger: you keep Xero, MYOB or NetSuite for the money, GST, BAS and STP, and add OpsUI for the operations, inventory, orders, receiving, shipping, warehouse and CRM, that your accounting system was never built to run.

Be honest with yourself about complexity, though. If you need deep finite-capacity scheduling for a high-mix engineering job shop, or you genuinely want to consolidate everything into a single mid-market suite, a Pronto Xi or MYOB Acumatica may suit you better, and a dedicated MRP like MRPeasy or Ostendo may be the closer fit for classic shop-floor MRP. We would rather tell you that than sell you the wrong thing. See our straight comparison at /compare/opsui-vs-mrpeasy.

Where OpsUI shines for SME makers is the operations and fulfilment side: real inventory by location with lot and batch tracking, order management, receiving and inbound, and shipping/outbound across Australian carriers, with NetSuite bidirectional sync live in production today and Xero and MYOB sync wired during rollout via the Finance and Accounting module. You buy only the modules you need, go live in weeks, and scale users and modules as you grow.

If you make things in Australia and the gap between your finance system and your floor is costing you margin, start with the manufacturing solutions overview at /solutions/manufacturing, sanity-check the numbers at /pricing, and book a working session at /book-demo so we can map your BOM, production and inventory flow to the modules that actually fit. No ledger migration required.