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 the cap is measured
Every revenue entry contributes its gross amount (cash + card) to your running YTD total. The total starts at zero on January 1st each year. The current value vs. your plan's cap is what nouz tracks for the warning banner and block.
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 The 80% warn, 100% block
The warn fires at 80% so you have time to upgrade calmly, not in a panic.
03 When the cap resets
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 a cap at all
Two reasons:
- 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.