When to Use a Custom Product Costs Import
Conjura Retail Analytics automatically retrieves Cost of Goods Sold (COGS) data from your integrated eCommerce and ERP systems. This COGS information is essential for calculating key performance indicators (KPIs) like Contribution Margin and Gross Profit Margin displayed on your dashboards. Use this import when:
Your connected platform does not provide COGS data (e.g. Amazon - COGS cannot be pulled automatically)
Your platform COGS is inaccurate or incomplete and you want to override it with your own values
You want to apply a percentage-of-revenue cost model instead of a fixed per-unit cost
Your Amazon SKUs don't exactly match your Shopify SKUs, so auto-matching can't determine the correct cost
Important: Imported COGS override any COGS pulled automatically from your connected platforms for the same product and date range. If your Shopify account already has accurate COGS, you don't need this import.
How to Use a Custom Product Costs Import
There are two methods for manually adding product costs: via CSV or by manual entry into the app. For large COGS uploads, the CSV method is typically faster. Here's how to do it:
Navigate to the Custom Data Import tab under ‘Connectors’ on the left-hand side navigation bar.
Select ‘Product Costs’.
Click on ‘Download CSV Template File’.
Fill out the spreadsheet offline with the following details:
Product Key (pre-populated, read-only): Internal product identifier.
Product SKU (pre-populated, read-only): Your product's SKU.
Product Name (pre-populated, read-only): The product name from your connected platform.
Product Category (pre-populated, read-only): The product category from your connected platform.
Store Name (pre-populated, read-only): The store this product is associated with.
Store URL (pre-populated, read-only): The store's web domain.
Start Date (optional): The start of the date range this cost applies to.If left blank, defaults to applying this cost to all historical orders.
End Date (optional): The end of the date range. If left blank, costs are applied indefinitely.
System Cost Amount (pre-populated, read-only): The per-unit COGS from your connected platform (e.g. Shopify) for this date range. Shown for comparison so you can see what value your import will override.
Imported Cost Amount: The fixed per-unit COGS for this product,
in the specified currency. Pre-populated with any previously imported cost for this date range.
Perc of Revenue Cost Amount (optional): A variable COGS expressed as a decimal fraction of the product's selling price. For example, enter 0.2 for a cost equal to 20% of revenue. Pre-populated with any previously imported percentage cost.
Currency (required): The currency code for the cost amount. Pre-populated with your organisation's default currency
Sold in Last 30 Days (pre-populated, read-only): Whether this product had any orders within the last 30 days. Useful for prioritising which products to update.
Repeat for desired SKUs and save.
Navigate back to the product costs import in Retail Analytics.
Before uploading your file, delete all rows in the table. You can see an example by hovering over "How to do it."
Either drag and drop your file or click 'Upload File'
Click 'Continue' to ensure all columns are correctly mapped.
Select ‘Submit Data’.
Your data will sync overnight and appear in your report.
Using CSV for Bulk Uploads:
Download the CSV template from the Product Lead Times & Target Stock page. The template includes a row per connected store with example values pre-populated. Fill in your data offline, delete all rows you don't need, and upload by dragging and dropping the completed file onto the editor.
How Costs Are Applied
Per-Unit vs Percentage-Based
Imported Cost Amount (fixed): Multiplied by the order line quantity, then converted to the order's currency using the daily exchange rate. This gives the total COGS for that line item.
Perc of Revenue Cost Amount (variable): Multiplied by the product's original selling price.
If a product has an Imported Cost Amount, it is always used. The percentage-based cost is only used as a fallback when no fixed cost amount exists for that product and date.
Date Ranges and Overlapping Periods
Costs are applied on a daily basis. When you specify a Start Date and End Date, the cost applies to every day within that range.
If date ranges overlap for the same product, the row with the most recent End Date takes priority on overlapping days.
If dates are left blank, the cost applies indefinitely. This is useful when a product's cost doesn't change over time.
You can define different costs for different periods by providing multiple rows for the same product with non-overlapping date ranges.
Managing Your Imports
To update costs: Upload a new file with the revised values. The latest upload takes priority - you do not need to delete old data first.
To remove all imported costs: Navigate to My Imported Data in the Custom Data Import tab and delete the import file. This will revert all products to their system COGS (if available).