Systems & operations

Why stock records disagree across sites, and how to fix them

Bring item definitions, transfers, counts and adjustments into one controlled process so stock records reflect what happens at each location.

Multi-site stock records depend on consistent item definitions and the recording of physical movements.

Stock records drift when physical movements and system updates separate. A transfer recorded only by the sending site, a box counted as individual units or a return left outside the normal process can all create a different answer at month-end.

Before selecting a new inventory system, identify which movements are missing or inconsistent. Better software needs a process that people can follow at the point where stock changes hands.

Agree the item and location records

Use consistent item identifiers, descriptions and units of measure. Keep sites, bins, yards and vehicles distinct where they hold stock. Name who approves new items and location codes.

Record conversion rules explicitly. A box of ten and one individual part are related quantities, not interchangeable entries. Review how the same item is represented in purchasing, stores and finance.

For assets, keep the asset identifier separate from the spare-parts inventory. Location, service status and ownership may belong to different systems, but each fact needs a defined authority and a reliable exchange.

Record transfers at both ends

A transfer needs a dispatch and a receipt, with a visible in-transit state between them. Resolve short receipts, damage and returns through defined adjustments rather than informal changes to the quantity.

Map movements beyond the main warehouse: van restocks, workshop issues, hire returns, warranty replacements and emergency parts. A perpetual record is only useful to the extent those events reach it.

Scanning can reduce entry effort and support consistent identifiers. It does not establish that the correct item, location or movement type was selected. Test the complete receiving and issuing process, including poor connectivity where relevant.

A field-service workflow links job coordination, technician activity and the shared record. Where parts are used, the stock movement also needs recording.

Investigate count differences before adjusting

Use regular counts to find errors closer to when they occur. Choose frequency from movement, value, criticality and the relevant obligations. Routine counting does not replace any statutory stocktake requirement that applies to the business.

For a sample count, agree the time and movement controls. Where practical, count without showing the expected quantity. Record the unit of measure and investigate differences before an authorised person approves the adjustment.

Microsoft's cycle-counting documentation illustrates scheduled counting and review of differences within its warehouse product. The operating principle is to make discrepancies visible and resolve their causes.

Measure accuracy consistently

One useful measure is the percentage of sampled item-location lines that match the system under an agreed rule. If 41 of 50 sampled lines match, sample record accuracy is 82%. That describes the sample; it is not proof that the whole inventory is 82% accurate.

Decide in advance whether a match requires an exact quantity or a justified tolerance. Keep the sampling method consistent and report important differences in value or criticality separately.

Avoid adding quantity variances across unrelated units. A difference of five filters cannot be meaningfully combined with five litres as though they were ten comparable units. Analyse variance within consistent units, by item or through an agreed valuation method.

Keep the count worksheet simple: item, location, unit, count time, recorded quantity, counted quantity, difference, likely cause and authorised adjustment. Include the movement cutoff or timing method so a later reviewer can interpret a difference correctly.

Review causes before making another software purchase. Repeated short receipts may require a better receiving step; repeated unit differences may require master-data correction. A clean adjustment total after stocktake does not establish that the cause has been removed.

Useful reviewWhat it can reveal
Transfers left in transitDispatch or receipt steps that are not being completed
Adjustments by cause and locationRepeated process or definition problems
Count accuracy over comparable samplesWhether records are becoming more dependable
Parts used against work ordersGaps between maintenance activity and inventory
Finance-to-inventory reconciliationDifferences requiring a defined financial explanation
Twin's Suntory PepsiCo programme connected enterprise and operational sources into governed reporting. It was a data hub programme, not a dedicated inventory implementation.

Connect systems after the ownership decisions

An inventory system, maintenance system and finance platform can perform different roles without producing competing records. Define ownership and reconciliation before connecting them.

The Suntory PepsiCo data hub story is relevant to combining governed sources for reporting. For an inventory project, require direct evidence that the proposed software handles your movements, units, sites and exception process.

Discuss your project with Twin Global