Sell-in vs sell-out in FMCG: how to reconcile the numbers

A retailer's week 14 file reports 86 units sold to consumers. Your ERP reports 120 units shipped to that retailer in the same period. The 34-unit difference is not automatically an error: 28 units may still sit in the retailer's stock and 6 may come back as returns. Sell-in and sell-out are different business events, and comparing their totals directly hides the stock and timing between them.

This guide defines both measures, shows why they diverge and gives a stock bridge you can reuse to reconcile them. It ends with the practical steps and the limits of the comparison.

What sell-in and sell-out actually measure

Sell-in is the supply event: orders, shipments, deliveries and invoices that move product from you to a retailer or distributor. It is recorded on your calendar, at your granularity, and it closes when the goods leave your control. Sell-out is the demand event: units that move from the retailer or distributor to consumers at the point of sale. It is recorded on the retail calendar, often weekly, and it is what the trade sees as the market's real consumption.

Sell-in · supplyYou ship to trade

Channel stockInside the retailer network

Sell-out · demandConsumers buy at the till

The units between the second and third node are neither a loss nor an error. They are the working inventory the channel needs to sell.

The two files may both be called sales, but they answer different questions. Sell-in answers "what did we ship and invoice this period". Sell-out answers "what did consumers actually buy this period". A retailer's sell-out is your demand signal; your own shipment file is a supply signal that depends on their ordering and your stocking decisions.

Why the two numbers rarely match

If sell-in and sell-out were copies of the same event they would match. They are not. Product moves through order, shipment, receipt, shelf and till across different calendars, and returns move back the other way. Each step sits in its own file, with its own identifiers and dates.

Sell-in · supply viewRecorded as you ship to trade

Order confirmed Goods shipped Invoice raised

Records product leaving your control on your financial calendar.

Sell-out · demand viewRecorded as consumers buy

Product on shelf Consumer purchase POS recorded

Records consumer demand on the retail calendar, often per week.

The gap between the two panels is timing, inventory and returns. It is the substance of the reconciliation, not a defect to remove. Comparing the two totals without that middle explains nothing and produces false alarms.

The stock bridge connects both numbers

The two measures meet inside a stock identity: opening stock plus sell-in, minus sell-out, minus returns and damage, must equal closing stock. Rebuild that identity and every unit has a place.

If the identity balances, the difference between sell-in and sell-out is explained by stock and returns. If it does not, the residual is an exception to classify, not a number to force to zero.

The sign convention above is for this bridge, not a universal accounting presentation. Define it once, apply it at the agreed grain and retain the evidence behind each term.

Comparing sell-in and sell-out without the bridge treats every difference as if it should be zero. That is why simple variance reports create false alarms, manual corrections and a process nobody can reproduce.

A worked sell-in / sell-out example

Assume one beverage SKU, one retailer and one retail week. The retailer opened with 40 units, received 120 units of sell-in and reported 86 units of sell-out. Six units were returned or written off as damage.

Recon dossierRetailer ES-042

Sell-in120units shipped in W14

Sell-out86units sold to consumers

SKU map · ES-4582 → EAN 8412345678901

Opening stock40 unitsReconciled

Sell-in · deliveries+120 unitsReconciled

Sell-out · POS−86 unitsReconciled

Returns and damage−6 unitsOpen · evidence

Closing stock68 = 68 unitsReconciled

The 34-unit gap between the two headline totals is fully explained: 28 units sit in closing stock and 6 are pending return evidence. The only open item is evidence, not an unexplained variance. Without the bridge, the same 34 units look like a forecast error or a billing problem that needs a manual adjustment.

Why timing and returns open a gap

Even a clean bridge moves items across periods. A delivery arriving after a week's cutoff is sell-in in one week and may be sold in another. A return recorded in a POS file can appear in a later file than the original sale.

Sell-in at the boundary+6 unitsDelivered after the W14 cutoff and recorded as sell-in in W15.Timing, not a loss

Sell-out returns−6 unitsRecorded in the W15 file and matched to the W14 sale.Closes with evidence

Agree in advance where each movement belongs: which calendar, which cutoff and which evidence closes it. Then a timing exception should clear in the next cycle instead of being carried forward and "corrected".

How to reconcile the numbers

Use the bridge as the spine of the process. Each stage below prepares one input so the identity can be rebuilt and the residual classified.

1

Register the sources

Capture sell-in, sell-out and stock figures with their calendars and cutoff rules.

2

Map the identifiers

Connect SKU, EAN, GTIN, store and customer codes across the files.

3

Rebuild the bridge

Apply the stock identity at the agreed grain and period.

4

Classify the residual

Split what remains into timing, returns, mapping and data exceptions.

1. Register the inputs. Record the retailer, period, file dates, expected columns and whether each file is original or corrected.
2. Map product and location identifiers. Connect retailer codes to EAN or GTIN and internal SKU, and stores to customers.
3. Align the calendar. Apply the retail week and the financial period with one agreed cutoff rule.
4. Standardize units. Convert cases, packs and eaches to one unit of measure with effective dates.
5. Set the stock grain. Decide whether the bridge runs at product-store-week or product-customer-month.
6. Rebuild the identity. Opening stock plus sell-in minus sell-out minus returns and damage equals closing stock.
7. Compare closing stock. Match the computed figure against counted or reported stock.
8. Calculate the residual. Keep sell-in, sell-out, stock change, returns and residual as separate fields.
9. Classify the residual. Use controlled causes: timing, return, mapping, duplicate, missing data or unexplained business difference.
10. Close the cycle. Save versions, evidence, owner and status, and carry unresolved items into the next period.

Limits and common mistakes

The bridge explains most differences, but not every comparison is meaningful. The stock figure must come from a reliable source and the calendar must be comparable, or the bridge produces a confident-looking wrong answer.

• Treating sell-in as consumer demand. Demand is sell-out, not shipments.
• Forcing the totals to match. Adjusting files to remove a gap hides the real stock position.
• Comparing gross sell-in with net-of-returns sell-out. Define the sign and returns treatment before comparing.
• Closing timing differences permanently. A timing exception should clear in a later period.
• Rebuilding mappings each cycle. Without versions, last month's result cannot be reproduced.
• Reporting a balanced bridge without evidence. A zero residual still needs the proof behind it.

Practical takeaway

Sell-in and sell-out measure different events. Reconcile them through a stock bridge that explains stock, timing and returns, then classify the residual by cause with evidence and an owner. That turns a recurring variance into a controlled, explainable process.

If your team reconciles retailer and distributor data every month, Marksyte's data reconciliation and controls service can review the process. Related work may include mapping product, customer and store identifiers or standardizing partner files and data-quality rules.

Frequently asked questions