Why We Separate Bin Locations from Acumatica Zones — and Why It Matters

If you've implemented Acumatica in a warehouse, you've worked with warehouse zones — logical groupings like RECEIVING, BULK, PICKFACE, and SHIPPING. They're useful for financial and operational reporting inside Acumatica. But they're not the same as physical bin locations, and treating them as if they were creates real problems on the warehouse floor.

WMS Intelligence maintains two distinct location namespaces, and they serve different purposes.

What Acumatica tracks

Acumatica zones are logical. BULK might contain hundreds of physical bins across three aisles. PICKFACE might span an entire floor. When Acumatica records that inventory moved to PICKFACE, that's useful for inventory valuation and order availability — but it doesn't tell a warehouse worker where to walk.

What WMSi tracks

WMSi is the system of record for physical bin locations. Every location in WMSi has a specific address: aisle, rack, level, position — something like A-01-003 or RECV-02. These are the coordinates that direct warehouse workers and scanners. Putaway rules, capacity constraints, allergen separation, and ABC zoning all operate at this level.

The bridge between the two

Every WMSi bin location carries an Acumatica Location mapping — the logical zone it belongs to in Acumatica. When WMSi posts a transfer or receipt to Acumatica, it translates the physical bin to its Acumatica zone automatically. The warehouse worker scans a bin. WMSi handles the translation.

This mapping is managed through the WMSi portal by warehouse managers, using a dropdown populated directly from Acumatica — no manual entry, no mismatches.

Why this matters in practice

Without this separation, you face a choice: either run Acumatica with hundreds of zones (one per bin, essentially), which creates an administrative burden and defeats the purpose of logical grouping — or collapse everything into a handful of zones and lose bin-level traceability inside your WMS.

WMSi takes a third path. Acumatica stays clean with meaningful logical zones. The warehouse operates with precise bin-level direction. Every transaction posted to Acumatica carries the right zone automatically, with a full audit trail of which physical bin the inventory actually came from.

For VARs implementing WMSi alongside Acumatica, this separation is one of the first things to configure — and getting it right at the start pays dividends through every module that follows.