Skip to main content

How to Handle Multi-Pack Unit Mismatches in Confido

How to reconcile a unit mismatch between the scan-level unit a retailer reports and the multi-pack level your team sells or forecasts at, using component sellable units or a custom equivalized unit of measure.

S
Written by Support

Some products are scanned by retailers at a different unit level than the level your team actually sells or forecasts at. For example, imagine a 1 oz item that's only ever sold to a customer in an 8-count pack: the retailer's point-of-sale system scans and reports the 1 oz item as the sellable unit, but your team plans, forecasts, and ships at the 8-pack level. When your scan-level (syndicated/POS) data comes in at the 1 oz level but your team works at the pack level, this creates a unit mismatch between what's reported and what you're actually managing.

Pack Composed of Other Sellable Units

This is the standard, recommended approach if your team is comfortable working from the case or pack view in Confido. On the Product List, set up both the individual item (e.g., the 1 oz UPC) and the multi-pack (e.g., the 8-pack UPC) as sellable units. Then, on the multi-pack's product record, turn on Pack composed of other Sellable Units and indicate that the pack is composed of the individual sellable unit, and that it ships through the same case. Once this is set up, any scan or syndicated data that comes in at the individual-unit level will automatically roll up to the case view for that pack — however that pack actually ships — so your forecasting and reporting reflect the true sell-through at the pack level without any manual math.

Why Do My Eaches and Units Totals Show Different Numbers for the Same SKU?

This section explains why the Eaches total and the Units total for the same SKU can show different numbers, even though no data issue has occurred.

Eaches is a read-only rollup view: it combines every sellable-unit row that ships as a component of the same consumer-facing item — including both the standalone single-unit row and any multi-pack/case row that is composed of that same single unit — into one combined Eaches total for that item. Units, by contrast, reflects each sellable-unit row's own total separately, without combining single and multi-pack rows together.

For example, if a single bar SKU sells both on its own (Single Bar) and inside a 12-pack case (12-Pack Case) set up as "Pack Composed of Other Sellable Units" using the single bar as its component, the Eaches total for the single bar will include units sold both as standalone bars and as bars sold inside the 12-pack case, rolled up into one number. The Units total, however, will show the Single Bar row and the 12-Pack Case row as two separate figures. This is why Eaches and Units totals will not match for SKUs sold in multiple pack configurations — it reflects how the rollup works, not a data error.

Note: Eaches is a read-only, calculated view — you cannot edit Eaches values directly. To correct a unit mismatch, adjust the underlying sellable unit and pack configuration as described above, not the Eaches figure itself.

Did this answer your question?