FMCG dashboard: distribution, promotions and margin

An FMCG dashboard connects distribution coverage, promotional results and product margin so a commercial team can decide where to act. For a US consumer packaged goods business, the useful layout puts shopper demand beside brand economics while labeling the source and period of each. A large shipment total alone cannot answer whether more stores are selling or whether an event paid its way.

Build the layout around the commercial review

Use the top of the page for the reporting week, product scope and source completeness. Under that, arrange the business questions in the order the team will discuss them. The existing CPG sales KPI guide owns the individual definitions; this page shows how to put selected measures together without mixing their bases.

Use the same retailer labels in every panel. Keep totals visible when a person moves into a retailer view, and label filtered results clearly. A store list answers a different question from a financial ledger; their totals do not need to be identical, but their scope must be understandable.

Start with exports that preserve the business meaning

Bring a retailer sell-out file, the eligible store roster, an approved promotion baseline, a shipment revenue and cost report, and the event expense register. Retain product, retailer, store, reporting week and event identifiers wherever those fields apply. Preserve the original transaction reference in the financial files.

Map retailer item codes to a common product identifier before comparing outlets. GS1 US explains that a GTIN identifies a trade item; this makes it a useful reference when the same product carries different retailer codes. Keep pack size beside that reference so cases and individual units stay distinct.

For store coverage, define the denominator explicitly. The example below uses eligible outlets in a fixed target roster. It is an outlet-count measure, not a sales-weighted measure: NIQ distinguishes numeric distribution from ACV and PCV weighted distribution. A missing retailer file belongs in a completeness warning rather than in a zero-sales calculation.

Worked example: an Ohio beverage brand

Consider a hypothetical Ohio beverage company reviewing one product for the week ending October 11, 2026. Each retailer has a separate set of outlets, all sell-out files are complete, and all quantities are individual consumer units. The baseline is an approved estimate of sales without the event for the same outlets and week.

The coverage panel shows 230 / 300 = 76.7%, leaving 300 - 230 = 70 outlets without recorded sales. That is an investigation list, not proof that all those stores were out of stock. Use the store-level approach in finding distribution voids to separate genuine gaps from other explanations.

The event panel shows 23,000 - 19,000 = 4,000 units above baseline, or 4,000 / 19,000 = 21.1% lift over baseline. Percentages here are rounded to one decimal place from unrounded values. The baseline is an estimate, so the comparison supports investigation rather than establishing causation by itself. NIQ's promotion measurement guidance recommends evaluating incremental sales and the factors affecting an event.

Next, read the brand's financial export. These are shipment-based financial results for the same week, not the shopper revenue implied by the unit table. Net revenue already reflects applicable sales reductions. Event expense below is a separate marketing expense approved by finance and has not also been deducted from revenue.

Gross profit is net revenue minus product COGS. The financial panel therefore shows $53,500 - $33,000 = $20,500, with a gross profit margin of 20,500 / 53,500 = 38.3%. Deducting $3,500 of selected event expense leaves $17,000. That contribution excludes other operating expenses and is not company operating profit or incremental promotion profit.

Read the panels together before choosing an action

West has 90 / 120 = 75.0% coverage and 1,000 / 8,000 = 12.5% lift over baseline. It contributes $6,600 after the selected expense, but those figures answer different questions. The account manager should investigate unsold outlets; revenue management should inspect the event result; finance should check costs before the team repeats the spending.

Do not divide shipment revenue by shopper units to invent a realized brand price. The transactions describe different points in the channel. If the commercial team suspects inventory building, use sell-in against sell-out by retailer as a separate investigation.

Change one input: additional event expense

Suppose West's event expense is revised from $1,500 to $2,500. Hold every store count, unit figure, revenue amount and product cost unchanged. The layout should reveal the financial change even though the coverage and event-volume panels look the same.

The revision reduces contribution by $1,000 without changing gross profit or shopper lift. This is a cost sensitivity, not a prediction that spending more would leave demand unchanged. The next meeting needs the reason for the expense revision and the person accountable for approving it.

Prove the totals before the meeting

The store panel must reconcile to the distinct eligible store roster. Within that scope, selling and non-selling outlets must cover the roster without overlap. The unit identity is 19,000 baseline + 4,000 above baseline = 23,000 actual units.

The financial identity is $33,000 COGS + $3,500 event expense + $17,000 selected contribution = $53,500 net revenue. Tie revenue and COGS to the approved financial export, and event expenses to their register. Investigate unmatched product or retailer codes before presenting a complete total.

Where it goes wrong

• Summing outlets across products. The same store may sell several items. Use distinct stores for brand coverage and store-product combinations for assortment analysis.
• Mixing sell-in and sell-out. Brand shipments and shopper purchases can move in different weeks. Label both rather than forcing their totals to match.
• Moving the baseline. Preserve the approved version and document revisions. Otherwise an event can appear to improve because its comparison changed.
• Deducting promotion costs twice. A sales reduction already included in net revenue must not be subtracted again as event expense.
• Calling the event window the full result. Stockpiling and a later sales dip can change the conclusion; use account-level promotion analysis for that longer review.

Review your CPG exports in Covirage

Bring a sample of your own store roster, sell-out, promotion and financial exports to Covirage. Covirage maps the columns, its tools compute and check the figures, and the external AI model explains the result with every figure traced to its rows. Create a free Covirage account, which takes about a minute, then set up your business and bring your files.

See Covirage for CPG brands for the industry context.