Mirakl Marketplace Connector (Seller + Operator)

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.