Method · 5 min read
Pocket margin: the seven steps between gross revenue and what you keep
Gross margin is a comfortable number. It stops at the cost of goods, which means it stops before the rebate, the return, the pallet you shipped and the commission the marketplace kept. Pocket margin keeps walking.
The question it answers
Most margin reports end one step too early. They subtract the cost of goods from net revenue and call the result the truth. Everything that happens off the invoice - the year-end rebate, the credit note, the freight, the listing fee - lands in an overhead line somewhere, where nobody can attribute it to a product.
Pocket margin puts those steps back where they belong, product by product, and shows which one moved. It is an accounting walk, not a model: every step is a column you mapped, and nothing is estimated.
The cascade, step by step
Three subtractions, in this order:
- Gross revenue − net revenue = the on-invoice discount. It has no column of its own; it is what the two amounts already say.
- Net revenue − rebates − returns = pocket revenue. The deductions that reduce what the customer effectively paid.
- Pocket revenue − cost of goods − freight − commissions − cost to serve = pocket margin. The deductions that reduce what the sale left you.
The catalogue of deductions is closed at five on purpose. A sixth would need a definition, not a checkbox - and an open list is how a cascade quietly becomes a dumping ground.
The two things only you can say
How each deduction is written. An export writes a rebate as +50 or as −50 depending on the tool that produced it, and nothing in the values themselves settles it. So the tool asks: you say how each one is written, per column, and it never guesses. A deduction read the wrong way round would add to the margin instead of reducing it, and the total would look perfectly normal.
Whether your net revenue is already after returns. In many exports it is. Mapping a returns column on top of that would deduct them twice, and no total on the screen would reveal it. You answer once; if you say the net is already after returns, the returns column becomes unavailable rather than merely discouraged.
Anything you do not have stays unmapped, and counts as zero - not as unknown. A file with no freight column is a perfectly valid file.
What it looks like on a small file
The sample that ships with the tool covers two half-years. Pocket margin falls from 1,108 to 892 - a drop of 216.
A gross margin report would have shown a smaller fall and blamed the cost of goods, which actually helped by 90. The cascade shows where the money went instead: net revenue took 250 off, and the off-invoice rebate another 60, while freight and commissions roughly cancelled each other out.
Four reconciliation checks hold the walk together: gross to net, net to pocket margin, the sum of the signed contributions against the change, and the sum of the products against the total.
Build yours
Your own cascade, in your browser
Drop an export with gross revenue, net revenue, a cost, and one column per deduction you have. It all runs inside your browser: nothing is uploaded, which you can check in the Network panel while you work.
Start a monthly reviewWhat it will not do
Pocket margin is an accounting calculation on the deductions in your file. No fixed cost or overhead is allocated, and nothing here is a recoverable amount. That sentence travels with the result, into the review pack and the workbook.
It will not spread your fixed costs across products. An allocation needs a key - headcount, floor space, machine hours - that somebody has to validate. Inventing one would make an arbitrary choice look like a measurement.
It will not check your sign conventions. It shows them next to the figures, on screen and in the pack, so a reader three weeks later can see what was declared. It cannot tell you that a declaration was wrong - only make it visible enough to be challenged.
It will not find deductions you did not map. What is not in a column is not in the cascade.
Questions
What if my net revenue already includes returns?
Say so, and the returns column becomes unavailable. That is the single most expensive mistake in this analysis, because double-counted returns look exactly like a real decline.
What if I only have some of the five deductions?
Map what you have. An unmapped deduction counts as zero, and the cascade says so rather than leaving a hole.
How is this different from a margin bridge?
A margin bridge explains why margin moved: price, cost, volume, mix. This explains what the price became on its way down. Read the bridge to narrow the search, then this to end it.
Does my file leave the browser?
No. The whole calculation runs in the page, on your machine. How to verify that in two minutes.