January 2026: the product card got rewritten (and the COGS snapshot got faster).

Three things shipped in v2.1, all on the products side: the product card got rewritten end-to-end, COGS snapshotting got noticeably faster, and the archive flow stopped being scary.

Rewritten product card

The product card — the screen you open when you click a single SKU — was the oldest unchanged screen in nouz. It still showed the same five fields it had at launch: name, price, COGS, VAT, category. Useful, but it didn't answer the question owners actually had when they opened it: "Is this product paying its way?"

The new card has three sections. Top: identity and pricing (name, SKU, current price, current COGS, current margin %). Middle: the live performance strip — units sold in the trailing 30 days, gross profit contribution, percentage of total location EBIT. Bottom: the snapshot history — every price change and every COGS change with the date it took effect, so you can see how the product has evolved over time without losing past P&L accuracy.

A reminder on snapshotting, because the new card surfaces it more clearly: revenue_product_entries store the COGS at the moment of the sale. Editing today's COGS does not change yesterday's gross profit. We wrote about why this matters for accurate historical P&L in why editing COGS doesn't rewrite history.

Faster COGS snapshot

Internal: every product sale fires a snapshot write that captures the COGS value as of that moment. In v2.0 this was a synchronous database write that added 80–120ms to each sale entry. With high-volume shops logging 200 sales an evening, that adds up. v2.1 moves the snapshot to a background write with a queue — entry is acknowledged in under 20ms, snapshot lands within two seconds. Same data, faster feel.

Worth noting because the snapshot is what guarantees historical P&L correctness. We didn't change what gets captured — only the timing of the write. If you delete an entry within the two-second window, the snapshot is never written; if you delete it later, the snapshot is reversed as part of the delete.

Cleaner archive flow

Archiving a product used to be a single confirm dialog with no preview of what would happen. Owners stopped archiving — they'd just stop selling discontinued products and leave them in the catalog, which made the products list noisy.

The new archive flow shows you what archiving means in plain language: the product disappears from the active catalog, you can't log new sales for it, but every past sale stays exactly as recorded (because of the COGS snapshot, those past sales don't depend on the product still existing). You can unarchive any time. See archiving a product for the full walkthrough.

What we got wrong (on the first try)

Two corrections this month.

• Margin % colour-coding was too binary. First version of the new card colour-coded margin green above 60% and red below. Bakeries (typical 40–55%) saw red on every product and assumed something was broken. We dropped the absolute thresholds and switched to a relative band — colour reflects how this product's margin compares to your trailing average for the category. Day 4 patch.
• Snapshot queue dropped writes during a brief outage. Two-hour database hiccup on Jan 17 caused about 40 snapshot writes to land out of order. Historical EBIT for the affected shops was off by less than €5 on the day. We rebuilt from the source entries and added a watchdog. Postmortem went out by email to the 11 shops involved.

What's next (February 2026)

February is the big multi-currency release. Eight new base currencies (CHF, GBP, DKK, NOK, SEK, PLN, CZK, HUF) joining EUR, set per location. Plus a full rewrite of the Statistics tab around five questions owners actually ask — heat-map calendar, runway card, insight tags, and a sharper product performance view.

Beyond February: team handover at shift change and two new locales in March, then the weekly view and mobile invoice scan in April. The products overview stays the canonical reference for the new card layout.

FAQ