Contribution Margin - BSD
Configure your contribution margin cost model using the BSD — a Google Sheet that maps your sales, marketing, and cost data.
Brand Supplied Data (BSD) Configuration
The BSD is a Google Sheet that tells the Contribution Margin model how to apply your costs. You configure it once — after that, the pipeline runs automatically every morning without any additional input.
This guide covers each tab and what it controls.
What You Need to Get Started
Not all tabs are required to run the model. The source mapping and marketing tabs are essential — without them, the model can't connect your data to contribution channels. The cost tabs improve accuracy but are optional.
Required:
Digital Sales Source Mapping — maps your digital stores to contribution channels
Retail Sales Source Mapping — maps your retail partners to contribution channels
Marketing Sources to Sales Sources — links your marketing spend to the correct sales sources
Optional (improve margin accuracy):
Top-Line COGS — We attempt to pull in your COGS from the SKU Cost BSD or from a custom data source if you have one connected. This is an optional way to add the cost of goods if you do not have use one of these other options
Payment Processing — add to capture processing fees per sales source
Other Costs — add to capture 3PL, fulfillment, or other operational costs if they are currently not present for your Direct to Consumer (Shopify, Amazon, etc.) sales
UMS Campaign Name to Product ID is optional but recommended if any of your campaigns are tied to a single product and you want that spend attributed directly rather than distributed.
Jump to:
Merchant Settings
Controls global allocation methods and which COGS source the model uses. These settings apply across all channels.
Allocation Metric For Marketing Spend
How marketing spend is distributed across products
gross_sales
gross_units_sold
Allocation Metric for Other Costs
How other operational costs are distributed
gross_sales
gross_units_sold
Allocation Metric for Top-Line COGS
How COGS is distributed across products
gross_sales
gross_units_sold
Preferred COGS
Which COGS source the model pulls from (custom or default)
custom
from_source
Preferred COGS options:
custom— uses the COGS values entered in the Top-Line COGS tabdefault— falls back to Daasity's system-calculated cost
Digital Sales Source Mapping
Maps your digital sales sources — Shopify stores, Amazon, and other DTC channels — to contribution channels in the CM model.
Store Name
Display name for the sales source
Shop ID
Unique identifier tying the row to your order data
Sales Channel
The channel classification for this source (e.g., Amazon.com, Non-Amazon)
Include
Whether this source is included in CM calculations (TRUE or FALSE)
Contribution Channel
The named channel this source rolls up to in your dashboards (e.g., DTC, Amazon)
Sources marked
FALSEwill not appear in CM output. Use this for test stores or inactive sources you don't want affecting margin data.
Retail Sales Source Mapping
Maps your retail and distributor POS sources to contribution channels.
Retail Source
Name of the retail partner or data source (e.g., Costco Circana, Kroger, Target)
Include
Whether this source is included in CM calculations (TRUE or FALSE)
Contribution Channel
The named channel this source rolls up to in your dashboards (e.g., Retail)
Marketing Sources to Sales Sources
Links your marketing data sources to your sales sources so spend can be attributed correctly in the model.
Marketing Source
The ad platform or marketing data source identifier
Sales Source
The corresponding sales source this marketing spend should be tied to
UMS Campaign Name to Product ID
Enables direct campaign-to-product attribution for spend that should not distribute across the full catalog.
Campaign Name
The exact campaign name as it appears in your ad platform
Product ID
The product this campaign's spend should attribute to entirely
Use this tab any time a campaign is promoting a single product. Without an entry here, campaign spend distributes proportionally by gross sales across all products in the mapped sales source.
Top-Line COGS
Defines aggregate cost of goods sold over time. Supports date ranges so cost changes don't affect historical data retroactively.
Start Date
Date this COGS value takes effect
End Date
Date this COGS value stops applying
COGS
The aggregate cost amount for this date range
This tab captures COGS at an aggregate level, not per-SKU. See Merchant Settings to control whether the model uses these values or falls back to Daasity's system-calculated default.
Other Costs
Covers operational costs not captured elsewhere — 3PL fees, fulfillment costs, platform fees, and similar items.
Start Date
Date this cost takes effect
End Date
Date this cost stops applying
Cost Name
Label or description for the cost
Cost Amount
Total cost for this date range
Trade and TPM commitments are currently entered here as manual line items. A dedicated Trade/TPM tab with direct platform integration is on the roadmap.
Payment Processing
Defines the processing fee applied per sales source.
Sales Source
The sales source this fee applies to
Percentage Fee
Processing fee as a percentage
Last updated
Was this helpful?