Sports and outdoor brands selling on Decathlon Marketplace hit the same wall: Decathlon runs on Mirakl, and ERPNext core has no concept of a Mirakl operator. So orders get re-keyed by hand from the Decathlon seller portal into ERPNext Sales Orders, stock levels drift between what ERPNext thinks you have and what the marketplace advertises, tracking numbers get pasted twice, and month-end settlement reconciliation becomes a spreadsheet exercise where Mirakl commission, refunds, and payouts never quite tie back to your ERPNext accounts. ERPNext gives you excellent inventory, pricing, and accounting primitives — Item, Warehouse, Bin, Sales Order, Delivery Note, Sales Invoice, Payment Entry — but nothing that speaks the Mirakl OR/PA/S/OF API dialect that Decathlon exposes to its sellers.

We build a proper Frappe app — installed into your own ERPNext bench, not a hosted middleman — that closes that gap. The app ships a Decathlon Settings single DocType holding your Mirakl shop credentials and API base URL, plus DocTypes such as Decathlon Offer, Decathlon Order, and Decathlon Sync Log that give you an auditable record of every push and pull. Inbound orders are polled from the Mirakl OR11 order feed on a Frappe scheduler_events cron, de-duplicated by Mirakl order id, and materialized as native ERPNext Sales Orders against a dedicated customer and price list, with marketplace fees mapped to the correct income/expense accounts. Catalog and offers flow the other way: hooks.py doc_events on Item and Item Price stage OF21 offer updates so a price or listing change in ERPNext publishes to Decathlon without a separate console.

Inventory stays honest with two-way sync. A scheduler job reads projected quantity from ERPNext Bin per configured warehouse and pushes available-to-sell offer stock to Mirakl, while acknowledged marketplace orders decrement the same source of truth — so you are not overselling gear you have already committed elsewhere. When you ship, the app writes the carrier and tracking number back to Decathlon (ST11/ST12) the moment a Delivery Note is submitted, and transitions the Mirakl order state accordingly. Settlement reconciliation pulls the Mirakl accounting/payout feeds and matches operator commission, refunds, and payouts against ERPNext Sales Invoices and Payment Entries, flagging variances instead of hiding them. Every integration point is exposed as a @frappe.whitelist() method so your team can trigger a manual resync, and a role profile (Decathlon Manager) plus DocType permissions keep marketplace operations scoped to the right users. Client scripts add resync and "view on Decathlon" actions right on the relevant forms.

Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call, confirm your Mirakl API access, your warehouse and price-list layout, your tax and fee account mapping, and your Frappe/ERPNext version (v15 or v16). We then build against a staging copy of your data, run UAT with you, and only cut over to production on a scheduled window with a documented rollback. Typical delivery is one working week from confirmed scope, depending on how many marketplace edge cases (multi-warehouse, partial shipments, refund handling) you need on day one versus a later phase. You receive the full source, a git repository handover, technical and user documentation, a training session, and a post-go-live support window.