This is the per order version of our true cost work. Our True Cost Calculator does the same plain arithmetic for hosting bills, and What WP Engine really costs walks through one host line by line. This page does it for the product sitting in the box.
Your numbers
What the customer pays for the product itself.
What the product costs you.
Box, tape, label, inserts. The small stuff counts.
Picking a gateway fills in the two rate fields below with the published default. Your own contract beats our default, so overwrite the fields if your rate differs.
Used by the price solver below. It works out the selling price that would leave this margin after fees and returns.
The fee stack, line by line
| Line | Amount |
|---|---|
| What the customer pays | $55.00 |
| Product cost | $20.00 |
| Your shipping cost | $6.00 |
| Packaging | $1.00 |
| Gateway fee (2.9% of $55.00 + $0.30) | $1.90 |
| Expected return losses per order (spread across all orders) | $0.00 |
| Margin | 47.46% |
| Monthly profit at this order count | $5,221.00 |
Expected profit per order
$26.11
After the full stack lands, this order keeps money. Check the margin line above, and test it against a higher return rate before you trust it.
To keep a 20% margin after fees and returns, this product needs to sell at $30.41.
Money figures round to cents for display. The calculator keeps full precision underneath, so a line can look a cent off if you add the rounded numbers by hand.
The gateway rates we start from
These are the published defaults the gateway picker fills in. Each one was read on the provider's own pricing or fees page. If your account has a negotiated rate, type yours over the top. Yours is the one that counts.
- Stripe: 2.9% + $0.30 per successful card charge. Source: Stripe's pricing page. Checked November 19, 2026.
- WooPayments: 2.9% + $0.30 for US cards. Source: WooCommerce's fees documentation. Checked November 19, 2026.
- PayPal Checkout: 3.49% + $0.49. Source: PayPal's merchant fee schedule. Checked November 19, 2026. Note: PayPal's standard card rate on that same schedule is 2.99% + $0.49, so check which rate your account actually uses and type it in if it differs.
- Custom: starts at 2.9% + $0.30 as a placeholder. Replace both fields with the rate on your own statement.
How the math works, in plain words
Say a product sells for $40, shipping is free to the customer, it costs you $26, shipping out costs $9, and packaging is $2. On paper that order earns $3. Now run the stack. PayPal Checkout at 3.49% + $0.49 takes $1.89 off the $40 the customer paid, which leaves $1.11. Then count returns. If one order in ten comes back, the shipping, packaging and gateway fee on that returned order never come back, and spread across every order that drags the expected profit below zero. A price that looked fine in your head can lose money once the full stack lands. That shape, a small seeming profit wiped out by fees and returns, is the whole reason this page exists. It is an illustration with round numbers typed into this same calculator, and you can reproduce it above.
The assumptions, stated up front
- The gateway charges its fee on the whole amount the customer pays, product price plus any shipping you charged. That total is the first line of the table.
- Gateways do not refund the gateway fee when an order is returned. The fee is gone either way, so it sits in both the kept order and the returned order math.
- A returned order gets refunded, and the product comes back to the shelf, so the product cost is not lost on a return. What never comes back on a return is your shipping cost, the packaging, and the gateway fee. We call that the return loss.
- Expected profit per order blends the two outcomes: the share of orders you keep, times the kept order profit, minus the share returned, times the return loss.
- Taxes are left out. Sales tax you collect passes through to the tax authority, so it is not your revenue and not your cost here.
- Hosting, apps, your time and ad spend are left out too. This is the profit on one order before overhead, the number a product has to clear before overhead even gets a say.
Questions store owners ask about this math
Why does the gateway fee apply to the shipping I charge?
Because the gateway processes the payment, and the payment is the full amount the customer paid at checkout. If a customer pays $50 for a product and $5 for shipping, the card charge is $55, and the percentage fee runs on $55. That is why the first line of the table is the full amount paid, and why free shipping offers still carry a fee cost on the product price.
Why spread return losses across every order?
Because returns are a cost of selling the orders that stay sold. One returned order loses the shipping out, the packaging and the gateway fee, and no single order causes that on its own. Spreading the expected loss across all orders gives you one honest number per order, the number you can compare against a price change or a cheaper box.
What price should I charge?
Start with the solver. Type in the margin you want to keep after fees and returns, and it works backwards to the selling price that leaves it, given your costs. If it says the target cannot be reached at any price, the math is telling you the fee and return load eats the whole margin before price can fix it. At that point the levers are cost, shipping charges and the return rate itself. Price alone cannot carry it.
Want the same treatment for the bill behind the store? Run the True Cost Calculator for your hosting costs, or read What WP Engine really costs for a worked example with overage fees included.
What costs are not in this math?
The costs that arrive as incidents instead of line items. Owners in the groups we read describe card-testing floods: dozens of bogus orders in a day, stopped by the payment provider, paid for in cleanup time and sometimes dispute fees. Every store's share of that is different, so it stays out of the calculator. If it happens to you often, it belongs in your packaging line as a few cents an order, spread the same way returns are.