Mirakl builds the software that retailers use to run their own marketplaces, where third-party sellers list alongside the retailer’s own stock. It was founded in 2012, with headquarters in Paris and Boston, and is run by its two co-founders, Adrien Nussenbaum and Philippe Corrot.
Its 2025 results put the platform at more than 450 marketplaces, over 100,000 third-party sellers and $14.6 billion of sales a year, up 31%. Macy’s, Decathlon, Carrefour and Asos run on it, and in the UK, B&Q’s marketplace on diy.com has been Mirakl-powered since 2022. John Lewis and Tesco launched theirs on Mirakl in 2025.
One platform, many marketplaces
For a seller, every Mirakl marketplace is its own shop. Each retailer runs a separate instance with its own rules, catalog and approval, and the seller gets a separate account and API key for each one.
That’s what Mirakl Connect was built for. It’s a single hub where a seller manages orders, stock and prices across the Mirakl marketplaces they sell on, with ready-made connectors for Shopify, Adobe Commerce, WooCommerce and BigCommerce. Amazon joined as a channel in October 2025, and Connect is sold on paid plans by volume, with no per-channel fees.
UK fulfillment partners are building on it too. THG Fulfil partnered with Mirakl Connect in June 2026, so orders from Connect marketplaces flow straight into its systems.
AI for catalogs
Every retailer wants product data in its own format. Mirakl’s Catalog Transformer uses AI to reshape a seller’s product data to fit, and since late 2025 it can fill missing attributes from product images. Corrections a seller makes are protected from being overwritten by the next import.
The seller API
Each marketplace exposes the same seller API at its own address, authenticated with the shop’s API key. It covers the whole order cycle: listing new orders, accepting them, adding tracking, confirming shipment, and handling refunds, cancellations and returns.
Offers, stock and prices can be sent one at a time or imported in bulk as CSV, XML or Excel files, and products go to the retailer’s catalog team through their own import. Every endpoint documents its own rate limit, and a request over it is told how long to wait before trying again.
Event notifications are an operator feature, so a seller’s integration checks each marketplace for new orders on a schedule.
Several clients in one basket
Our Mirakl case study comes at Mirakl from the warehouse side. A UK 3PL’s client needed to sell on several Mirakl-powered marketplaces, each with its own instance and key, and one marketplace order could contain products held for different clients of the 3PL. The integration collects orders from every store, divides them between the clients’ Mintsoft accounts, and reports shipping back through each marketplace’s seller API.
Each store named the same product its own way, so mapping references took the most work in a build of around five weeks. The major client stayed with the 3PL, and bringing on the next client who sells through Mirakl is now a configuration task. Our post on outgrowing low-code automation uses this build as an example, and who owns it after launch covers what keeps it running.