Mirakl: connect your PIM to 400+ marketplaces via a single connector

Mirakl is the marketplace platform behind Leroy Merlin, Carrefour, Decathlon, La Redoute, Boulanger, Conforama and over 400 other retailers. With a single connector, your PIM can feed all these channels simultaneously. Here’s how it works.

What is Mirakl?

Mirakl is a software provider specialising in B2C and B2B marketplaces. It provides hundreds of retailers with an infrastructure to launch their own third-party seller marketplaces — just as Amazon has done, but for any retailer.

As a seller (distributor, importer, brand), you access the Mirakl ecosystem via a standardised API. The same integration allows you to sell onall Mirakl marketplaces at once— without specific development for each retailer.

Some examples of marketplaces powered by Mirakl in France:

• Leroy Merlin
• Carrefour Marketplace
• Decathlon
• La Redoute
• Boulanger
• Conforama
• Maisons du Monde
• Alltricks
• Electro Dépôt

And hundreds more across Europe, North America and Asia.

The problem without Mirakl (and without PIM)

Without the Mirakl API, selling on 10 different marketplaces means 10 separate technical integrations, 10 different file formats, 10 category mappings, and 10 support teams to manage.

With the Mirakl API, it’s a single integration. But the issue of product data remains: for each marketplace, you have to adapt your titles, descriptions, categories and attributes to the specific requirements of each retailer.

This is where a PIM connected to Mirakl makes all the difference.

How the Pixee PIM Mirakl connector works

The Pixee PIM Mirakl connector creates a bridge between your product database and the Mirakl API. The complete workflow:

1. Configuration of target marketplaces— you select the Mirakl marketplaces on which you wish to sell (Leroy Merlin, Carrefour, Decathlon…)
2. Category mapping— Pixee PIM translates your category tree into the specific taxonomies of each Mirakl marketplace
3. Attribute mapping— your product fields are mapped to the attributes required by each retailer (some require attributes specific to their sector)
4. Generation of offers— prices, stock, delivery terms by marketplace, with your specific pricing rules per channel
5. Push to Mirakl— scheduled or real-time synchronisation to all your target marketplaces simultaneously
6. Order and stock updates— sales and stock updates are automatically fed back into your PIM

Product and offer: the distinction that shapes everything

This is the point sellers new to Mirakl usually grasp too late. Mirakl separates two objects, and that separation drives the whole organisation of your flows:

• The product— the descriptive record, shared between all sellers on the marketplace: title, images, technical attributes, category. If the product already exists in the retailer’s catalogue, you don’t recreate it, you attach yourself to it.
• The offer— your proposition on that product: price, stock, condition (new, refurbished), lead time and delivery terms, minimum quantity. It belongs to you, and it is what puts you in competition with the other sellers on the same record.

Both flows have names you will find throughout the Mirakl documentation: the Product Integration File for products, the Offer Integration File for offers. Pixee PIM feeds both, and that is not a detail: a connector pushing only the product catalogue would leave you keying prices by hand in every back office.

This distinction has a direct consequence on update rhythms. A product record barely moves; a price and a stock level move constantly. There is therefore no reason to synchronise both flows at the same frequency, and that setting is what weighs most on API load. The architecture for tuning those rhythms flow by flow is covered in our article on real-time multichannel synchronisation.

What Mirakl standardises — and what it does not

The single-integration argument is accurate technically and misleading operationally. What Mirakl unifies: the protocol, the file formats, the processing statuses, the mechanics of orders and refunds. One set of calls, one authentication logic, one way to track an import.

What it does not unify: each retailer’s taxonomy, its mandatory attributes, its allowed list values, its naming rules, its image formats, its lead-time requirements. Leroy Merlin asks for a weight where Decathlon asks for dimensions; two retailers in the same sector will not label the same category the same way.

The real work is therefore not the integration, it is the mapping — and it repeats with every retailer you activate. Hence the value of doing it once in the PIM, in a reusable way, rather than in one spreadsheet per marketplace.

The tangible operational benefit

For a retailer with 15,000 active SKUs across 8 Mirakl marketplaces:

• Before: 8 manual exports per week, 8 different formats to maintain, error management for each marketplace separately
• After: 1 automatic push from the PIM to all 8 marketplaces at the same time, with centralised error monitoring

