Acumatica Warehouse and Inventory Help: Scanning, Counts, Master Data
Warehouse and inventory hub
Fix the data first. Then buy the scanners.
Scanning that never worked. Counts that freeze the whole system. On-hand nobody trusts.
Why it happens in Acumatica
Scanning depends on three things: a populated barcode cross-reference, the right lot settings and stable part numbers. If any one is missing, hardware will not help. Native partial cycle counting exists, and many teams have never been shown it.
Barcode scanning readiness
A client wanted scanners for about a dozen warehouse users. Scanning had never worked because the barcode field was empty, lot tracking was off and part numbers were about to change. The zero-cost proof came first: load the codes and demo on devices they already owned. An independent firm can say that. A reseller cannot.
Cycle counting
One warehouse team had only ever run full counts that froze the system. Native partial cycle counting had been available the whole time. It was the feature they already paid for, turned on.
Inventory master data cleanup
Run in waves, each gated by sign-off from operations, engineering and finance. One obsolescence pass covered several hundred items. Not a spreadsheet dump.
Item class design
Item class drives planning, accounts and lot behavior. Get it right and new items inherit the right defaults. Get it wrong and every new item is a future ticket.
Replenishment and min/max
Replenishment settings that match how you actually buy, including seasonal demand.
How AI helps
Master data review at volume: duplicates, obsolete items, missing barcodes, items in the wrong class. 3PL inventory reconciliation with variances classified by likely cause.