Adobe Commerce development
Storefront design
Performance & SEO
AI & agentic commerce
Release tracker
Adobe Commerce does not include multi-vendor marketplace features, so a Magento marketplace is built in one of three ways: a marketplace extension that adds sellers, commissions and seller dashboards inside Magento; a dedicated marketplace platform such as Mirakl connected to Adobe Commerce; or a custom seller portal built around Magento's APIs. The right choice depends on how many sellers you expect, how strictly you must moderate their catalogs, and how money moves between buyers, sellers and you.
Below are the requirements every marketplace needs, followed by a comparison of the build options.
Marketplace requirements checklist
Use this as the backbone of your specification. Each area is a real workload, not a checkbox.
Seller onboarding
- Application and approval workflow, with document upload
- Identity and business verification (often handled by the payment provider)
- Seller agreement acceptance and version tracking
- Tax details collection, which may be a legal requirement for platform reporting
- Seller profiles and storefront pages
Catalog and moderation
- How sellers add products: forms, CSV, API or feed
- Single listing with multiple offers (several sellers selling one product) or separate products per seller
- Attribute mapping to your category structure
- Moderation queue for new and changed products, images and prices
- Rules for prohibited items and content quality
Orders, shipping and returns
- Splitting one cart into seller sub-orders
- Shipping rates per seller, and how multi-seller shipping is shown at checkout
- Seller-side order acceptance, shipping confirmation and tracking
- Returns, refunds and dispute handling between buyer, seller and operator
- Service levels and seller performance scoring
Commissions and payouts
- Commission rules by seller, category or product, plus fixed fees
- Who is the merchant of record for each sale, which affects tax, invoices and liability
- Split payments or collect-then-transfer payouts
- Payout schedules, holds for returns and chargebacks, and negative balances
- Seller statements and invoices for commissions
Compliance and reporting
- Seller reporting duties. In the EU, Directive (EU) 2021/514 (DAC7) requires platform operators to collect and report information on sellers to tax authorities
- Marketplace facilitator sales tax and VAT rules in the markets you sell to
- Consumer protection rules for showing who the seller is
Tax and platform rules vary by country, so get professional advice; this is general information, not legal or tax advice.
How money moves: payouts with a payment provider
Marketplace payments are best handled by a payment provider's platform product, such as Stripe Connect or Adyen's marketplace product (Adyen for Platforms), rather than custom code. These products onboard and verify sellers, split or transfer funds, and handle payouts. Stripe's documentation, for example, describes "separate charges and transfers", where the platform charges the buyer and then transfers funds to sellers, which suits carts with several sellers. Stripe notes that this model is more complex and that the platform is responsible for refunds, fees and negative balances. Choose the funds flow early, because it shapes checkout, refunds and accounting. Our guide to Adobe Commerce payment gateways covers the wider provider choice.
Build options compared
| Factor | Marketplace extension | Marketplace platform (e.g. Mirakl) | Custom seller portal |
|---|---|---|---|
| Where sellers work | Seller dashboard inside the Magento storefront | Platform's own seller back office | Your own portal app |
| Catalog moderation | Basic approval queues | Mature mapping, moderation and offer management | Whatever you build |
| Payouts | Commission records; payouts via payment provider add-ons | Built-in payment and payout integrations | Payment provider platform product |
| Scale | Rule of thumb, not a vendor limit: tens to low hundreds of sellers | Designed for large seller networks | Depends on design |
| Effort and cost | Lowest; licence plus customization | Platform subscription plus integration | Highest build effort, full control |
| Upgrade risk | Touches many core areas; test on every Magento upgrade | Connector must stay compatible | Your team maintains it |
Marketplace extensions
Several vendors sell multi-vendor marketplace extensions for Magento, typically adding seller registration, seller dashboards, commission rules and per-seller shipping. They are the quickest way to launch, and a good fit for a curated marketplace with a modest number of sellers. Because they touch catalog, checkout and orders, check code quality, upgrade history and compatibility with your other extensions before you buy.
Mirakl and similar platforms
Mirakl publishes a connector that turns Adobe Commerce into a storefront for a Mirakl-run marketplace, synchronizing taxonomy, products, offers, seller information and orders, and its documentation states that it is compatible with both Adobe Commerce and Magento Open Source. Sellers work in Mirakl's back office, and Mirakl handles offers, moderation and payouts. This suits larger operators, or retailers adding third-party sellers alongside their own catalog, who want proven marketplace operations rather than building them.
Custom seller portal
A custom portal fits when your sellers are not typical merchants: manufacturers supplying a distributor, franchisees, or B2B suppliers with negotiated terms. Magento remains the catalog, cart and order system, and a separate application gives sellers exactly the workflows they need. Our guide to customer portal development covers similar architecture choices, and many of the same patterns apply to seller portals.
B2B marketplaces
B2B marketplaces add company accounts, negotiated pricing, quotes and purchase orders on top of the requirements above. Adobe Commerce's B2B features cover the buying side, but they were not designed for multiple sellers quoting against each other, so this usually needs custom work or a platform that supports B2B. Our B2B ecommerce guide explains the buyer-side features in detail.
Decision guide
- Launching a curated marketplace with a few dozen sellers: start with a well-maintained extension and a payment provider's platform product.
- Adding third-party sellers to a large retail catalog: evaluate a marketplace platform with an Adobe Commerce connector.
- Unusual seller workflows or B2B supply: keep Magento as the commerce engine and build a seller portal around its APIs.
A phased launch plan
- Pilot with a handful of sellers you know well, using manual onboarding and close support.
- Prove the money flow: run real orders, refunds and a chargeback through payouts and seller statements before scaling.
- Automate onboarding and moderation once you know which checks matter.
- Add seller performance rules for shipping times, cancellations and returns, with clear consequences.
- Scale seller recruitment only when support and moderation can keep up.
Frequently asked questions
Can Adobe Commerce run a marketplace out of the box?
No. It supports multiple websites and stores for one merchant, not independent sellers with their own catalogs, orders and payouts.
Who should be the merchant of record?
It depends on your business model, tax position and risk appetite. Decide this with your accountant and payment provider before designing checkout and refunds.
Can I start with an extension and move to a platform later?
Yes, but seller data, offers and order history will need migrating. Keep seller data clean and documented from day one.
Next step
Write down your seller numbers, funds flow and moderation rules, then shortlist options. Mistri's Adobe Commerce development team can integrate an extension or platform, and our web application development service covers custom seller portals.
Sources
Mirakl connector for Adobe Commerce (Mirakl developer docs); Create separate charges and transfers (Stripe Docs); Council Directive (EU) 2021/514 (DAC7) (EUR-Lex); Marketplaces (Adyen Docs).
