A stock movement report is being mistaken for customer demand

A falling quantity is a movement, not a sale

A stock report answers a narrow question: how many units the system says you hold. When the number falls, the summary rarely tells you why, and that gap is where the mistake begins. A dispatch to a customer, a transfer between locations, an internal withdrawal, a damaged-unit write-off and a count correction all reduce the on-hand figure, and a report that totals only the net change makes them indistinguishable.

The inventory system's own history is built to make the distinction. On Shopify, the adjustment history records the time, the activity, staff, app or channel attribution and the quantity change for each movement, and its reasons include counts, corrections, receipts, returns, damage, loss and donations, with both automatic and manual changes appearing. That is Shopify's vocabulary; another platform's movement log must be read on its own terms. The discipline is the same everywhere: the cause of a decrease is a recorded fact to look up, not something to infer from the direction of the number.

Classify each decrease against its own evidence

Work movement by movement for the period you intend to measure. A customer dispatch must tie to a real order or fulfillment record for the same product and quantity. A transfer must tie to a transfer record showing the units leaving one location; units that have left but not yet been received at the destination are in transit or awaiting receipt, not a loss, and they stay attributed to that transfer until receipt is confirmed. Only where the transfer record cannot account for the units — no in-transit state, no destination receipt, no return — does an unresolved shortage remain, and that shortage is investigated rather than declared a loss by default. An internal withdrawal needs the authorized record of who removed the units and for what purpose.

Damage, loss and correction decreases need the recorded reason and the attribution the history provides, because these are the movements most often mistaken for sales in a rushed total. Where the evidence for a decrease is missing, mark it unclassified and assign an owner to resolve it. The unclassified bucket is a finding in its own right; folding it into demand because the units are gone converts an evidence gap into a fabricated sale.

Rebuild the demand measure from the classified population

Only the customer-dispatch class belongs in a measure of what customers actually took. Sum those movements for the period, by product, and keep the exclusions visible beside the total: transfers moved units without changing what customers received, corrections fixed the record rather than the shelf, and losses removed units without a buyer. A measure assembled from the net decrease conflates all of these with sales.

Handle returns explicitly. A documented return adds units back and belongs to the original sale, so it must not be counted again as new demand, and the dispatch figure should state whether it is gross dispatches or dispatches net of recorded returns for the same period. Write the period, the locations covered and the classification basis on the measure itself, so the next person does not have to reverse-engineer which movements were allowed in.

Turn the classification into a bounded replenishment input

Present the result to whoever owns replenishment as three figures: classified customer dispatches for the period, each excluded category with its reason, and the unclassified remainder with its assigned owner. That presentation lets the replenishment owner weigh the evidence honestly instead of anchoring on a single net number, and it gives the business a clean answer when someone asks why the demand figure is smaller than total depletion.

Keep the measure's limits attached to it. A classified dispatch history describes what went out in a period you chose; it is an input to a judgment about reordering, not a forecast and not evidence of what future customers will want. If the underlying problem is that the storefront, checkout or order records cannot link movements to orders reliably, that is the point to raise in a scoped Prism consultation: describe the platform and the record that fails to connect, and confirm scope, responsibilities, fees and terms before any work.

Stock-movement classification worksheet

Apply one row to each decrease in the period you intend to measure, using your own inventory, order and transfer records. Enter only nonsensitive references and counts. A movement that fits no class stays unclassified with an owner; it never defaults to customer demand.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.