Operating Intelligence 13 min read

Operating Intelligence for Food and Beverage Companies

How F&B operators use operating intelligence to manage COGS volatility, distributor margin stacking, SKU proliferation, and co-packer costs in one unified view.

Siddharth Gangal

Why F&B Operating Data Is Uniquely Fragmented

A software company has one product and a handful of data sources. A food or beverage brand has ingredient invoices from six suppliers, production runs across two co-packers, retail shipments through three distributors, a growing DTC channel, and a finance team still reconciling last month's chargebacks.

The result is an operating picture that is always wrong by design. COGS in the accounting system reflects what was invoiced, not what ingredient costs are today. Distributor sell-through data arrives 30 to 60 days late. Co-packer invoices include line changeover charges that no one budgeted. Shrinkage hits as a single write-down at quarter-end rather than a weekly signal.

Operating intelligence does not solve this by building a better spreadsheet. It solves it by creating a unified data layer that pulls from every source, applies F&B-specific margin logic, and tells operators what to do next — not just what happened last month.

This post covers the six structural challenges that make F&B operating data difficult, the metrics framework that addresses each one, and how to build the operating layer that connects all of it.

COGS Volatility and Commodity Exposure

COGS in food and beverage is not a stable number. It is a weighted average of inputs — commodities, packaging, freight, and co-packer labor — each of which moves independently and often at speed.

The commodity problem in 2025 and 2026

Cocoa prices hit multi-decade highs in 2024 driven by West African supply disruptions, then partially corrected into 2026 — but remained at $5,000–$6,000 per ton, still well above pre-2022 averages. Coffee surged sharply between 2024 and 2025 due to Brazilian and Vietnamese weather events. Corn, wheat, and sugar remain sensitive to climate-linked yield disruptions and geopolitical freight pressure. For any brand with meaningful exposure to these categories, a single commodity spike can move COGS by 300–500 basis points in a quarter.

The typical response — update COGS assumptions in the budget model once a year — is structurally too slow. By the time an annual budget catches up to commodity reality, the brand may have priced promotions, committed to retail programs, and agreed to distributor terms that are now margin-negative.

Tracking landed COGS in real time

Effective COGS management in F&B requires three things:

  • Ingredient-level cost tracking — Every raw material mapped to its commodity index, updated monthly or weekly for high-exposure categories.
  • Landed cost modeling — COGS per SKU that includes not just ingredient cost but also packaging, inbound freight, co-packer conversion cost, and quality holds.
  • Margin threshold alerts — Automated flags when a SKU's gross margin drops below a pre-defined floor (typically 40–45% for branded CPG, lower for private label). The alert fires at the data layer, not at the quarterly business review.

The goal is not to predict commodity prices. It is to know, at any given moment, which SKUs are currently margin-safe and which are at risk — so pricing, promotional, and sourcing decisions are made with current data.

Distributor Margin Stacking: The Channel Math Nobody Builds

Most F&B brands know their gross margin. Far fewer know their net realized revenue per case by channel — and that gap is where margin disappears without explanation.

How margin stacking compounds

A standard three-tier distribution structure looks like this:

Channel Layer Typical Margin Take Impact on $10 MSRP Product
Broker 5–7% $0.50–$0.70 off MSRP
Distributor 20–30% $2.00–$3.00 off MSRP
Retailer 30–50% $3.00–$5.00 off MSRP
Trade spend 10–25% of MSRP $1.00–$2.50 in promotions, slotting, MCB

A $10 MSRP product can net the brand $2.50–$4.00 per unit after these deductions. That is a realized revenue capture of 25–40% of retail price. Modeled against COGS that was calculated at MSRP economics, the resulting gross margin picture is dramatically wrong.

What "net realized revenue" tracking requires

Tracking net realized revenue per channel requires pulling distributor deduction reports (MCBs, scan-backs, off-invoice allowances), separating trade spend by SKU and customer, and reconciling the resulting net figure against COGS on the same unit basis. This is not natively available in QuickBooks, NetSuite, or most standard accounting setups — it requires a data layer that maps deductions to SKUs and channels automatically.