The time saved on catalogue operations is reallocated to enriching product listings (descriptions, images, technical attributes) — which directly improves the conversion rate on each marketplace.

The five most frequent rejections at launch

The first weeks on a Mirakl marketplace rarely pass without rejections. The causes are almost always the same:

• A category that is too generic— attaching a product to a high-level category loses the mandatory attributes of the leaf category, and the offer errors out or stays invisible.
• A missing, wrong or reused EAN— this is the identifier that attaches you to the right shared product. A wrong code publishes your offer on somebody else’s product, which shows up with the first customer review. Validating codes upstream is not a luxury.
• A price inconsistent with the expected currency or VAT regime— excluding or including tax, the currency of the retailer’s country, environmental contributions included or not: three causes of rejection or, worse, of silently selling at a loss.
• Stock that is not kept up to date— an offer published with a stock level that is never refreshed turns into cancellations, and cancellation rates drive your visibility with the operator.
• Non-compliant images— minimum dimensions, background, format, number of views: the rule differs from one retailer to the next and the check is automatic.

What these five causes have in common: every one of them is detectable before the push. That is precisely what a PIM is for.

Data quality and marketplace compliance

Each Mirakl marketplace has its own quality requirements: minimum completeness score, mandatory attributes by category, specific image formats. Sellers who do not meet these requirements have their listings de-listed or their products relegated to the bottom of the results.

The Pixee PIM Catalogue Completeness module allows you to check, before any push, that each listing meets the minimum requirements of each target marketplace. Incomplete products are placed on hold with a list of missing fields.

Tracking what goes out and what comes back

A marketplace integration is judged on its ability to answer a mundane question: why is this SKU not live? Without traceability, the answer costs half a day of navigating a back office.

Every push is therefore tracked line by line, with detailed errors and the status returned by the operator — accepted, refused, under review. You trace the cause from the PIM, without switching tools or asking someone for an extra login.

A second point that matters at scale: updates are incremental. Only the differences — prices, stock, modified attributes — go out, rather than the full catalogue on every cycle. On a catalogue of several thousand SKUs distributed across a handful of retailers, that is the difference between a permanent stream and a few hundred lines a day.

Mirakl B2B: an often-overlooked use case

Mirakl also operates in the B2B sector — Amazon Business, Manutan, Office Depot and other B2B retailers use Mirakl for their marketplaces selling professional supplies and equipment. Note that Amazon is also reachable directly through another route: the SP-API and Code2ASIN matching. For B2B distributors, this is a significant growth channel, accessible via the same Mirakl connector.

Which plans does the Mirakl connector come with?

The Mirakl connector is available on the Growth (up to 3 connectors), Scale (up to 6 connectors) and Enterprise (unlimited connectors) plans. Since a single Mirakl connector is enough to reach every marketplace running on that technology, the Growth plan already covers most needs; Scale adds the dedicated stack for high volumes.

Frequently asked questions

Do you need a contract with each retailer, or a single one with Mirakl?

Mirakl provides the infrastructure; it does not sell on your behalf. The commercial relationship — commissions, the categories opened to your account, service rules — is contracted retailer by retailer. The single connector saves you the technical integration work, not the contracting or the validation of your seller application, which remain the real lead time for opening a channel.

How many connectors do you need to sell on several Mirakl marketplaces?

Just one. That is the whole point of the model: the Mirakl connector counts as a single integration in your plan, whatever the number of retailers you activate behind it. The Growth plan allows three in total, which leaves room for a storefront and a Google Merchant Center feed alongside it.

Can a retailer be activated for one season and then switched off?

Yes, and it is a common pattern: garden in spring, seasonal decoration in autumn. Marketplaces are activated one by one from the PIM, the mapping stays in place between two seasons, and a retailer that does not perform is deactivated without touching the others. Unpublishing offers cleanly is still preferable to leaving them live with no stock.

Does the connector pull orders back?

Orders and stock movements are fed back into the PIM, which keeps a consolidated view of what sells per channel. Be careful not to confuse roles, though: a PIM is not an order management system. Picking, shipping, invoicing and after-sales service remain the job of your ERP or WMS.