Lana Korzhuk β€” Founder & CEO of SIMARA AI

Lana Korzhuk

Founder & CEO Β· LinkedIn

With 20+ years progressing from senior developer to Chief Operating Officer, Lana brings deep expertise in IT systems, ERP implementation, and operational strategy.

Published Β· 11 min read
Supply chain, procurement & inventory

Inventory Management System Implementation: The Stock Cutover Decision

Inventory Management System Implementation: The Stock Cutover Decision
πŸ’‘

TL;DR

  • ●Time required: Set aside a protected window for counting and reconciliation. Base it on your stock locations, transaction volume and ability to pause or capture movements. Do not set a switch time until you know those constraints.
  • ●Difficulty: Moderate to high. Warehouse, operations, finance and system owners must agree on stock states, evidence and who can authorise the switch.
  • ●Expected outcome: A documented decision to proceed, delay or roll back, supported by a ledger connecting the physical count to opening balances, movements, reservations and open receipts.

Switch stock control to the new system only when you can explain how each relevant quantity reached its go-live balance and account for transactions during migration. A successful import alone does not show that the new record is safe to use.

The decision is operational: from a named point in time, which record will staff use to receive, reserve and despatch stock? If you cannot account for a movement or protect a customer reservation, delay the switch. A reassuring total may hide the problem.

This guide starts after you have selected a system and planned an implementation of an inventory management system. For product trials, see the inventory software test scorecard. For a detailed test of one cross-system write, see how to test a recoverable handoff. Neither replaces the cutover decision across the stock record as a whole.

Required tools and prerequisites

Prepare a shared cutover ledger, a physical count sheet and exports from both the old and new stock records. A controlled spreadsheet can work as the ledger, provided the team can preserve versions, restrict edits and identify who made each change.

Before the count, agree the scope: every SKU and location the new record will control, including damaged or quarantined stock, relevant batches or serial numbers, open orders and stock in transit. Record units of measure and conversion rules. You cannot safely compare a count in boxes with an import in individual units without an agreed conversion.

Definition: Stock cutover: the controlled change from one authoritative stock record to another at an agreed point in time.

Name an operations decision-maker, a count owner, a system owner and a finance approver for adjustments. Assign a deputy for each role. Agree how staff will record receipts, despatches, reservations and returns if either system is unavailable. Keep those records accessible if the new system has to be taken offline.

The count and system export do not have to happen simultaneously, but the team must be able to identify and account for every movement between their respective cut-off points. If that is not possible, freeze movements or delay the count.

Step 1: Set the count boundary and tolerances

Choose a count cut-off and a proposed switch cut-off. At each boundary, state which system is authoritative, whether physical movements are paused and where any movements are recorded. Tell warehouse and order-processing staff which instruction takes priority if a screen shows a different balance.

Definition: Cut-off: the agreed point at which a balance is measured or control changes hands. Events on either side must be assigned consistently.

Set tolerances before you see the results. For each stock category, specify an allowed quantity variance, an allowed value variance if relevant and who can approve an exception. A tolerance is a business choice, not evidence that the records are correct.

We recommend a stricter gate for reservations, missing movements, controlled batches or serial numbers and high-impact items. Do not use an aggregate value tolerance to offset a shortage in one SKU against an excess in another. A variance may be within tolerance and still need an owner, an explanation and an approved treatment.

For the illustrative examples below, the business chooses zero unexplained units for the item and zero missing reservation or receipt events. These are scenario assumptions, not universal thresholds. If an actual business accepts a non-zero variance, its approver should record why the residual risk is acceptable and what follow-up will resolve it.

Step 2: Build the cutover reconciliation ledger

Use one ledger line per SKU, location and relevant stock state. Add batch or serial references where they affect what can be issued. Keep on-hand stock, reserved stock and open purchase order quantities separate. They answer different questions and must not be added together as though they were all available goods.

Definition: Opening balance: the quantity loaded into the new record at its stated baseline, before later movements are applied.

For each line, capture the count timestamp and quantity, the old-record balance at that point, any approved count adjustment, the imported opening balance, subsequent movements and the new-record balance at the switch. Record movement IDs, timestamps, quantities, locations, source evidence and posting status. Include the person responsible for any unresolved difference and the decision deadline.

For this worksheet, use these equations, adapting them to your actual stock-state definitions:

  • Expected switch on-hand = verified count at the count cut-off + receipts into on-hand βˆ’ despatches βˆ’ write-offs, plus or minus other documented physical movements.
  • Expected available = switch on-hand βˆ’ active reservations βˆ’ separately recorded non-available stock, where those quantities do not overlap.
  • Open receipt balance = purchase order quantity still due after accepted receipts and any documented amendments.