Brands that build this view typically discover two things: their best-selling retail SKU is not their most profitable one, and at least one distribution market is running below break-even on a contribution basis before overhead.

SKU Proliferation: The Hidden Operational Tax

Every new SKU feels like a revenue opportunity when it launches. At 50 SKUs, the cumulative cost of that complexity begins to exceed the marginal revenue each one generates.

The compounding costs of SKU count

SKU proliferation drives costs in ways that rarely show up on a single line item:

  • Co-packer line changeovers — Each SKU variant requires a changeover, which takes 20–30 minutes of line time and shortens production runs. Shorter runs mean higher cost per unit.
  • CIP (clean-in-place) cycles — More SKUs mean more cleaning cycles. CIP time does not produce revenue; it consumes line availability. Plants with high SKU counts report CIP cycles consuming 20–30% more daily line time than their low-SKU counterparts.
  • Warehouse complexity — More SKUs mean more pick locations, more pallet positions, and higher labor costs per case picked. A 3PL billing per pallet slot amplifies this directly.
  • Forecast accuracy decay — Each additional SKU makes demand planning harder. Lower forecast accuracy means both stockouts on winners and excess inventory on slow movers — the latter triggering markdowns or write-offs that hit gross margin directly.

SKU rationalization: the right framework

SKU rationalization is not about cutting product. It is about identifying where complexity cost exceeds contribution margin. McKinsey analysis of CPG SKU rationalization programs found that removing roughly 40% of a brand's SKU count increased production output by about 10% while cutting manufacturing costs by nearly 20%.

The operational decision framework for rationalization:

  1. Calculate contribution margin per SKU net of trade spend, co-packer changeover cost, and carrying cost.
  2. Flag SKUs below 2% of total gross profit that also require dedicated changeovers or unique ingredients.
  3. Evaluate whether the SKU serves a strategic customer or channel relationship that justifies its operating cost.
  4. Sunset or reformulate SKUs that fail both tests.

Operating intelligence makes this analysis continuous rather than annual. When COGS rises on a specific ingredient shared by multiple SKUs, the platform immediately surfaces which of those SKUs are now margin-negative — before the next production run is scheduled.

Co-Packer Management: Costs That Hide in Invoices

Co-packers are essential infrastructure for most emerging and mid-market F&B brands. They also represent one of the most opaque cost centers in the P&L — because their billing is complex, variable, and often disputed only after the fact.

The three layers of co-packer cost opacity

Contracted rate versus actual rate: Co-packer contracts set a base price per case for a given production volume. Most contracts include minimums, overrun charges, and rush fees that only appear on individual invoices. A brand running 10% below its volume commitment can face per-case charges 15–20% above contract rate.

Changeover and downtime billing: Every SKU changeover consumes line time. If the brand added SKUs since the last contract negotiation, changeover charges may be unbundled and billed separately — or absorbed into a higher base rate that was never renegotiated. Brands with 20+ SKUs at a single co-packer often cannot reconstruct what their true all-in cost per case is without line-item invoice analysis.

Quality hold and rework costs: When a production run is placed on quality hold, the brand typically bears rework or destruction costs. These are frequently coded to a catch-all COGS line in accounting rather than tracked at the SKU and production-run level. That makes it impossible to identify which co-packer or which production configuration is driving the problem.

What good co-packer visibility looks like

A complete co-packer operating view tracks three things per production run: cost per case (contracted versus actual, with variance flagged), quality hold rate and associated rework cost, and on-time fill rate versus committed schedule. Brands with this visibility renegotiate contracts from data rather than memory, and catch cost overruns in billing cycles — not quarterly reviews.

DTC vs. Wholesale: Channel Economics That Require Separate P&Ls

DTC and wholesale are not competing channels for F&B brands — they are different businesses with different P&L structures that happen to share a product.

The gross margin illusion in DTC

DTC gross margin looks exceptional by CPG standards. A brand selling a 6-pack DTC at $36 with $18 COGS captures 50% gross margin. That same product through a distributor nets $22 per case — a gross margin of 18%. On paper, DTC wins decisively.

Operating margin tells a different story. DTC requires customer acquisition, paid media, fulfillment infrastructure, packaging for DTC (often different from retail), and return handling. When those costs are included, DTC EBIT margins are frequently lower than wholesale EBIT margins — a finding validated across a wide range of CPG brands that have disclosed channel-level economics.

The correct conclusion is not that one channel is better. It is that each channel requires its own contribution margin model — and that blended P&Ls obscure which channel is actually making money at the unit level.

Building per-channel contribution margin

A channel-level contribution model for F&B tracks:

  • DTC: Revenue minus COGS, minus platform fees (Shopify, payment), minus CAC, minus fulfillment cost per order, minus return rate cost.
  • Wholesale/distributor: Net realized revenue (post-deductions) minus COGS, minus broker fee, minus trade spend per case, minus freight to distributor.
  • Amazon/marketplace: Net revenue minus referral fee, minus FBA or 3PL fulfillment, minus ad spend (ACoS-adjusted), minus COGS.

This model tells operators which channel is covering its own variable costs — and therefore which channel to grow, which to rationalize, and where a pricing or trade spend change will have the most margin impact.

The F&B Operating Intelligence Metrics Framework

The following framework covers the eight metrics that matter most for F&B operating intelligence. Each metric maps to a specific operational decision, not just a reporting number.

Metric Definition Decision It Drives
Landed COGS per SKU Ingredient + packaging + inbound freight + co-packer conversion per case Pricing, reformulation, SKU retirement
Net realized revenue per case by channel Gross shipment revenue minus all distributor deductions and trade spend Channel mix, distributor renegotiation
Contribution margin by channel Net realized revenue minus COGS minus channel-specific variable costs Channel investment, promotional planning
SKU-level gross margin Net revenue per unit minus landed COGS per unit SKU rationalization, portfolio prioritization
Shrinkage and spoilage rate Write-offs as % of production, by SKU and facility Co-packer performance, demand planning accuracy
Co-packer cost variance Actual cost per case versus contracted rate, per production run Contract renegotiation, dual-sourcing decisions
Fill rate by SKU % of orders shipped complete and on time versus total orders placed Production scheduling, safety stock levels
Trade spend as % of net revenue All promotional, slotting, and MCB spend divided by net revenue Promotional ROI, retailer program decisions

These eight metrics require data from at least five separate systems: accounting (COGS, deductions), co-packer invoices, distributor sell-in/sell-through reports, DTC platform data, and demand planning or ERP. No single system natively produces all of them. That is the core problem that operating intelligence solves.

Building the Operating Intelligence Layer for F&B

The data integration challenge

F&B operating data lives in disconnected systems with no standard format. Co-packer invoices arrive as PDFs. Distributor deduction reports come as monthly Excel files. COGS lives in QuickBooks or NetSuite. DTC data lives in Shopify. The typical operator is manually assembling these into a spreadsheet that is two weeks out of date by the time a decision needs to be made.

An operating intelligence layer automates this integration. It ingests from each source, normalizes units and SKU naming (a persistent problem when the same product has different names in Shopify, the distributor portal, and QuickBooks), applies landed cost logic, and surfaces a clean operating view.

What the operating view should answer

A well-built F&B operating intelligence system answers three operational questions daily:

  1. Which SKUs are margin-healthy right now? Accounting for current landed COGS, not budgeted COGS.
  2. Which channels are covering their variable costs? Net realized revenue versus contribution margin floor by channel.
  3. Where is cost variance appearing? Co-packer overruns, distributor deductions above contract, shrinkage above normal range.

The output is not a dashboard to explore. It is a short list of decisions: adjust the promotional rate on SKU X in Region Y, flag the co-packer invoice for line item Z, increase safety stock on the top-margin SKU ahead of the seasonal demand spike. Operators should spend less than 15 minutes reviewing these outputs in a daily or weekly standup.

