Bin Location Optimization and Wave Picking

Where standard bin locations stop

SAP Business One gives you bin locations, and for a single stockroom that is enough. A growing warehouse outgrows them quickly. Bins exist, but nothing decides which bin an item should live in, so fast movers end up at the back of the building and pickers walk further every month. The Pick and Pack Manager releases pick lists one sales order at a time, so six orders for the same item mean six separate trips to the same bin. Replenishment from bulk to forward pick faces happens because someone noticed an empty face, not because a rule fired. And nothing verifies at the packing bench that what is in the carton matches what is on the Delivery — the first check is the customer's.

The symptoms are familiar: pickers walking a mile a day, forward faces running dry during the afternoon rush, mis-ships that are only discovered as returns, and a warehouse manager who cannot say which bins are actually productive.

ECOSIRE builds an add-on that puts slotting, waves and verification on top of the bin locations you already have.

What ECOSIRE builds

The add-on is a SAP Business One extension using the Service Layer for inventory transactions and document work, and the DI API where a movement must post inside the same unit of work as a B1 document. Warehouse configuration and wave data live in UDTs and UDOs; item and bin attributes we need are added as UDFs. Your OBIN bin structure, WHS warehouses and standard inventory documents remain the system of record — we do not build a shadow stock ledger.

Slotting

Every bin gains attributes: zone, aisle, level, pick face or bulk, capacity by volume and weight, and permitted item class. Every item gains velocity and dimension data. A slotting engine then scores current placement against demand — pulled from Sales Order and Delivery history — and produces a re-slotting worklist: which items should move to a faster face, which should move back to bulk, and which bins are being wasted. The worklist is executed as standard Inventory Transfer documents, so the movement is a real, auditable B1 transaction, not a private table update.

Replenishment rules

Min/max levels are set per bin, not just per warehouse. A background service watches forward pick faces and raises replenishment tasks from bulk before the face runs dry, honouring batch and serial rules and the FEFO or FIFO policy you configure. Tasks appear on a replenishment queue and post as Inventory Transfers on completion.

Wave and batch picking

Open Sales Orders are grouped into waves by the criteria you choose — carrier cut-off, route, customer, order value, single-line versus multi-line. Within a wave, a picker can be given a batch pick: one trip that collects the same item for several orders, sorted into totes, followed by a consolidation step. Pick tasks are generated against bins with an optimised sequence through the aisle layout you give us, so the walk path is ordered rather than list-ordered. Short picks raise an exception on the task instead of quietly leaving the line unpicked, and the wave shows its own progress: released, in progress, short, complete.

Pack verification

At the bench, the packer scans each item against the picked order. The add-on checks quantity, batch and serial where relevant, and refuses to close the carton on a mismatch. Carton contents, weight and dimensions are recorded and the Delivery document is created from the verified contents — so the Delivery reflects what physically shipped. Where you want a supervisor override, that override is logged with the user and the reason.

Visibility

Crystal Reports are delivered for pick productivity by picker and by wave, bin utilisation and dead-bin analysis, replenishment exceptions, and short-pick history. These are the reports a warehouse manager runs on a Monday morning, not developer tooling.

Who it is for

Distribution, wholesale, e-commerce fulfilment and light manufacturing operations running SAP Business One where the warehouse has grown past what Pick and Pack Manager comfortably handles — typically multi-aisle warehouses, several hundred order lines a day and up, or any operation where mis-ships have become a measurable cost.

Compatibility

SAP Business One 10.0 on Microsoft SQL Server and SAP HANA, on-premise or cloud-hosted. Bin location management must be enabled on the warehouses in scope. Handheld scanning is supported through a browser-based interface on your existing Android or Windows devices, or through your current scanning hardware where it can reach the Service Layer — device choice is settled during scoping since it affects the screens we build.

How delivery works

1. Scoping call. We walk your warehouse layout, aisle and bin naming, item classes, batch/serial policy, carrier cut-offs and current pick process. Your real order profile drives the wave rules. 2. Fixed quote. A written scope covering the slotting rules, wave criteria, screens, scanning flow, reports and acceptance criteria, at a fixed price. Nothing is built before you approve it. 3. Build. Typical lead time is 2 to 4 weeks from approval. Nothing is pre-built — this is written for your warehouse layout and your order profile. 4. Install into test. Installed into your test company database with a copy of your bin structure. We run a real day's orders through it and hand you a test script your warehouse supervisor can work through on the floor with handhelds. 5. Install into production. After sign-off, we install into production, load your bin attributes and slotting rules, and stand by for the first live wave. 6. Support. A support window from go-live covering defects, tuning of wave and replenishment rules against real throughput, and your team's questions.

An honest note on sequencing

Slotting only pays off if your bin master data is accurate. If your bins are named inconsistently or your item dimensions are missing, we will tell you that in scoping and include the clean-up as a defined step — because the alternative is an optimisation engine producing confident nonsense.