Revenue caps are how nouz prices fairly across shop sizes. A €40k/year café shouldn't pay the same as a €400k/year one — but neither should be charged based on what they make, just what tier of capacity they need.
01 How is the revenue cap measured?
Every revenue entry contributes its gross amount (cash + card) to your running year-to-date total. That total starts at zero on January 1st each year and climbs as you log. nouz compares the current value against your plan's cap — that ratio is what drives the warning banner and the block. The cap is on gross revenue, VAT included, not on net.
Math lives in lib/billing/revenue-cap.ts and is computed server-side on every revenue write — so the check is authoritative, not browser-trusted.
02 What happens at the 80% and 100% thresholds?
The warn fires at 80% so you have time to upgrade calmly, not in a panic.
03 When does the revenue cap reset?
On January 1st, the YTD count resets to zero. If you crossed your cap in December, you start fresh in January at €0 of €100k (or whatever your plan's cap is). You don't have to do anything — the reset is automatic.
04 Why is there a revenue cap at all?
There are two reasons for the cap, and both come back to fairness. A bigger shop uses more of our infrastructure, so tying price to a capacity tier keeps pricing honest across shop sizes. And the cap doubles as a natural upgrade trigger — when your shop grows out of Starter, the number tells you, so you don't sit on the wrong plan forever. The details below cover each.
- Fair pricing. A bigger shop uses more of our infrastructure (more entries, more queries, more support volume). Tying price to capacity tier is the cleanest fairness model we found.
- Natural upgrade trigger. When your shop grows out of Starter, the cap tells you. Without it, you'd stay on the wrong plan forever and feature requests would diverge from what your shop actually needs.
Was this article helpful?
Your vote helps us decide what to write next.