SAP Business One: keep it for finance, add the warehouse layer it never had

SAP Business One runs the back office for a lot of mid-market manufacturers and distributors across Australia and New Zealand.

It is implemented by an SAP partner, your finance team is trained on it, and your auditor is comfortable with it.

Here is what nobody trying to sell you a replacement wants to admit:

B1 is good at what it is for.

It is a real ERP. It handles multi-entity finance, A/R and A/P, and the kind of reporting a growing business actually needs.

Ripping it out to fix the warehouse would be expensive, slow, and mostly unnecessary.

So why does the warehouse still feel broken?

Because an ERP is a system of record, not a warehouse floor.

SAP Business One knows what you own and what it cost.

It does not run a wave pick. It does not drive a pack station.

It does not print a compliant carrier label at 4:55pm on a Friday.

So the gap gets filled the way it always does:

• A spreadsheet for bin locations B1 does not track.
• A second screen for the courier portal.
• A whiteboard for what is actually getting picked today.
• Someone re-keying deliveries back into B1 after the fact.

None of that is B1 failing. It is B1 being asked to do a job it was never built for.

The usual answer is SAP EWM — and it is heavy

The SAP-world answer to a weak warehouse is to add Extended Warehouse Management, or to push up to S/4HANA.

For a 40-person distributor that is a sledgehammer: another licence, another implementation project, another set of partner hours, and a system designed for far larger operations.

Most ANZ SMBs do not need EWM. They need picking, packing, and dispatch that works, wired back to the ERP they already run.

The move is to extend, not replace

Keep SAP Business One as the system of record for finance.

Add a modern ops layer on top for the warehouse and dispatch.

Wire the two together so data flows both ways automatically.

That is exactly what the OpsUI SAP Business One connector does.

What flows where

SAP Business One stays the source of truth for master data and finance:

• Business partners — customers and suppliers — flow into OpsUI.
• Item master, chart of accounts, and purchase orders come across read-side.

OpsUI runs the floor and feeds the results back:

• Picking, packing, and dispatch happen in OpsUI.
• Sales orders, deliveries, A/R invoices, and inventory movements sync back to B1.
• Carrier labels and tracking are handled in the Shipping module, not a second tab.

No nightly batch. No iPaaS in the middle. No 5pm CSV export.

Built into your rollout, not sold as a box

We are honest about this: the SAP Business One connector is built during your rollout, against your own B1 company database — over the Service Layer on HANA deployments or the DI API on SQL deployments — not shipped as a self-serve download today.

B1 installs and add-ons vary, so the sync is scoped to how yours is actually configured.

And to be clear: OpsUI is not an SAP partner or reseller. You keep your existing B1 licence and partner relationship. We just add the operations layer on top.

The rest of OpsUI — orders, inventory, picking, dispatch — runs in production now, alongside B1, whether or not the connector is live yet.

The point

You do not need to leave SAP Business One to fix the warehouse.

You need to stop asking B1 to be the warehouse.

Keep the system of record. Add the ops layer. Get on with shipping product.