The direct answer: distributor stock records and physical counts usually differ because they measure different things at different moments. A stock record is a running calculation built from documents, posting timestamps and unit definitions. A physical count is what is actually on the shelf at one moment. They rarely agree to the unit, and that is normal. The two numbers diverge when a document lands on one side of a cutoff and the count on the other, when one side counts cases and the other counts eaches, when returned or damaged goods sit in an area the system still treats as sellable, or when the count covers a different set of locations than the record does. The correct response is not to overwrite the number. Define the scope and cutoff, compare the evidence, trace the transactions, identify the cause, then correct and validate.
What a distributor stock record actually measures
Most records are maintained as a running balance: an opening quantity plus receipts, minus issues, plus or minus adjustments, held separately for each combination of location, product and unit. Because the balance is built from transactions, it can be correct in total and still wrong at the level you are comparing. A warehouse total may balance while a single pick face does not; a company-level total may look fine while one route van is short.
Inventory workflows depend on location, product identity, units, status and data freshness. Microsoft’s store-inventory documentation is a third-party example of implementation-specific limits and does not describe any particular distributor system. The practical lesson is the same: a stock figure only means something when you state which location, product, unit and status it covers, and how fresh its underlying transactions are.
Common causes of a difference between records and physical stock
The causes below are possibilities to test, not conclusions about any specific business. Most real variances come from two or three of them overlapping.
Transaction timing and cutoff
Goods received on Tuesday morning may be posted to the system on Tuesday afternoon. If the physical count was taken Tuesday morning, the goods are on the floor but not yet in the record. The same applies in reverse to deliveries: goods leave the warehouse before the delivery note is confirmed, so the record still shows them as on hand. The gap is a timing difference, not a loss, and it disappears once both sides are restated to the same moment.
Units of measure and pack conversion
One team counts outer cartons, another counts selling units, and the conversion factor in the product master is wrong or missing. A single case recorded as 24 eaches when the pack actually holds 12 produces a variance that grows with every transaction. Suggested master data includes products, units, warehouses and pricing validity dates; inconsistent identifiers or units are a recognised way to create discrepancies. Fixing the conversion factor is a master-data task, not an inventory adjustment.
Returns, damaged and expired goods
Returned goods often arrive into a returns or quarantine area and are recorded as received, but they may not yet be inspected, repacked or scrapped. Whether they belong in a sellable balance depends entirely on how the system handles stock status. Damaged and expired goods create the same problem: physically present, commercially unsellable, but counted in the same pile. A variance may be a status issue rather than a quantity issue.
Transfers, in-transit goods and location boundaries
Items moved between warehouses, from a warehouse to route vans, or to a customer on consignment are legitimately in two places for a short period. If the transfer out is posted at the origin but the transfer in is not yet confirmed at the destination, the record double-counts or under-counts depending on which side you query. Always check both ends of a transfer before treating the quantity as missing.
Counting scope and counting method
Variances often come from the count itself. The count may cover the main warehouse but exclude a mezzanine overflow, a returns cage, route vans or consignment stock at customer sites. Partially opened cases may be estimated rather than counted. Two counters may apply different rules to the same shelf, or a count sheet may be missing a page. Before questioning the system, confirm exactly which locations, statuses and product lines the count actually covered.
Identifiers, master data and manual entry
Duplicate product codes, a retired code still receiving goods, transposed digits on a manual receipt, or an adjustment posted without a reason code all create unexplained quantities. These causes leave a document trail, which is why tracing transactions matters more than re-counting the same shelf a third time.
Set the counting scope and cutoff before you compare anything
The comparison only becomes testable once it is defined. Write down the statement you are testing, for example: the record balance for product code X, in warehouse Y, sellable status only, expressed in eaches, as at 06:00 on Monday, compared with the physical count of those same locations, statuses and units at the same 06:00 cutoff.
Name the roles explicitly. An inventory coordinator prepares the record extract and the transaction list. A warehouse lead or an independent counter performs the physical count. A channel operations manager or distributor principal approves the scope, the cutoff and any resulting adjustment. If the same person builds the record, counts the items and approves the adjustment, the investigation loses its independence.
How to investigate a stock variance: an ordered process
- Restate the question as one specific comparison. Fix the product, location, unit, status and cutoff. Vague questions such as why the warehouse is short cannot be traced.
- Confirm the scope and cutoff are shared. Ask the counting team what they included and excluded, and ask the system owner what the record covers at that timestamp.
- Pull both evidence sets. Collect the movement history, goods receipt notes, delivery orders, return documents, transfer notes, count sheets and the adjustment log for the period.
- Reconcile in layers, not all at once. Start at total level, then break the variance down by location, then by product, then by unit, then by date. The layer where the gap appears narrows the cause.
- Trace the individual transactions behind the gap. Follow each document end to end, including its posting timestamp and the user who posted it.
- Classify the cause. Decide whether it is timing, unit conversion, status handling, counting scope, or a data-entry or process error. Different causes need different fixes.
- Correct with evidence. Post the adjustment to the correct location, status and period, with a reason code and a reference to the document that supports it.
- Fix the upstream step and check for repeats. Ask whether the same cause affects other products, warehouses or routes, and close the process gap that allowed it.
Diagnostic table: match the symptom to the evidence
| Symptom in the record | Evidence to pull | Cause to test first |
|---|---|---|
| Record shows stock in a location the count did not cover | Count sheet, location list, scope memo | Counting scope boundary |
| Quantity appears after the count was taken | Goods receipt notes, posting timestamps | Cutoff timing |
| Record in cases, count in eaches | Product master, pack conversion, order lines | Units of measure |
| Items sit in a returns or damage area | Return documents, inspection and scrap records | Status handling |
| Transfer out recorded, transfer in missing | Transfer notes at both locations | In-transit goods |
| Small unexplained balances across many SKUs | Adjustment log, manual entry history | Data entry and process control |
Why changing the stock number without finding the cause makes things worse
Overwriting the balance makes today’s record agree with today’s count, and nothing else. The cause remains in the process, so the same variance reappears next cycle — often larger. You also lose the audit trail that would have explained the gap, which makes it impossible to tell a timing error from a genuine loss. A repeated pattern of unexplained write-offs can quietly mask shrinkage, distort sell-in and sell-out analysis, and make returns and damage costs look smaller or larger than they are. Adjustments are a legitimate part of inventory control, but they should be the last step in an investigation that already has a named cause and a supporting document.
Where a distributor management system fits
Airpalm’s public site describes mobile visits, route planning, store audits, sales orders, inventory and promotion management (airpalm.com, checked 2026-10-09). For a distributor evaluating a distributor management system (DMS), the investigation above translates into specific demonstration questions: which locations and stock statuses the inventory view covers, which unit of measure is stored and displayed, how returns, transfers and damaged goods are represented, what timestamp a figure carries, and who may post adjustments and under which reason codes. An educational order workflow — capture, validation, stock review, fulfillment status, delivery review and reconciliation — is a useful way to structure those questions, but confirm each answer in a demonstration and a scope document rather than assuming it. Availability, setup effort and commercial terms are confirmed separately.
Useful next reading: order management in a distributor management system, the distributor management system topic index, and Airpalm.
Investigation checklist
- One written comparison statement with product, location, unit, status and cutoff.
- Count scope confirmed in writing, including exclusions.
- Both evidence sets dated and extracted from the same period.
- Variance broken down by location, product, unit and date.
- Each unexplained quantity traced to a specific document.
- Cause classified before any adjustment is posted.
- Adjustment approved, reason-coded and referenced.
- Upstream fix agreed with an owner and a review date.
Frequently asked questions (FAQ)
Should we adjust the system balance first and investigate later?
No. Adjusting first destroys the transaction trail you need and usually lets the cause repeat. Treat the adjustment as the last step: identify the cause, gather the supporting document, assign a reason code, then post the correction to the right location, status and period. If the cause cannot be identified, record the variance as an open investigation item rather than a silent write-off.
How often should a distributor count stock?
There is no single correct frequency. Common industry practice is cycle counting, where counting effort is weighted towards fast-moving, high-value or high-exposure items, with a full count at a fixed interval. Choose frequency by SKU velocity, unit value, number of handling points such as vans and returns areas, and how reliable the record has proved in the past. Whatever the schedule, use the same scope and cutoff rules each time so results are comparable.
Why do returns and damaged goods cause so many stock differences?
They add a status dimension to a quantity question. Returned goods are physically present but may not be sellable until inspected, repacked or credited, and damaged or expired items sit in the same building without belonging in a sellable balance. If the record, the count and the commercial report all treat returns differently, the variance is about status rather than about missing units. Define which statuses are in scope for each comparison.
Can a distributor management system remove stock differences?
No software removes the need for a defined cutoff, consistent units of measure and clear status definitions. What a system can do, where those capabilities are in scope, is make transaction trails, posting timestamps and adjustment history easier to retrieve when a variance appears. Confirm the specific inventory coverage, unit handling, status logic and adjustment controls in a demonstration and a written scope document before relying on them.
Put this guide into practice
This general-purpose worksheet is a starting point. Adapt its fields, responsibilities and rules to your business process.
