How to Track Warehouse Stock Movements and Investigate Variances

A delivery note lists 24 components, but the receiving clerk counts 22. By late afternoon, the system shows 18 available while the shelf holds only 16. Without consistent document references, locations, and checkers, the team cannot tell whether the discrepancy started at receipt, during a transfer, or when material was issued to production.

A stock movement record helps owners, operations managers, and warehouse teams answer practical questions: what changed, when, from where to where, in what quantity, and who checked it? The goal is not to build the largest possible spreadsheet. Each change should be traceable to a document and the person who carried out the process.

Separate the current balance from its history

A balance answers how much stock is recorded now. A movement history explains how that balance came to be. If you keep only the latest number, an incorrect adjustment can hide a short delivery or an issue that was never recorded.

Create a new row for each event instead of repeatedly overwriting one item’s balance. Assign each item a stable code and a clear unit such as pieces, metres, or kilograms. Do not mix cartons and individual units without a written conversion rule. Choose locations precisely enough for the work: “warehouse” is too broad when items move between rack A-03, a quarantine area, and the production floor.

A useful first set of fields includes date and time, movement reference, item code, description, transaction type, quantity, unit, source location, destination, supporting document, recorder, checker, and status. Transaction types might include receipt, issue, location transfer, return, or adjustment after a physical count. Either record separate inbound and outbound quantities or use signed quantities consistently.

Time	Reference	Item	Change	Location	Document	Status
Oct 31, 09:10	M-261031-01	Component K-14	+22 pcs	Receiving	DN-882	2 short, held
Oct 31, 10:05	M-261031-02	Component K-14	+20 pcs	A-03	QC-882	Checked
Oct 31, 14:20	M-261031-03	Component K-14	-4 pcs	Production	WO-119	Handed over

This is an illustrative example: the delivery note lists 24 pieces, but the first count finds 22. The team holds the two unaccounted pieces out of available stock, moves 20 pieces that pass inspection to the rack, and issues four against a work order. Do not alter the source document to make it match the count. Record the difference and its follow-up.

Record events when they happen

If staff enter movements only at the end of the week, they must reconstruct several days of activity from memory. Set a recording point in each physical process: record receipt after the goods are counted, issue when goods are handed over, and transfer when both locations confirm the movement.

For a receipt, compare the purchase order, delivery note, physical quantity, unit, condition, and temporary location. Record shortages, damage, or items awaiting inspection separately. Do not add goods to usable stock just because the supplier’s document says they were dispatched.

For an issue, require a reference that explains its purpose: an order, work order, department request, or shipping document. A note that says “issued 5” will not help an investigation next month. Record the recipient and the person handing the goods over. For high-value items, require a second check if company policy and staffing allow it.

A transfer between locations is neither a new receipt nor consumption. Create linked source and destination entries with the same reference. If 12 units move from rack A-03 to an assembly area, A-03 falls by 12 and assembly rises by 12. The company-wide quantity remains unchanged. Paired entries make it easier to find goods that left one location but were never confirmed at the other.

Keep usable, held, and damaged stock distinct

One balance can mislead when some items have not passed inspection or are already reserved for an order. Use operationally meaningful statuses such as available, quarantine/inspection, damaged, or allocated. Define who can change a status and which document supports that change.

For example, 80 units appear at the main location, but six are awaiting quality inspection and 15 are allocated to an approved job. Planning needs to see three different figures: 80 recorded physically, 59 available for a new allocation, and 21 unavailable for those reasons. This is an illustrative calculation, not data from a particular company. Set allocation rules and inventory valuation according to your process and applicable accounting policy.

The official Bekasi City Government SIMDARA site explains that under perpetual inventory recording, acquisitions and usage are recorded as movements occur, while a physical inventory count is still used to confirm the actual condition of goods. Its discussion concerns local government, not a universal rule for every business. The operational lesson is narrower: do not wait until period end to learn that a movement happened. Read SIMDARA’s explanation of inventory recording and apply accounting treatment relevant to your organisation.

Investigate variances without erasing the trail

When the physical count differs, hold the adjustment until basic checks are complete. Compare transactions since the last matching count, receipt and issue documents, location transfers, units of measure, returns, and damaged goods. Record who counted, when and where, the system quantity, physical quantity, and what the review established.

A practical sequence:

1. Pause movements at the location being counted, or record every movement while counting is underway.
2. Recount with a different person if possible, using the same item code and unit.
3. Compare the movement history and supporting documents, starting with the last transaction that matched.
4. Record a cause only when evidence supports it. If unknown, mark it unresolved and assign an owner.
5. Enter a separate adjustment after authorization; never replace the old movement row.

Example: the record shows 50 units, but the shelf count is 47. Do not immediately record three as “used.” Check for an issue without a reference, a transfer not yet received, damaged goods in another area, or a carton-to-piece conversion error. If evidence does not explain the difference, say so and assign further review. An adjustment is not a substitute for an investigation.

Schedule cycle counts according to operational risk and impact, rather than relying only on one large annual stocktake. Frequently moved items, or items whose absence could stop production, may warrant more frequent checks than slow-moving goods. Set criteria based on movement patterns and team capacity, then review whether recounts keep finding the same types of error.

Assign process owners and useful reporting

The operations manager defines item codes, units, locations, statuses, correction rights, and required documents. Receiving staff count and report discrepancies; stock custodians record storage; people taking goods provide a reference; and a checker reviews corrections where duties can be separated. In a small team, one person may hold several roles, but the review trail should still be recorded.

A useful daily report is more than a list of balances. Show receipts awaiting inspection, pending issue requests, transfers not yet acknowledged, items below an internally set threshold, and open variances. Include the age of each follow-up and its owner. Do not treat a zero in an empty report as proof that nothing is wrong; first confirm all locations and periods were included.

Common recurring mistakes include using item names without codes, overwriting balances, delaying entries until the weekend, using different units across departments, and assuming a dispatched item has already been received. Managers can also create too many statuses without definitions, so different people use “hold” differently. Write a short definition and an example document for each status.

If movement spreadsheets and issue approvals are becoming hard to trace across locations, you can review Sora’s business apps page as one option for designing a workflow. Its public retail app page describes stock changing with sales and incoming goods. That is a stated capability of the retail template, not a claim that every warehouse or company workflow is covered automatically. See the retail store app and Sora’s articles page to explore related guidance.

Start with one location today

Choose one location and one group of frequently moved items. Set their codes, units, statuses, and the documents required for receipts and issues. Give each movement a unique reference, then make an opening physical count witnessed by a second person if available. Keep discrepancies open until evidence explains them instead of forcing the numbers to match.

After one week, review which transactions were most often late or incomplete and improve one process point first. A dependable trail begins with a clear handoff and a consistent reference, not a more complicated spreadsheet.