In this article
The marketplace keeps a larger percentage of each transaction, yet has less money left to fund the business. That can happen without any contradiction. Take rate describes the fee relative to transaction value; it does not tell the team what delivering those transactions cost.
Before increasing a fee or celebrating a richer mix of orders, build a transaction-level bridge from customer spend to the amount retained after defined costs. Keep the definition stable enough that product, operations and finance can explain the same result.
Start with the transaction, then follow the adjustments
Choose a unit with an identifiable beginning and end: an order, booking or completed service. Record the original customer amount, the platform fee and the supplier’s share. Attach later refunds, fee reversals, payment expenses and platform-funded incentives to that original transaction.
a16z’s marketplace metrics framework distinguishes GMV from marketplace revenue. That distinction is the starting point: money passing through a marketplace is not all money the marketplace keeps.
Define what your GMV includes before calculating a rate. Taxes, tips, shipping and pass-through charges can change the denominator without changing the underlying service. This article’s example excludes them so the arithmetic stays visible. Your operating report should follow an agreed definition and reconcile to the systems that hold the actual transactions.
Compare two fully specified order cohorts
The following cohorts are invented. Each contains 100 originally completed orders at $100 per order, producing $10,000 of original GMV. All relevant refunds have arrived by the observation cutoff. Cohort A has ten fully refunded orders; B has fifteen. The platform reverses its fee proportionally on refunded value.
Payment costs, incentives and support allocations are assumed amounts, not provider prices. Incentives are funded by the platform and are not already deducted from the fees shown. The example has no other transaction-variable costs; a real marketplace should add any it bears.
| Ledger item | Cohort A | Cohort B |
|---|---|---|
| Original completed orders | 100 | 100 |
| Original GMV | $10,000 | $10,000 |
| Fee rate on original GMV | 20% | 25% |
| Original platform fees | $2,000 | $2,500 |
| Refunded GMV | $1,000 | $1,500 |
| Platform fees reversed | $200 | $375 |
| Net GMV | $9,000 | $8,500 |
| Retained platform fees | $1,800 | $2,125 |
| Payment costs | $300 | $350 |
| Platform-funded incentives | $300 | $700 |
| Allocated variable support | $200 | $400 |
| Contribution after listed costs | $1,000 | $675 |
| Contribution per original order | $10.00 | $6.75 |
Net take rate is retained fees divided by net GMV: $1,800 / $9,000 = 20% for A and $2,125 / $8,500 = 25% for B. But B’s higher retained fees are more than offset by its larger listed costs. Contribution falls from $1,000 to $675.
This comparison does not show that raising the fee caused higher refunds or support costs. The cohorts are fictional, and even observed cohorts could differ in customer mix or service complexity. It shows which quantities the team must inspect before drawing a conclusion from take rate alone.
Keep the denominator through the refund
Contribution per original order uses all 100 orders in each cohort. That preserves the cost of orders that later refunded. Dividing only by the remaining unrefunded orders would answer a different question and could conceal how expensive unsuccessful transactions were.
Keep a second view if the team needs contribution per retained order or per buyer. Name it explicitly and preserve the original-order view alongside it. An operational change that reduces failed orders can improve total economics even if the surviving orders’ average fee barely changes.
Use the same observation age when comparing cohorts. A new cohort with few recorded refunds may simply be too young. Define a cutoff suited to the marketplace’s refund and service cycle, show immature cohorts separately, and revise results when late adjustments arrive.
Follow the actual money movement
A refund in the customer interface does not necessarily reverse every connected transfer or fee. Stripe’s destination-charge documentation describes separate controls for reversing a transfer and refunding the application fee. By default, refunding the charge does not automatically reclaim the transferred funds from the destination account.
That behavior is specific to the documented payment flow. The broader product requirement is to reconcile the customer refund, supplier recovery and platform fee adjustment separately. Otherwise, the marketplace may report a fee it returned, assume it recovered money it still bears, or count one adjustment twice.
For each transaction, preserve the gross charge, refunded amount, transfer recovery and fee reversal with their settlement status. Unresolved adjustments belong in an exception view. Do not quietly treat them as settled simply to close the monthly product report.
Decide which costs belong in the comparison
The example subtracts payment costs, incentives and allocated variable support. It does not deduct product development, central administration or other fixed overhead. Its contribution figure is therefore not operating profit.
Use costs that vary with the transaction or are deliberately allocated to the intervention being evaluated. If a new service requires manual dispatch, include that work under a stated cost-per-minute or per-case assumption. If refunds create extra support, avoid hiding those cases in a general overhead bucket while crediting the full fee to the product change.
Keep cash-funded discounts separate from supplier-funded discounts. If an incentive already reduced retained fees, do not subtract it again. Apply the same principle to payment fees recovered from suppliers and to taxes collected for another party. A short definition beside each line prevents a surprisingly large amount of confusion.
Sensitivity matters when allocations are rough. Show the result under a plausible lower and higher support cost rather than presenting an estimate as an exact transaction expense. The operational decision should survive reasonable uncertainty in the assumptions that matter most.
Use the ledger to choose a narrower change
In the example, B earns $325 more retained fees but spends $650 more across the listed costs. The immediate investigation belongs in incentives, support and refunds. A second fee increase might compensate for those costs, but it would leave the cause unresolved and could affect supplier participation or buyer demand.
Compare similar services, markets and order sizes before attributing differences to pricing. Then decide whether to change the fee, reduce an avoidable operational cost, narrow an incentive or stop offering an uneconomic transaction type.
For choosing what to charge against, see pricing metrics. For connecting order economics to acquisition and repeat use, use a product growth model. Bring the ledger to either discussion: original value, retained fee, named costs and the amount left per original order.
Sources
Something we should clarify?
Suggest a correction


