Mixing manual entries and product sales on the same day is supported intentionally — but it's also where the only real "double-count risk" in nouz lives. Understanding the data model makes the safe pattern obvious.
01 Two storage tables
Under the hood, nouz has two separate tables for revenue:
revenue_entries— manual entries with cash + card columns, plus optional notes.revenue_product_entries— product sales with a snapshot of the product's price, COGS, and tax rate at the moment of the sale.
Both tables are scoped per location and per date. When the P&L computes a day, it reads both and sums them.
02 P&L sums all entries
A typical day: three product sales (€45 each) and one manual entry (€120). The P&L reads:
- Product sales total: €135 gross.
- Manual entries total: €120 gross.
- Day total: €255 gross.
There's no overlap risk because the two tables hold genuinely different rows. A product sale is never also a manual entry — and vice versa.
03 Avoiding double-counting
The only failure mode: you log a manual entry for the day's total and log individual product sales that overlap with it. Then you're counting the same revenue twice. The fix is conceptual: pick one mode per "chunk" of revenue. Either log products and a manual entry for everything-else, or log one manual entry for the whole day — never both for the same money.
04 The discipline rule
The cleanest pattern: think of each day's revenue as a pile of money. Every euro in the pile should be in exactly one entry — either a manual entry or a product sale, never both. The pile total = sum of entries. Anything else creates the double-count.
Was this article helpful?
Your vote helps us decide what to write next.