Marketplace & Multi-Vendor Commerce
Multi-vendor architecture for food halls, festivals, B2B merchant exchanges, and pop-up markets. Each vendor connects their Square account — payments split automatically at checkout.
Three Multi-Vendor Commerce Patterns We Build
Multiple food or retail vendors under one roof, one checkout experience. Buyers add items from multiple vendors to a single cart. Payment splits to each vendor's Square account at checkout. The marketplace operator takes a platform fee automatically.
Square merchants list excess or cold inventory for other merchants to purchase. Lateral commerce: your overstock becomes another merchant's opportunity. Payments route through Square; no cash, no invoicing.
A buyer-facing marketplace where customers discover and purchase from multiple vendors in one experience. Built on Medusa + Mercur + Next.js — open-source, self-hosted, and Square-native.
The Technical Stack
Medusa.js Commerce Core
Medusa provides the headless commerce engine: catalog, cart, checkout, orders, and customers. In multi-vendor context, each vendor's products live under a Medusa vendor store, isolated but discoverable in the unified marketplace.
Mercur Multi-Vendor Layer
Mercur is an open-source multi-vendor extension for Medusa. It adds vendor onboarding, product listings, vendor dashboards, and commission management. We extend Mercur with Square-specific payment splitting.
Square OAuth Per Vendor
Each vendor connects their own Square account via OAuth. When a buyer checks out, payment is routed to the appropriate vendor's Square account — minus the platform fee, which routes to the marketplace operator's Square account.
Developer Fee Injection
The platform fee (your commission) is injected at the Medusa checkout level and automatically deducted from each vendor payment. No manual invoicing, no monthly reconciliation.
Next.js Buyer-Facing Storefront
The marketplace storefront is a Next.js application — server-rendered, SEO-friendly, and fast. Buyers browse by vendor, by category, or search across the full catalog. Add to cart works cross-vendor.
Frequently Asked Questions
Common questions about multi-vendor marketplace development.
Start Your Marketplace Project
Describe your marketplace model: how many vendors, what they sell, and how you want to handle the platform fee.
Square OAuth per vendor
Each vendor connects their own Square account.
Automatic payment splitting
Platform fee deducted and routed at checkout.
Open-source Medusa + Mercur
No SaaS marketplace platform fees.
Cross-vendor cart and checkout
Buyers purchase from multiple vendors in one transaction.
Start Your Marketplace Project
Describe your marketplace model: how many vendors, what they sell, and how you want to handle the platform fee.
Square OAuth per vendor
Each vendor connects their own Square account.
Automatic payment splitting
Platform fee deducted and routed at checkout.
Open-source Medusa + Mercur
No SaaS marketplace platform fees.
Cross-vendor cart and checkout
Buyers purchase from multiple vendors in one transaction.
