Vendors, commissions, split orders and automated payouts — production-ready, self-hosted, and yours. Months of engineering you don't have to do.
Marketplaces running on this plugin
Different starting points, same requirement: a marketplace that runs on software you own.
Your store works. Suppliers, brands or partners are asking to list their own products, and every workaround you've tried ends in a spreadsheet.
Fees on every transaction, a commission model you can't change, and features you can't add. You want the same operation on code you control.
You quote it, and the number is a project of months. This is that project, already finished, with an agency license so you can deploy it for every client.
Not mockups: these are the actual screens the plugin ships, rebuilt in HTML so they stay sharp and translate with the page. Three your team works in, three your vendors live in, one your customer sees. Open the demo if you want to click them.
Every vendor product enters a queue as draft or pending, and nothing reaches your storefront until you move it. You approve it, or you reject it with a reason the vendor can act on — they see it in their own panel and resubmit. You also decide which changes need a second look, so a price edit on an approved product can go straight through while a new listing waits. Your catalogue stays yours, without you typing any of it.
The customer checks out once and pays once. Behind that, the plugin creates one order per vendor: its own items, its own shipment with tracking, its own commission and its own net. Each moves through its own state machine at its own pace, so a vendor who ships same-day is never held up by one who takes a week. You see the parent order and every child from the same screen.
Balances per vendor, each with the payout method that vendor configured. Pay one, or select twenty and pay them together. Every movement — sale, commission, refund claw-back, withdrawal — is a line in a ledger that reconciles itself, so what you owe is a number on screen instead of a spreadsheet you rebuild every month. Payouts run on their own state machine too: requested, processing, paid, failed.
A guided flow the vendor completes on their own: store profile, payout method, billing details, and whatever documents you decide to require. You see who finished and who is stuck on step two, and you approve when you are ready. Adding a vendor stops being an afternoon of emails and becomes a notification you either accept or you don’t.
A page of their own inside your marketplace: products, description, rating, reviews and followers. It is what makes a vendor treat your platform as somewhere they are building something, rather than a channel they dump a catalogue into. And it is what makes a buyer come back to a seller instead of only to a search result.
The vendor’s own wallet: available balance, what is still clearing, what they have already withdrawn, and the statement line by line. When they reach the minimum they request the withdrawal themselves. Every question a vendor would otherwise email you — how much am I owed, when was I paid, what was that deduction — is answered on a page they can open at two in the morning.
A cart holding products from three vendors stays one checkout and one payment. Shipping is chosen per vendor, because that is how it actually ships, and the customer is told how many parcels are coming before they pay rather than after. None of the multi-vendor machinery leaks into their experience except the part that genuinely affects them.
It installs like a Sylius plugin, because it is one. No fork, no vendored copy, no patched core — and nothing here that a Sylius developer has not done before.
One command from the private repository, then the migrations — the plugin ships its own, so going live is a deploy and not a data project. A module is then enabled just by being present: the package's features, routes and admin screens appear on their own. Nothing to register, nothing to wire.
Commission model, payout method, what a vendor has to submit before selling, which product changes need approval. All of it from the Sylius admin, none of it in code.
Swap an entity with resolve_target_entities, a service with a container alias, a screen with a Twig Hook. Your changes sit beside ours instead of on top of them, so they survive the next update.
composer require odiseoteam/sylius-marketplace-plugin
bin/console doctrine:migrations:migrateNo form, no sales call — the storefront is open and both panels come with credentials. The demo data resets on its own, so break whatever you want.
sylius / sylius
seller1 / 123456
You're not buying a black box. Every entity, service and template is a replacement away from being yours.
Swap entities with Doctrine's resolve_target_entities, services with a container alias, UI with Twig Hooks instead of overriding templates. Adding a state transition is YAML, not a fork. The same subplugin mechanism the official modules use is available to your code.
Arabic, German, English, Spanish, French, Italian, Japanese, Dutch, Polish, Brazilian Portuguese, Russian, Turkish and Simplified Chinese. Messages and validators, not just labels.
111 Behat scenarios and 244 PHPUnit tests, in separate unit, functional and integration suites. PHPStan at level max. CI runs eight Sylius / Symfony / PHP / database combinations on every push, PostgreSQL included.
API Platform 4, with its own JWT firewall for the seller API. Build a mobile app for your vendors without touching the plugin.
Vendor status, order state, payment and shipping run on real state machines. Your transitions live next to ours.
Doctrine migrations ship with the plugin. Installing it on a live store is a deploy, not a data project.
Admin, seller panel and storefront, each themable on its own.
Installation, configuration, the domain model, every extension point. It's public, and it's the same documentation you'd get after buying — the fastest way to find out whether this fits your project.
One price for the marketplace itself, and modules you only pay for if you use them. Pick yours and the total updates as you go.
$1,690 one-time
Includes 1 year of support and updates
Core plus all eight modules. À la carte it adds up to $7,210 — that's 38% off.
$1,690 one-time
Request a quoteBuy once and the plugin is yours to run forever. There's no kill switch — the subscription buys updates and support, not the right to keep it running.
$690 a year keeps your updates — major versions included — and support current. Optional: the license is perpetual, so if you don’t renew, the plugin keeps running.
Unlimited client stores under one license. If you build marketplaces for a living, this is the line for you.
We come back with the quote, the repository access and an answer to whatever the demo did not cover. Usually the same day.
Prices in USD, one-time.
The core is not a demo: on its own it is an operable marketplace. Each module adds one concrete block on top of it.
A commercial plugin has no public install count, so here's its provenance instead: Marketplace extends our own Sylius Vendor Plugin, open source since 2017 and used across the ecosystem. Same authors, same code standards.
Access to the private Composer repository, the full source, the documentation, and a year of updates and support. You install it with composer require, like any other Sylius plugin.
Nothing stops. The license to use it is perpetual — the subscription only covers updates and support. It's $690 a year, and you can renew whenever you want them back.
Yes, while your updates and support are current. If they lapsed, renewing gets you the latest version.
One in production, plus all the development and staging environments you need. Building marketplaces for clients? The agency license covers unlimited client stores at 2.5× list price.
Yes. Modules are separate packages — you require the new one and it wires itself in. Nothing to migrate, nothing to reinstall.
No, and the reason is simple: once you have the source, you have it. That's why the demo is open with credentials and the documentation is public — evaluate it fully before you pay anything.
If you're on Sylius 2.0, 2.1 or 2.2, yes. It brings its own migrations and extends Sylius' entities rather than replacing them, so your products, orders and customers stay where they are.
Version 3 targets Sylius 2.x. If you're on 1.x, upgrading Sylius comes first — and it's work we do.
That's what it's designed for. 74 interfaces, entities you can replace through Doctrine, UI extended with Twig Hooks, state machines you extend in YAML. Your changes survive updates because you're not overriding files.
Thirteen: Arabic, German, English, Spanish, French, Italian, Japanese, Dutch, Polish, Brazilian Portuguese, Russian, Turkish and Simplified Chinese.
Direct contact with the people who wrote the plugin: bugs, installation questions, and guidance on how to extend it. Custom development is quoted separately.
Yes — we've been building Sylius since 2014, and marketplaces are the kind of build we specialise in. Ask for a quote along with the license.
Still have a question? Ask us directly
We wrote it, and we build the marketplaces that run on it. Integrations, a custom commission model, a storefront of your own — same team, quoted as a project.
Send us your selection and we come back with the quote, the access and an answer to whatever the demo didn't. If you'd rather talk it through first, book a call.
