Outgrowing Xero’s inventory module

Xero’s inventory module is fine. For about 30 SKUs.

When you outgrow it, you do not have to leave Xero.

Here is where Xero stops working, and what to add alongside.

What Xero inventory is actually for

Xero’s tracked-inventory feature lets you record items, their average cost, and stock on hand. It updates COGS when you sell. It rolls into GST and your P&L.

That is the job of an accounting inventory module: get the valuation right, get the tax right, get the books right.

It is not the job of an accounting inventory module to tell a picker where to walk.

Where it visibly breaks

You will know you have outgrown Xero inventory when one or more of these is true in your business:

• You have more than ~200 SKUs. Xero handles them, but the UI gets slow and managing variants becomes painful.
• You run more than one location. Xero tracks total stock on hand, not stock-on-hand-at-location. If you have a main DC and a satellite store, Xero cannot tell you where the unit actually is.
• You need lot, batch, or serial tracking. FMCG, food, beverage, pharma, electronics. Xero does not capture lot or serial against a stock movement. If your auditor or your customer asks for traceability, you cannot give it.
• You kit or bundle. Xero supports bundled items lightly. It does not handle proper kit / BOM logic with component depletion the way a real ops system does.
• You do cycle counts. Xero lets you adjust stock. It does not let you plan a count, walk the count, and reconcile against a plan with an audit trail.
• You ship from a floor. Xero does not generate a pick wave, does not print a carrier-ready label, does not capture a scan, does not produce a manifest.

Hit two or three of those and Xero is no longer the right place for the operational view of inventory. It is still the right place for the accounting view.

The mistake most teams make next

They go shopping for a “Xero replacement”. The big ERP sales call begins. Three demos later they are quoting NetSuite at NZ$80k of setup + per-seat fees on top.

That is the wrong shape. The accountant did not ask to leave Xero. The auditor did not ask to leave Xero. The bookkeeper does not want to learn another platform.

The warehouse manager asked for warehouse software. That is a different problem.

What to add (without leaving Xero)

A proper operations layer that:

• Runs the picking, packing, dispatch, and receiving workflows on the floor
• Holds the operational truth about where stock is, in what state, in which bin, against which lot
• Posts to Xero in real time so the accounting view stays correct
• Lets your couriers, your customers, and your team see what they need without anyone learning the accounting platform

Two systems is not a sign of failure. It is a sign of sized scope. Xero is best at one thing, an ops system is best at another. The job is to make them talk.

What good integration looks like

• Invoices created on dispatch flow to Xero within seconds, not on a Friday batch
• Payments recorded in Xero update order status in the ops system
• Inventory adjustments produced by cycle counts post to Xero as journal entries with the right tax treatment
• Customer record updates propagate both ways so the team is never working off two contact lists
• The auditor sees a clean trail across both systems

That is the shape OpsUI is built to fit into. The Xero connector is in the “Built on rollout” tier (we wire it against your tenant during onboarding) and the warehouse modules run live in production today against NZ Couriers and (for AU customers) the AU carrier set.

You do not have to leave Xero. You just have to stop asking it to be a warehouse system.