US stock counts while orders continue: reconcile open picks, transfers and returns

Choose a small count scope and a reference time

Orders continuing elsewhere do not remove the need to control the stock being counted. Choose a SKU group or physical zone, name the counter and movement owner, and define the start, finish and comparison timestamps with timezone. Where practical, pause movements in that zone briefly while other work continues. If movements cannot pause, record each crossing and its evidence instead of promising an uninterrupted, error-free count.

Inveck's LinkedIn cycle-counting overview provides a supplier-practitioner perspective on rotating checks and accountable zones. Use it to plan responsibilities, then verify quantities through your own records. Shopify is the example platform here; choose the counting method and controls that apply to your operation.

Compare like quantities across the same boundary

Write exactly what the count includes: shelves, pick staging, packing benches, quarantine and returns receiving. If a shelf zone excludes staging, its count cannot be compared directly with the whole location balance. Either include the other areas or retain a documented boundary reconciliation. Record SKU, variant and sale unit so a pair sold as one product is not mistaken for one physical component.

Shopify's adjustment history defines On hand as Committed plus Unavailable plus Available, with Incoming separate. Compare an inclusive location count with On hand, not just Available. Reserved and held units still need physical verification. Keep condition and permission to sell separate from whether a unit exists, particularly when damaged stock or a returned item is present.

Map open picks without subtracting reservations twice

List open picking tasks by order line, quantity, current phase and actual stock position. Ask which tasks began before the count and who can confirm where their units now sit. A move from a shelf to staging within the same location is an internal relocation, not a loss from that location's physical total. Ensure the counter checks both areas without counting the same tote twice.

Creating an order or reserving units changes allocation rather than proving physical departure. Do not subtract its quantity again from an On hand count. Record an outbound physical movement only when evidence establishes that units crossed the defined count boundary. Keep its time and reference distinct from the order creation, label print or platform status change.

Log transfers and returns as separate events

For location transfers, keep origin, destination, shipment reference, units, observed departure and observed receipt. Shopify's transfer documentation distinguishes destination Incoming from received inventory. Goods expected but not physically received should not appear in the destination count. Its count-planning guidance recommends pausing between-location transfers during count windows to avoid double counting. Agree that control for the actual operation or record unavoidable movements explicitly.

For returns, record arrival, original order where known, observed units, check status and authorised stock decision. A refund or Return restock activity is not a physical receipt or condition assessment. Keep newly arrived returns identifiable while their records are reconciled, and do not add them to available stock merely to eliminate a variance. Assign unmatched items to a review owner.

Use a timed reconciliation before proposing a correction

This invented example uses UTC and a whole-location boundary. At 09:00, the recorded On hand balance is 60: 12 committed, four unavailable and 44 available. An opening physical check also confirms 60 across that boundary. Three units physically leave at 09:04; two transferred units are received at 09:07; one return arrives in quarantine at 09:08. Recorded movements therefore explain a physical closing total of 60: 60 minus three, plus two, plus one.

An additional two-unit reservation at 09:06 changes allocation, not that physical total. Five units moved from shelving to staging also remain inside the boundary. Suppose the count observations, reconciled to 09:10, confirm 60, but the platform shows 59 because the return is not yet recorded. Check the return reference and whether another process will post it. Resolve its held status through the approved workflow; a blind Available adjustment would misstate permission to sell.

Submit the relevant count without overwriting later events

Shopify's planning guidance distinguishes Quick count, the reviewable POS Pro stock-count workflow, and admin adjustments or CSV updates. It warns that sales between counting and submitting Quick count can produce discrepancies, and recommends submitting a completed zone promptly. These are platform-specific distinctions. Confirm which method, permissions and concurrency handling your actual account supports before applying a count.

Attach count time, submission time and the intervening event references to the proposed correction. Do not overwrite a later valid movement with an earlier observation. Ask the authorised inventory owner to select the applicable workflow and compare its result with the closing physical record. Recount when evidence cannot explain the difference; an acceptable variance threshold must be your approved rule, not an assumed universal allowance.

Review the adjustment trail and preserve the cause

Shopify's adjustment history shows Date, Activity, Created by and changes to inventory states. Use those fields to connect a change with the relevant person, app or channel, then compare the quantities and timestamps with the physical evidence. A Count, Correction or Return restock reason identifies a recorded activity; it does not establish why a unit was absent, damaged or suitable for resale.

Keep the original observation, recount result, approved correction and final balance under one exception reference. Check delayed order or transfer updates before closing it. The reviewed variant history displays the recent 180-day window; Shopify directs older-history enquiries to its adjustment changes report. Preserve your own count evidence under the merchant's retention policy rather than treating a screen as the complete operational record.

Show differences at the counted row level

Keep both the signed quantity difference and its absolute size for each comparable SKU-location row. A positive difference at one row can cancel a negative difference at another in a net total. State the population counted, units and comparison time before presenting an overall result. Preserve the first count separately from any approved correction.

Close the zone and decide the next count

Release the zone through the agreed operating process after quantities and holds are understood. Review recurring differences by SKU, location and movement type before deciding which stock to count next. Bring the completed example and unresolved references to a Jeton warehouse discussion to confirm counting scope and reporting responsibilities. No general frequency or system capability is assumed.

• Retain the boundary, count timestamps and counter's identity.
• Reconcile physical receipts and departures once; keep internal moves and reservations separate.
• Confirm the authorised stock-state outcome and any remaining hold.
• Record submission, resulting balance, next review time and exception owner.