How to Run Ecommerce Inventory Cycle Counts

Shopify describes a planned inventory count as a way to confirm that physical stock matches the quantity recorded in the admin. A cycle count applies that comparison to a bounded subset of inventory instead of closing the entire operation for a full count. Name the location, storage zones, SKUs, inventory states, count window, counters, reviewer, and transaction cutoff in one count record before work begins.

Choose the scope from risk and operational value, not convenience alone. High-movement SKUs, items with prior discrepancies, compact high-value products, recently received inventory, and locations with frequent manual adjustments may justify more frequent review. Keep that prioritization descriptive unless the business has its own approved thresholds. Do not invent a universal count frequency or tolerance that has not been supported by the operation's observed error and cost data.

Prepare the floor and the system. Label locations, separate damaged and quality-control stock, clear unidentified units, finish or quarantine open receiving, and identify orders or transfers touching the count scope. Shopify notes that inventory counts can be coordinated across devices and locations, and that sales occurring between a count and submission can create a discrepancy. The cutoff plan must therefore explain how movements during the count are handled.

Issue count sheets or device sessions by location and zone. Record the counter, start time, completion time, SKU or barcode, inventory state, physical quantity, and exception note. Where the workflow permits, avoid showing the expected system quantity to the first counter. A blind count reduces the temptation to stop when the physical number happens to match the screen and makes the result more useful as independent evidence.

Use scanning to confirm product identity, but do not treat a successful scan as proof of quantity or condition. Count sealed cases only when packaging, case quantity, and integrity are verified. Open mixed or damaged cartons. Keep available, damaged, safety stock, quality control, and other unavailable states distinct because Shopify tracks movements among inventory states and adjustment history can show where units moved.

If orders, returns, transfers, or receipts continue, create a movement log for every affected SKU and time. Do not simply add today's sales to the physical count after the fact without timestamps and location evidence. The same unit can otherwise be included in a count, picked for an order, and then adjusted again. When the movement record cannot be reconciled, recount the affected SKU after the activity is stable.

Compare the physical count with the correct system state at the same cutoff. Investigate differences through orders, reservations, received transfers, supplier receipts, returns, cancellations, damage, theft or loss, product-location assignments, and app-created adjustments. Shopify's adjustment history identifies who or what made a change and records activities created by manual actions, orders, apps, and transfers. Use that evidence before changing the quantity.

Require a second count for discrepancies that exceed the operation's approved tolerance or indicate a product-identity problem. The second counter should inspect nearby bins, mislabeled cases, unprocessed returns, pick carts, packing stations, and receiving exceptions. Do not average two counts. Resolve which count reflects the stock at the documented cutoff, or record the item as unresolved and keep it out of an unsupported final adjustment.

When the cause is understood, Shopify supports setting inventory to an exact quantity or adjusting by a movement. It also supports reasons such as count, damaged, theft or loss, and received. Choose the action that matches what happened. Record the old quantity, physical quantity, final quantity, reason, supporting transaction, reviewer, and timestamp so the adjustment is an auditable conclusion rather than a silent overwrite.

After posting approved adjustments, confirm the count record, system quantity, and adjustment history agree. Shopify notes that its adjustment history preserves recent product-level changes and that broader inventory-adjustment reports can support analysis beyond the immediate product view. Retain the local count evidence according to the business's record policy so a later investigation can connect physical observations to system changes.

Group discrepancies by supported cause, SKU, zone, shift, location, app, and process step. Do not assign blame from correlation alone. A recurring variance near receiving can still originate in supplier quantities, product identity, transfer handling, or a system integration. Use the grouped evidence to choose a focused control such as barcode verification, location labeling, receiving holds, return processing, permissions, or movement scanning, then test that control in later counts.

Schedule the next count from observed risk and operational capacity. Increase review for unresolved or recurring variance and reduce unnecessary recounting of stable, low-risk areas only when the evidence supports it. Keep the count calendar separate from replenishment forecasts: a count establishes what is physically present at a cutoff, while a reorder decision also depends on demand, lead time, incoming inventory, and the desired stock policy.