COGS values in nouz are snapshot at the moment of each sale, not stored as live references. This is what makes editing products safe — but it also means a "wrong" COGS only applies going forward, not retroactively, unless you fix it on the historical entries directly.
01 The snapshot rule
Each revenue_product_entry row carries its own COGS value, snapshot from the product at the moment of the sale. This is deliberate — your March P&L always shows March's COGS, even if you bump the product's COGS in May. See Editing a product later for the full rule.
02 Fix it going forward
- 1Open Products
Click the affected product's row.
- 2Update the COGS field
Type the correct per-unit cost.
- 3Save
Every new sale from this moment uses the corrected value.
03 Fixing past entries
If you need to correct historical data — say, you discovered the COGS was wrong since day one — open each historical revenue entry and edit its individual snapshot. Tedious for many entries, but precise.
For most owners, the right move is to fix the product going forward and leave the past alone. Historical accuracy at the product level is rarely worth hours of manual editing.
04 When to audit COGS
Worth doing a COGS audit:
- Quarterly. Suppliers raise prices; recipes drift. Once a quarter, redo the per-unit math.
- When margin drift fires. The Statistics insight tag often points at a stale COGS — first thing to check.
- After a supplier change. New supplier, new prices. Update affected products before logging new sales.
Was this article helpful?
Your vote helps us decide what to write next.