Sync catalog, offers, orders, shipments and returns between Odoo and Mirakl marketplaces. Built-to-order and installed by ECOSIRE for Odoo 17/18/19. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $799.00 USD; request a quote for a scoped proposal.
应用清单
围绕您的工作流程构建
Sync catalog, offers, orders, shipments and returns between Odoo and Mirakl marketplaces. Built-to-order and installed by ECOSIRE for Odoo 17/18/19.
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
以一次性构建价格开始。我们在启动时与您共同确定范围。
ECOSIRE 在您的 Odoo 上构建、配置并安装。
约 2–4 周内上线，并提供上线后的支持期。
Selling on a Mirakl-powered marketplace — Decathlon, El Corte Inglés, and dozens of other operator-run platforms — means living in two systems at once. Mirakl expects catalog data in its exact attribute and value-list format, offers priced and stocked to the minute, orders accepted inside a shipping SLA, and returns processed against its own workflow. Do that by hand and your team burns hours copy-pasting between spreadsheets, the Mirakl seller UI and Odoo, while overselling, late shipments and mismatched credit notes chip away at your seller scorecard.
The Mirakl Marketplace Connector is a net-new Odoo module that ECOSIRE designs, builds, installs and supports for your specific Mirakl setup. It is NOT an off-the-shelf apps.odoo.com download you install yourself and hope fits — it is a bespoke integration engineered against your operator's attribute schema, carrier list, warehouse topology and pricing rules, then delivered to your Odoo 17, 18 or 19 database in 2–4 weeks. Your product.template records, stock.quant quantities, sale.order flow, stock.picking shipments and account.move credit notes become the single source of truth; the connector keeps Mirakl in lock-step through its REST APIs.
Under the hood it is real, maintainable Odoo. A clean __manifest__.py declares dependencies on sale_management, stock and account; new models built on models.Model store per-operator credentials, attribute mappings, offer state and sync logs, with computed fields via @api.depends for warehouse-aware available quantity. Access is locked down through ir.model.access.csv plus record rules so operator credentials and marketplace data are scoped to the right teams. Backend screens are standard XML/OWL views with a marketplace dashboard, and QWeb reports give you offer-publication and reconciliation summaries. Scheduled automated actions (ir.cron) drive incremental catalog, offer, order, shipment and return sync on the cadence Mirakl allows, and everything is exposed to your other tools over XML-RPC/JSON-RPC.
Because Mirakl is a marketplace network, one Odoo database can drive many operators. The connector is multi-operator by design: each Mirakl instance (Decathlon, El Corte Inglés, a best-buy-style operator, your own operator platform) gets its own configuration record, credentials, attribute mapping set and offer catalog, so a single warehouse and product catalog can fan out to every marketplace you sell on — seller-side, operator-side, or both — without duplicating your master data.
You get a marketplace operation that runs from inside your ERP: catalog that conforms to Mirakl's schema, offers that reflect true stock, orders that turn into pickings automatically, shipments that confirm with the correct carrier and tracking, and returns that land as warehouse receipts and credit notes with no double entry. And because ECOSIRE builds it, you get engineers who understand both Odoo internals and Mirakl's API — not a support ticket queue for a generic add-on.
Owns the seller scorecard across several Mirakl operators. Needs offers to reflect real stock, orders accepted within SLA and shipments confirmed with correct tracking — without a team of people re-keying data between the Mirakl UI and the ERP.
Distributes one product catalog across Decathlon, El Corte Inglés and other Mirakl marketplaces plus their own store. Wants Odoo as the single master for catalog, pricing and inventory, fanning out to every operator from one place.
Responsible for the Odoo estate and its integrations. Wants a maintainable, well-documented module built on standard Odoo patterns (models, ir.cron, XML-RPC) that they own in Git — not an opaque third-party add-on they cannot audit or fix.
Cares that marketplace orders, shipments and returns tie out to invoices and credit notes. Needs returns to post as warehouse receipts and account.move credit notes automatically so inventory and the ledger stay reconciled.
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Fits your operator's exact attribute schema & carrier codes | 包含 | 部分支持 | 部分支持 | |
| Multi-operator (many Mirakl instances, one Odoo) | 包含 | 部分支持 | 部分支持 | |
| Warehouse-aware offer/stock sync via stock.quant compute fields | 包含 | 部分支持 | 部分支持 | |
| Automated returns → warehouse receipt + credit note | 包含 | 部分支持 | 不包括在内 | |
| Built, installed & version-targeted for you (Odoo 17/18/19) | 包含 | 包含 | 不包括在内 | |
| You own the source in Git and can audit/extend it | 包含 | 包含 | 不包括在内 | |
| Named-engineer support window + optional maintenance retainer | 包含 | 不包括在内 | 部分支持 | |
| Time & cost to reach a working integration | 包含 | 不包括在内 | 部分支持 |
This is a build-to-order module, not an instant download. After a short scoping call to capture your Odoo version and edition, your Mirakl operator(s), attribute schema, carrier list and warehouse setup, typical delivery is 2–4 weeks. ECOSIRE builds the module, configures each operator, deploys it to your staging database for sign-off, then installs to production and trains your team. Timeline depends on the number of operators and any custom mapping or business rules.
Every build includes a post-launch support and bug-fix window with a named ECOSIRE engineer for issues, questions and minor adjustments. Because Mirakl evolves its APIs and operators change their attribute and carrier requirements over time, we also offer an optional maintenance retainer that tracks those changes, onboards new operators and adds features. You receive the full source in a private Git repository, so you can also maintain or extend it yourself at any time.
Yes — multi-operator support is a core design goal. Each Mirakl instance (for example Decathlon, El Corte Inglés, a best-buy-style operator, or your own operator platform) gets its own configuration record with separate credentials, attribute mapping, offer catalog and sync schedule. A single product master and warehouse can publish offers and process orders across all of them from one Odoo instance.
The module is built for Odoo 17, 18 or 19, on either Community or Enterprise. We target the build to your exact version and edition using standard Odoo patterns — __manifest__.py dependencies, models.Model, ir.model.access.csv with record rules, XML/OWL views, QWeb reports and ir.cron scheduled actions — so it upgrades cleanly and behaves like native Odoo. If you later upgrade Odoo versions, we can port it under a maintenance engagement.
Offers publish with a warehouse-aware available quantity computed from stock.quant via @api.depends compute fields, respecting reserved and incoming stock and any safety-stock buffer you define. You choose which warehouses feed each operator. Scheduled ir.cron sync keeps quantities current at the polling cadence each operator permits, so when stock moves in Odoo the offer updates on Mirakl — dramatically reducing oversell and late-shipment penalties on your scorecard.
Yes. When a return is imported from Mirakl, the connector creates the correct reverse warehouse receipt (stock.picking) and generates an account.move credit note automatically, so inventory and finance stay reconciled without double entry. Every step is written to the sync log, and QWeb reconciliation reports give finance an auditable view of orders, shipments and returns per operator.
Sync catalog, offers, orders, shipments and returns between Odoo and Mirakl marketplaces. Built-to-order and installed by ECOSIRE for Odoo 17/18/19.