Quick Answer
Define the commissionable base and who pays before choosing a percentage. Work backward from attributable processing, payout, support and loss costs plus a contribution target. Test low-value and cross-border segments separately, then reconcile fee decisions and measure buyer and seller behavior in a controlled rollout.
Key Takeaways
- Fee base, GMV and contribution are different measures; define all three.
- Fixed costs can make a low-value sale unprofitable at the same percentage as a larger sale.
- Provider pricing depends on country, account product and seller program.
- A higher headline rate can reduce total contribution if participation or conversion falls.
- Keep seller liability, holds, adjustments and payout separate in reconciliation.
How to Choose a Marketplace Commission Rate#
Start with the fee base, costs and contribution you need per order. Then test whether buyers and sellers will accept the resulting price. A headline 10% can work for one order segment and lose money in another because fixed transaction and support costs consume more of a small sale.
| TCGplayer fee component | Published basis | Scope |
|---|---|---|
| Marketplace commission | 10.75% of order subtotal; $75 cap per product | Level 1–4 marketplace seller |
| Transaction fee | 2.5% of items + shipping + tax, plus $0.30 | Usual domestic marketplace order; international order rate is 3.5% + $0.30 |
| PayPal payout adjustment | 2%, capped at $20 | Non-US sellers paid through PayPal; separate account adjustment |
As of October 2026, TCGplayer’s fee page lists distinct seller programs and calculation bases. Its Level 1–4 marketplace commission is 10.75% of the order subtotal, with a $75 cap per product; the usual transaction fee is 2.5% of the order total including shipping and tax, plus $0.30. International-order transaction fees and non-US PayPal payout adjustments differ. A cap on one component does not cap the whole seller charge.
Use examples to identify fee components, not to import another marketplace’s rate. Your value to sellers, order mix, service costs and buyer behavior determine whether the same structure works for you.
Start with the economics that actually matter#
Define the retained platform fee and contribution by segment. Here, contribution means platform fee revenue less the attributable payment, payout, loss and operating costs you include in the model. Dividing that contribution by the defined GMV gives the contribution rate; it is not the seller’s retained share or company-wide profit margin.
| Stripe US standard online-card input | Published amount | Applies when |
|---|---|---|
| Domestic card baseline | 2.9% + 30¢ per successful transaction | Published domestic card baseline |
| International card add-on | +1.5% | International cards |
| Currency conversion add-on | +1% | When currency conversion is required |
Use clear definitions up front:
- Commission rate: platform fee divided by its expressly defined commissionable base.
- Contribution: platform fee revenue plus other allocated revenue, less the attributable costs in the model.
- Contribution rate: that contribution divided by a consistently defined GMV; keep company fixed overhead separate.
For a US account on Stripe’s standard online-card pricing, the published domestic rate is 2.9% + $0.30, with 1.5 percentage points added for international cards and 1 point if currency conversion is required. These are processing inputs, not an all-in marketplace quote: Connect, payout or other product charges may also apply. PayPal rates likewise depend on the product and account.
You can model a proposed rate before implementing it. Before rollout, reconcile sample calculations to the provider’s actual pricing and verify who bears each fee so an expense or pass-through revenue is not counted twice.
Choose who pays before you choose the percent#
Test the fee payer as part of the commercial model. A buyer fee can reduce the seller deduction but increase the buyer’s total; a seller fee can still influence the seller’s listing price. Neither design guarantees better conversion. Compare total prices, seller participation and contribution in a controlled cohort.
Distinguish the contractual fee payer from economic incidence. Sellers may raise prices to recover a charge, and buyers may change purchases in response. State who is invoiced, then measure how behavior and total prices change.
Seller-paid vs buyer-paid vs split: use as test hypotheses#
| Design | Conversion risk | Seller acquisition friction | Margin predictability | Support burden | Communication complexity |
|---|---|---|---|---|---|
| Seller paid | Lower buyer-price surprise risk when pricing is clear | Seller participation can fall if the deduction exceeds perceived value | Often easier to model per transaction | Lower to medium | Lower |
| Buyer paid | Higher risk if fee visibility is late or unclear | Lower for seller activation | Depends on buyer response and the fee base, not just presentation | Medium to high | Medium to high |
| Split fee | Balanced but sensitive to implementation details | Medium | Medium to strong when rules are explicit | High on refunds/disputes if policy is unclear | High |
Compare fee bases and refund treatment#
For each relevant competitor, compare the same seller program, region, category and order value. Record the fee base, percentage, fixed charge, caps, payout adjustments and refund treatment. The published headline is only one column.
If you test explicit buyer fees, prioritize clarity over internal margin optics: disclose early, use plain labels, and keep receipt/refund wording consistent across product, support, and finance. If you need both access fees and transaction fees, treat it as a deliberate hybrid model, not incremental add-ons; see hybrid pricing models.
Related: How Interchange Fees Change the Price You Need to Charge.
Build the commission backward from net take by segment#
Work backward from attributable costs plus the target contribution. If subscriptions or other fees also fund the order, allocate that revenue explicitly rather than pretending commission must recover everything alone.
Model costs at the segment level first, not marketplace-wide. A domestic payment and an international order should not share one cost assumption.
Use the PayPal US merchant fee schedule for the exact product, currency and domestic or international classification. Do not blend card, PayPal-wallet and Pay Later rates into one assumption. Custom contracts, payout fees and dispute charges can change the modeled result.
Reference inputs#
| Input | What to model | Verification checkpoint | Confidence grade |
|---|---|---|---|
| GMV | Order value and order mix by segment | Use ledger-backed orders split by market, payment method, and seller type | A = measured, B = sampled, C = forecast |
| Payment processing | Processor percent + fixed fee per transaction | Record product, account market, contract or published schedule, currency and retrieval date | A = billed/contracted, B = current published pricing, C = estimated |
| Payout costs | Payout fees and method differences | Check the specific payout product (PayPal has a dedicated Payouts section) | A/B/C |
| Fraud and dispute allowance | Chargebacks, dispute fees, refund leakage | Use segment-level dispute data; PayPal has dedicated Chargeback Fees and Dispute Fees sections | A/B/C |
| Compliance overhead | KYC/KYB, tax review, reconciliation, manual ops | Translate team/vendor effort into per-seller or per-order cost | A/B/C |
| Support load | Tickets driven by fees, refunds, payout confusion | Tag fee-related tickets so estimates can be replaced with measured cost | A/B/C |
| Target contribution margin | Required margin after variable costs | Confirm target with Finance before pricing tests | A = approved, C = aspirational |
Use the equation in the right order#
For one defined fee base, commission revenue needed = attributable costs + target contribution − other allocated platform revenue. Required commission rate = that revenue divided by the commissionable base. Convert fixed per-order costs using the same base and period. If the fee base differs from GMV, do not divide by GMV and present the result as the checkout rate. If a buyer fee is added to the charge, processing may apply to the enlarged total. Recalculate that cost before solving the rate; a fee deducted from seller proceeds does not enlarge the buyer charge.
A common failure mode is one blended processor assumption across all orders. That hides margin erosion in low-AOV orders, international corridors, and higher-cost payment methods. Keep an evidence pack for each assumption: fee page, update date, market, payment method, and confidence grade.
If the result exceeds likely price tolerance, change the economics or structure: reduce cost-to-serve, introduce a transparent minimum, add paid services or revise who funds the fee. Raising a percentage alone cannot fix a model that customers reject.
Worked example: the fixed-cost effect#
The following examples assume the commission is deducted from the seller’s proceeds, so the buyer charge stays at the stated sale amount. Assume a $100 commissionable sale, with no shipping or tax in this simplified example. US domestic card processing at 2.9% + $0.30 costs $3.20. Assume another $0.50 for payout, $0.80 for support and $0.50 for expected loss, for $5 of attributable cost. A $3 contribution target requires $8 of platform fee revenue: an 8% rate. At 10%, fee revenue is $10 and modeled contribution $5. The non-processing costs and target are illustrative assumptions.
On a $20 sale with the same $1.80 of other costs, processing costs $0.88, so total cost is $2.68. Keeping the same $3 contribution target requires a $5.68 fee, or 28.4%. At 10%, contribution is −$0.68. You might instead reduce the fixed cost, change the target or test a disclosed minimum. This arithmetic does not prove customers will accept that price.
Price for cross-border reality and compliance overhead#
Model cross-border segments separately where processing, FX, payout or review costs differ. Segmented rates are one option; a transparent payout charge or paid service may fit better. Do not charge more merely because a corridor feels complex—use measured costs and commercial evidence.
Where cross-border cost actually rises#
KYC, KYB, and AML gates are not distributed evenly across seller types, corridors, or payout methods. An individual seller, a business seller, a domestic payout, and a cross-border payout can create different exception rates, manual review load, and support burden. Even with vendor tooling, retries, document collection, account restrictions, and escalations still add operating cost.
A practical pre-launch check is to split onboarding and payout exceptions by seller type and country pair, then compare approval time, manual touches, and support tickets. If you cannot produce that view, your compliance cost is still a guess.
Tax and reporting details that affect policy#
Tax and documentation workflows can add real operating work. VAT, GST/HST, W-8, W-9, and 1099 processes can change what data you collect, what gets validated, how support responds, and what records finance retains. Treat those as policy and pricing inputs early, not cleanup after launch. If Canada is in scope, review GST/HST platform fee rules.
Scope tax and reporting costs to the duties of the platform and seller under the actual program. Identify who collects transaction tax, who issues required reports and which tax-status documents are needed. Personal foreign-account reporting is not a routine commission-setting input for every cross-border marketplace.
Assign a tax or compliance owner to each applicable assumption and record its jurisdiction and review date. Keep amounts collected for a tax authority separate from platform revenue.
Translate the pricing model into product and payment operations#
Your pricing model only works when product, payments, and finance all land on the same number for the same transaction. If fee logic lives only in a spreadsheet, leakage usually shows up first at checkout and then gets exposed in payout and reconciliation.
Write fee events before you build flows#
Define fee events in the product spec before implementation: what is charged, when it is charged, what amount it uses, who pays it, and what happens on refund, retry, or reversal. A headline commission is rarely enough once minimums, subscriptions, listing fees, or category logic are in play.
| Fee example | Amount or timing | Note |
|---|---|---|
| Amazon US Individual plan | $0.99 per item sold | Separate from category referral fees |
| Amazon US Professional plan | $39.99 per month | Separate from category referral fees |
| Category referral fee | Category-specific percentage or bands and minimum where applicable | Check the exact category and defined total-price base |
The Amazon US pricing page separates the $0.99-per-item Individual plan and $39.99-per-month Professional plan from category referral fees and other services. Referral percentages, minimums and calculation bands depend on category. A seller plan subscription is not the same thing as a per-sale commission.
Version the pricing rule before using it at checkout. Record the fee decision and apply its accounting effect under the recognition policy; payout can occur later. Link seller liability, holds, adjustments and remittances rather than assuming every order fee equals a bank payout.
Make operational touchpoints explicit#
Keep fee components separate in transaction data so finance can explain outcomes without reverse-engineering configs. At minimum, keep gross amount, commission basis, flat fee, minimum fee trigger, seller net, buyer total, currency, and fee version clear and traceable.
If you are implementing on Gruv, keep API fields, webhook-driven async status updates, and ledger reporting aligned to one fee model. Also decide Merchant of Record and Virtual Accounts responsibilities upfront, because those choices can shift where costs and operational ownership land.
Catch leakage before customers do#
Most leakage comes from execution drift: stale fee configs, payout mapping mismatches, non-idempotent retries, and reconciliation breaks between product and finance views. Store the applied fee-rule version on each order and carry it through payout and ledger records so you can reconcile outcomes directly.
Before rollout, check a normal sale, partial refund, minimum-fee order, threshold crossing and unknown payout outcome with payment execution disabled during replay. Reconcile the applied fee, seller amount owed, holds and actual remittance separately. Resolve an unknown provider outcome before another submission.
You might also find this useful: Building Subscription Revenue on a Marketplace Without Billing Gaps.
The mistakes that make marketplaces undercharge or overcharge#
Most undercharging and overcharging comes from treating commission as a copied headline number instead of a tested operating model.
- Copying a "typical percent" without rebuilding your own margin stack. Pulling a rate from Reddit, Facebook, or competitor teardowns is a shortcut, not validation. Before approving a fee, require a segment-level margin view and primary policy pages or rate cards for any external reference.
- Treating seller-paid vs buyer-paid as a UI label. Partitioned pricing separates a base price from mandatory surcharges, and buyers may not fully process every price component. If you move part of the fee to the buyer, validate total-price perception and checkout behavior, not just modeled take rate.
- Hiding compliance and tax work inside "fixed overhead." If review, onboarding, or operations effort changes by segment, model it as variable cost. If a single percentage cannot absorb that effort, use a structure that reflects the real work instead of forcing one flat rule.
- Using one global policy where market mechanics differ. Compare exact categories, account products and markets against current primary schedules. Record which inputs are measured and which remain assumptions.
If you want a deeper dive, read Recurring Billing for Marketplaces: How to Charge Buyers and Pay Sellers on the Same Cycle.
Run a 90-day decision and validation checklist#
Use the following suggested 90-day cycle to test the fee model and seller response. The duration is an operating choice, not a guarantee that every seasonal effect or loss tail will be visible.
Convert the segment model into a dated decision record. Define GMV and commissionable base separately, specify fee revenue and attributable costs, and assign product and finance owners for the calculation and outcome measures.
| Phase | What to do | Evidence to keep | Decision rule |
|---|---|---|---|
| Weeks 1 to 2 | Gather baseline data by segment and lock definitions | Recent order history, current fee configs, payout paths, dispute and support cost views | Model provisionally if needed; reconcile the baseline GMV, fee revenue and attributable costs before approving a pilot |
| Weeks 3 to 5 | Model 2 to 3 fee structures and run sensitivity tests | Assumption log with confidence grades for conversion, seller activation, processing, payout, support, and compliance | If net take turns negative under realistic assumptions, change structure before testing at scale |
| Weeks 6 to 8 | Run a controlled test through your API and webhook events | Test cohort definition, fee calculation outputs, payout split records, and monitoring for conversion and seller activation | Stop for calculation defects or breached pilot guardrails; assess contribution and conversion together |
| Weeks 9 to 12 | Review outcomes and publish change rules | Ledger review, rollback criteria, approval record, versioned pricing memo | Keep, adjust or roll back using reconciled contribution and observed seller/buyer behavior |
Keep the market, seller program, product, fee base and retrieval date with every external fee assumption. Recheck material inputs when the provider changes its schedule or before expanding a cohort.
Measure onboarding effort per activated seller and allocate it over a stated expected volume or period. It is not automatically a per-order variable expense. Keep the allocation visible so low-volume sellers do not disappear inside an optimistic average.
Confirm the payment program supports your countries, currencies and intended collection-and-payout flow. A split calculation does not establish legal authority to hold funds or erase provider eligibility requirements. Match fee decisions to the actual ledger and provider reports.
If commission alone still misses margin targets, move to Hybrid Pricing Models: How to Combine Subscription Fees Plus Usage Charges on a Single Invoice or add recurring billing where value is ongoing rather than purely transactional.
For a step-by-step walkthrough, see Choosing Between Subscription and Transaction Fees for Your Revenue Model.
Test one segment before expanding#
Choose a rate that covers the modeled cost and contribution target, then test whether sellers participate and buyers convert. Keep the fee base, payer and adjustment rules visible in the same decision record.
If the checkout explanation, seller statement and finance calculation disagree, correct the rule before expanding. Preserve historical versions and issue traceable adjustments rather than silently repricing completed orders.
Review completed transactions after the pilot and compare contribution per order, total contribution, seller activation and buyer conversion with the baseline. A higher percentage can still produce less total contribution if volume falls.
Frequently Asked Questions
What percent should a marketplace charge as commission?
Work backward from your commissionable base, attributable costs and target contribution, then test buyer and seller response. There is no universal rate. For a seller-deducted commission, a $100 base with $5 of modeled costs and a $3 contribution target requires $8 of fee revenue, or 8%, before other allocated revenue. An added buyer fee can increase the processing base, so its required amount needs a separate calculation.
Is a 10% commission actually "typical," or just a rough starting point?
Treat 10% as a hypothesis until the segment math and pilot support it. The same percentage generates $10 on a $100 base and $2 on a $20 base; fixed processing, support and payout costs can make those very different businesses.
Should payment processing fees be included in commission planning or treated separately?
Include processing costs in the model even if the seller pays them separately. Record the corresponding revenue or reimbursement consistently so you do not count the same cost twice. Reconcile the actual provider charge, commission base and seller statement before expanding the fee.
How do I decide whether buyers, sellers, or both should pay marketplace fees?
Choose based on where your conversion risk sits. If seller acquisition and onboarding are the bottleneck, test buyer-paid or split-fee structures. If checkout conversion is fragile, lean toward seller-paid and keep buyer pricing simple. Also remember that marketplaces often use more than one fee type, including transaction, commission, listing, subscription, and referral fees, so "who pays" is often a mix, not a single switch.
When should I move from a single commission rate to segmented pricing?
Segment when measured costs, order values, service levels or price sensitivity differ enough to justify added complexity. A minimum fee can cover fixed costs on low-value orders, but disclose it and test its effective percentage. Use a current primary rate card when comparing competitors.
How do tax and compliance requirements change commission decisions in cross-border marketplaces?
Cross-border flows can add FX, payout, review and jurisdiction-specific tax or reporting work. Scope the obligations first, then model the attributable cost and fee-tax treatment. Tax collected for an authority is not platform contribution, and personal FBAR obligations are not automatically a marketplace fee cost.
Try a related tool
Researched and edited by the Gruv editorial team. Gruv builds cross-border billing, payouts, and finance-operations software for global businesses.
Sources
Includes 2 external sources outside the trusted-domain allowlist.
Educational content only. Not legal, tax, or financial advice.
Related Posts

Canada GST/HST for Platform Fees: How Marketplaces Decide What to Charge, Track, and Report
You can make defensible calls on **canada gst hst platform fees** without building a large tax operations function, but only if your controls are explicit and documented. The core questions are straightforward: who is making the supply, what is being charged, which rate applies, and what evidence supports that treatment.

Recurring Billing for Marketplaces: How to Charge Buyers and Pay Sellers on the Same Cycle
**Recurring billing in a marketplace works best when buyer charges, seller payouts, and finance close follow aligned cycle logic.** When checkout timing, payout timing, and finance close are designed separately, you can end up with charges that succeed, payouts that stall, and records that only make sense after manual cleanup.

Hybrid Pricing Models for One Subscription and Usage Invoice
Treat this as a billing and operations project, not just a pricing exercise. A hybrid pricing model can be commercially strong. The real test is whether you can put a recurring subscription fee and usage-based charges on a single invoice without forcing Finance to stitch things together at month-end.

