OMS vs WMS vs ERP: what each one actually does (and which you need)

OMS, WMS and ERP get used interchangeably. They should not be.

Each one runs a specific layer of the business. Mixing them up costs money.

Here is the honest definition of each, and how they fit together.

The one-line definitions

OMS — Order Management System. Runs orders from order entry to fulfilment. Aggregates orders from every channel (web store, marketplaces, B2B portal, phone, in-person), checks stock, routes to the right warehouse, tracks status, handles cancellations and returns. The OMS does not move stock — it tells other systems what stock should move.

WMS — Warehouse Management System. Runs the warehouse. Receiving inbound stock, putaway to bins, picking, packing, dispatch, cycle counting, returns processing. The WMS does not know what an order means commercially — it only knows what to pick, where it is, and where to send it.

ERP — Enterprise Resource Planning. Runs the whole business. Customers, products, orders, inventory, purchasing, finance, sometimes manufacturing, HR and projects. An ERP typically includes light OMS and light WMS functionality but does not replace dedicated platforms for either.

The shorthand: OMS is "what the customer wants". WMS is "what the warehouse does". ERP is "what the business is".

What each one actually does well

OMS strengths:

• Multi-channel order aggregation (Shopify, Amazon, TradeMe, eBay, B2B portals all into one view)
• Distributed order routing (which warehouse fulfils which order, by stock + proximity + cost)
• Promise-date calculation against real inventory
• Returns initiation and refund orchestration
• Channel-aware pricing and inventory allocation

WMS strengths:

• Bin-level inventory accuracy with scanner workflows
• Wave, zone, batch, cluster, and discrete picking strategies
• Putaway optimisation and slotting
• Cycle counting that replaces annual stock-takes
• Carrier-rate shopping and label generation at dispatch
• Returns disposition (restock, refurbish, scrap) with traceability

ERP strengths:

• Single source of truth for customers, products, and transactions
• Financial reporting across the whole business
• Purchasing tied to inventory and demand
• Project / job costing across departments
• HR, payroll, and time tracking
• Light versions of OMS and WMS functionality built in

When you need each one

You need an OMS when you sell across multiple channels with shared inventory and the order routing decisions become too complex for spreadsheets. The trigger is usually two or more sales channels plus two or more fulfilment locations. Below that, your ecommerce platform plus your ERP usually handles it.

You need a WMS when picking accuracy, throughput, or cycle-count costs become a P&L line item. The trigger is usually one of: more than a few hundred lines picked per day, multi-zone warehouse, batch / lot / expiry tracking requirements, returns volume above ~5% of dispatches. Below that, ERP-native warehouse functionality is usually enough.

You need an ERP when you have outgrown best-of-breed point solutions and the reconciliation overhead exceeds the cost of a unified system. The trigger is usually three or more disconnected tools each holding part of the truth — accounting in Xero, inventory in Unleashed, CRM in a spreadsheet, projects in Asana, none talking to each other.

The honest overlap

OMS, WMS and ERP overlap deliberately. Every modern ERP claims OMS and WMS functionality. Every modern WMS claims order management. Every modern OMS claims inventory tracking. The marketing makes them sound interchangeable.

They are not. The right test for any "all-in-one" claim is to ask three questions:

• For OMS depth: can it route a single order across three warehouses based on real-time inventory and shipping cost?
• For WMS depth: can it run a wave pick across five pickers in three zones with scanner validation?
• For ERP depth: can it produce a consolidated P&L across three entities with intercompany eliminations?

A "yes" to all three usually means the vendor is overstating one of the three. Pick the layer where you have the deepest pain and choose a system that does that layer exceptionally well — the other two layers can be lighter.

How OpsUI fits

OpsUI is a modular ERP. The Order Management module handles real OMS workflows: multi-channel aggregation, distributed routing, promise dates, returns. The Warehouse module handles real WMS workflows: bin-level inventory, wave / zone picking, scanner support, dispatch routing, cycle counting. Finance, CRM, HR and Analytics modules handle the rest of ERP.

If your pain is purely order routing across channels, a dedicated OMS (Shipbob, Bringg, IBM Sterling) may be a better fit. If your pain is purely warehouse throughput, a dedicated WMS (Manhattan, Blue Yonder, Mintsoft) may be a better fit. If your pain is operational sprawl across multiple disconnected tools, a modular ERP like OpsUI consolidates without replacing what works.

The bottom line

OMS, WMS and ERP are not synonyms. They are three different layers that the right business needs in different combinations.

Most ANZ SMBs we talk to need ERP depth with embedded OMS and WMS — not three separate platforms. That is the shape OpsUI is built for.

See also

If the WMS layer is where your pain lives, the WMS in New Zealand 2026 buyer's guide compares every shape of warehouse system on the NZ market — local specialists, inventory-led platforms, 3PL systems and modular platforms — honestly.