This comparison covers the four platforms that appear most frequently in enterprise marketplace procurement processes: Esetrix, Mirakl, Marketplacer, and Medusa. It is organised by the dimensions that matter most to buyers -commercial model, marketplace capability, catalogue governance, and operational support -using a consistent framework across all four vendors.
The data reflects 2026 pricing and capability profiles. For deeper head-to-head analysis, see the dedicated Esetrix vs Mirakl and Esetrix vs Marketplacer comparisons.
How to read this comparison
Each section covers a specific operational domain. Esetrix is listed first in each table not alphabetically but because this comparison is published by Esetrix -readers should apply appropriate scrutiny. Where the data is sourced from vendor-published pricing or capability documentation, that is noted. Where it reflects typical deployment patterns, that is also noted.
A note on Medusa: Medusa is an open-source framework, not a packaged marketplace platform. "Custom" entries in the Medusa column reflect the reality that the capability exists in principle but must be built by the operator's development team. This is not a limitation -it is the product's intentional design. Buyers considering Medusa should cost the engineering effort, not just the licence.
Commercial & implementation model
The commercial model comparison is where the platforms diverge most sharply. Pricing structure, contract commitment, implementation timeline, and SI dependency all compound -a platform that is cheaper per month can be far more expensive in total once implementation cost, SI fees, and headcount are included.
| Dimension | Esetrix | Mirakl | Marketplacer | Medusa |
|---|---|---|---|---|
| Platform model | SaaS subscription | Enterprise SaaS | Enterprise SaaS + % GMV | Open-source, custom build |
| Typical monthly cost | ~£5k flat | £20k+ | £2.5k + 1.5% GMV | Dev-dependent |
| Revenue share / GMV fee | None | Yes | Yes (1.5%) | None |
| Contract commitment | 12 months | Multi-year enterprise | Enterprise contract | Dev-led |
| Time to market | 6-8 weeks | 6-12 months | 4-9 months | 6-12 months |
| SI required | No mandatory SI | Yes | Often | Yes |
| Implementation risk | Controlled, defined governance | High complexity programme | Commercial scaling risk | High development risk |
Marketplace & dropship capability
Core marketplace functionality -multi-vendor support, dropship workflows, supplier settlement, and commission logic -is present across all four platforms, but the mode of delivery differs. For Esetrix, Mirakl, and Marketplacer it is pre-built. For Medusa it is a construction project.
| Dimension | Esetrix | Mirakl | Marketplacer | Medusa |
|---|---|---|---|---|
| Multi-vendor marketplace | Yes | Yes | Yes | Custom |
| Dropship support | Native automated workflows | Supported | Supported | Custom logic |
| Supplier settlement | Automated | Yes | Yes | Custom |
| Split shipments | Yes, with workflow controls | Yes | Yes | Custom |
| Commission logic | Configurable framework | Advanced | Configurable | Custom |
| Trade & consumer pricing | Yes | Yes | Yes | Custom |
The distinction to note is in dropship support. Esetrix offers native automated dropship workflows -meaning order routing, supplier notification, tracking integration, and exception handling run autonomously. The competing platforms support dropship but require manual workflow configuration or SI involvement to achieve comparable automation.
Catalogue & governance layer
Catalogue quality is one of the most significant ongoing operational costs in marketplace management. Platforms that automate harmonisation and governance reduce this cost structurally; platforms that require manual moderation create a headcount requirement that scales with supplier count.
| Dimension | Esetrix | Mirakl | Marketplacer | Medusa |
|---|---|---|---|---|
| Data harmonisation | Standardised harmonisation layer | Enterprise taxonomy | Enterprise tooling | Custom |
| Supplier onboarding | Structured + approval controls | Structured | Structured | Custom |
| SLA tracking | Configurable dashboards | Advanced | Yes | Custom |
| Dispute management | Structured case workflows | Yes | Yes | Custom |
| Returns & refund routing | Integrated accountability workflows | Yes | Yes | Custom |
| Case management | Integrated Service Cloud module | Advanced | Yes | Custom |
Operational support & managed services
This section is where the comparison becomes most commercially significant for operators who do not have large internal marketplace teams. The difference between "included in platform" and "professional services add-on" is a real budget line that does not appear in headline pricing.
| Dimension | Esetrix | Mirakl | Marketplacer | Medusa |
|---|---|---|---|---|
| Supplier onboarding support | Included managed support | Professional services add-on | Additional service fee | Internal team required |
| Customer service support | Included managed support | Internal or SI-managed | Internal or add-on | Internal required |
| Dedicated marketplace resource | Included (~£2k/month value) | Enterprise services model | Add-on | No |
| Operational cost offset | Embedded -reduces headcount requirement | Additional cost layer | Partial | None |
Summary: which platform for which operator
No single platform is the right choice for every operator. The correct answer depends on timeline, engineering capability, GMV trajectory, and SI appetite. Here is where each platform is the strongest fit.
Operator needs to be commercially live within weeks, has no SI budget, wants predictable flat-fee costs at scale, and requires autonomous workflows without headcount growth. Managed support included.
Organisation has funded a 12-month transformation programme, has an established SI partner, and is operating at very large enterprise scale where the GMV pricing model has been modelled and accepted.
Mid-market operator who wants a proven platform with a built-in storefront, can absorb the 1.5% GMV fee at target transaction volume, and has 4-9 months for implementation.
Organisation with a strong in-house engineering team that wants complete architectural control and is willing to build and maintain all marketplace operational logic internally.
For deeper analysis of specific head-to-head comparisons, see Esetrix vs Mirakl and Esetrix vs Marketplacer.