Illustrative previewPublish offers, import orders and manage returns for the Decathlon marketplace (Mirakl) directly from Odoo
17/18/19. Built, installed and supported by ECOSIRE.
What is Decathlon Marketplace Connector (Mirakl)?
Publish offers, import orders and manage returns for the Decathlon marketplace (Mirakl) directly from Odoo 17/18/19. Built, installed and supported by ECOSIRE. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
Key Features
Built to order, done for you
No DIY setup — a working app, built, installed and supported by ECOSIRE.
- 1
You order
Start with a one-time build price. We scope it with you at kickoff.
- 2
We build & install
ECOSIRE builds, configures and installs it on your Odoo.
- 3
Go live + support
You go live in about one working week, with two weeks of go-live support. Defects in the code we deliver are fixed free of charge.
Technical Specifications
- Odoo Compatibility
- Odoo 17, Odoo 18, Odoo 19
- Editions
- Enterprise & Community
- License
- Licence confirmation required
- Python Requirement
- Python 3.10+
- Database
- PostgreSQL 12+
About this Product
Selling on the Decathlon marketplace means living inside Mirakl: uploading catalog data against Decathlon's attribute taxonomy, keeping offers priced and in stock, accepting orders inside Mirakl's acceptance window, mapping carriers to Decathlon's accepted shipping list, and processing returns and refunds without breaking your inventory. Doing that by hand in the Mirakl seller portal, then re-keying everything into Odoo, is slow, error-prone and does not scale past a handful of SKUs.
The Decathlon Marketplace Connector is a purpose-built Odoo application that ECOSIRE designs, develops, installs and supports for your business. It is NOT an off-the-shelf apps.odoo.com download you install and forget — it is a net-new module we build to fit your Decathlon offer strategy, your warehouse routing and your accounting. Because Decathlon runs on Mirakl, the connector talks to the Mirakl Marketplace API (offer, order, shipment, refund and carrier endpoints) using authenticated JSON/REST calls, and surfaces everything as first-class Odoo records you already understand: products, sale orders, deliveries, invoices and returns.
Under the hood the module is real Odoo engineering, not a black box. New models (models.Model) hold the Decathlon offer, marketplace order and mapping data; computed fields with @api.depends keep offer price and available stock in sync with your pricelists and on-hand quantities; ir.cron scheduled/automated actions run the publish, import and status sync jobs on the cadence you choose; QWeb reports give you per-marketplace reconciliation; and every table is protected by ir.model.access.csv plus record rules so warehouse, sales and finance users only see what they should. The connector is delivered for the exact Odoo version and edition you run — Community or Enterprise — and is validated on Odoo 17, 18 and 19, with the __manifest__.py dependencies pinned to your stack (sale, stock, delivery, and account where relevant).
The result: your Odoo product catalog becomes the single source of truth. You map SKUs and attributes to Decathlon's categories once, publish price and stock automatically, pull orders in the moment Decathlon confirms them, ship with the correct mapped carrier and tracking number, and receive returns back into the right warehouse location with a proper stock move — all without ever logging into the Mirakl portal for day-to-day operations.
What you get
- Complete, installable Odoo module (source code) targeting your exact Odoo version (17, 18 or 19) and edition (Community or Enterprise), with a pinned __manifest__.py.
- Configured Decathlon/Mirakl connection: API credentials wired, catalog/attribute mapping set up for your product categories, and carrier mapping completed for your shipping methods.
- Data mapping workbook and setup: SKU-to-Decathlon-category mapping, attribute value mapping and pricing/stock rules configured against your live catalog.
- Automated jobs configured: ir.cron schedules for offer publication, order import, status sync and return import tuned to your operational cadence.
- Security configuration: ir.model.access.csv access rights and record rules set for your warehouse, sales and finance user groups.
- Administrator and operator documentation: how the connector works, how to add/map new products, how to reprocess errors, and a go-live runbook.
- Live training session for your operations, warehouse and finance staff, with a recording for future onboarding.
- UAT support and go-live assistance: we validate offer publication, a test order, shipment confirmation and a return end-to-end before you go live.
Who this is for
Marketplace / e-commerce manager at a sports brand
Owns the Decathlon channel and its P&L. Needs offers to stay accurately priced and in stock, orders to flow in on time, and a clear view of channel performance — without living in the Mirakl portal or re-keying data into Odoo.
Warehouse & fulfilment lead
Responsible for picking, packing, shipping with the right carrier, and processing returns. Needs Decathlon orders to appear as normal Odoo deliveries, correct carrier codes on every shipment, and returns received back into the right location with proper stock moves.
Finance / operations controller
Cares that every Decathlon order, shipment and refund reconciles cleanly against Odoo sale orders and accounting. Needs role-scoped access, an audit trail of marketplace transactions, and period-end reconciliation reporting.
How Decathlon Marketplace Connector (Mirakl) Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Decathlon/Mirakl-specific catalog & attribute mapping | Built specifically to Decathlon's Mirakl taxonomy and mapped to your catalog | Possible but you build and maintain the mapping logic yourself | Generic Mirakl mapping; rarely tuned to Decathlon's exact attributes | Not included |
| Offer publication (price/stock) to Decathlon | Automated via ir.cron with computed price/stock fields | Depends entirely on what you scope and code | Usually supported, but generic and not always Decathlon-current | Not included |
| Order import & acceptance within Mirakl window | Native Odoo sale orders, auto-accepted in the acceptance window | Buildable, but timing/edge-cases are on you | Partial support | Not included |
| Carrier mapping & shipment confirmation with tracking | Odoo carriers mapped to Decathlon's accepted list; confirmed on delivery validation | Must be designed and tested by your team | Partial support | Not included |
| Return import with warehouse receipt (real stock move) | Returns received into the correct location as proper stock moves | Buildable but often skipped or done manually | Partial support | Not included |
| Fits your Odoo version/edition (17/18/19, Community/Enterprise) | Delivered and pinned to your exact stack, installed for you | You own version compatibility over time | Version support varies; upgrades can lag | Included |
| Role-based security (ir.model.access.csv + record rules) | Configured for your warehouse/sales/finance groups | You implement and audit it | Partial support | Partial support |
| Build, install, training & post-launch support | ECOSIRE builds, installs, trains and supports for a fixed window | Your internal team or contractors carry all of it | Vendor support quality and responsiveness varies | Not included |
Frequently Asked Questions about Decathlon Marketplace Connector
How long does delivery take, and what happens after I buy?
This is a build-to-order module, not an instant download. Typical delivery is one working week depending on how many product categories and attributes need mapping and how customized your pricing, warehouse and refund rules are. After purchase we hold a short scoping call, confirm your Odoo version/edition and Mirakl access, then build, install in your environment, run end-to-end UAT (offer publish, test order, shipment, return) and train your team before go-live.
What support and updates do I get after go-live?
Your plan includes a post-launch support and bug-fix window (two weeks) covering any defects in the delivered module. Because Decathlon runs on Mirakl and their APIs and attribute requirements evolve, we also offer ongoing maintenance so the connector stays compatible with Mirakl API changes and, if you upgrade, with a new Odoo version. Enhancements beyond the original scope are quoted separately.
Does it work with my Odoo version and Community vs Enterprise?
Yes. The connector is validated on Odoo 17, 18 and 19 and is delivered for whichever edition you run. It depends on core apps such as sale, stock and delivery (and account where refunds touch invoicing), so it works on Community; Enterprise-only features are only used if your instance already has them. We pin the __manifest__.py dependencies to your exact stack.
Do I still need to use the Mirakl seller portal?
For day-to-day operations, no. Offer publication, order import and acceptance, shipment confirmation and returns all happen inside Odoo. You may still use the Decathlon/Mirakl portal for onboarding, account settings and any dispute handling Decathlon requires, but your operational source of truth becomes Odoo.
How does stock stay accurate if I sell on other channels too?
Offers publish available quantity from a warehouse or stock buffer rule you choose, and computed fields recompute availability when on-hand stock changes. You can reserve a buffer so Decathlon never draws down inventory another channel needs, reducing oversell risk. Returns are received back as real stock moves so quantities stay correct.
Can other systems read the Decathlon data in Odoo?
Yes. Every offer, order, shipment and return is a native Odoo record, so anything that talks to Odoo via XML-RPC or JSON-RPC can read and act on marketplace state. This makes it straightforward to feed BI, an OMS or custom automations without scraping the Mirakl portal.
Related Modules
Customs & HS Code Compliance for Odoo
Build-to-order Odoo module for HS/HTS codes, customs declarations, CN22/CN23 forms and duty/tax estimates on cross-border shipments.
Cycle Counting & Stock Audit for Odoo
Recurring cycle counts and blind stock audits per location, product, lot or ABC class — built, installed and supported by ECOSIRE.
Delivery Base Module
A build-to-order foundation module that gives every Odoo shipping-carrier integration a shared, consistent base layer — rate abstraction, label storage, tracking hooks, and a common `delivery.carrier` extension pattern. ECOSIRE scopes, builds, installs, and supports it.
Delivery Route Optimization for Odoo
Auto-build the most efficient Odoo delivery routes by distance, capacity and time windows to cut miles, fuel and driver hours.
Decathlon Marketplace Connector
Publish offers, import orders and manage returns for the Decathlon marketplace (Mirakl) directly from Odoo 17/18/19. Built, installed and supported by ECOSIRE.
- Decathlon catalog and attribute mapping: map Odoo products and attributes (variants, sizes, colors) to Decathlon's Mirakl category taxonomy and required attribute values, stored in dedicated mapping models so re-listing is repeatable.
- Offer publication to Decathlon: push price and available quantity from Odoo pricelists and on-hand stock to Decathlon offers, with computed fields (@api.depends) recalculating the offer whenever price or stock changes.
- Scheduled offer sync: an ir.cron automated action re-publishes changed offers on a configurable cadence, so Decathlon always reflects current Odoo price and inventory without manual re-uploads.
- Order import and acceptance: automatically pull new Decathlon marketplace orders into Odoo as native sale orders and accept them within Mirakl's acceptance window, including customer, shipping address and line-item mapping.