A brand can know exactly what it invoiced to a distributor and still not know what reached retailers. It may also receive a distributor report labelled “sell-out” that describes shipments to stores, not consumer purchases at the till. The phrase secondary sales data is useful only when the event, seller, buyer and unit are defined.
In FMCG, secondary sales usually describe the distributor-to-retailer transaction. They are different from primary sales from the brand to the distributor and from retailer sell-out or tertiary sales to the final consumer.
The three sales events are not interchangeable
| Event | Typical seller | Typical buyer | Common source |
|---|---|---|---|
| Primary sales | Brand or manufacturer | Distributor or retailer | Brand ERP or invoice file |
| Secondary sales | Distributor | Retailer or outlet | DMS, distributor invoice or sales file |
| Retailer sell-out | Retailer | Consumer | POS, EPOS or retailer report |
The same product can appear in all three datasets with different identifiers, dates, units and commercial meanings. A case invoiced to a distributor is not the same event as twelve individual units sold by a store. A correct analysis keeps the events separate and connects them through product, location and time mappings.
What secondary sales data can show
Good secondary sales data can show which distributor supplied which outlet, what products moved, in what quantity, at what price or value, and during which period. At outlet level it can reveal distribution gaps, slow movement, assortment differences and the point at which stock leaves the distributor network.
It is particularly useful when primary sales look healthy but inventory remains in the channel. The comparison can show whether the issue is demand, coverage, timing or stock accumulation. That is an inference from the joined evidence, not something that a secondary sales row proves by itself.
What it cannot prove by itself
Secondary sales do not automatically prove consumer purchase, on-shelf availability or final consumption. A distributor invoice to a retailer may represent a replenishment order, a stock transfer, a promotional build or a return correction. The meaning depends on the source system and transaction type.
Do not use the label “sell-out” as a substitute for a data definition. Ask whether the row records an invoice, a delivery, an order, a POS transaction or a summarized estimate. Also ask whether quantities are units, cases or value, and whether returns and credits are included.
Where the data comes from
Secondary sales may arrive through distributor management systems, billing exports, field-sales applications, spreadsheets, EDI files or retailer portals. The format is less important than the event definition and traceability. Each source needs an owner, a delivery cadence, a stated grain and a way to identify corrected submissions.
When several distributors report the same market, their files will rarely share product codes, outlet codes, calendars or measures. A common dataset requires source-to-target mappings rather than a copy-and-paste consolidation.
The minimum data model
At a useful minimum, retain source, submission version, distributor, retailer or outlet, product code, canonical SKU, transaction type, transaction date, reporting period, quantity, unit of measure, value, currency and return or credit status. Keep source identifiers beside canonical identifiers so a total can be traced back to the original record.
The model should also record coverage. A distributor report with 80% of expected outlets is not equivalent to a complete report with lower sales. Coverage is part of the interpretation, not a footnote added after the total.
Controls before using secondary sales
- Define the event. State whether the source records sale, order, delivery, invoice, return or stock movement.
- Align the grain. Confirm what one row represents and do not compare outlet-level data with distributor totals without an aggregation rule.
- Map identity. Resolve distributor product codes and outlet codes to canonical references with effective dates.
- Normalize measures. Separate units, cases, packs, value and currency. Store conversion rules explicitly.
- Check coverage and duplicates. Report missing outlets, unmapped SKUs, duplicate transactions and late or corrected files.
These checks turn secondary sales from a persuasive spreadsheet into evidence that can support a channel decision. They also show where the evidence stops, which is often more valuable than a larger but less defined total.
Practical takeaway
Secondary sales are the distributor-to-retailer layer of FMCG data. They help explain what moved into the retail network, but they should not be presented as consumer sell-out unless the source actually records the point-of-sale event. Define the transaction, map the identities, preserve the source and measure coverage before drawing a conclusion.
Marksyte’s data mapping and integration service helps connect distributor, retailer and internal data while keeping transformations, assumptions and exceptions visible. For the broader bridge, see how to reconcile sell-in and sell-out in FMCG. For the operational multi-file workflow, see how to consolidate sell-out data from multiple distributors.
Frequently asked questions
What is secondary sales data in FMCG?
It usually records products sold or invoiced by a distributor to retailers or outlets. It sits between primary sales from brand to distributor and retailer sell-out to consumers.
Is secondary sales the same as sell-out?
Not always. Secondary sales usually describe distributor-to-retailer movement, while retailer sell-out usually describes retailer-to-consumer purchases. Some organizations use sell-out loosely, so the transaction definition must be checked.
What systems contain secondary sales data?
Common sources include distributor management systems, billing or invoice exports, field-sales applications, spreadsheets, EDI files and retailer portals.
Sources and methodology
Definitions vary across markets and organizations. This article uses secondary sales for distributor-to-retailer transactions and retailer sell-out for retailer-to-consumer transactions, while recognizing that source files may use the terms differently.