Best Mirakl Connector for Odoo 2026
Three ways to connect Mirakl marketplaces (Makro, Leroy Merlin, Decathlon, Brico Depot) with Odoo: custom development, building on OCA, or a packaged connector. Here are the real numbers and the limits of each option, no fluff.
What problem a Mirakl connector solves
Mirakl is the technology behind many large-retail marketplaces: Makro, Leroy Merlin, Decathlon, Brico Depot, El Corte Inglés, GACD and dozens more. The upside for you is that they all speak the same API. The downside is that the API is not trivial: you have to authenticate with a shop key, page through results, handle retries and map their objects onto Odoo's. What you actually need to keep in sync boils down to four flows:
- Orders —
OR11lists the marketplace's orders andOR21accepts or rejects lines. Without this, orders never land in Odoo assale.order. - Offer stock and price —
OF24pushes your updated stock and price to the marketplace from Odoo's stock. If it fails, you sell what you don't have. - Catalog — the
PM(product import) andCA(categories) families upload your products and attributes to the marketplace. - Logistics and tracking — tracking number, carrier and shipment status pushed back to the marketplace when you ship.
Anyone who tells you this is "a couple of clicks" has never touched the API. The question isn't whether you need these flows, it's who maintains them when Mirakl changes a field or a marketplace adds a new validation.
The three options, one sentence each
Your team or a partner writes the entire Mirakl client. Maximum control, maximum cost, and you keep the maintenance forever.
You reuse the OCA connector framework, but the Mirakl client doesn't exist in the OCA: you write it anyway. Free license, not free hours.
A base connector implementing Mirakl's common API plus per-marketplace add-ons. 100 EUR one-time, OR11/OR21/OF24/PM/CA ready to go, 12 months of support.
12-criteria comparison
| Criterion | Custom development | On top of OCA | FlexigoTech connector |
|---|---|---|---|
| Starting price | 4,000–15,000 EUR in hours | 0 EUR license + hours for the Mirakl client | 100 EUR base + add-on per marketplace |
| Orders (OR11 / OR21) | You implement it | You implement it | Included, mapped to sale.order |
| Stock / offers (OF24) | You implement it | You implement it | Included from stock.quant |
| Catalog (PM / CA) | You implement it | You implement it | Included (PM and CA) |
| Multiple Mirakl marketplaces at once | Yes, if you design it that way | Yes, if you design it that way | Yes, common base + add-ons |
| Makro / Leroy / Decathlon / Brico | Each one by hand | Each one by hand | Makro direct; the rest with an add-on |
| Sync frequency | Whatever you schedule | Whatever you schedule | Configurable cron (not streaming) |
| Odoo 17 / 18 / 19 compatibility | You port it | You port it | All three versions |
| Edition (CE / Enterprise) | Both | Both | Community and Enterprise |
| Maintenance for API changes | Yours and billable | Yours and billable | We maintain it |
| Support | Whatever you hire | Community, no SLA | 12 months included |
| Full control of the code | Total | Total | You can read the code; it's not custom-built |
Price ranges are indicative, based on real Odoo integration projects in Spain. Your actual cost depends on how many marketplaces you sell on and how clean your catalog is.
When to pick each option (no sales pitch)
you have very specific business logic (dynamic per-channel pricing, unusual stock-allocation rules) that no standard connector will cover, and you have the budget and a team to maintain the API long term. It's the most expensive and the most flexible option.
you want everything under AGPL, you have Odoo developers in-house, and you're fine building the Mirakl client on top of connector-ecommerce. Honestly: you save on the license, but as of 2026 there's no Mirakl module in the OCA, so you end up writing the same thing as "custom" but with a base framework.
you sell on one or several Mirakl marketplaces and want orders, stock and catalog working already, without becoming the API's maintainer. 100 EUR base, an add-on per marketplace, and we absorb Mirakl's changes. It's not custom: if your case is very atypical, we'll say so and point you to custom development.
What no Mirakl connector gives you (let's be realistic)
- It's not strictly real-time. Sync runs on a cron (every X minutes). Mirakl doesn't expose webhooks for everything, so a delay of a few minutes is normal in any solution, including ours.
- A dirty catalog stays dirty. If your products in Odoo don't have correct EANs/attributes, the connector will upload garbage faster. Data quality is on you.
- Every marketplace validates its own way. Leroy Merlin, Decathlon or Brico Depot reject offers based on their own rules. The add-on covers their known ones; business-level rejections are yours to resolve.
- It doesn't replace your agreement with the marketplace. Commissions, terms and policies are between you and Makro/Leroy/Decathlon; the connector only moves data.
Mirakl marketplaces we already cover
Works directly with the base connector, no extra add-on needed.
Vendor add-on on top of the base. See the Decathlon connector page (200 EUR).
Vendor add-on with the marketplace's own validations.
Vendor add-ons on top of the same Mirakl base connector.
Is your Mirakl marketplace not on the list? Since it runs on the same API, it's usually covered by the base connector and, if it has its own quirks, a custom add-on. Tell us about it and we'll confirm before you pay anything.
Frequently asked questions
What is the best Mirakl connector for Odoo in 2026?
It depends. If you sell on a single marketplace and have an Odoo team in-house, custom development can be worth it. If you sell on several (Makro, Leroy, Decathlon, Brico) and don't want to maintain the Mirakl API yourself, a packaged connector with a common base plus add-ons (like ours, 100 EUR) is more cost-effective than paying for hours. There is no maintained OCA module for Mirakl, so that route means custom development too.
Is there a free Mirakl connector in the OCA?
The OCA maintains the connector framework and connectors for Magento, Prestashop or WooCommerce, but as of 2026 there is no published OCA module for Mirakl. It's free in licensing, not in hours: you still write the Mirakl client yourself.
Which Mirakl endpoints does it actually use?
Orders via OR11 (listing) and OR21 (accept/reject lines), offer stock and price via OF24, and catalog via the PM family and CA categories. All of it maps to sale.order, stock.quant and product.template in Odoo.
Does one connector work for Makro, Leroy and Decathlon at once?
The base connector (Mirakl's common API) is the trunk. Makro works directly; Leroy Merlin, Decathlon, Brico Depot and GACD each need their own vendor add-on on top because each has its own fields and validations.
Selling on Mirakl marketplaces with Odoo?
We're engineers in Barcelona, not salespeople. Check out the connector page or take the free quiz and we'll tell you honestly what fits your case.