A refund is money you return to a customer for an order they already paid for. A cancellation voids an order, or some of its lines, usually before it is fulfilled. Both reduce your revenue, both are easy to count in the wrong place, and together they are the part of ecommerce profit that most stores get wrong. A sale collected today and returned two weeks later is not the same sale, and treating it as if it were makes your margin a work of fiction.
The typical mistake: mixing periods
The usual approach is to add up the month's sales and subtract the refunds processed that month. It looks reasonable, but it subtracts returns from orders that belong to an earlier month. Every month inherits part of the previous month's refunds and pushes part of its own into the next one. The result is a margin that rises and falls with the timing of your return queue rather than with how the business is doing.
Worked example: processing date vs original order
Take a hypothetical store. In May it sells 40,000 EUR of orders and in June 50,000 EUR (both net of VAT). Refunds arrive like this: 2,800 EUR of April orders are refunded in May; May orders are refunded 1,200 EUR in May and 2,000 EUR in June; June orders are refunded 1,000 EUR in June and 1,500 EUR in July.
| May | June | |
|---|---|---|
| Orders placed | 40,000 | 50,000 |
| Refunds by processing date | 4,000 (2,800 + 1,200) | 3,000 (2,000 + 1,000) |
| Refund rate by processing date | 10% | 6% |
| Refunds anchored to the original order | 3,200 (1,200 + 2,000) | 2,500 (1,000 + 1,500) |
| Refund rate anchored to the order | 8% | 5% |
| Net revenue, anchored | 36,800 | 47,500 |
By processing date, May looks like a bad month (10% refunded) and June looks like a big improvement (6%). Anchored to the original orders, May's real refund rate was 8% and June's was 5%. The trend is the same direction, but the size is wrong, and a team reading the first row would credit or blame the wrong campaigns, products and months.
Recent periods are provisional
Anchoring has one consequence you should accept openly: the numbers for recent days keep changing as late refunds arrive. If your return window is 30 days, last week's margin is an estimate that will come down. Label recent periods as provisional, or apply your historical refund rate as an expected deduction until the window closes.
Three rules to count them correctly
- Count the refund against the original sale, not against the period it is processed in.
- Distinguish a cancellation (voided order, usually not shipped) from a refund (money returned after payment, often after delivery).
- Include partial cancellations and partial refunds: lines removed from an order, a discount granted afterwards, a shipping fee returned.
What a refund really costs
Subtracting the refunded amount from revenue is only half the story. When an order comes back, several costs you already paid stay paid.
- Outbound shipping: the carrier delivered the parcel; you pay for it either way.
- Return shipping, if you provide or reimburse the label.
- Payment fees: many payment processors do not return the original processing fee on a refund. Check your gateway's terms.
- Handling: inspecting, repackaging and restocking take time or a 3PL fee.
- Product cost, when the item cannot be resold or is not worth shipping back.
- Ad spend: the money you spent to acquire the order is gone.
Worked example: one returned order
A hypothetical order with a net price of 60 EUR, product cost 18 EUR, outbound shipping 5 EUR, payment fee 1.50 EUR and an acquisition cost of 15 EUR. A return costs 6 EUR in shipping and 2 EUR in handling.
Kept order profit = 60.00 − 18.00 − 5.00 − 1.50 − 15.00 = 20.50 Returned, resellable = 5.00 + 6.00 + 1.50 + 15.00 + 2.00 = 29.50 lost Returned, not resellable = 29.50 + 18.00 = 47.50 lost Kept orders needed to cover one unsellable return = 47.50 / 20.50 = 2.32
In this example, a single return the store cannot resell wipes out the profit of more than two kept orders. Even when the item goes back on the shelf, the loss is 29.50 / 20.50 = 1.44 kept orders. That is why the refund rate belongs next to ROAS when you judge a product or a campaign: a product with a strong ROAS and a high return rate may be worse than a quieter one.
Cancellations are cheaper, but not free
A cancellation before fulfilment reverses the revenue and usually avoids product and shipping costs. What remains is the payment fee, if your processor keeps it, and the ad spend that brought the customer in. For your margin, a cancelled order is an order you paid to acquire and earned nothing from.
Partial cancellations
Say an 80 EUR order has two lines, 50 EUR and 30 EUR, and the 30 EUR line is removed because it is out of stock. Revenue becomes 50 EUR and that line's product cost is no longer incurred, but the acquisition cost was paid for the full basket. If your report still shows 80 EUR, or drops the order entirely, both your average order value and your margin are wrong.
Chargebacks and disputes
A chargeback is a refund forced by the customer's bank. It reverses the payment, processors usually add a dispute fee, and you may lose the product too. Count it like a refund against the original order, plus the fee. If you win the dispute, reverse the deduction on that same order.
Putting it into your profit formula
Net revenue = Gross sales − Refunds and cancellations (anchored to the original order) Refund costs = Return shipping + Handling + Unrecovered product cost + Dispute fees Net profit = Net revenue − COGS − Shipping − Payment fees − Refund costs − Ad spend
Then look at the refund rate by product, by campaign and by country. A high refund rate in one market or on one product usually points to something fixable: a size guide, a misleading creative, a carrier that damages parcels or a delivery promise you are not keeping.
A profit that doesn't count returns properly isn't optimistic, it's fiction.
Doing it automatically
Doing this by hand means matching every refund line from Shopify to its order and date and redoing the month each time a late return comes in. ProfitFly anchors every refund and cancellation to its order and its correct date, so your daily margin reflects reality and not an artifact of the accounting calendar.
Frequently asked questions
What is the difference between a refund and a cancellation?
A cancellation voids an order, or some of its lines, usually before it ships. A refund returns money for an order that was already paid, often after delivery. Refunds usually cost more because shipping and handling have already happened.
Should refunds be counted on the day they are processed?
For cash flow, yes. For margin and product or campaign decisions, count them against the original order and its date, otherwise each period carries returns from earlier sales.
Do I get the payment fee back when I refund an order?
Often not. Many payment processors keep the original processing fee on refunds. Check your gateway's terms and include unrecovered fees as a refund cost.
How do I handle refunds that arrive after I have reported a month?
Treat recent periods as provisional and update them when late refunds arrive, or deduct an expected refund rate based on your own history until the return window closes.