These are control calculations, not a claim that your software labels fields this way. Before calculating availability, document whether on-hand includes quarantined items and whether reservations overlap with them. Record in-transit transfers at the appropriate locations so the same goods are not counted twice.

Step 3: Reconcile a count, import and live movements

The following is illustrative and synthetic. All quantities, times, IDs and results are assumptions for this example, not a real assessment or a product capability claim. The item has no quarantined stock, and its unit of measure is one individual unit. A controlled log captures movements while the new system is prepared.

At the count cut-off of 09:00, the physical count and old-record balance for SKU EX-A at location MAIN both show 100 units. A customer order, SO-7, reserves 20 units. Purchase order PO-4 has 10 units outstanding. The team imports 100 units as the new opening balance.

Illustrative event On-hand calculation Reservation or open receipt Evidence to retain
09:00 count and opening import Count 100; imported opening 100 SO-7: 20 reserved; PO-4: 10 due Signed count sheet, old export and import result
Receipt R-4 100 + 6 = 106 PO-4: 10 βˆ’ 6 = 4 due Delivery and receipt record showing 6 accepted units
Despatch D-7 against SO-7 106 βˆ’ 8 = 98 SO-7: 20 βˆ’ 8 = 12 still reserved Despatch record and updated order status
Switch reconciliation New record: 98; expected: 98 12 reserved; 4 due; available 98 βˆ’ 12 = 86 New export, movement log and sign-off

The receipt is included once in on-hand and reduces the open purchase order by the same accepted quantity. The despatch reduces both on-hand and the reservation for that order. Subtracting the original reservation of 20 after despatch would understate availability.

Illustrative result: the four control figures agree with the assumed evidence, so this line passes the example's zero-variance gate. The wider cutover can proceed only if the rest of the agreed scope and the decision gates also pass. Replace every assumed result with observed exports and signed source records.

Step 4: Decide whether to proceed or delay

The operations decision-maker should sign a cutover record stating the switch time, the authoritative system, the scope reviewed, outstanding exceptions and the names of those accepting them. Keep the supporting exports and ledger version with the decision.

Proceed when the reconciled opening and subsequent movements support the new balances, reservations and open receipts are represented correctly, and every exception is resolved or formally accepted within the previously agreed tolerance. Confirm that staff know where to work and that outstanding events have a named owner.

Delay when an unexplained difference exceeds tolerance, a required reservation or receipt cannot be accounted for, or the team cannot establish which record is current. Continue using the old record if it remains operational, capture movements there and set a fresh cut-off. Keep the count and movement log even if the switch is delayed.

What if the import is wrong? In the illustrative EX-A scenario, suppose the import shows 99 rather than the counted 100. After the same receipt and despatch, the new record would show 97, against an expected 98. Assign the difference to the system owner, check the import evidence and correct it through an authorised method. Reconcile the result again before switching. An adjustment that merely makes totals match, without an explanation, does not resolve the evidence gap.

Step 5: Prepare a rollback that preserves transactions

A rollback involves more than reopening the old system. Once the new record becomes authoritative, it may contain real receipts, despatches, reservation changes and corrections that the old record does not yet have. Returning to the old record without those events would lose the operational history needed to bring its balance up to date.

Definition: Rollback: a controlled return to the former system of record after the switch, including reconciliation of transactions created while the new system was authoritative.

Before go-live, agree who can declare rollback, how new writes will be stopped or queued and how every event will be exported or captured independently. Keep a known old-record baseline at the switch and a unique reference for each event. Check the destination for an event before re-entering it. If its posting status is uncertain, hold it for investigation rather than replaying it blindly.

What if a despatch happens after the switch? In a further illustrative continuation of EX-A, assume the old record was frozen at 98 on-hand and 12 reserved. The new system records D-8, a despatch of 3 units against the same reservation. Its balance is now 95 on-hand and 9 reserved; available remains 86. If rollback is declared, capture D-8, verify it is absent from the old record, then apply it once using the approved process. Reconcile the old record to 95 on-hand and 9 reserved before making it authoritative again. The 4 units still due on PO-4 must also remain visible.

If the old system cannot accept the event, or its status cannot be established, keep affected stock and orders under a controlled manual process and escalate. Do not declare rollback complete until owners can account for the physical stock, orders and outstanding events.

