How commission and payout logic should actually work in a multi-vendor platform
Most multi-vendor platforms break down not at launch but at payout time, when commission rules don't match real vendor agreements and money moves to the wrong place. Here's how to build payout logic that holds up at scale.
Eleven weeks. That's how long 3 vendors on one marketplace received incorrect payouts before the founder noticed. The platform's commission logic was correct for standard sales, but nobody had accounted for refunds, and the refund cost was being absorbed entirely by the platform instead of splitting back to the vendor. Eleven weeks of silent financial leakage.
This is the most common failure point in marketplace builds. If you're planning a multi-vendor marketplace platform, the commission and payout architecture deserves more design time than almost anything else on your roadmap.
The difference between a commission rate and a commission rule
Most early-stage marketplaces set a flat commission rate, say 12%, and call it done. That works until a vendor negotiates a different rate, or you add a product category with different margins, or you run a promotional period where you absorb part of the fee to drive volume.
A commission rule is the full logic tree: base rate, category overrides, vendor-specific agreements, promotional periods, and what happens to that rate when an order is partially refunded. You need all of it written down before a single line of code is written, because retrofitting rule logic into a live payout system is genuinely painful.
Where refund handling breaks most platforms
When a buyer refunds an order, three things need to happen in the right sequence: the buyer gets their money back, the vendor's payout is reduced (or clawed back if already paid), and the platform's commission is recalculated correctly.
Most platforms handle step one. Many miss step three. Almost none handle the edge case where a vendor was already paid out before the refund came in, which means you need a clawback or deduction mechanism against the vendor's next settlement cycle.
According to Chargebacks911's industry data on chargeback rates, ecommerce platforms see dispute rates between 0.5% and 1.5% of total transactions. On a platform doing $200,000 in monthly GMV, that's up to $3,000 in disputed transactions every month. Your refund logic has to be airtight.
Tiered commission structures and when they're worth the complexity
Some marketplaces use tiered commissions where a vendor pays a lower rate once they cross a volume threshold. For example: 15% on the first $5,000 in monthly sales, 10% above that. The idea is to reward high-performing vendors and reduce churn.
The problem is that tiered logic requires real-time or near-real-time sales tracking per vendor, and the tier calculation has to reset correctly at the start of each period. If your platform calculates tiers monthly but your payout cycle is weekly, you need a reconciliation step that most off-the-shelf solutions don't include by default.
Use tiered commissions only if your vendor agreements explicitly require them. The added complexity has a real cost in engineering and support time.
What a clean payout cycle actually looks like
The mechanics that matter most in a reliable payout system:
- Settlement period definition: weekly, biweekly, or monthly, set per vendor or globally, with a clear cutoff date for which orders are included in each cycle
- Hold period for refund risk: a buffer of 5 to 14 days between order completion and payout eligibility, so refunds can post before money moves
- Deduction line items: each payout statement should show gross sales, platform commission, any refund deductions, and net payout as separate fields, not a single number
- Clawback mechanism: if a refund arrives after a vendor has already been paid, the system needs to deduct from the next settlement automatically, with a clear audit trail
- Tax documentation hooks: the payout system needs to record enough data to generate 1099s (or equivalent) at year end, which means capturing vendor tax IDs at onboarding, not after the fact
Vendor-facing payout dashboards aren't optional
Vendors who can't see their own commission breakdown will email your support team constantly. Every question about why their payout was $847 instead of $900 is a support ticket that didn't need to exist.
A vendor dashboard that shows order-level commission detail, pending payouts, deductions, and settlement history cuts that support volume significantly. It also builds trust, which matters if you want vendors to stay on your platform when a competitor comes knocking.
The dashboard doesn't need to be complex. It needs to show the math clearly. Vendors want to verify the numbers themselves, and letting them do that is the right call.
Getting commission and payout logic right before launch is far cheaper than fixing it with live vendor money on the line. Cloudgramam builds marketplace platforms with this logic designed in from the start, not bolted on after the first angry vendor email. If you're in the planning or rebuild stage, talk to the team about what your specific vendor agreements actually require.
Put an AI voice agent to work on your calls.
Answer every call, book appointments, qualify leads and follow up, 24/7, in 70+ languages, from โน5/min. Book a free demo and hear it handle a call like yours.
Book a free demo โ