> For the complete documentation index, see [llms.txt](https://help.daasity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.daasity.com/core-concepts/contribution-margin/contribution-margin-bsd.md).

# Contribution Margin - BSD

Configure your contribution margin cost model using the BSD — a Google Sheet that maps your sales, marketing, and cost data.

{% hint style="info" %}

## Contribution Margin - Brand Supplied Data (BSD)

Configure how sales sources, marketing spend, cost inputs, fees, and exclusions flow into Daasity's Contribution Margin model.

**10 workbook tabs | Channel mapping | Cost allocation | Input verification**
{% endhint %}

{% columns %}
{% column width="16.666666666666664%" %}

<figure><img src="https://410725593-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FamTMWiPne1v1V3L7mbuj%2Fuploads%2F7mwjMLi8Kao2MTzbAce6%2FAudio_Icon.png?alt=media&amp;token=ae573cd7-c740-4b92-9bfa-5fad56839cc6" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column width="83.33333333333334%" valign="middle" %} <mark style="color:$danger;">**LISTEN**</mark>

## Connect Your AI with Daasity

{% endcolumn %}
{% endcolumns %}

Prefer audio? Listen to **Configuring the Daasity Contribution Margin Workbook**, then use the page below as your setup reference.

Audio length: 1 minute, 34 seconds

{% embed url="<https://on.soundcloud.com/xbCQlGRd5Ge9bqreUH>" %}

<details>

<summary>Read the full transcript</summary>

**\[00:00]** This is the brief on configuring the Daasity Contribution Margin workbook.

**\[00:04]** Well, this workbook is your absolutely essential tool for routing your sales, marketing, and shared operational costs so you can accurately track and compare true profitability across different retail and digital channels. You can kind of think of it as a financial sorting hat: raw data goes in and precise, trustworthy profitability comes out.

**\[00:25]** First, every single sales source, like Amazon or DTC, has to be individually mapped to a contribution channel. But listen, the system is literally ruthless with exact naming conventions. A single stray space, capitalization error, or punctuation mark won’t just cause a glitch; it will create an entirely separate, incorrect channel.

**\[00:46]** Second, once those sources are mapped, costs must be applied logically. You’ll choose to allocate shared costs by gross sales, if revenue is the driver, or gross units sold, if volume is your driver. Watch out for this easily missed detail, though: payment-processing percentages have to be formatted as decimals. Entering a 3% fee as `3` instead of `0.03` will completely derail the model’s cost accuracy.

**\[01:08]** Finally, even with perfect mapping, bad data can still sneak in. So we use order-tag exclusions to filter out unwanted orders. But you’ve got to be highly skeptical of negative rules, like “not contains.” These broad strokes frequently delete perfectly legitimate expected orders by accident.

**\[01:26]** A meticulously configured workbook transforms chaotic data into a trustworthy model, showing you exactly what your business actually keeps after costs.

</details>

{% hint style="success" %}
**Objectives**

## What you will be able to do

* Explain how each Contribution Margin BSD tab affects the model.
* Map digital, retail, and marketing sources to consistent Contribution Channels.
* Organize Contribution Channels into reporting groups and subgroups.
* Choose allocation metrics and the preferred COGS source for your implementation.
* Add date-bounded COGS, other costs, payment-processing fees, campaign mappings, and order-tag exclusions.
* Verify that the completed workbook is accurate and ready for upload.
* Connect, configure, and create the Contribution Margin BSD spreadsheet in Daasity.
* Resolve common configuration and data problems.
  {% endhint %}

### Answer the questions that drive your business

<table data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td>Which digital, retail, and marketing sources should feed each Contribution Channel?</td></tr><tr><td>How should Contribution Channels roll up for consistent reporting?</td></tr><tr><td>Should each shared cost be allocated by gross sales or gross units sold?</td></tr><tr><td>Are the required mappings, costs, dates, fees, and exclusions complete and consistent?</td></tr><tr><td>Is the spreadsheet ready to connect and upload to Daasity?</td></tr></tbody></table>

