The most common confusion with Mirakl is treating it like Amazon. It is not. Mirakl is the platform Decathlon, Leroy Merlin, Bricodepot, GACD and dozens of other chains use to open their own marketplace to third-party sellers. For you that has one very good consequence and one middling one.
The good one: the API is the same for all of them. A well-built Mirakl integration serves your first operator and your fifth, changing the operator URL and the API key. The middling one: on top of that common base, each operator adds its own rules — its category tree, its mandatory attributes, its deadlines, its penalties, even which parts of the API it exposes — and those are not shared.
What they all share
The cycle is always the same: you publish offers (product, price, stock, lead time), the operator sends orders, you accept or reject them, you ship with tracking and you get paid by settlement. The Mirakl connector turns that cycle into ordinary Odoo documents on 17, 18 and 19: it publishes offers with price, stock and lead time to ship, imports orders as sales orders, accepts them (by hand, or automatically if you switch it on), sends the delivery's carrier and tracking number to Mirakl and imports settlements to post them in accounting.
A detail that surprises people: in Mirakl you can reject order lines. It is not a failure, it is part of the protocol. Our connector does not reject individual lines: it accepts the whole order. If there is a line you cannot fulfil, reject it in the Mirakl back office before accepting, and bear in mind that automatic acceptance, off by default, accepts everything that comes in.
What changes with each operator
The category tree and mandatory attributes, which look nothing alike between a sports chain and a DIY chain. The acceptance deadline, measured in hours at some operators. And product data requirements: some operators reject an offer without an EAN, and others also demand a full spec sheet.
That is why we have a page per operator as well as one for the connector: Decathlon, Leroy Merlin, Brico Depot and GACD. The base connector is the same and each operator is one more instance, with its own URL and key; for some operators there is also an add-on profile that presets the URL and its defaults. What really changes is the catalog preparation.
What to prepare before applying
Three things, none technical. An EAN on every reference you will publish: some operators will not accept the offer without one. A lead time you can actually meet, not the one you would like; promising 24 hours and shipping in 72 is paid for on your account. And photos that meet their spec, usually stricter than your own site's.
And a warning from our own experience
We audited our own Mirakl connector while its test suite was passing green on Odoo 19, 18 and 17, and found 18 confirmed defects, among them a call log that never wrote anything and a sync looking at the wrong date. The whole story is in auditing an inherited connector. If someone is selling you a Mirakl integration, ask what happens when the API returns an error, not how many tests it has.
Frequently asked questions
Does one Mirakl account open every operator?
No. Each operator accepts you separately, with its own commercial process. What is reused is the technical integration, not the commercial relationship.
Can I have different prices per operator?
Yes, and you should: commissions are not the same. In the connector each operator is an instance, and each instance computes its price with its own strategy: the product's sales price, an Odoo price list or cost plus margin.
What about settlements?
They arrive per operator and must be reconciled against sales, net of commission. It is the most neglected part and where money leaks unnoticed.
Useful links inside FlexigoTech
What we do about this
Accepted onto a Mirakl marketplace?
Tell us which operator and how many references you want to publish. We will check whether your catalog meets what they will demand before they reject it. Write to comercial@flexigobe.com or book a call.