Skip to main content
Configure your costs in the Expenses module so Converge can calculate profitability metrics. Without cost data, Converge tracks revenue but can’t tell you how much is actually profit. Each tab covers a different cost type, and a final Fallback costs tab handles any gaps. Converge supports three cost types:

​
Product costs (COGS)

The Product costs tab shows every product variant (with SKU) per event source, alongside its cost of goods sold (COGS) data. Use this tab to review synced unit costs (from your e-commerce platform), spot gaps, and set manual overrides.
Product costs
ColumnDescription
StatusThe mapping status of the product variant (see below)
SourceThe source that ingested the order
ProductThe product name
VariantThe variant name
OrdersThe number of orders that include this variant
SKUThe product variant’s SKU identifier
Unit PriceThe selling price of the variant
Synced COGSThe (in-platform) cost of goods sold synced from your e-commerce platform (e.g. Shopify)
COGS OverrideA manual cost override you set in Converge. This takes priority over the in-platform cost
Automatic COGS syncing is currently supported for Shopify, BigCommerce, and Magento. You can monitor the sync status in the Products tab of the corresponding event source. If your e-commerce platform is not listed but supports cost-of-goods data, reach out to the Converge team to request support. In the meantime, you can use cost overrides or a CSV upload to configure costs manually.
Each SKU has a data status indicator:
  • = No COGS data exists for this variant. The COGS value will be estimated using the fallback gross margin.
  • = COGS data is available for this variant (either an override, an in-platform cost, or both).
The COGS coverage badge in the top-right corner of the table shows what percentage of orders have a COGS mapping. It reflects your current view, including the selected date range and any active filters. The badge is color-coded:
  • Green: 85% or more of orders are covered
  • Yellow: between 50% and 85%
  • Red: below 50%

​
Product cost hierarchy

Converge determines the cost for each variant using a three-tier hierarchy. The first available value wins:
  1. Cost override (highest priority): If you’ve set a manual override in the COGS Override column, Converge uses that value.
  2. In-platform cost: If no override exists, Converge uses the cost price synced from your e-commerce platform (shown in the Unit COGS column).
  3. Fallback gross margin (lowest priority): If neither of the above is available, Converge estimates the cost using the gross margin percentage configured in the Fallback costs tab.

​
Setting a (single) manual override

  1. Find the product variant in the table (use the search bar to filter by SKU, product name, or variant name).
  2. Click Set cost… in the COGS Override column for that variant.
  3. Enter the cost value, click Save.
The override takes effect shortly after saving and applies to all future cost and profit calculations for that variant.

​
Bulk override using a CSV upload

To set or update COGS for many product variants at once, use the Upload CSV button in the top-right corner of the table.
A common workflow is: filter the table to only show variants with missing costs, export the result, fill in the COGS values in the exported file, and upload it back into Converge.
Your CSV file should have the following columns:
ColumnRequiredDescription
skuYesThe product variant’s SKU
datasource_idYesThe numeric ID of the event source (find it in Event Sources)
cogsYesThe cost of goods sold for one unit (non-negative number)
currencyNoISO 4217 currency code (e.g. USD, EUR). Defaults to workspace currency
To upload a CSV file:
  1. Click Upload CSV in the top-right corner of the Product costs table.
  2. Drag and drop a .csv file into the upload area, or click to browse for one.
  3. Review the preview table (it shows the first 10 valid rows), and check for any validation warnings.
  4. Click Upload to apply the overrides. Only the valid rows are saved.
If your CSV contains duplicate SKU + datasource ID combinations, the last occurrence wins. After upload, a toast notification shows how many SKUs were updated and how many duplicates were detected.

​
Fallback gross margin

In the Fallback costs tab, you can configure a default gross margin percentage. Converge uses this to estimate COGS for any product variant without a specific cost mapping. Always set this field. Gross margin is the percentage of a product’s selling price that’s profit after subtracting the cost of goods. For example, a product selling for $100 with a gross margin of 60% has:
  • $60 in gross profit
  • $40 in estimated cost (COGS)
The fallback gross margin applies the same margin to every product. For more accurate profitability data, set individual cost prices in the Product costs tab, especially for high-volume or high-value items.

​
Transaction costs

Transaction costs represent payment processing fees. Converge subtracts these from revenue when calculating contribution profit.
There’s no dedicated Transaction costs tab yet. Configure transaction costs in the Fallback costs tab. Support for manually mapping payment methods to custom costs is coming soon.

​
Transaction cost hierarchy

Converge determines the transaction cost for each order using a two-tier hierarchy. The first available value wins:
  1. Synced transaction fees (highest priority): If your e-commerce platform provides actual transaction fees per order, Converge uses those. Currently, only Shopify syncs transaction fees (for Shopify Payments).
  2. Fallback processing fees (lowest priority): If no synced fees exist, Converge estimates the cost using the processing rate and flat fee configured in the Fallback costs tab.

​
Fallback transaction costs

In the Fallback costs tab, configure fallback transaction costs. These are used when actual transaction fees are not available from your platform. Any field that has not been configured shows an amber warning indicator. Depending on your payment provider, you may need one or both settings:
  • Payment processing rate: A percentage of the order total charged per transaction.
  • Payment processing flat fee: A fixed amount charged per order. You can select the currency for this fee separately from your workspace currency.
Most providers combine both (e.g. 2.9% + $0.30 per transaction), but some only charge a flat fee or only a percentage. Configure whichever applies to your setup. Converge uses the formula: order total × rate + flat fee.

​
Shipping costs

Shipping costs represent inbound fulfillment and delivery expenses. Converge subtracts these from revenue alongside COGS and transaction costs when calculating contribution profit. Unlike product and transaction costs, there’s no automatic syncing from your e-commerce platform yet.
There’s no dedicated Shipping costs tab yet. Configure shipping costs in the Fallback costs tab. Support for manually configuring per-order shipping costs is coming soon.

​
Fallback shipping costs

In the Fallback costs tab, you can configure how Converge estimates shipping costs. Two modes are available, choose whichever best matches your business:
  • Use customer shipping charges: Sets your shipping cost equal to what customers paid for shipping on each order. This works well when your shipping charges closely reflect your actual fulfillment costs.
  • Flat fee per order: A fixed amount representing the average cost you pay to ship one order. You can set the amount and currency independently. This is useful when your shipping costs are relatively uniform regardless of what customers are charged.