In the beverage alcohol industry, the moment a case leaves a distributor’s warehouse is the moment a supplier’s brand strategy either works or it doesn’t. Everything before that point is forecasting. Everything after it is measurement.
The problem is that the supplier who owns the brand does not own the transaction. Understanding depletion reporting — what it is, where the data comes from, and why it so often arrives late, incomplete, or unusable — is the foundation of every credible market decision a supplier makes.
What Is Depletion Reporting?
Depletion reporting is the measurement and analysis of product sold and delivered by a distributor to licensed retail accounts. It is the point at which inventory is “depleted” from the wholesale tier and enters the retail tier.
Because the U.S. operates under a three-tier system, a supplier’s product changes hands — and changes owners — at least twice before a consumer buys it. Each handoff generates a different data set, and conflating them is the most common analytical error in the category.
Depletions vs. Shipments: The Critical Distinction
| SHIPMENTS | DEPLETIONS | |
|---|---|---|
| Movement measured | Supplier → Distributor | Distributor → Retailer |
| Also called | Sales to wholesaler, “shipments out” | Sales to retail, wholesaler depletions |
| Who owns the transaction record | The supplier | The distributor |
| What it actually tells you | How much product you sold into the distributor tier | How much product is reaching retail |
| Account-level visibility | None — the transaction ends at the distributor’s warehouse | By account, chain, premise type, and class of trade |
| Primary use | Revenue recognition, production planning | Demand signal, market share, retail execution |
- Shipment data is a supply-side metric. It reflects distributor purchasing behavior — which is driven by inventory strategy, program timing, and buy-in incentives as much as by consumer demand. A strong shipment month may simply mean a distributor loaded up ahead of a price increase.
- Depletion data is a demand-side metric. It reflects what retailers are actually buying, in which accounts, at what velocity.
The gap between the two is inventory sitting in a distributor warehouse. Suppliers who track only shipments are measuring their own invoices and calling it market performance.
The Depletion Data Path
The defining characteristic of this system is that product and data travel in opposite directions.
Figure 1. The depletion data path across the three-tier system.
The Dual Nature of the Path
Moving product forward is a solved problem. The industry has spent a century optimizing it: warehouse management, route optimization, delivery scheduling, temperature control. Physical logistics has an owner at every step, and that owner has a direct financial incentive to get it right.
Moving data backward has no such natural owner.
The distributor generates the depletion record as a byproduct of doing business — invoicing an account, closing a route stop, adjusting inventory. That record exists to run the distributor’s operation, not to inform the supplier’s brand strategy. Passing it upstream is, from the distributor’s perspective, additional work performed on behalf of a third party.
This creates the structural asymmetry at the heart of the category:
- The supplier has the most at stake in understanding depletion performance — it owns the brand, funds the marketing, and carries the P&L.
- The supplier has the least direct access to the data that would explain it. It sits two tiers away from the transaction.
- The distributor holds the data but has hundreds of supplier relationships, each with different reporting expectations, formats, and cadences.
Depletion visibility, in other words, is not a reporting problem. It is a data infrastructure problem.
The Breakdown Point: Where Depletion Data Actually Originates
Depletion data is not created in a reporting tool. It is created in a distributor’s operational systems, as a byproduct of transactions:
- Route accounting systems — the invoice generated at the point of delivery, capturing account, item, quantity, price, and date. This is the canonical depletion record.
- Distributor ERP — pricing, deals and allowances, credits, and returns that adjust the gross transaction into a true net depletion.
- Warehouse management systems (WMS) — receipts, transfers, adjustments, samples, and physical inventory counts that establish on-hand position and reconcile what should have shipped against what did.
- Mobile sales applications — pre-sell orders, in-account surveys, and display and point-of-sale placements captured by the sales rep in the field.
Every one of those systems was purpose-built to run a distributorship. None was designed to produce supplier-facing analytics. That mismatch is where the flow breaks.
Why the Flow Breaks Down
Inconsistent formats. A supplier working with 200 distributors may receive 200 structurally different files. Item identifiers differ. “Cases” may mean physical cases, standard cases, or nine-liter equivalents. Account names are entered by hand and arrive as three or four spellings of a single outlet. Before any analysis can begin, an analyst has to reconcile the vocabulary.
Delayed reporting. Monthly depletion files delivered a week or two after close mean a supplier is reacting to a market that has already moved on. A soft period in a key chain surfaces six weeks late — long after the reset window closed and the display space went to a competitor.
Misaligned reporting periods. A supplier comparing its own calendar month against a distributor’s depletion period is comparing two different spans of time. Because depletion periods vary in length, the mismatch surfaces as growth or decline that never happened — a five-week period looks like a strong month, a three-week period looks like a collapse. This is one of the most common sources of unexplained discrepancy in depletion reporting, and among the hardest to spot, because nothing in the file looks wrong. The numbers reconcile internally. They simply are not answering the same question.
Siloed visibility. Because each distributor reports independently, suppliers get a collection of local views rather than a national picture. Comparing performance across markets requires normalizing everything first, which means the comparison is only as good as the analyst’s spreadsheet — and it breaks the moment someone changes a tab.
Aggregation loss. Summary-level reporting is the most expensive shortcut in the category. A state-level total showing 4% growth hides the fact that a brand grew 30% in chains and declined 12% in independents. The insight that would change a supplier’s behavior is precisely the detail that summarization destroys.
Manual reconciliation as a full-time job. The compounding cost is human. Supplier insights teams routinely spend the majority of a reporting cycle rebuilding the same file, in the same way, to answer the same questions — time that should be spent on analysis, spent instead on data janitorial work.
The result: suppliers make brand-level investment decisions on data that is stale, partial, and unverifiable.
The iDIG Solution: How VIP Closes the Loop
VIP’s position in this system is structural rather than incidental. Where a distributor runs its business on VIP’s route accounting, ERP, and warehouse systems, depletion data does not have to be requested, exported, or reconstructed. It is captured natively, at the moment of the transaction, in the system that created it.
The iDIG analytics platform surfaces that data to suppliers. Here is how it works:
1. Native Capture at the Source
Depletion records are generated inside the distributor’s operational system as transactions occur — invoices closed on the route, inventory movements posted in the warehouse, orders written in the field. There is no separate reporting step for the distributor to perform, and therefore no step to skip, delay, or format incorrectly. The data is a product of the operation, not an additional task layered on top of it.
2. Continuous and Overnight Aggregation
Transaction data flows from distributor systems into VIP’s data environment on an ongoing cycle. Sales post as they are registered, with a full data build running overnight so suppliers open to a refreshed picture each morning. Inventory positions update continuously, and open-order visibility can be configured to refresh on a near-real-time interval. The reporting cadence shifts from monthly retrospective to daily operational.
3. Standardization and Cleansing
This is the step that makes cross-market analysis possible, and the one that is effectively impossible to replicate downstream:
- Item standardization. Supplier-maintained item catalog data provides a single authoritative definition of each product — brand, package, size, and equivalency factors — so a case means the same thing in every market.
- Retail outlet cleansing. Account records arriving from hundreds of distributor systems are matched, de-duplicated, and resolved to a cleansed outlet master, so the several spellings of one store collapse into a single outlet correctly attributed to its chain, premise type, and geography.
- Hierarchy alignment. Distributor, territory, chain, and geographic hierarchies are mapped consistently, so the same question returns the same answer regardless of which market it is asked about.
- Calendar and depletion period alignment. Depletion data is collected on both bases — the calendar and the distributor’s own depletion period — rather than being converted after the fact. Because both are captured at the source, a supplier can state a figure on either basis and have it reconcile, instead of approximating one from the other.
4. Visual Surfacing in iDIG
Suppliers access their depletion data through iDIG directly — not through a file a distributor remembered to send. The platform provides:
- Saved report structures that refresh automatically. A report is defined once — measures, dimensions, period basis, filters — and then updates as new data arrives. Suppliers do not rebuild a report each cycle to see the current picture: the structure persists and the numbers move.
- Reporting on either period basis. Suppliers choose whether to run a report on calendar periods or depletion periods, so internal financial reporting and distributor-facing performance conversations can each use the basis appropriate to the audience — from the same underlying data, with no manual reconciliation between the two.
- Drillable reporting from national totals down to the individual account and item, with no loss of granularity at any level.
- Configurable report templates, including historical comparison views for period-over-period and year-over-year analysis.
- Multi-measure analysis — volume, revenue, distribution, and inventory examined together rather than in separate files.
- Standard exports and scheduled delivery for teams feeding downstream models or scorecards.
5. Governance and Restatement
Data quality is treated as an ongoing operational discipline. Corrections and restatements flow through defined processes so historical periods stay accurate as adjustments, credits, and reclassifications occur. Suppliers can reference a consistent number across reporting cycles — which is what makes the data usable in a business review rather than merely interesting.
Converting Visibility into Action
Visibility is not the deliverable. A dashboard nobody acts on is an expensive screensaver. The value of daily, account-level, standardized depletion data is that it shortens the distance between noticing something and doing something about it.
Optimizing Retail Execution and Display Compliance
A supplier funds a national floor display program. Depletion data at the account level shows which outlets actually moved incremental volume during the display window and which show no lift at all — the strongest available signal that the display never went up.
The action: Rather than escalating a nonspecific compliance concern to the distributor, the supplier arrives at the market review with a named account list and a volume comparison, and redirects the next cycle’s display spend toward outlets with demonstrated lift.
Preventing Out-of-Stocks with Days-on-Hand Tracking
Combining distributor inventory position with recent depletion velocity yields days on hand at the item and warehouse level. When velocity accelerates — a seasonal swing, a competitor’s supply gap, a media hit — days on hand contracts before anyone runs out.
The action: The supplier flags the shortfall to the distributor while there is still time to place a replenishment order, protecting shelf presence during the exact window when demand is highest. An out-of-stock during a peak period costs both the immediate volume and, frequently, the facing.
Measuring True Promotional ROI
Promotional analysis performed on shipment data measures whether a distributor bought in. Performed on depletion data, at the account level, it measures whether the promotion sold through — and what happened afterward.
The action: The supplier separates genuine incremental volume from pull-forward, identifies which account segments respond to which mechanics, and reallocates trade spend accordingly. Programs that reliably move volume in independents but not in chains get funded where they work instead of nationally by default.
Reallocating Distribution Effort
Depletion data reveals distribution gaps with precision: accounts carrying three SKUs of a portfolio that should carry six, and comparable accounts nearby proving the sixth SKU sells.
The action: The supplier builds a targeted, evidence-backed call list for the distributor’s sales team rather than a generic push for “more distribution.”
The Bottom Line
Depletion reporting is only as valuable as the infrastructure beneath it. Data that arrives late, in inconsistent formats, summarized past the point of usefulness, cannot support the decisions suppliers most need to make.
VIP’s approach starts one layer lower than reporting: capturing depletion data natively in the systems where distributors already run their business, standardizing it against authoritative item and outlet masters, and surfacing it to suppliers in iDIG at the granularity where action becomes possible.
That’s the difference between knowing what happened last month and knowing what to do this week.