Common Pitfalls / Troubleshooting

An open receipt is treated as stock already on the shelf. Separate goods physically accepted from quantities still due. If a delivery arrives during the count, record whether it was included in the count and whether its receipt has been posted. Include it once, not in both the opening count and the later movement total.

A return is credited before it is physically received. Decide which event changes the stock position in your process. For example, Zoho Inventory's sales return guidance distinguishes raising a return from receiving goods into the warehouse. Check the behaviour and configuration of your own system before mapping return events.

Stock is moved between locations while counting. Record the departure, arrival and any goods still in transit against the count boundary. Zoho Inventory's transfer order guidance describes transfer records between warehouses. Your reconciliation must still establish where each item was at the relevant cut-off; a transfer document alone is not a physical count.

A reservation total looks right but belongs to the wrong orders. Reconcile customer order references and remaining quantities, not just the aggregate. Assign mismatches to the order owner before releasing stock for picking.

Trade-offs, risks and limitations

A protected cutover window can interrupt receiving, picking and customer commitments. Allowing work to continue reduces that interruption but leaves a larger movement log to reconcile. Choose deliberately: an incomplete log can be more disruptive than a planned pause.

Detailed reconciliation takes staff time. Warehouse staff must count and investigate; system owners must validate imports and transaction statuses; finance may need to review stock adjustments and valuation consequences. A quantity match alone does not prove that stock value, ownership, expiry dates or batch attributes are correct.

A spreadsheet ledger can make the decision visible, but it is another record to control. Preserve source exports, timestamp versions and limit who can amend the decision sheet. If a figure changes, retain the prior evidence and reason rather than overwriting the only copy.

AI is not required to make this cutover decision. If you later want to assess automated purchasing, the separate supplier data threshold guide for AI reorder points addresses that question. The cutover ledger establishes what stock record you can use now; it does not establish whether historical data is suitable for forecasting.

When this cutover recommendation does not apply

Do not use the simple on-hand calculation unchanged if your operation needs to distinguish ownership, consignment stock, serial-controlled items, expiry, manufacturing work in progress or complex stock states. Extend the ledger to reconcile those attributes and involve the relevant operational and finance owners. A matched quantity can still be the wrong item, batch or owner.

A whole-business switch may also be the wrong unit of control if locations cannot share a reliable cut-off. Consider a phased switch only if you can define which record owns each item and location, prevent staff from acting on conflicting balances, and reconcile transfers across the boundary. If you cannot demonstrate those controls, delay rather than assume phasing removes the risk.

This worksheet cannot prove that a specific import, integration or rollback function exists in your chosen product. Confirm the actual configuration and rehearse the process with your system owner. A failed rehearsal or an inability to capture live transactions is evidence against switching on the planned date.

What to explore next

If you are still deciding which process to automate first, the optional Automation Priority Scorer ranks candidate workflows by effort, impact and risk. It does not replace the stock cutover decision.

Sources & Further Reading

Frequently Asked Questions

Common questions about this topic, answered briefly.

Does a successful stock import mean we can go live?
No. Compare the imported opening balances with the count and reconcile all subsequent movements, reservations and open receipts. The switch also needs an agreed decision owner and a way to capture transactions if rollback is required.
Should we stop all warehouse movements during cutover?
Not necessarily. A pause can simplify reconciliation, but it has an operational cost. If movements continue, use a controlled log that identifies each event, its timing, source evidence and posting status. If you cannot account for those movements, pause or delay.
Can we accept a small stock discrepancy?
Only against a tolerance agreed in advance by the appropriate owner. Record the affected item, explanation, risk, approver and follow-up. A small aggregate difference does not excuse a missing reservation, an unknown movement or a critical item mismatch.
What happens to purchase orders that are only partly received?
Reconcile the quantity accepted into stock separately from the quantity still due. Preserve the purchase order reference and remaining balance in the record staff will use after the switch. Investigate any receipt whose physical or posting status is uncertain.
How do we avoid losing transactions during rollback?
Stop or control new writes, capture the events recorded after the switch and compare them with the old record before applying them. Reconcile balances and open orders, including unresolved events, before declaring the old record authoritative again. To discuss your stock cutover, [Contact SIMARA AI](/contact).

See your numbers before you spend a penny

Free, no sign-up: the Automation Priority Scorer ranks your candidate workflows by effort, impact and risk so you start with the highest-return one.

Try the free Automation Priority Scorer

Or talk to us directly: