Different SKUs, different economics
Product groups with different ingredient and unit-cost structures cannot be evaluated with one assumed margin.
Commerce case study · Multi-SKU food commerce
Wins Food is a multi-SKU food-commerce case where product mix matters as much as topline sales. D2 brought Orders, settlement, Ads, product cost and packaging into one operating view so growth could be evaluated against contribution — not against revenue alone.
Direct answer
D2 created a repeatable way to separate total-shop growth from SKU-level economics. The operating model ties sales to the correct product cost, packaging, Ads and marketplace deductions, then uses short-cycle contribution review to decide where budget, assortment and operating attention should move next.
Why the shop needed a multi-SKU model
Product groups with different ingredient and unit-cost structures cannot be evaluated with one assumed margin.
Paid traffic can increase sales while contribution deteriorates if Ads, fees and product costs consume the available headroom.
For food commerce, product cost is not the only order-level cost. Packaging and fulfillment-related operating costs need to remain visible.
A shorter review cycle is needed when product mix, promotions and Ads can change the commercial picture within days.
Profitability model
The purpose of the model is not to create a larger spreadsheet. It is to keep each commercial layer separate enough that the team can see which product and cost decision is changing the outcome.
Start from the marketplace sales period and product mix.
Separate sales value from the platform's adjustments and settlement timing.
Account for marketplace fees, vouchers and campaign economics where applicable.
Attach paid acquisition cost to the period and product decisions it is supporting.
Apply the correct product-group cost structure and order-level packaging cost.
Use the remaining economics to decide what to scale, reprice, bundle, hold or correct.
Evidence basis
D2 keeps sales-period evidence, settlement evidence and cost evidence distinct before reconciling them. That preserves the difference between marketplace activity, cash movement and profitability.
What sold, in which quantities and product combinations, during the declared sales period.
What the marketplace recognized and paid after its own timing, deductions and settlement logic.
The paid acquisition layer that must be read against the same period and commercial basis.
The SKU or product-group cost assumptions used to calculate contribution rather than a blended shop-level guess.
Order-level operating cost kept visible so food-commerce contribution is not overstated.
What D2 changed
Create a consistent cost basis by product group so contribution is not distorted by a single blended margin assumption.
Bring revenue, platform deductions, Ads, product cost and packaging into one declared review basis before comparing performance.
Identify which product groups are creating contribution, which are consuming spend and which need a pricing, bundle or traffic decision.
Review smaller operating windows so campaign, Ads and assortment changes can be corrected before they become a month-end surprise.
Decision framework
Once contribution is visible by product group and review period, the next question is not “What happened?” but “What should change now?”
Put more traffic or operating attention behind products that remain inside the required contribution guardrail.
Change selling structure when a product has demand but the current offer leaves too little contribution headroom.
Avoid scaling paid traffic when the product or campaign economics are not yet strong enough to absorb more acquisition cost.
Correct fee, cost, packaging, mapping or reconciliation issues before treating the reported result as decision-ready.
What this case proves
The case demonstrates a first-party operating model for reconciling a multi-SKU food business where assortment, Ads and product costs need to be reviewed together rather than in separate platform dashboards.
Claim boundary
This page does not publish a specific GMV lift, ROAS improvement or profit result without a confirmed period, cost basis and reconciliation scope. Its evidence supports the operating model and decision logic used for Wins Food.
Related D2 capabilities
Daily marketplace ownership across catalog, pricing, promotions, campaigns, shop health and operating follow-through.
Explore serviceCatalog, pricing, campaign and marketplace operations with fees, Ads and profitability kept in the same commercial picture.
Explore serviceOrders, settlement, Ads, COGS and exceptions reconciled into a repeatable operating decision layer.
Explore serviceFAQ
D2 organized Wins Food's multi-SKU commerce reporting around a common operating logic for Orders, settlement, Ads, product cost and packaging so the team could read contribution by product group instead of relying on topline sales alone.
Different products can carry different COGS, packaging, promotion and advertising economics. A shop can grow overall revenue while the mix shifts toward products that contribute less profit, so total-shop numbers can hide where margin is actually being created or lost.
The documented evidence basis includes Orders, Settlement / Income, Ads spend, a product cost master and packaging cost. These sources answer different questions and are reconciled before contribution conclusions are drawn.
Shorter review periods make it easier to see whether a change in Ads, product mix, campaign participation or cost structure is improving contribution or only increasing GMV. The objective is a faster decision loop rather than a larger monthly spreadsheet.
No quantified lift is published without a confirmed reporting period, cost basis and reconciliation scope. This case demonstrates the operating method, evidence model and decision logic used for a multi-SKU food business.
Your product mix
D2 can reconcile the operating data and turn product-level economics into a clearer scale, hold and corrective-action framework.