Count inventory during fulfilment: Reconcile timing and stock movements

An inventory count is meaningful only when the counted quantity and system quantity refer to the same item, place and point in time. If fulfilment continues during the count, removals, receipts and transfers need to be traceable within the counting window. Do not compare a shelf count taken at 10:00 with a later updated balance without accounting for movements in between.

Cover image: AI-generated symbolic inventory-counting scene with separate trays. Not an actual Shirtee facility or a prescribed warehouse process.

Define what is being counted first

“Count the winter stock” is too vague as an instruction. Identify the specific variant, counting area and unit. Are you counting individual units, sealed cartons or sets? Does the scope cover one shelf or the entire location, including the packing area? An item already picked from a shelf may still belong to the physical stock at the location.

For an original example, consider one variant of pre-produced merchandise at a storage location. The agreed count includes every unit physically present within the defined area, including items set aside for inspection. Goods that have already left that area are excluded. Reservations remain additional information; they do not automatically remove an item physically from the counting area.

This scope must match the meaning of the actual system fields. The Shopify documentation on inventory states, for example, distinguishes on-hand, available, committed and unavailable inventory. This is a platform example, not a statement about field names or automatic data transfer at Shirtee.Cloud.

Choose a controlled counting window

A small count is easiest to assess when goods temporarily stop moving within the defined area. Agree any pause with the people responsible; it is not something an external partner can automatically provide. If work must continue, assign responsibility for recording every relevant movement, including time, quantity and supporting reference.

The Shopify guide to planning a count describes, within its own workflows, the problem of sales occurring between counting and submission. This raises a useful question for your coordination: which point in time does the submitted number represent? Entering a count later must not silently turn it into a new physical observation.

Before starting, write down how ongoing picks, incoming cartons and transfers will be handled. A carton on the counting table needs an explicit classification. “Not yet put away” does not automatically mean “not physically present”, and “allocated to an order” does not automatically mean “already shipped”.

Bring the count and movements to the same point in time

The following example is entirely fictional. It concerns only the previously defined physical counting area, not the quantity available to sell in the shop.

The calculation is 118 − 3 + 5 = 120 units. If the system already includes both movements correctly since its snapshot, it shows 120 − 3 + 5 = 122 units at 10:10. The variance therefore remains −2 units. This result accounts for the movements rather than ignoring them.

Comparing the old count of 118 with the later system quantity of 122 would make the difference appear to be −4. Setting the later balance to 118 without checking would also disregard the intervening quantity changes. If a movement reference is missing, the calculation is incomplete. Resolve it before adjusting stock, or count again under controlled conditions.

Treat a variance as a question to investigate

Where practical, have an unclear discrepancy recounted independently. Check the scope first: wrong variant, another bin, units per pack or stock in the packing area? Then look for records from the relevant time window. A misclassified receipt and genuinely missing stock require different responses.

The historical Oracle documentation on cycle-count reports describes separate records for counts, recounts and adjustments awaiting approval. That separation is useful when designing your own record: preserve the first observation and add the recount and decision, instead of silently overwriting the original number. This is not a recommendation for that software or any particular configuration.

Hand over an adjustment with supporting evidence

A useful coordination note for the example would read: “Variant W-01, counting area A, count time 10:00, 118 units; system snapshot 120 units; two documented movements through 10:10; calculated variance −2; see record for recount and approval.” Add the actual responsible person and supporting references internally.

Then establish which system owns the stock balance and who transfers an approved adjustment. Simultaneous manual changes in the shop and warehouse could apply the same correction twice. The Shopify guide to quantity adjustments distinguishes setting an absolute quantity from making a relative change. Check what those operations mean in the specific tool being used.

Shirtee.Cloud publicly describes its warehousing and fulfilment offering. The scope, count date, movement records and approval route for your stored goods require separate agreement. This process promises neither a native counting feature nor a particular service scope. Its purpose is a traceable instruction: the same goods, the same area, the same point in time and an evidence-backed decision about the discrepancy.