A wrong part doesn't just cost a return. It costs a customer a day on the lift.
How a high-volume auto parts distributor moves from a disconnected WMS to scanner-verified fulfillment, scan-to-pack verification and automatic label printing — all native to Acumatica.
This is a composite scenario, not a customer. The operation described is assembled from implementations across high-volume parts distribution, with the identifying details removed. There are no performance figures on this page because we do not publish numbers we cannot attribute to a named customer.
What is real is the workflow: every step below is what the software actually does, and you can verify all of it in a twenty-minute demo.
Rejected at the bin
A wrong part scan fails before it reaches a box.
Verified at the carton
Nothing seals with a discrepancy.
One workflow, both sites
Pick, pack and ship status across facilities in one portal.
Two warehouses, and a WMS that never quite stays in sync.
A regional aftermarket distributor serving independent repair shops, dealership service departments and fleet operators across two warehouses. A mix of single-line rush orders for a car already on a lift and multi-line wholesale orders going to shop inventory.
They run Acumatica. Their fulfillment WMS is a separate system that never quite stays in sync with it.
Wrong parts. Angry shops. A returns process that cost more than the parts.
Auto parts SKU density is brutal. A distributor might carry hundreds of brake pad SKUs differentiated only by application year and vehicle trim. Paper pick tickets and visual SKU verification worked — until they didn't. At volume, pickers started pattern-matching on part number prefixes and reaching for the wrong bin.
Nobody in an operation like this thinks the error rate is zero. They know roughly what it is, they know it rises with volume and with overtime, and every instance costs a return, a credit memo, a reshipment and a phone call from a shop with a customer waiting.
The pack station has no systematic verification either. A packer builds a carton from what is in the tote, seals it, and the only check on whether the tote was right is the same pair of eyes that picked it.
And with two facilities running on a WMS that does not agree with the ERP, nobody has a single view of what is picked, what is packed and what has shipped. Status is a phone call to the other building.
A pick-error range once appeared on this page as if it had been measured at a real customer. It has been removed rather than moved: any number here would have to be attributed to an observed range from our own implementation history, and stated as exactly that.
Three verification points, before the box is sealed.
Pick accuracy isn't a training problem. It's a system design problem.
Picking runs against the Acumatica Shipment itself, not a copy of it. Every line is scanned, and the scan either matches the shipment line or it does not — a wrong part is rejected at the bin, in the aisle, by the scanner, before it reaches a tote. Short picks are handled inside the workflow rather than discovered later in reconciliation.
Pick state lives in the database rather than a browser session, so a dropped scanner, a dead battery or a device swap resumes at the exact step it stopped on. When Customer Service amends an order in Acumatica mid-pick, WMSi diffs the lines and updates the live session instead of the picker finding out at ship time.
At the pack bench, every item is scanned into the carton. A discrepancy flags before the box seals, and confirming the pack fires the carton label to the bench printer with no manual print step. Several packers can work the same batch at once without two of them pulling the same order.
At ship, carrier routing rules run first, then live rate shopping across the connected carrier accounts; one tap buys the label and it prints at the ship station. WMSi writes package contents and tracking numbers onto the Acumatica Shipment and calls ConfirmShipment, so the shipment is released in the ERP as the truck leaves. Both facilities run the same workflow and both appear in the same manager portal.
In prose: a scan that does not match the shipment line is rejected at the bin rather than accepted and discovered later; the correct part scans through and is verified against the Acumatica line; and at ship the carton is rate-shopped, labelled and confirmed back into Acumatica in one step. Document numbers are illustrative.
Scanner screen for this workflow:
Verification moves from the eye to the scanner.
Accuracy stops depending on whether a picker under time pressure reads the last three characters of a part number correctly. The scan either matches the shipment line or it doesn't, and if it doesn't, the picker finds out at the bin instead of the shop finding out at the counter.
The label process collapses from three manual steps across two systems to zero. Carton labels print on seal, carrier labels print on ship, and the packing team stops handling label generation at all.
The reconciliation problem disappears because there is nothing to reconcile — Acumatica is the single source of truth for order status, because WMSi writes every fulfillment event directly into it.
| Area | What it becomes |
|---|---|
| Pick verification | Every line scanned against the Acumatica shipment. A wrong scan is rejected at the bin. |
| Pack verification | Every item scanned into the carton. Discrepancies flag before the box seals. |
| Labels | Carton label on seal, carrier label on ship. No manual step, no mismatched label. |
| Systems to reconcile | None. Acumatica is the source of truth; WMSi writes to it directly. |
Nine mechanisms, all of them demonstrable.
- Shipments pushed in from Acumatica by webhook, so the picker works the order as it is now
- Scan-verified picking against the Acumatica shipment line, with a wrong scan rejected at the bin
- Replenishment-first verification, so no ticket reaches the floor against a pickface that cannot fill it
- Crash-resilient pick state held in the database, not the browser session
- Mid-pick amendment detection, diffed against the live session
- Scan-to-pack carton verification, with discrepancies flagged before seal
- Concurrent packer locking, so several packers work one batch without collision
- Carton label on pack confirm and carrier label on ship, both printed automatically
- Package contents and tracking written to the Acumatica Shipment, then
ConfirmShipment
The three modules this scenario runs on.
Order fulfillment
Scan-verified picking against the live Acumatica shipment, pick state that survives a dropped scanner, and mid-pick amendments resolved without pulling a manager.
How fulfillment works OutboundPack & ship
Scan-to-pack verification, volumetric carton suggestion, live carrier rate shopping, and ConfirmShipment posted as the truck leaves.
Label printing
Carton labels on pack confirm, carrier labels on ship, printed to the right printer at the right bench without anyone choosing from a dropdown.
How label printing worksRecognize this floor?
Twenty minutes with a WMSi specialist. Real scanner workflow, real Acumatica integration. No slides.