***

{% columns %}
{% column width="16.666666666666664%" %}
![](https://410725593-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FamTMWiPne1v1V3L7mbuj%2Fuploads%2Fdi5VsO8mzhRt7jVy9NPw%2FLearn_Icon.png?alt=media\&token=f8e3e66f-e303-46a8-8621-195399535443)
{% endcolumn %}

{% column width="83.33333333333334%" valign="middle" %} <mark style="color:green;">**LEARN**</mark>

### Understand what the connection does <a href="#learn" id="learn"></a>

{% endcolumn %}
{% endcolumns %}

#### What the Contribution Margin BSD controls

The workbook supplies business rules and cost inputs that Daasity cannot determine from source systems alone. It connects source-level data to the Contribution Channels used in Contribution Margin reporting and specifies how selected costs should be applied.

After the configuration is established, the Contribution Margin pipeline runs automatically each morning. Update the workbook when a source, hierarchy, allocation rule, cost, fee, campaign relationship, or exclusion changes.

<table data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td><p><strong>1. Map</strong></p><p></p><p>Connect digital, retail, and marketing sources to Contribution Channels.</p></td></tr><tr><td><p><strong>2. Organize</strong></p><p></p><p>Roll each Contribution Channel into a subgroup and group.</p></td></tr></tbody></table>

<table data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td><p><strong>3. Configure</strong></p><p></p><p>Set allocation metrics, COGS preference, costs, fees, and exclusions.</p></td></tr><tr><td><p><strong>4. Verify</strong></p><p></p><p>Check row completeness, coverage, naming, and downstream results.</p></td></tr></tbody></table>

#### Workbook tabs at a glance

<table data-search="true"><thead><tr><th>Tab</th><th>Purpose</th><th>Use it when</th></tr></thead><tbody><tr><td><strong>Digital Sales Source Mapping</strong></td><td>Maps each digital store and sales channel to a Contribution Channel and controls whether it is included.</td><td>You have digital commerce or marketplace sales sources.</td></tr><tr><td><strong>Retail Sales Source</strong> <strong>Mapping</strong></td><td>Maps each retail source to a Contribution Channel and controls whether it is included.</td><td>You have retail or wholesale sales sources represented in the workbook.</td></tr><tr><td><strong>Marketing Sources</strong> <strong>to Contribution</strong> <strong>Channel</strong></td><td>Assigns each marketing source to the Contribution Channel that should receive its spend.</td><td>You need marketing costs aligned to channel-level contribution.</td></tr><tr><td><strong>Channel Hierarchy</strong></td><td>Rolls Contribution Channels into Channel SubGroups and Channel Groups.</td><td>You want consistent channel reporting and comparisons.</td></tr><tr><td><strong>Merchant Settings</strong></td><td>Defines allocation metrics for marketing spend, other costs, and top-line COGS, plus the preferred COGS source.</td><td>You need to define how shared costs are distributed.</td></tr><tr><td><strong>UMS Campaign</strong> <strong>Name to Product ID</strong></td><td>Maps a campaign name to a product ID.</td><td>A campaign should be associated with a specific product.</td></tr><tr><td><strong>Top-Line COGS</strong></td><td>Supplies a COGS value for a defined date range.</td><td>Your implementation uses custom top-line COGS inputs.</td></tr><tr><td><strong>Other Costs</strong></td><td>Adds named costs for a defined date range.</td><td>An applicable cost is not supplied through another source.</td></tr><tr><td><strong>Payment</strong> <strong>Processing</strong></td><td>Assigns a payment-processing percentage fee to a Contribution Channel.</td><td>A channel has an applicable processing rate.</td></tr><tr><td><strong>Order Tag</strong> <strong>Exclusion</strong></td><td>Defines order-tag matching rules for orders that should be excluded.</td><td>Tagged orders should not enter the Contribution Margin model.</td></tr></tbody></table>

***

{% columns %}
{% column width="16.666666666666664%" %}
![](https://410725593-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FamTMWiPne1v1V3L7mbuj%2Fuploads%2FwPQ9r5jZZGFgdcQ7RVIe%2FDo_Icon.png?alt=media\&token=523b86d9-c11c-47da-8243-cc27bfe0569f)
{% endcolumn %}

{% column width="83.33333333333334%" valign="middle" %} <mark style="color:blue;">**DO**</mark>

## Connect and verify your AI tool <a href="#do" id="do"></a>

{% endcolumn %}
{% endcolumns %}

#### What you need to get started

The current Contribution Margin guidance treats the source-mapping and marketing-mapping tabs as essential because they connect incoming data to the model. Cost tabs are optional inputs that improve accuracy when the same costs are not already available from another source.

{% columns %}
{% column width="16.666666666666664%" valign="middle" %}

<figure><img src="https://410725593-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FamTMWiPne1v1V3L7mbuj%2Fuploads%2FFEqKM3gzvgWQlPX1eMr1%2FEssential.png?alt=media&amp;token=872783d9-1d3c-4b63-a5dd-bf53f10531de" alt="" width="188"><figcaption></figcaption></figure>
{% endcolumn %}

{% column width="83.33333333333334%" valign="middle" %}

### **Essential mappings**

{% endcolumn %}
{% endcolumns %}

* **Digital Sales Source Mapping:** maps digital stores and channels.
* **Retail Sales Source Mapping:** maps retail and distributor sources.
* **Marketing Sources to Contribution Channel:** maps marketing spend to the correct Contribution Channel.
* **Channel Hierarchy:** gives every used Contribution Channel its intended subgroup and group.

{% columns %}
{% column width="16.666666666666664%" %}
![](https://410725593-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FamTMWiPne1v1V3L7mbuj%2Fuploads%2F46Y6T5mKvPnQX5TEbhtU%2FOptional.png?alt=media\&token=acf44941-6727-40a6-92db-49c8fde260cc)
{% endcolumn %}

{% column width="83.33333333333334%" valign="middle" %}

### **Optional inputs that improve accuracy**

{% endcolumn %}
{% endcolumns %}

* **Top-Line COGS:** supplies aggregate COGS when your implementation is not using SKU Cost BSD or another connected custom source.
* **Payment Processing:** adds processing rates when they are not already represented.
* **Other Costs:** adds applicable 3PL, fulfillment, platform, and similar operational costs that are not captured elsewhere.
* **UMS Campaign Name to Product ID:** is recommended when a campaign promotes one product and its spend should be attributed directly.
* **Order Tag Exclusion:** is used only when tagged orders should be excluded from the model.

Not every optional tab must contain data. Complete only the inputs that apply to your implementation, and leave an unused input area blank rather than entering placeholder data.

Confirm the single-row **Merchant Settings** choices before submission because they control allocation and COGS behavior across channels.

> **Protect the workbook structure.** Do not add, delete, rename, or reorder columns. Complete every field required for a populated row, and use the workbook's supported values or dropdowns. A malformed row can prevent BSD data from refreshing correctly.

{% hint style="info" %}
Contribution Margin BSD Example

## Example Contribution Margin BSD Workbook

Use the example workbook below to see how a completed **Contribution Margin Brand Supplied Data (BSD)** file is structured across all 10 workbook tabs. It includes sample sales and marketing source mappings, channel hierarchy, merchant settings, cost inputs, payment processing fees, and exclusion rules.

Use this workbook as a **reference for structure and configuration** as you complete your own BSD file. The values shown are examples only. Replace them with the sales sources, channels, costs, fees, and settings that apply to your brand.

{% endhint %}

{% file src="/files/YVIEzfaJqKXTpjHgjo4D" %}

### Use this completion order

{% stepper %}
{% step %}

### Map sales sources

Review the digital and retail source rows, decide which sources belong in Contribution Margin, and assign each included source to a Contribution Channel.
{% endstep %}

{% step %}

### Map marketing sources

Assign each applicable marketing source to the same Contribution Channel naming system.
{% endstep %}

{% step %}

### Build the channel hierarchy

Add one hierarchy row for every Contribution Channel used in the mapping tabs.
{% endstep %}

{% step %}

### Set merchant-level choices

Choose the allocation metric for each supported cost type and confirm the preferred COGS option.
{% endstep %}

{% step %}

### Add applicable costs and product mappings.

Complete the campaign, top-line COGS, other-cost, and payment-processing tabs that apply.
{% endstep %}

{% step %}

### Add exclusions carefully

Define only the order-tag rules you intend to exclude, then test the effect.
{% endstep %}

{% step %}

### Verify the workbook

Check every populated row, date range, value, mapping, and exclusion before upload.
{% endstep %}

{% step %}

### Create and sync the Google Sheet

In Daasity, add a new Google Sheet from Brand Supplied Data, share it with Daasity, select the worksheet, configure its destination and column mapping, and create the connection.
{% endstep %}

{% step %}

### Verify the refreshed results

After the next pipeline refresh, confirm the expected sources and costs before using the analysis.
{% endstep %}
{% endstepper %}

### Make the configuration choices

**Define useful channel boundaries**

A Contribution Channel should group activity that you intend to evaluate together. Use names consistently across digital sales, retail sales, marketing sources, payment-processing rates, and the channel hierarchy.

| Question                                                              | Use it to decide                                                                      |
| --------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| **Should these sources share** **costs and reporting?**               | Whether they belong in the same Contribution Channel.                                 |
| **Will the business act differently** **on the results?**             | Whether the sources need separate Contribution Channels.                              |
| **How should leaders compare** **channels?**                          | The Channel SubGroup and Channel Group structure.                                     |
| **Does the marketing source** **support one channel or** **product?** | The correct channel mapping and whether a campaign-to-product mapping is appropriate. |

**Choose an allocation metric**

| Option             | Use when                                         | Consider                                                              |
| ------------------ | ------------------------------------------------ | --------------------------------------------------------------------- |
| `gross_sales`      | The cost is better represented by revenue value. | Higher-priced activity receives a larger share of the allocated cost. |
| `gross_units_sold` | The cost is better represented by unit volume.   | Each sold unit contributes to the allocation regardless of price.     |

Use the same business rationale consistently across reporting periods. A change to an allocation metric can change the distribution of cost and make period-over-period comparisons harder to interpret.

**Choose the preferred COGS source**

Keep `from_source` when the implementation is intended to use source-provided COGS. Use `custom` only when custom COGS is the approved configuration for the merchant. Confirm this choice before changing it because it can materially affect Gross Margin and every downstream contribution measure.

> **Do not change a setting simply to make a result look more plausible.** Verify the governing cost source, business rule, and date coverage first.

#### Field reference

Open each section below for the fields and checks on that workbook tab.

<details>

<summary>Digital Sales Source Mapping (Essential)</summary>

Review each source row already present in the workbook. Preserve source identifiers and make decisions in the inclusion and Contribution Channel fields.

![Example Digital Sales Source Mapping sheet with Store Name, Shop ID, Sales Channel, Include, and Contribution Channel columns](https://content.gitbook.com/content/amTMWiPne1v1V3L7mbuj/blobs/jYuWkEZAew4tazBTxbL4/Unknown%20image)

Example digital source mapping. The screenshot shows included and excluded digital channels rolling into Amazon or DTC.

| Field                | How to use it                                                                | Check                                                                                                                               |
| -------------------- | ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Store Name           | The store label associated with the source data.                             | Do not replace a source label without Daasity guidance.                                                                             |
| Shop ID              | The source-system identifier for the shop.                                   | Preserve the exact value supplied in the workbook.                                                                                  |
| Sales Channel        | The source sales channel within the store.                                   | Review every populated source row, including less common channels.                                                                  |
| Include              | Controls whether the source row is included in Contribution Margin.          | Use the accepted value format already used in your workbook. A source marked `FALSE` does not appear in Contribution Margin output. |
| Contribution Channel | The reporting channel that receives the source's sales and applicable costs. | Match the name exactly to a row in Channel Hierarchy.                                                                               |

> **One source, one intended destination.** Similar source names can still represent different businesses or channels. Review the Store Name, Shop ID, and Sales Channel together before assigning the Contribution Channel.

Use `FALSE` for a test store or inactive source that should not affect margin data.

</details>

<details>

<summary>Retail Sales Source Mapping (Essential)</summary>

![Example Retail Sales Source Mapping sheet with Retail Source, Include, and Contribution Channel columns](https://content.gitbook.com/content/amTMWiPne1v1V3L7mbuj/blobs/h5IKLuDZCrGUBc0IT2gr/Unknown%20image)

Example retail and distributor sources assigned to the Retail Contribution Channel.

| Field                | How to use it                                                                | Check                                                        |
| -------------------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------ |
| Retail Source        | The retail or wholesale source represented by the row.                       | Preserve the source name supplied in the workbook.           |
| Include              | Controls whether the retail source is included.                              | Use the accepted value format already used in your workbook. |
| Contribution Channel | The reporting channel that receives the source's sales and applicable costs. | Match the name exactly to a row in Channel Hierarchy.        |

</details>

<details>

<summary>Marketing Sources to Contribution Channel (Essential)</summary>

![Current-page example of marketing source mappings with Marketing Source and Contribution Channel columns](https://content.gitbook.com/content/amTMWiPne1v1V3L7mbuj/blobs/xFrFUlpdFWjnuiH4uXjS/Unknown%20image)

Current-page example of marketing-source mapping.

| Field                | How to use it                                                              | Check                                                                                    |
| -------------------- | -------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| Marketing Source     | The marketing source value used in Daasity data.                           | Use the exact source value; do not normalize spelling or capitalization unless directed. |
| Contribution Channel | The Contribution Channel that should receive the source's marketing spend. | Use a channel name that also appears in Channel Hierarchy.                               |

Map all applicable marketing sources, including identifiers that may look like account IDs rather than display names.

</details>

<details>

<summary>Channel Hierarchy (Essential)</summary>

The hierarchy creates consistent reporting levels. Every Contribution Channel used elsewhere in the workbook should have one intended hierarchy path.

| Field                | How to use it                                                           |
| -------------------- | ----------------------------------------------------------------------- |
| Contribution Channel | The most specific reporting channel used in source and cost mappings.   |
| Channel SubGroup     | The middle reporting level that combines related Contribution Channels. |
| Channel Group        | The broadest reporting level.                                           |

Amazon 3P grouped under the Amazon subgroup and Digital channel group

| Contribution Channel | Channel SubGroup | Channel Group |
| -------------------- | ---------------- | ------------- |
| Amazon 3P            | Amazon           | Digital       |

> **Use exact names.** A difference in spacing, punctuation, or capitalization can create a separate value instead of the intended rollup.
>
> ![](https://410725593-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FamTMWiPne1v1V3L7mbuj%2Fuploads%2FbD0HM50kvC0ZfQh43Ye0%2FChannel%20Hierarchy.png?alt=media\&token=b0d8fa79-4c53-48d3-ac44-7710934ef476)

</details>

<details>

<summary>Merchant Settings (Optional)</summary>

This tab contains one merchant-level configuration row. Use the workbook dropdowns rather than typing unsupported values.

![Merchant Settings row showing allocation metrics set to gross sales and Preferred COGS set to custom](https://content.gitbook.com/content/amTMWiPne1v1V3L7mbuj/blobs/dDo4AzzvQ4s8PkjRKisf/Unknown%20image)

Example Merchant Settings. In this screenshot, shared costs allocate by gross sales and Preferred COGS is custom.

| Field                                 | Supported choices in the workbook   | Decision                                                                                                                                                                                                          |
| ------------------------------------- | ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Allocation Metric For Marketing Spend | `gross_sales` or `gross_units_sold` | Choose whether shared marketing spend is allocated in proportion to gross sales or gross units sold.                                                                                                              |
| Allocation Metric for Other Costs     | `gross_sales` or `gross_units_sold` | Choose whether other costs are allocated in proportion to gross sales or gross units sold.                                                                                                                        |
| Allocation Metric for Top-Line COGS   | `gross_sales` or `gross_units_sold` | Choose whether top-line COGS is allocated in proportion to gross sales or gross units sold.                                                                                                                       |
| Preferred COGS                        | `from_source` or `custom`           | Choose the COGS source established for your implementation. `custom` uses the aggregate values entered in Top-Line COGS. `from_source` uses the source-provided or system-calculated cost available to the model. |

Older explanatory copy may refer to the source option as `default`. The newer workbook dropdown uses `from_source`; follow the workbook value exactly.

> **Allocation changes distribution, not the source total.** Select the metric that best represents how the shared cost should be distributed across the applicable sales activity.

</details>

<details>

<summary>UMS Campaign Name to Product ID (Optional)</summary>

![Example UMS campaign name mapped to one product ID](https://content.gitbook.com/content/amTMWiPne1v1V3L7mbuj/blobs/r3jLT57q6EnQakLFvHt3/Unknown%20image)

Example direct campaign-to-product attribution.

| Field         | How to use it                                                                   |
| ------------- | ------------------------------------------------------------------------------- |
| Campaign Name | Enter the campaign name exactly as it appears in the applicable marketing data. |
| Product ID    | Enter the exact product identifier to associate with that campaign.             |

Use this tab when a campaign promotes a single product and the relationship is known. The mapped campaign's spend is attributed entirely to that product. Without an entry, campaign spend distributes proportionally by gross sales across products in the mapped source. Do not guess a product ID from the campaign name.

</details>

<details>

<summary>Top-Line COGS (Optional)</summary>

![Example Top-Line COGS sheet with start date, end date, and aggregate COGS values](https://content.gitbook.com/content/amTMWiPne1v1V3L7mbuj/blobs/FRJy2J2tP51NoVcHxzFh/Unknown%20image)

Example aggregate COGS values with date-bounded coverage.

| Field      | How to use it                                                    | Check                                                                 |
| ---------- | ---------------------------------------------------------------- | --------------------------------------------------------------------- |
| Start Date | The first date covered by the COGS value.                        | Use `YYYY-MM-DD`.                                                     |
| End Date   | The last date covered by the COGS value.                         | Use `YYYY-MM-DD`; confirm it is not before Start Date.                |
| COGS       | Enter the approved aggregate COGS amount for the defined period. | Confirm the amount and period against the governing financial source. |

This tab captures COGS at an aggregate level, not per SKU. Date-bounded rows allow cost changes to apply prospectively without rewriting historical periods.

> **Avoid gaps and unintended overlaps.** Review adjacent date ranges before adding a new row, especially when the value changes over time.

</details>

<details>

<summary>Other Costs (Optional)</summary>

![Example Other Costs sheet with date ranges, 3PL, fulfillment, and platform fee line items](https://content.gitbook.com/content/amTMWiPne1v1V3L7mbuj/blobs/BfZ5G3riUxe6AtNYNkLp/Unknown%20image)

Example operational costs entered as time-bounded line items.

| Field       | How to use it                                | Check                                                                |
| ----------- | -------------------------------------------- | -------------------------------------------------------------------- |
| Start Date  | The first date covered by the cost.          | Use `YYYY-MM-DD`.                                                    |
| End Date    | The last date covered by the cost.           | Use `YYYY-MM-DD`.                                                    |
| Cost Name   | A clear, stable name for the cost.           | Use consistent naming for the same cost across periods.              |
| Cost Amount | The approved cost amount for the date range. | Confirm the amount and coverage period against the governing source. |

Add only costs that belong in the approved Contribution Margin model and are not already supplied elsewhere. Duplicate inputs can overstate costs.

**Current-state note:** Trade and trade-promotion-management commitments are entered here as manual line items. The current page identifies a dedicated Trade/TPM tab with direct platform integration as planned future functionality.

</details>

<details>

<summary>Payment Processing (Optional)</summary>

![Current-page example of payment-processing fees by Contribution Channel](https://content.gitbook.com/content/amTMWiPne1v1V3L7mbuj/blobs/3r3VxPI3FKwztnASRhJF/Unknown%20image)

Current-page example of payment-processing rates.

| Field                | How to use it                                                | Check                                                                                                         |
| -------------------- | ------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------- |
| Contribution Channel | The channel to which the processing rate applies.            | Match the name exactly to Channel Hierarchy.                                                                  |
| Percentage Fee       | The approved payment-processing percentage for that channel. | Enter it using the percentage convention established in your workbook. Convert 3% to `0.03` and 6% to `0.06`. |

If rates differ by channel, use a separate row for each applicable Contribution Channel.

</details>

<details>

<summary>Order Tag Exclusion (Optional)</summary>

Add an exclusion only when orders matching the specified tag rule should be removed from the Contribution Margin model.

| Field                     | How to use it                                        |
| ------------------------- | ---------------------------------------------------- |
| Order tags to be excluded | Enter the tag text to evaluate.                      |
| Wildcard Logic            | Select the matching rule from the workbook dropdown. |

| Wildcard option   | Matching test                                  |
| ----------------- | ---------------------------------------------- |
| `exact`           | The tag matches the entered value exactly.     |
| `starts_with`     | The tag begins with the entered value.         |
| `ends_with`       | The tag ends with the entered value.           |
| `contains`        | The tag contains the entered value.            |
| `not_contains`    | The tag does not contain the entered value.    |
| `not_starts_with` | The tag does not begin with the entered value. |
| `not_ends_with`   | The tag does not end with the entered value.   |

> **Do not remove the example row.** The supplied workbook marks the example as a row to preserve. Negative rules such as `not_contains` can match more orders than expected. Validate the result on a known sample before relying on the model.

</details>

***

{% columns %}
{% column width="16.666666666666664%" %}
![](https://410725593-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FamTMWiPne1v1V3L7mbuj%2Fuploads%2Fas0HHuel3QVlr1yGElvO%2FDecide_Icon.png?alt=media\&token=efd5bc20-7fcc-4d32-a4f1-60faadccc159)
{% endcolumn %}

{% column width="83.33333333333334%" valign="middle" %} <mark style="color:cyan;">**DECIDE**</mark>

## Use, investigate, or stop <a href="#decide" id="decide"></a>

{% endcolumn %}
{% endcolumns %}

### Verify and upload the spreadsheet

Use this final readiness gate to decide whether the completed Contribution Margin BSD spreadsheet is accurate, complete, and ready to upload.

#### Verify before the next refresh

* No columns were added, deleted, renamed, or reordered.
* Every populated row has all required fields completed.
* Workbook dropdowns and supported values were used where provided.
* Every included sales source has an intended Contribution Channel.
* Every Contribution Channel used in a mapping or fee row appears in Channel Hierarchy.
* Channel names match exactly across tabs.
* Date ranges use `YYYY-MM-DD`, cover the intended period, and have no unintended gaps or overlaps.
* Cost and fee values are supported by the governing financial source and are not duplicated elsewhere.
* Allocation metrics and Preferred COGS reflect the approved merchant configuration.
* Order-tag exclusions were tested against known included and excluded orders.

#### Upload the Contribution Margin BSD spreadsheet

**If all checkboxes above have been completed, the final step is to upload the new Contribution Margin BSD spreadsheet to Daasity.**

![Daasity Brand Supplied Data page with the Data section selected, Brand Supplied Data open, and the New Google Sheet button in the upper-right corner](https://content.gitbook.com/content/amTMWiPne1v1V3L7mbuj/blobs/7NlBK3lxg5RfSNJzVTHq/Unknown%20image)

#### Open Data, select Brand Supplied Data, and use New Google Sheet to begin.

{% stepper %}
{% step %}

### Open your workspace

Log in to Daasity and navigate to your Daasity workspace.
{% endstep %}

{% step %}

### Open Data

In the left-hand navigation, select **Data**.
{% endstep %}

{% step %}

### Open Brand Supplied Data

In the navigation pane, select **Brand Supplied Data**. This area supports custom spreadsheets in CSV or Excel format.
{% endstep %}

{% step %}

### Start a Google Sheet connection

Select **New Google Sheet** in the upper-right corner of the window.
{% endstep %}

{% step %}

### Name the Google Sheet

Enter a clear name for the new Google Sheet connection.
{% endstep %}

{% step %}

### Share the file with Daasity

Complete the sharing instructions shown in Step 1 of the setup workflow.
{% endstep %}

{% step %}

### Select and sync the worksheet

Select the worksheet you want Daasity to pull in, then select **Sync**.
{% endstep %}

{% step %}

### Configure the destination and columns

Provide the **Destination Schema Name**, **Destination Table Name**, and intended **Column Mapping**.
{% endstep %}

{% step %}

### Create the connection

After the required information is complete, the **Create** button becomes active. Select it to complete the process.
{% endstep %}
{% endstepper %}

**Upload tips**

* **File format:** CSV is generally the most reliable upload format.
* **Column headers:** Headers must match Daasity's expected template exactly. Check the setup screen for a template download option.
* **Historical data:** Format date columns consistently, such as `YYYY-MM-DD`.

> **Need help?** If you receive an error or do not see the Brand Supplied Data option in your workspace, contact Daasity Support at <support@daasity.com> or use the in-app chat. Support can confirm the workflow for your account and provide the correct template.

***

{% columns %}
{% column width="16.666666666666664%" %}
![](https://410725593-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FamTMWiPne1v1V3L7mbuj%2Fuploads%2F9vDETqAQJSK5UipMupa7%2FResolve.png?alt=media\&token=061b4b41-614e-49e0-b3bb-8adc9eb6200c)
{% endcolumn %}

{% column width="83.33333333333334%" valign="middle" %} <mark style="color:purple;">**RESOLVE**</mark>

## Fix common connection and answer problems <a href="#resolve" id="resolve"></a>

{% endcolumn %}
{% endcolumns %}

#### Troubleshoot an unexpected result

| What you see                                    | Check first                                                                             | Then verify                                                                        |
| ----------------------------------------------- | --------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| **A sales source is missing**                   | Include value and Contribution Channel on the applicable digital or retail mapping tab. | The channel appears exactly once in the intended Channel Hierarchy path.           |
| **Marketing cost appears on the wrong channel** | Marketing Sources to Contribution Channel.                                              | The marketing source spelling or identifier matches the underlying data.           |
| **Margin looks higher than expected**           | Preferred COGS, top-line COGS coverage, Other Costs, and Payment Processing.            | The relevant costs are present, complete, and not outside the analysis date range. |
| **Margin looks lower than expected**            | Duplicate cost coverage and overlapping date ranges.                                    | The same cost is not supplied by both a source integration and the BSD workbook.   |
| **Cost distribution looks wrong**               | The applicable Merchant Settings allocation metric.                                     | The selected metric reflects the intended business driver.                         |
| **Orders are unexpectedly missing**             | Order Tag Exclusion.                                                                    | Negative wildcard logic is not matching more orders than intended.                 |
| **BSD refresh reports an error**                | Incomplete populated rows and manually typed values where a dropdown is required.       | The workbook structure and all required fields remain intact.                      |

#### The result is still unexpected

Capture the affected date range, Contribution Channel, source, product or campaign if applicable, the value you see, the value you expected, and the workbook row that appears relevant.

Then contact Daasity Support with those details so the team can investigate efficiently.

### Related guidance

* [Follow-up video](https://www.loom.com/share/d63a04480eca4f719ec5dfc9acec93c2)
* [Daasity Metric Glossary](https://help.daasity.com/core-concepts/metrics/metric-glossary)