When a WMS cutover changes the movement trail
A go-live can be routine for IT and material for the people who have to explain last month’s on-hand.
Inventory applications are cut over for vendor support, a new scanner fleet, or a move from a plant ledger into a shared WMS. From our point of view the question is narrower: did the cutover change how quantities are stored, adjusted, or logged, and can last period’s on-hand still be reproduced?
We have seen cutovers that recast location codes, reset reason-code lists, or archive movement history into a format the current enquiry cannot search. None of those events is automatically a misstatement. All of them make the next count more expensive if nobody kept an extract.
If you have a cutover between two month-ends, export location balances and a sample of movement types before the switch. If you want us involved, the useful moment is before go-live, not after the first noisy variance. Adjustment verification exists partly for this: a named set of postings, re-tested on the new version, with a short letter beside the cutover note.