A distributor reports 24,000 units sold to the channel in March. Retailer files show only 17,500 units sold to shoppers. The gap is often treated as a data problem, or worse, as evidence that one commercial team is reporting the wrong number. Neither conclusion follows from the difference alone. The distributor may have built inventory, the shipment and checkout may belong to different periods, returns may be posted later, or the two files may cover different products and accounts.
Sell-in and sell-out are connected, but they are not interchangeable. A distributor sale records a movement into a channel. Retailer sell-out records a later movement out of that channel, often through a POS transaction. The difference is useful only when the events, products, units, locations and periods are aligned.
Sell-in, sell-out and channel stock
Sell-in usually refers to products shipped or sold from a manufacturer to a distributor or retailer. Sell-out usually refers to products sold onward by the distributor or retailer, often to the next buyer or consumer. The exact terminology varies by company, so the source definition should be recorded with the data.
The bridge between the two flows is channel inventory. In a simplified period balance:
Opening channel stock + sell-in − sell-out + returns and adjustments
This is not a universal accounting formula. It is a diagnostic model. It assumes the values use the same product, pack, location, unit and period definitions. If they do not, the residual contains definition errors as well as physical stock movement.
| Event | Typical source | What it records |
|---|---|---|
| Shipment to distributor | ERP or order system | Product leaving the manufacturer or entering distributor ownership |
| Receipt by distributor | Distributor inventory | Product accepted into the distributor’s stock |
| Shipment to retailer | Distributor sales file | Product moving from distributor to retailer or store network |
| Retailer receipt | Retailer inventory | Product received into retailer stock |
| POS sell-out | Retailer POS or sell-out feed | Product sold from retailer to shopper |
| Return or credit | ERP, distributor or retailer adjustments | Product or value reversed after the original event |
Two teams can each report a valid number while describing different rows in this flow. The reconciliation task is to identify which event each number represents and whether the period closes at the same point.
Why the numbers diverge
Inventory is building in the channel
If sell-in is greater than sell-out, the distributor or retailer may be holding more stock at the end of the period. This can happen ahead of a promotion, a seasonal peak, a new store opening or a planned service-level increase. The difference is not automatically excess inventory; it becomes a concern when stock remains high while sell-out slows or aged inventory increases.
The events fall in different periods
A shipment on 31 March may be recorded as March sell-in while the retailer receives it on 2 April and sells it during April. A monthly comparison then creates a temporary gap that may close when the periods are bridged. Retail calendars, late files and different cut-off times make this more common across countries and distributors.
Returns and credit notes arrive later
A retailer may return damaged or unsold product after the original shipment. The physical return, distributor receipt and financial credit can have different dates. If one report reverses sales immediately and another waits for the credit note, the same product appears at different points in the two flows.
Promotions shift shipments ahead of consumption
A distributor may receive or ship additional stock before a promotion begins. Sell-out may remain flat until the promotion reaches stores and shoppers. Comparing the shipment spike with the same week’s POS sales confuses preparation for demand with realized demand.
Products and packs are not measured at the same level
Distributor data may report cases while POS reports individual units. A case of 12 can look like 12 times the sell-out if the conversion is missing. Similar problems occur with multipacks, displays, bundles, variable-weight products and free goods. Product identity also needs to be mapped consistently across the distributor and retailer accounts.
Coverage is different
The distributor file may include independent stores, wholesalers or exports that are absent from the retailer sell-out feed. Conversely, a retailer may report ecommerce and stores while the distributor file covers only physical replenishment. A coverage mismatch creates a gap even when every included record is correct.
Stock moves between locations or channels
Transfers between a distribution centre, stores, ecommerce fulfilment and third-party logistics sites can be reported as sales in one system and inventory movements in another. Without source and destination locations, the reconciliation can mistake a transfer for a new sale or a missing unit.
What the direction of the gap suggests
The direction of the difference helps choose the next check, but it does not prove the cause.
| Pattern | Possible explanation | First check |
|---|---|---|
| Sell-in above sell-out for one period | Inventory build, shipment before receipt or promotion loading | Opening and closing channel stock, receipt dates |
| Sell-in above sell-out for several periods | Slow movement, overstock, missing sell-out coverage or unit mismatch | Stock age, store coverage and pack factor |
| Sell-out above sell-in for one period | Opening stock is being consumed or sell-in arrived in an earlier period | Opening stock and prior-period shipments |
| Sell-out above sell-in for several periods | Missing distributor records, alternate supply route or incomplete sell-in scope | All suppliers, channels and source accounts |
| Gap appears after a product launch | New SKU or retailer code not mapped across both sources | First-seen date, product mapping and pack level |
| Gap changes after a file refresh | Returns, late files, restatements or revised mappings | File version, correction log and effective dates |
A persistent gap should be quantified rather than explained with a single story. Separate the portion attributable to opening stock, timing, returns, product definitions, coverage and unresolved residual.
How to reconcile the two data sources
Start at the lowest useful grain: product, pack, distributor, retailer or location and period. Aggregate only after the records can be compared at that grain.
- Define the event. Label each source as shipment, receipt, distributor sale, retailer receipt, POS sell-out, return or adjustment.
- Align product and pack. Map source codes to a canonical product and convert cases, multipacks, litres or kilograms into the agreed unit.
- Align accounts and locations. Identify distributor, retailer, banner, store, warehouse and channel. Keep transfers separate from external sales.
- Bridge the calendar. Retain source dates, retail periods, receipt dates and posting dates. Define the cut-off used for the comparison.
- Bring in stock balances. Use opening and closing inventory where available to distinguish demand from channel accumulation.
- Reconcile returns and adjustments. Link credits, damages, cancellations and reversals to the original product and event.
- Measure coverage. Quantify the distributors, retailers, stores, products and periods missing from either side.
- Classify the residual. Assign an owner and status to the difference that remains after documented movements.
| Field | Example | Why it matters |
|---|---|---|
| Canonical product | MX-2041 | Prevents source-code differences from becoming false gaps |
| Pack and conversion | Case / 12 units | Aligns distributor and POS measures |
| Distributor and retailer | Distributor A / Retailer B | Defines the channel relationship |
| Source event | Receipt, shipment or POS sale | Separates different movements |
| Source period and date | March / 31 March | Shows timing and cut-off differences |
| Opening and closing stock | 4,000 / 10,500 units | Tests whether the gap is inventory accumulation |
| Returns and adjustments | -450 units | Explains reversals and late corrections |
| Coverage status | Retailer POS 92% complete | Separates missing data from demand |
| Residual and owner | 1,100 units / Supply chain | Makes unresolved differences actionable |
A worked channel-flow example
A distributor begins April with 4,000 units, receives 20,000 units from the manufacturer, ships 18,000 units to retailers and records 450 units returned. Retailer sell-out totals 12,050 units. The numbers can be reconciled as follows:
4,000 opening + 20,000 received − 12,050 sell-out − 450 returns = 11,500 units
If the physical and system stock across the defined channel is close to 11,500 units, the difference is mainly channel inventory rather than a missing sale. If the stock balance is 9,800 units, the remaining 1,700 units need investigation: an unreported transfer, a pack conversion, a missing retailer feed, a duplicate shipment or another unresolved movement.
The example is deliberately simplified. A live reconciliation may need separate ownership, goods in transit, damaged stock, consignment inventory, intercompany transfers and distributor-to-retailer sales. The principle remains the same: connect flows to balances before interpreting the residual.
Controls before interpreting the gap
- Event control. Confirm that each metric is labeled as shipment, receipt, sell-in, sell-out, return or adjustment.
- Unit control. Check product, pack, unit of measure and conversion factors on both sides.
- Timing control. Compare source dates, receipt dates, retail periods and cut-off rules.
- Stock control. Reconcile opening and closing inventory, including goods in transit and consignment stock where relevant.
- Coverage control. Report the accounts, stores, channels, products and periods represented in each source.
- Mapping control. Keep unmapped and ambiguous product or location records visible instead of dropping them from the join.
- Revision control. Preserve file versions, corrections and mapping versions used for the bridge.
- Residual control. Track unresolved differences by owner, cause, value, age and next review date.
Do not use sell-in as a substitute for consumer demand when sell-out is available. Do not use sell-out as a complete channel inventory measure when stock balances and distributor movements are missing. Each source becomes more useful when its position in the flow is explicit.
Practical takeaway
Distributor sales and retailer sell-out do not need to match period by period. The meaningful question is whether the difference can be explained by channel stock, timing, returns, units, coverage and other documented movements. Build the bridge at product, account, location and period level before escalating a discrepancy as a data error.
Marksyte’s data reconciliation service helps connect distributor, retailer, POS, ERP and inventory records, quantify coverage and classify residual differences. For the broader reconciliation method, see how to reconcile sell-in and sell-out in FMCG. For the broader definition of secondary sales, see what secondary sales data means in FMCG. For international period and scope differences, see why retail sales data cannot be compared directly across countries.
Frequently asked questions
Why do distributor sales not match retailer sell-out?
They record different events and can occur in different periods. The difference may reflect inventory in the channel, shipment timing, returns, promotions, units, product mappings, missing accounts or incomplete coverage.
What is the difference between sell-in and sell-out?
Sell-in usually describes product shipped or sold from a manufacturer to a distributor or retailer. Sell-out usually describes product sold onward by a retailer or distributor, often at the point of sale. They should not be treated as the same event.
Does higher distributor sales than sell-out mean overstock?
Not automatically. It may indicate inventory building in the channel, a timing difference, a promotion shipment, different product units or a coverage mismatch. Check opening and closing channel stock before drawing that conclusion.
How do you reconcile sell-in and sell-out data?
Align product, pack, account, location and period; compare opening stock, shipments, returns, adjustments, closing stock and sell-out; then document the remaining difference by cause and data coverage.
What does it mean when sell-out is higher than sell-in?
The channel may be consuming stock received in an earlier period, or sell-in records may be incomplete. Check opening inventory, prior shipments, alternate supply routes and the coverage of the distributor file.
Should sell-in or sell-out be used to measure consumer demand?
Sell-out is generally closer to the consumer purchase event, while sell-in reflects movement into the channel. The appropriate measure depends on the question, but they should not be substituted without a documented bridge.
Sources and methodology
- FMCG Hire, Sell-in and sell-out glossary
- Sellforte, Should I use sell-in or sell-out data?
- UNSW BusinessThink, The challenges of using true demand through the supply chain
The sources support the distinction between sell-in, sell-out and consumer demand. The channel-flow model, worked example and reconciliation controls are Marksyte’s practical interpretation for distributor, retailer, POS, ERP and inventory data.