Foundation · 2 min
What you need to know
How should inventory be migrated?
Map every sellable SKU and inventory location, including available, reserved and incoming quantities where supported. Load a controlled snapshot and final delta, then reconcile before opening the new store for sale.
When should inventory quantities be migrated?
Move the main inventory snapshot close enough to cutover to limit changes, then capture a final delta after writes are frozen or synchronized. The exact timing depends on order volume and the inventory system of record.
How do I prevent inventory changes during cutover?
Use a short write freeze or a reliable change-capture process for orders, adjustments, receipts and transfers. Record every change after the snapshot, so none is lost between systems.
How should multiple inventory locations be migrated?
Preserve each SKU-location relationship and map source locations to approved destination locations. Test routing, availability, and transfer behavior instead of collapsing stock into one total unintentionally.
How should reserved inventory be handled?
Carry reservations only when they correspond to valid open orders or operational holds. Rebuild them from those records and prevent the same units from being reserved twice.
How do I reconcile inventory after migration?
Compare available, reserved and physical quantities by SKU and location, then investigate every difference. Keep selling disabled for affected items until the source of the mismatch is understood.
A quick store check
Compare available, reserved, and physical quantities for several SKU-location pairs at the same cutoff time.
Foundation · 2 min
Frequently asked questions
Can inventory be migrated days before launch?
A preliminary load can, but a final snapshot or captured delta is needed close to cutover.
What should happen to mismatched items?
Keep unsafe items unavailable and investigate the specific order, reservation, receipt, or mapping behind the difference.