Catalogue owners · Imports into nouz
Product cost list
A product cost list holds one row per variant: the SKU, what a unit costs you, the currency, the date that cost starts applying, and the unit's weight in grams. It is the input a P&L needs to turn revenue into margin, and the same file nouz imports as COGS.
The file
nouz-product-costs.csv · 7 columns · one example row
Unit cost is the number shop catalogues lose most often, and the one nothing downstream works without. A missing cost does not read as missing in most reports; it reads as zero, and a zero cost shows you margin you do not have. That failure mode is exactly what Shopify's COGS report keeps out of view, and it is why this file starts from the catalogue rather than from the accounts.
The effective_from column is the quiet star. When a supplier raises prices in February, you add a new row with the new cost and the February date, and every order before it keeps the cost that was true when it was placed. That habit is called effective dating, and it is what stops one price change from rewriting last quarter's margin.
Weight is in the file because carriers bill by it. A missing weight does not make shipping free, it makes the cost wrong, so it belongs in the same file the costs live in, filled once per variant.
How to use it
- 01Export your variants from your shop admin, or start typing into the example row.
- 02Fill unit_cost with what a unit costs you to buy or make, never its selling price.
- 03Set effective_from to the date each cost started applying. When a cost changes, add a new row rather than editing the old one.
- 04Add weight_grams for anything you ship; rate cards price parcels by weight bracket.
- 05Import the finished file into nouz under Costs, and every order from each date forward is priced with it.
What is inside
| Row | sku | product | variant | unit_cost | currency | effective_from | weight_grams |
|---|---|---|---|---|---|---|---|
| 1 | HEAVY-HOODIE-2 | Heavy Hoodie | M | 28.36 | EUR | 2026-02-01 | 550 |
| 2 | |||||||
| 3 |
Every column, explained
| sku | The variant's SKU exactly as your shop spells it; it is how rows are matched. |
|---|---|
| product | The product's name, for humans reading the file. |
| variant | The variant label, like a size or a colour. |
| unit_cost | Your cost for one unit, net of VAT. The selling price does not belong in this file. |
| currency | Three-letter code, matching your shop currency. |
| effective_from | The date this cost starts applying. Orders before it keep the earlier row's cost. |
| weight_grams | The unit's weight in grams; shipping rate cards price by it. |