Every category has a marketplace waiting to be built: local makers, specialist gear, second-hand luxury, digital templates, freelance services, regional food producers. The pattern is always the same — you connect people who have something to sell with people who want to buy it, and you take a cut of every transaction that flows through your platform. The economics are compelling because you don't hold inventory and you don't do the fulfilment. What you own is the trust, the audience, and the rails.

The problem is that those rails are enormous. A real multi-vendor marketplace needs vendor accounts, a shared catalogue, orders that split across sellers, stock and shipping, buyer and seller identity, payment collection, and — the part everyone underestimates — paying each vendor out correctly. Most founders either spend a year building all of that, or rent it from a hosted platform that owns their customers and takes a slice on top of the slice they were hoping to keep. This is a guide to a third path: assembling the commerce substrate from VBWD's plugins so you can spend your time on the part that actually differentiates you.

What VBWD gives you out of the box

VBWD is a self-hosted, source-available full-stack SDK — one Python backend core with a Vue/TypeScript web front end plus native iOS and Android SDKs, all served from the same backend. The core is deliberately agnostic; capabilities arrive as plugins that toggle on and off without a restart. For a multi-vendor marketplace, a surprising amount of the hard part is already sitting in that plugin catalogue:

• marketplace — the multi-vendor layer itself: many independent sellers operating under one storefront.
• shop — products, orders, stock, and shipping. This is your catalogue and your order engine.
• RBAC + multi-tenant — roles and tenant isolation so a vendor can manage their own listings and orders without ever seeing another vendor's data, while your staff see everything.
• many payment providers — Stripe, PayPal, PromptPay, Mercado Pago, Conekta, Toss, YooKassa, TrueMoney, plus provider-agnostic and non-custodial crypto/stablecoin settlement. You collect payment through whatever your buyers actually use.
• withdraw — payouts. This is how vendors get their money out, and it is the piece most home-grown marketplaces get badly wrong.
• token_payment — a token/credit economy and metered billing, if you want platform credits, wallets, or usage-based charges.
• subscription — tarif plans, subscriptions, add-ons, and checkout: vendor membership tiers, or buyer memberships.
• discount and referral — promotions, coupons, and a referral engine to grow both sides of the market.
• cms / cms_ai — landing pages, category pages, vendor spotlights, and editorial content.
• booking — if your marketplace sells time rather than things (appointments, rooms, seats, spaces), this turns it into a service marketplace.

Underneath all of it the core is event-driven with native signed webhooks, so every order, payout, and subscription change can drive downstream automation you build. This isn't theoretical extensibility: real vertical apps already run on VBWD — a pharmacy shop (shop_pharma), a tarot app, and a dice-market game — which is your proof that the plugins compose into genuinely different products.

The honest boundary

VBWD gives you the commerce substrate. It does not give you a marketplace — a marketplace is a business, and the business is the part only you can build. Specifically:

• You define the niche. The plugins don't know whether you're selling vintage synthesizers or lawn-care appointments. Positioning, category structure, and who you say no to are yours.
• You set vendor policy. Onboarding requirements, commission rates, quality bars, dispute handling, refund rules, and what gets a seller removed — these are decisions, not features.
• You own trust and curation. Reviews, verification, fraud judgement, and the editorial taste that makes buyers return — VBWD gives you the hooks (roles, events, CMS, webhooks) but the curation is your work.
• You design the differentiated UX. The web front end and native SDKs are yours to shape; the reason someone chooses your marketplace over the incumbent has to come from you.

Put plainly: VBWD means you are not rebuilding payments, payouts, catalogue, and accounts from scratch. It does not mean the marketplace builds itself. That's an honest trade, and it's the right one — the undifferentiated plumbing is solved, and your time goes to the differentiated part.

A rough build outline

The core workflow comes together in a handful of concrete steps:

• Stand up the SDK and enable marketplace, shop, and your payment provider plugins. Because plugins toggle without a restart, you switch the substrate on and start configuring immediately.
• Model vendors with RBAC + multi-tenant. Give sellers a scoped role over their own catalogue and orders; keep platform staff above it. This is what makes it multi-vendor rather than a single shop.
• Configure the catalogue and checkout in shop: product types, stock, shipping, and a checkout wired to the payment providers your buyers use.
• Wire payouts with withdraw. Decide your take-rate and let the payout flow settle the remainder to each vendor. Use the signed webhooks so an order-paid event feeds your commission and payout logic.
• Layer growth and monetization plugins:subscription for vendor tiers, discount and referral to grow both sides, cms for the storefront and vendor pages.
• Build the front end and, when you're ready, ship native iOS and Android apps from the same backend — no second implementation of your business rules.

Monetization — and why owning it wins

A marketplace has more than one revenue line, and VBWD supports the common ones directly. The classic take-rate on every transaction runs through shop plus withdraw. Vendor subscriptions — monthly plans that unlock more listings, lower fees, or better placement — run through subscription. Featured listings and promotions are a straightforward paid product, and buyer-side memberships or platform credits are natural extensions with subscription and token_payment.

The deeper reason to build this way is ownership. On a rented marketplace platform, your vendors, your buyers, your transaction history, and your pricing power all sit inside someone else's account — and they take a percentage of the percentage you were trying to keep. VBWD is self-hosted and source-available: the code runs on your infrastructure, the customer relationships and the data are yours, and there is no platform above you clipping every payout. You're building an asset, not renting a storefront.

Start by cloning the public SDK at github.com/VBWD-platform/vbwd-sdk-public — enable the marketplace, shop, and payment plugins and you'll have a multi-vendor checkout running the same day. If you'd rather have it stood up and configured for your niche, request an enterprise installation.

VBWD is source-available under BSL 1.1 — free for commercial use while annual VBWD-attributable sales stay under the value of 6.7 BTC per year.

Build a business with VBWD — the series:Mobile game · Travel aggregator · Marketplace (this one) · Booking SaaS · AI assistant SaaS