Brands selling into enterprise Mirakl marketplaces — Best Buy, Kroger, Decathlon, Worten, ManoMano and 400+ other operators running the Mirakl platform — quickly hit a wall with native ERPNext. ERPNext has no concept of a Mirakl offer, no OR11/OR21 order polling, no shipping tracking writeback, and no way to reconcile the transactions Mirakl reports back per operator. Teams end up rekeying orders from each seller portal into Sales Order, manually adjusting Bin quantities across channels, and reconciling settlement spreadsheets by hand — which does not scale past a handful of daily orders and silently drifts stock and margin out of sync.

ECOSIRE builds a proper Frappe app (its own module, DocTypes, hooks.py events and scheduler jobs) that speaks the Mirakl Marketplace API generically, so a single integration serves every operator you sell on. Order import polls the Mirakl order endpoints on a scheduler_events cron, maps each Mirakl order line into an ERPNext Sales Order (or Sales Invoice) against a configurable Item and customer, and idempotently stores the Mirakl order id so re-polling never duplicates. Offer management publishes and updates offers per operator from your ERPNext Item catalog through the Mirakl offer import feed, tracking async import status back onto a Mirakl Offer DocType. Inventory and price sync runs two-way: ERPNext Stock Ledger Entry / price list changes are pushed out as offer updates via a doc_events hook, and Mirakl-side changes are reconciled back so you have one source of truth.

Technically, each connection is configured in a Mirakl Operator Settings DocType (base URL, API key, warehouse and price-list mapping, currency), so adding a new operator is data entry, not code. Shipping and tracking writeback listens on on_submit of Delivery Note, resolves carrier and tracking number, and calls the Mirakl ship/tracking endpoints to move the marketplace order to shipped. Settlement reconciliation pulls the per-operator transaction/settlement logs into a Mirakl Settlement DocType and matches commissions, refunds and payouts against your ERPNext accounting entries. Everything is exposed through Frappe's permission model with dedicated role profiles, whitelisted methods for controlled server-side actions, and optional client scripts for in-form actions. Built and tested against Frappe/ERPNext v15 and forward-compatible with v16.

Because this is build-to-order, nothing is a black-box download. We start with a short scoping call to confirm which operators, order-to-invoice flow, warehouse/price-list mapping and settlement depth you need, then build against your exact ERPNext version and configuration. Typical delivery is one working week from confirmed scope. You receive the installable source for your version, staging UAT with a rollback plan, documentation, a training session, and a post-go-live support window — plus the git repository so your team fully owns the code.