Concept · article 06 of 15

Product shows
wrong COGS.

How the COGS snapshot works, why edits aren't retroactive, and how to correct it going forward.

Ibrahim Ölmez Ibrahim ÖlmezFounder · nouz · 5 min read · Updated May 18, 2026
COGS lives on the entry, not the product. When you log a product sale, nouz copies the COGS from the product at that moment. Editing the product later doesn't change past entries.

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 How does the COGS snapshot rule work?

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 How do I fix the COGS going forward?

  1. 1
    Open Products

    Click the affected product's row.

  2. 2
    Update the COGS field

    Type the correct per-unit cost.

  3. 3
    Save

    Every new sale from this moment uses the corrected value.

03 Can I fix the COGS on past entries?

Yes, but you have to do it entry by entry. Because each sale stores its own COGS snapshot, correcting historical data — say, you discovered the COGS was wrong since day one — means opening each historical revenue entry and editing its individual snapshot. It's tedious across many entries but precise, which is why it's only worth it when the historical accuracy genuinely matters.

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 should I audit my COGS?

A COGS audit is worth doing at three moments: quarterly, since suppliers raise prices and recipes drift; whenever a margin-drift insight fires in Statistics, which often points straight at a stale COGS; and after any supplier change, before you log new sales at the old cost. Each trigger is detailed below — together they keep your per-unit costs honest without a constant manual chore.

  • 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.

Still stuck? Email support@nouz.co — a founder replies, usually the same business day.