A sell-out report documents what consumers actually purchased at retail — not what you shipped to your distributor, and not what a retailer has on their shelves. It is the closest thing to a demand signal that exists in wholesale distribution, and for most brands, it is remarkably hard to get in a useful form.
Most wholesale partners do send something. A monthly Excel file. A quarterly summary. A portal you can log into if you remember the password. What they send technically qualifies as a sell-out report. Whether it is actually useful is a different question.
The definition: what a sell-out report actually is
A sell-out report captures sales from a retail location to the end consumer. This is distinct from:
- Sell-in data — what you shipped to the retailer or distributor (this comes from your own systems)
- Inventory data — what is currently on shelves or in a warehouse (often bundled with sell-out but a separate figure)
- Sell-through rate — a calculation derived from sell-out and sell-in, not the raw report itself
At the SKU level, a proper sell-out report tells you: how many units of each product sold, at which location, in which time period. That is the minimum viable data point for replenishment decisions.
What a useful sell-out report contains
A sell-out report that supports real decision-making should include:
- SKU or product reference — the specific variant sold, not a rolled-up product family
- Units sold — in the reporting period, not cumulative unless specified
- Store or location — which specific point of sale, not just the retailer name
- Time period — clearly defined start and end date, not ambiguous month labels
- Closing inventory — units remaining on shelf at period end (needed to calculate weeks of supply)
Revenue figures are useful but secondary. If a partner only sends revenue, you cannot accurately track unit velocity or spot a stockout at an individual location.
What partners typically send instead
In practice, most sell-out reports from wholesale partners have at least one of the following problems:
- SKU codes that do not match your internal product references
- Aggregated data across multiple stores with no location breakdown
- Irregular or inconsistent reporting periods (sometimes weekly, sometimes monthly, sometimes "when we get around to it")
- Missing closing inventory, making it impossible to calculate weeks of supply
- Revenue in local currency with no unit split
- Tester units mixed into sellable inventory without distinction
None of these is unusual. They are the norm. Retail partners optimize their reporting for their own internal purposes, not for their suppliers.
How to standardize sell-out data collection
Getting better sell-out data from partners is partly a commercial relationship question and partly a technical one. On the relationship side: when onboarding a new retail partner, define reporting requirements in the trading agreement — format, frequency, fields required, and what constitutes an acceptable SKU reference. Partners who have been operating for years without these requirements rarely volunteer to restructure their reporting, but most will comply with a specific request.
On the technical side: even when partners comply, they rarely use your SKU codes. Their systems use theirs. The practical solution is a mapping layer — a translation table that converts each partner's product references into your internal taxonomy before analysis. Doing this manually for 15 partners is a significant ongoing burden. Automating it with a tool that handles format variation natively removes that burden entirely.
The realistic goal is not a perfectly standardized report from every partner. It is a system on your end that normalizes whatever you receive into a format you can actually use.
Frequently asked questions
How often should I receive a sell-out report from retail partners?
Weekly is the standard for brands with meaningful volume at a retail location. Monthly is a minimum floor. Anything less frequent than monthly makes replenishment planning reactive rather than proactive — you are always one cycle behind.
What is the difference between a sell-out report and a POS report?
A POS (point of sale) report is a specific type of sell-out report drawn directly from a retailer's point-of-sale system. Not all sell-out reports are POS reports — some are manually compiled summaries. POS reports tend to be more granular and timely; manual summaries are often slower and less detailed.
What should I do if my retail partner refuses to share sell-out data?
Some retailers — particularly large department stores and certain specialty chains — treat their sell-out data as proprietary and do not share it with suppliers. In that case, your options are to use sell-in data as a proxy (imperfect), request aggregated category data, or rely on periodic sell-through discussions with the buyer. Where data sharing is contractually possible, negotiate it at onboarding — it is much harder to add later.
Can I automate sell-out report collection?
Yes. Tools that use layout-aware AI parsing can ingest sell-out reports in whatever format a partner sends — Excel, CSV, PDF summaries — and normalize the data automatically without manual mapping for each new format. This removes the main bottleneck in sell-out data workflows.
Stop chasing reports. Start using the data.
TaskifAI parses and normalizes sell-out reports from every retail partner, whatever format they use, and delivers one reconciled report by the 14th of every month.
Book a demo to see it with your own partners' data.