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 $799.00 USD; request a quote for a scoped proposal.
Manifiesto de la app
Diseñado en torno a tu flujo de trabajo
Publish offers, import orders and manage returns for the Decathlon marketplace (Mirakl) directly from Odoo 17/18/19. Built, installed and supported by ECOSIRE.
Sin configuración por tu cuenta: una app funcional creada, instalada y con soporte de ECOSIRE.
Empieza con un precio único de desarrollo. Definimos el alcance contigo en el arranque.
ECOSIRE la crea, la configura y la instala en tu Odoo.
Sales en vivo en unas 2–4 semanas, con un periodo de soporte posterior al lanzamiento.
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.
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.
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.
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.
| Criterio | ECOSIRE | Construcción personalizada | Competidor | Odoo Nativo |
|---|---|---|---|---|
| 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 | |
| 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 | |
| Order import & acceptance within Mirakl window | Native Odoo sale orders, auto-accepted in the acceptance window | Buildable, but timing/edge-cases are on you | Apoyo parcial | |
| 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 | Apoyo parcial | |
| 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 | Apoyo parcial | |
| 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 | |
| Role-based security (ir.model.access.csv + record rules) | Configured for your warehouse/sales/finance groups | You implement and audit it | Apoyo parcial | |
| 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 |
This is a build-to-order module, not an instant download. Typical delivery is 2-4 weeks 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.
Your plan includes a post-launch support and bug-fix window (typically 30-90 days) 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.
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.
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.
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.
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.
Publish offers, import orders and manage returns for the Decathlon marketplace (Mirakl) directly from Odoo 17/18/19. Built, installed and supported by ECOSIRE.