--- title: "Setting Up a Multi-Vendor Marketplace" canonical_url: "https://daras.com.tr/en/blog/setting-up-a-multi-vendor-marketplace" last_updated: "2026-10-07T09:15:01.757Z" locale: en meta: description: "Explains how vendor approval, commission structure, order splitting, and vendor payouts work together so store owners can set up a multi-vendor marketplace correctly." "og:description": "Explains how vendor approval, commission structure, order splitting, and vendor payouts work together so store owners can set up a multi-vendor marketplace correctly." "og:title": "Setting Up a Multi-Vendor Marketplace" "twitter:description": "Explains how vendor approval, commission structure, order splitting, and vendor payouts work together so store owners can set up a multi-vendor marketplace correctly." "twitter:title": "Setting Up a Multi-Vendor Marketplace" --- [Marketplace](https://daras.com.tr/en/blog/category/marketplace) # **Setting Up a Multi-Vendor Marketplace** Explains how vendor approval, commission structure, order splitting, and vendor payouts work together so store owners can set up a multi-vendor marketplace correctly. Daras Team28 August 20265 min read Moving from an e-commerce site where you sell only your own products to a marketplace where other vendors sell too is not just a technical feature you bolt on — it's a new business model. Vendor approval, commission structure, order splitting, and vendor payouts: if these four pieces aren't set up correctly, marketplace operations turn into chaos fast. This post walks through the four core processes you run into when building a multi-vendor marketplace. ## What is the multi-vendor model? In classic e-commerce there is a single seller — the store owner. In the marketplace model, the platform lets multiple independent vendors sell their own products on the same storefront. A customer can buy products from different vendors in a single cart and pay once; behind the scenes, the platform splits the order by vendor and pays each vendor their amount after commission. The upside of this model is that you can grow your product range without growing your own inventory. The challenge is that you're no longer managing only your own operation — you also have to manage every vendor's product quality, shipping performance, and payment process. ## How does vendor approval work? Adding a new vendor to a marketplace shouldn't be as open as "sign up and start selling immediately" — uncontrolled approval raises the risk of low-quality products or bad-faith sellers. - A new vendor application usually starts in a **pending** state, where basic information is collected: business name, contact details, logo and banner. - The platform admin reviews the application and can **activate, reject, or suspend it.** An active vendor can later be suspended again for rule violations, poor performance, or a buildup of complaints. - Bulk approval/rejection — evaluating several pending applications at once — cuts operational overhead as vendor count grows. - Each approved vendor gets a **commission rate** and, where needed, a **team/role structure** defining who on the vendor's own panel can act with which permissions. - Vendor approval isn't a one-time gate; it's an ongoing process supported by mechanisms like product approval (reviewing newly added products before they go live), dispute tracking, and performance monitoring. ## How is the commission structure set up? Commission is the foundation of the marketplace's revenue model — it can be a flat percentage or it can scale with sales volume. - A **flat rate** is simple: the same percentage applies to every vendor on every sale. It's easy to manage but doesn't incentivize high-volume vendors. - **Tiered commission** applies different rates based on a vendor's gross merchandise value (GMV) over a given period — a higher rate on the first tier, a lower rate once a vendor crosses a certain volume threshold. This structure works as an incentive to keep growing vendors on the platform. - On top of tiers, you can define a **flat fee** — an additional fixed amount per transaction — typically used to cover payment processing costs. - Commission doesn't have to vary only by vendor — it **can also be differentiated by category**: a lower rate on electronics and a higher rate on handmade or niche products can make sense, for example. - Bulk rate updates — changing the rate for multiple vendors at once — become necessary as the platform grows and pricing strategy evolves. ## How does order splitting (sub-orders) work? If a customer's cart has products from more than one vendor, the system automatically splits a single parent order into **sub-orders, one per vendor.** - Each sub-order tracks its own status independently (pending → accepted → preparing → shipped → delivered); one vendor's order can already be shipped while another vendor's order is still being prepared. - Each sub-order stores the amount for that vendor's products along with a **snapshot of the commission rate at that moment** — so even if the commission rate changes later, the calculation on past orders is unaffected. - A sub-order can be canceled, but the cancellation reason is recorded and stays visible to both the vendor and the customer. - Being able to cross-navigate from the parent order to all its sub-orders, and from each sub-order back to its parent, matters for customer service — it's how you quickly answer "where is this customer's whole order." ## How are vendor payouts managed? Paying vendors their net amount, after commission, on a regular and transparent basis is what a marketplace's credibility rests on. - A payout run is usually executed for a **date range**: sales completed in that period (delivered, not returned) are totaled, commission and any deductions (such as withholding tax) are subtracted, and a single **draft payout** is created per vendor. - Once the bank/PSP transfer is complete, the draft payout is marked "paid" by entering an **external reference number** (a bank transfer ID or payment provider transaction number) — this record matters both for the audit trail and for vendor transparency. - If there's a balance carried over from a previous period (for example, an overpayment after a return), it can be automatically deducted from the next payout. - Providing each vendor a detailed **statement** (how much gross, how much commission, how much net was paid, per order) reinforces trust between the vendor and the platform. - If a payout needs to be canceled (due to a calculation error or a bank error, for example), the reason must be recorded — it should never be silently deleted. ## Frequently asked questions **Is a flat commission or a tiered commission better?** If you're starting with a small group of vendors, a flat rate keeps management simple. As vendor count and volume grow, a tiered structure gives you a stronger incentive to keep high-volume vendors on the platform. There's no single "right" answer here — decide based on the size of your platform. **If an order has products from more than one vendor, how many packages does the customer receive?** This depends on the system's order-splitting logic: since each vendor ships their own sub-order from their own warehouse, the customer generally receives as many separate packages as there are vendors involved. Making this clear to the customer before checkout (for example, a "this cart will ship from multiple vendors" notice) matters for setting expectations. **If the commission rate changes later, are past orders affected?** No, they shouldn't be. Each sub-order should store a snapshot of the commission rate at the time it was placed; when you update the commission rate, it should apply only to new orders, and past records should not change. ## Multi-vendor marketplaces in Daras The **Marketplace** module in the Daras panel covers all four of these processes end to end. From the **Vendors** screen, you review vendor applications and activate, suspend, or reject them; bulk approval actions and vendor team management (role-based access) also happen from the same screen. On the **Commission Tiers** screen, you can define a percentage rate and a flat fee per vendor based on GMV range, and update the rate for multiple vendors in bulk. When a multi-vendor cart is placed, the system automatically splits the parent order into **sub-orders**; each vendor processes and ships their own sub-order from the **Sub-orders** screen. From the **Vendor Payouts** screen, you run a payout for a given date range, mark it "paid" with an external reference after the PSP transfer, and generate a vendor-specific statement. Because all of these screens share the same commission-snapshot logic, no calculation from a past period is ever affected by a rate change made afterward. marketplacemulti-vendorcommissionvendorpayouts ## Related posts Marketplace ### [Trendyol, Hepsiburada, and N11 Integration](https://daras.com.tr/en/blog/trendyol-hepsiburada-n11-integration) A step-by-step guide to connecting Trendyol, Hepsiburada, and N11 in one panel, mapping products to categories, syncing stock and price, and pulling in marketplace orders. Marketplace ### [Marketplace Commission and Net Profit Calculation](https://daras.com.tr/en/blog/marketplace-commission-net-profit-calculation) Shows how to calculate true net profit after marketplace commission, shipping, and VAT, and lists the hidden deductions sellers most often forget when pricing. Get started ## **Try it in your trial store, go live when you are ready.** The migration team moves your products, customers, orders and theme; a 301 redirect map keeps your SEO intact. [**Start free**](https://app.daras.com.tr/register) [**Developer portal**](https://developers.daras.com.tr/docs)