What the implementation timeline looks like

For most F&B brands with 10–50 SKUs and two to three distribution channels, standing up an operating intelligence layer takes four to six weeks. The bulk of that time is data normalization — getting SKU naming conventions consistent across systems — not the integration itself. Brands that have already standardized naming in their ERP or accounting system can move faster.

The priority sequencing is: connect accounting first (COGS, revenue, deductions), then add the co-packer data feed, then DTC, then distributor sell-through. Each layer adds incremental decision-making capability. The first two layers alone — accounting and co-packer — typically surface enough variance to pay for the operating intelligence investment in the first quarter.

Frequently asked questions

What is operating intelligence for food and beverage companies?+

Operating intelligence for food and beverage companies is the practice of unifying data from production systems, co-packers, distributors, retail channels, and finance tools into a single margin-aware operating view. Unlike standard BI dashboards, it surfaces specific actions — not just reports — so operators know which SKUs to cut, which channels are leaking margin, and where commodity exposure is highest.

How do F&B brands track COGS when commodity prices change constantly?+

The key is moving from static COGS assumptions to rolling ingredient-level cost tracking. Assign a commodity index to every major input, recalculate landed cost per SKU monthly (or weekly for high-exposure categories like coffee or cocoa), and set margin thresholds that trigger alerts when a SKU crosses a pre-defined floor. Operating intelligence platforms automate this reconciliation instead of requiring spreadsheet updates after every invoice.

What is distributor margin stacking and why does it matter?+

Margin stacking is the cumulative margin each channel layer takes before a product reaches the end consumer. A typical CPG three-tier structure looks like this: broker 5–7%, distributor 20–30%, retailer 30–50%. If you layer trade spend of 10–25% of MSRP on top of that, net realized revenue can be 40–55% below your MSRP. Tracking net realized revenue per channel — not just gross shipment revenue — is the only way to know where your product actually earns money.

How many SKUs should a food or beverage brand carry?+

The right SKU count depends on contribution margin per SKU, not just revenue. McKinsey research found that CPG companies that rationalized roughly 40% of their SKUs increased output by about 10% while reducing manufacturing costs by nearly 20%. A useful framework: SKUs contributing less than 2% of gross profit that also require dedicated co-packer line changeovers should be flagged for review first. Operating intelligence surfaces SKU-level margin automatically so these decisions become data-driven rather than political.

What metrics should a food and beverage COO track weekly?+

A weekly F&B operating review should cover: (1) Gross margin by channel versus prior week — detecting trade spend overruns early. (2) Landed COGS variance versus budget — flagging commodity and freight surprises. (3) Shrinkage and spoilage rate by facility or co-packer. (4) Fill rate by SKU — low fill rates trigger excess inventory in other SKUs and missed revenue. (5) Net realized revenue per case by channel — tracking distributor and retail deductions in real time. (6) DTC contribution margin — isolating fulfillment cost creep before it compounds.

What is the difference between DTC and wholesale economics for F&B brands?+

Gross margin favors DTC — a brand selling direct keeps 100% of MSRP minus COGS. But EBIT margins are often lower in DTC because customer acquisition costs (CAC), fulfillment, and return handling erode the gross margin advantage. Wholesale moves volume with predictable economics but compresses margin through distributors and retailers. The right answer is channel-mix optimization: use DTC data to understand true product economics, then deploy wholesale to drive scale on the SKUs with the strongest unit economics.

How should F&B brands manage co-packer performance?+

Co-packer management requires three tracking layers: (1) Quality — defect rate and hold rate per production run. (2) Cost — actual cost per case versus contracted rate, including line changeover charges for SKU complexity. (3) Capacity — scheduled versus actual fill rate, and lead time variance. Brands that track co-packer performance through a single operating view catch cost overruns in invoicing, not at the quarterly review, and can negotiate or dual-source from a position of data, not guesswork.