Changelog

This is the changelog. Every month the nouz product team writes down what shipped, why we built it, and what we got wrong on the first try. If you run a café, a shop, a salon or a small online store, you do not have time to dig through release notes. You want to know one thing: did anything change that affects how I track today's profit, and do I need to do anything about it? These posts answer exactly that, in plain language, with no jargon and no marketing gloss.

Most of what we ship is small on purpose. A keyboard fix that shaves a few seconds off your evening entry. A screen rewrite that loads faster. A new locale so the app speaks your language at the till. Occasionally we change something bigger, like how fixed costs are modeled over time, and when we do, we explain the reasoning so you can trust that your historical numbers still mean what they did yesterday. Reading the changelog is the quickest way to understand how nouz is evolving around the daily routine you already keep.

Monthly release notes

Each month gets its own post covering the handful of things that actually shipped. We tell you what is new, who it helps, and whether it touches your daily close-out. Quieter maintenance months get the same honesty as the big ones, because a bug fix that removes a daily annoyance often matters more to you than a flashy feature.

Bigger model changes

Now and then we change how the underlying numbers work, like giving fixed costs proper start and end dates so a mid-cycle rent increase models correctly without rewriting your past P&L. These are the posts to read closely. We walk through what changed, why it was the right call, and the rule we hold to: editing something today never quietly rewrites your history.

Looking back and looking ahead

A few times a year we step back from individual features to take stock. Year-in-review pieces look at what landed, what we learned from real support tickets, and what is shaped up next. These give you the bigger arc, so you can see where nouz is headed and decide whether anything on the roadmap is worth waiting for.