Investigate stocktake differences before adjusting inventory

Preserve the counted snapshot

Keep count time, location, shelf, SKU, recorded quantity, physical count, difference and counter. If sales or receipts continue during counting, capture the movements across that interval. Comparing an earlier count only with the current balance can turn a legitimate later shipment into an apparent discrepancy. Define the count boundary and reference time. State whether goods in packing, returns holding areas or another shelf are included rather than leaving every counter to make that choice.

Recount the same defined scope

For ST-031, suppose the register shows twenty units and the shelf count is seventeen. Ask another person to recount the same location and unit. Check boxes versus individual units, similar variants, neighbouring shelves and returns holding areas. Preserve both results with their counters. If the counts disagree, reconcile their scope rather than averaging the numbers. An average is not evidence of how many physical items exist or where they are located.

Review movements and pending work

Review receipts, dispatches, returns, transfers, reservations and sample loans as relevant to the business. Distinguish an unrecorded shipment from goods received but not reviewed or goods moved to another location without an update. Use transaction references as evidence and follow a repeatable review order. Do not force an unexplained difference into a convenient cause. An honest unresolved discrepancy is more useful than a confident reason that cannot be supported.

Check pending updates before adjusting

If a delayed shipment update will arrive later, manually reducing the same units now can create a second deduction. Review pending integration work and decide how the authoritative update will be applied. Shopify supports inventory adjustments; verify SKU and location before using them. Record the reason and reviewer, then reconcile the resulting balance. A corrected screen is not sufficient if a queued transaction can change it again after the count is closed.

Keep unresolved differences visible

For an unresolved difference, record the affected goods, practical impact, evidence checked and next reviewer. A responsible person should decide the operational response for that product, including how to avoid promising unavailable goods. Do not hide an investigation merely because a provisional balance was entered. At the next count, review whether the same SKU or location repeats the problem. Repeated unexplained differences may point to a process boundary rather than a one-off counting error.

Test movements across the count boundary

Test a dispatch immediately after counting, stock at another location, pack-unit confusion, an uninspected return and delayed synchronisation. The reviewer should be able to explain the reference time and scope, not just the final difference. Check that a late update cannot be counted twice and that the original count survives the correction. Completion requires both a reconciled quantity and a reviewable explanation of how the balance was reached.

ST-031: account for a shipment after the count

ST-031 has seventeen physical and recorded units at 14:00. Two dispatch at 14:10, leaving a 14:20 balance of fifteen. Comparing fifteen with the earlier count of seventeen invents a two-unit surplus. Reconcile to the same time first. If the 14:00 register instead showed twenty, a separate three-unit difference still needs investigation. Time alignment and discrepancy analysis are different steps. Preserve the count and movements so a delayed sync cannot cause the same shipment to be deducted again through an adjustment.

Choose a tool and budget around the actual workload

For a small stockroom, a count sheet and targeted recount may be enough. Estimate shelves, movements, recounting and investigation time as well as SKU count. Automation can help preserve evidence and connect transactions, but an unverified visual guess should not determine the physical quantity. First examine whether consistent units and reference times remove much of the discrepancy. Buying a new application does not solve a count boundary that the team has never defined.

• Send low-stock alerts with Make
• Reconcile daily orders with Make
• Share a spreadsheet safely between people and automations