A dropped scanner doesn't lose the pick.
Pick and pack fulfillment for Acumatica ERP.
Pick state lives in the database, short picks are caught before dispatch, and mid-pick Acumatica amendments resolve themselves without pulling a manager.
Three things break a picking day, and none of them is the picker.
A ticket goes to the floor against a pickface that cannot fill it, and the trip is wasted before it starts. A scanner drops, reboots, or a battery dies, and the picker starts over.
And Customer Service amends the order in Acumatica while the picker is halfway down the aisle, so the right work is now the wrong work and nobody knows for another twenty minutes.
Illustrative only. A pick confirming into a tote, an Acumatica amendment arriving mid-pick and pausing the affected session for a line diff, and the same session resuming at step seven on a different scanner. Document numbers are examples, not a customer's.
The wasted trip never happens.
- Replenishment-first verification No pick ticket reaches the floor until WMSi confirms the pickface can fulfil it. The wasted trip never happens. See replenishment.
- Hot orders re-sequence live work A priority order entering the queue is flagged and surfaced to pickers immediately, and work in progress re-sequences around it.
State lives in the database, not the browser.
Crash-resilient state
Pick flow state is stored in the database, not the browser session. A crash, a browser restart or a device swap resumes at the exact step it stopped on.
Single and batch picking
Single-order picking for high-priority or complex orders; batch picking assigns multiple orders to one picker with tote and bin tracking per order across the path.
The scanner reacts mid-pick
It polls continuously and responds to order amendments, lot changes, location changes, session pauses and return-to-stock obligations without losing the picker's place.
Zebra devices are recommended for scanning; most Android devices running Chrome are compatible. The scanner polls every 5 seconds.
The amendment is diffed, not discovered.
Amendment detection and diff. When Acumatica amends a shipment mid-pick, WMSi pauses the affected sessions, diffs the lines, and either resumes or escalates to a manager — automatically.
The escalation lands in the manager portal, and the amendment itself arrives over the webhook channel described on the integration page.
Same scanner, all the way out.
- Carton suggestion and live rate shopping Volumetric carton suggestion at the pack bench and live carrier rate shopping at ship time, both from the same scanner. See the full pack and ship flow.
- Configurable Acumatica transmission Post at pick complete, pack complete or ship complete — a portal setting, not a code change.
- Sales Order follow Anyone can subscribe to a Sales Order and receive digest notifications at each milestone — pick complete, short pick, amendment, pack, ship — without watching the portal.
The order as it is now, not as it was at the last sync.
Shipments arrive from Acumatica by webhook, so a picker is working the order as it exists now, not as it existed at the last sync. When Acumatica amends a shipment mid-pick, WMSi diffs the lines and updates the live session rather than discovering the change at ship time. You choose whether the result posts back at pick, pack or ship complete.
- Inbound
- Sales Orders and Shipments arrive by Acumatica push notification. Amended lines are diffed against live pick sessions.
- Outbound trigger
- Pick complete, pack complete or ship complete — a portal setting.
- Duplicate protection
ExternalRefon every post, so a retry after a timeout cannot create a second document.- Architecture
- The full integration architecture — auth scope, idempotency and the 30-minute reconciliation pass.
Twenty minutes, a live pick workflow, no slides.
A real Acumatica shipment posting at the end of it. We sell through Acumatica VARs — tell us how your floor runs and we will introduce you to the right partner.