- nouz
- Methodology
Methodology
How every number on this site is computed.
Every figure we publish comes from one of three places: the engine that runs the product, a vendor's own published page on a stated date, or a named regulation. This page says which, and what we refuse to do.
On this page, 7 sections
- 01 The engine is the only source of our own figures
- 02 The example store, and why it is not customer data
- 03 The recognition rules behind every figure
- 04 Competitor prices, and how they are dated
- 05 What we refuse to publish
- 06 What the calculators share with the product
- 07 When something here is wrong
- In short
A site that publishes numbers about money owes its readers an account of where they came from. This is that account, and it is deliberately short enough to check.
01 The engine is the only source of our own figures
Every euro figure on this site that describes a store, from the worked example inside a calculator to the fourteen-month anatomy in a data study, is computed by the same code that computes a paying customer’s profit and loss statement. Nothing is typed in by hand, and nothing is rounded into a nicer shape for a headline.
That matters most where a page shows two numbers at once. A waterfall beside a screenshot, a table beside a calculator default, a study beside a glossary definition: all of them read from one run of one engine, so they cannot drift apart while somebody edits a paragraph.
- 7Gross Revenue€40.607,66
- 10Returns−€688,23
- 12Taxes−€5.623,45
- 17COGS−€13.112,01
- 21Logistic Costs−€3.184,63
- 23Transaction Costs−€1.090,13
- 27Marketing Costs−€7.488,86
- 31Overhead Costsone day's share−€1.112,23
…20 August closed at €40.607,66 of gross revenue and €8.308,12 of EBITDA, and every column between the two is a cost that was booked to that day on purpose.Read the entry
…€40.607,66 of gross revenue ends as €8.308,12 of EBITDA once returns, VAT, goods, logistics, payment fees, marketing and one day's share of overhead have each taken their piece.Open the template
02 The example store, and why it is not customer data
Our worked examples come from a generated store: a realistic catalogue, fourteen months of orders, refunds, discounts, several payment gateways, shipping zones with weight brackets, packaging fees and a fixed cost book. It is priced by the real engine under the real recognition rules, and it is not any merchant’s business.
We use it because the alternatives are worse. Real customer data cannot be published, and invented benchmarks presented as industry figures are the thing this category does far too much of. A generated store is honest about being one, and every page that uses it says so.
03 The recognition rules behind every figure
Sales and their cost of goods belong to the order date. Refunds belong to the day the refund was issued, never backdated against the order they reverse. Advertising belongs to the day it was spent, taken from each platform’s billing side rather than from attributed revenue. Recurring fixed costs are spread across the days they cover, and one-off costs land on the day they were booked. Every date is in the store’s own timezone.
Costs carry the day they took effect, so an order is priced by the rule that was true on its own date, and a later cost change never rewrites a closed day. Cancelled and test orders are excluded everywhere. VAT is removed from what was kept rather than from what was sold, so a refund hands its tax back too.
| Amount | Belongs to | Statement line |
|---|---|---|
| Sales | The order date | to |
| Cost of goods | The order date | |
| Refunds | The day the refund was issued, never backdated against the order it reverses | |
| Advertising | The day it was spent, from each platform's billing side rather than attributed revenue | |
| Recurring fixed costs | Spread across the days they cover | |
| One-off costs | The day they were booked | |
| Cost rules | The day they took effect; a later change never rewrites a closed day | every cost line |
| VAT | Removed from what was kept, not from what was sold | |
| Cancelled and test orders | Excluded everywhere | every line |
Every date is in the store’s own timezone.
04 Competitor prices, and how they are dated
Every competitor price on this site was read from that vendor’s own published page and carries the date it was checked, in the prose rather than in a footnote. When we write or revise a comparison we re-read the pricing pages that day rather than trusting an earlier note, because prices in this category move within weeks.
Our own prices are never typed into an article at all. They are interpolated from the same plan data the checkout charges from, so a page cannot quote a price the product does not sell.
Monthly price for one store at four volumes, checked 1 Oct 2026; the nouz row is read live from its plans.
| Plan | On Shopify | Direct, net |
|---|---|---|
| Base | $55 | €49 |
| Pro | $115 | €99 |
| Scale | $289 | €249 |
05 What we refuse to publish
- Ratings, review scores or star countsfor ourselves or anybody else, including in structured data where only a crawler would see them.
- Testimonials or customer quotesthat were not given for publication by a named merchant.
- Industry benchmarkswe did not measure, and survey figures we did not run.
- Maintained rate tablesfor packaging schemes or payment gateways, because those are quoted privately and revised annually; every calculator takes the merchant’s own rate as an input instead.
- Compliance advice.We compute what a regulation costs, never who must register or what is owed.
06 What the calculators share with the product
The public calculators are not a separate implementation. Each one runs the same arithmetic the statement uses, and a test feeds a real engine statement back through every calculator and requires it to reproduce the engine to the cent, including on a split payment. A public tool that disagreed with the product by a cent would undo the one thing the product sells.
Every result row carries the statement line number it corresponds to, so a figure in a calculator can be traced to the line it would occupy on a real profit and loss statement.
07 When something here is wrong
Two things have already been corrected rather than quietly adjusted: a claim about how Shopify handles historical unit costs, and a rounding rule that lost a fraction of a cent on every parcel. Both are described in the posts they affect. If you find another, tell us and it will be fixed with the correction visible rather than the page silently rewritten.
- Correction 1
A claim about how Shopify handles historical unit costs.
Described in Historical COGS on Shopify: what the cost field keeps, and what it cannot1 Sep 2026 - Correction 2
A rounding rule that lost a fraction of a cent on every parcel.
Described in The rounding drift: how a cent a parcel became €600 a year1 Sep 2026 - The next one
Found a figure that does not add up? It gets fixed here, with the correction visible.
In short
One engine, one example store, and a date on every borrowed number.
If a figure on this site cannot be traced to one of those three, it should not be here. That is the whole rule.
Keep reading
Everything else we have written down.
- BlogHow margin actually behaves in an ecommerce business.
- GlossaryEvery term on a nouz P&L, defined in plain language.
- Help centreConnecting, costing, syncing and billing, answered.
- Templates15 free spreadsheet templates with the columns nouz uses.
- Calculators32 free calculators for margins, break-even, fees, ads, stock and packaging.
Every rule above, applied to your own store.
Install nouz in minutes from the Shopify App Store. It imports every order your store has ever taken and prices each one by these rules. Cancel anytime.