← Inventory & exceptions

YUNXIU / OPERATIONS GUIDE

Warehouse system cutovers: reconciling two ledgers safely

When old and new systems overlap, receipts can be posted twice and orders executed twice. Parallel ledgers should verify a transition, not create two uncontrolled sources of execution. Define one operational authority, a cut-off and discrepancy ownership.

Yunxiu · Operations planning reference · Updated 8 November 2026

Choose the execution authority

Separate testing, shadow records and live execution. A trial system may receive copies without issuing real pick or shipping instructions. Define cutover points and identifiers by transaction type. Preserve order lineage across cancellation and recreation. Retries need duplicate-detection controls rather than reliance on operator memory.

Migrate states and relationships

Beyond SKU totals, preserve owner, batch, dates, location, holds, allocations and relevant off-site stock. Missing fields are discrepancies, not a reason to mark everything available. Retain old-to-new mappings. Define alternatives for unsupported states before launch rather than leaving staff to explain them informally.

Reconcile transactions and dimensions

Compare opening stock and transition-period receipts, dispatches, returns, relocations and adjustments. Confirm key events executed once. Matching totals can conceal batch or owner swaps. Track late data, retries and manual entries with source IDs. Define stop conditions for unexplained differences rather than accepting approximate agreement.

Protect new activity during rollback

Restoring an old backup can erase real post-cutover movements. Define how new transactions are preserved, which execution source pauses and who authorises recovery. Check duplication risk. Retire old operating access only after acceptance while preserving needed history. Rehearse with isolated data, not arbitrary changes to real stock or customer orders.

Illustrative decision or record

Illustrative retry: order O100 has already executed in the old system when the new system receives it again. It should recognise the processed event or require review, not issue another real pick instruction. Retain source ID, target ID and execution state. Test with isolated data, never by duplicating a real shipment to demonstrate a control.

Before you proceed

  • One source controls real execution
  • States, batches and open work are mapped
  • Rollback preserves post-cutover activity

Related operations

Review the cargo and the work together

Share the product, packaging, batches and quantities, customs status, expected schedule and the special requirements discussed here. Confirm acceptance before arranging delivery.