What a case pack is
A case pack is the number of selling units packed inside one shipped case. If a 12-count case of cold brew goes to UNFI, the case pack is 12, the case is what moves on the truck, and the each is the single bottle a shopper buys at Sprouts. Three different units, one product, and most of the reporting pain in CPG starts with people quietly swapping one for another.
The selling unit, or the each, is the consumer-facing item with its own UPC. The case is the shipping unit the distributor and retailer order in. The pallet is how the warehouse moves cases in bulk. A brand doing $40M through KeHE talks in cases on the purchase order, eaches on the SPINS report, and pallets on the freight bill, and nobody flags the switch because everyone in the room assumes everyone else is using their unit.
Eaches, cases, and pallets
The cleanest way to keep these straight is to write the conversion factors down once and stop guessing. Here's a realistic line for a single sparkling-water SKU moving through a natural-channel distributor:
| Unit | Definition | Conversion |
|---|---|---|
| Each (unit) | One 16 oz can, one UPC | 1 each |
| Inner pack | Shrink-wrapped 6-pack | 6 eaches |
| Case pack | Shipped case | 24 eaches |
| Layer | One layer on the pallet | 8 cases / 192 ea |
| Pallet (TI x HI) | 8 cases per layer, 6 layers | 48 cases / 1,152 ea |
So one pallet is 48 cases, and 48 cases at a 24-count case pack is 1,152 eaches. Those numbers have to tie out in both directions, because the purchase order is written in cases and pallets, while the consumption data that comes back from SPINS or Circana is counted in eaches. If you can't move cleanly between the two, you cannot reconcile what you shipped against what sold.
Where mixing the unit of measure breaks the math
Here's the failure I have watched happen more times than I'd like. An analyst pulls shipment data in cases, pulls consumption data in eaches, and divides one by the other to get a sell-through rate. The case pack never enters the calculation, so the answer is off by exactly the case pack factor, and it looks plausible enough that nobody catches it for a quarter.
Run it on the sparkling-water SKU. Say the brand shipped 500 cases to a banner over four weeks and the retailer scanned 9,600 eaches at the register.
| Metric | Wrong (mixed units) | Right (normalized) |
|---|---|---|
| Shipped | 500 cases | 12,000 eaches |
| Sold (scanned) | 9,600 eaches | 9,600 eaches |
| Sell-through | 1,920% (nonsense) | 80% |
| Implied weeks of cover | near zero | healthy |
The wrong column divides 9,600 by 500 and reports a 1,920% sell-through, which should set off alarms but often just gets rounded into a slide. The right column converts the 500 cases to 12,000 eaches first (500 x 24), then divides to get a sane 80% sell-through. The only difference between the two is whether someone remembered the case pack. Velocity math has the same trap: units per store per week means nothing if you don't know whether those units are cases or eaches, and a 24x error there will either hide a stockout or invent one.
The case pack also drives how much inventory a store is actually holding. Convert cases to eaches before you compute days of supply, or you'll either think a store is drowning in product or about to run dry, and act on the wrong one. The same discipline runs through all of CPG distribution: the unit of measure has to be explicit at every hop from brand to shelf.
Why case pack matters to a brand-side analyst
The case pack reads like a logistics footnote, but it is the conversion factor that makes shipment data and consumption data comparable, and those two data sets are how a brand knows whether its trade spend, its forecast, and its distribution are working. Get the case pack wrong and every downstream number inherits the error: velocity, sell-through, weeks of cover, forecast accuracy, and the deduction reconciliation that depends on matching shipped cases to sold eaches.
It also shifts on you. A retailer may request a smaller pack to fit a shelf set, or a brand may move from a 12-count to a 24-count to cut freight per unit. The moment that changes, every historical comparison that assumed the old case pack quietly breaks, and the velocity trend looks like a cliff when nothing about real demand changed at all.
Where Scout fits
The case-pack conversion is exactly the kind of thing that lives in a tribal-knowledge spreadsheet and breaks silently when the pack size changes. Scout connects your SPINS or retailer consumption data, counted in eaches, to the sell-in side, counted in cases, and keeps the unit of measure straight so a sell-through or velocity number means what you think it means. It measures and reconciles the units. It does not write your purchase orders or run your warehouse.
The short version
- A case pack is the count of selling units (eaches) inside one shipped case. The each is what the shopper buys, the case is what ships, the pallet is how the warehouse moves cases.
- Shipment data comes in cases, consumption data comes in eaches. The case pack is the conversion factor between them, and the numbers have to tie out both directions.
- Skip the conversion and your sell-through, velocity, and days-of-supply math are all off by exactly the case pack. A 24-count pack means a 24x error, and it rarely looks wrong enough to catch.