Produktdetails werden auf Englisch angezeigt. Übersetzungen folgen in Kürze.
Kurze Fakten
- Preis
- $799.00 USD
- ERPNext-Versionen
- —
- Rüstzeit
- 30 Min
- Lizenz
- Einmalig und unbefristet
- Sprachen
- 11 Sprachen
Einmalkauf
ERPNext Mirakl Marketplace Connector
A build-to-order Frappe app that connects ERPNext to any Mirakl-powered marketplace — importing orders, publishing offers, syncing inventory and price, writing back shipments, and reconciling per-operator settlements from one operator-agnostic connector. ECOSIRE scopes, builds, installs and supports it for you.
$799.00USD
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
Hauptfunktionen
Operator-agnostic Mirakl API client — one connector serves any of the 400+ Mirakl-powered marketplaces via per-operator credentials, no per-marketplace rebuild
`Mirakl Operator Settings` DocType holds base URL, API key, warehouse, price list, currency and tax mapping so onboarding a new operator is configuration, not code
Scheduled order import polls Mirakl order endpoints on a `scheduler_events` cron and maps each line into ERPNext `Sales Order` / `Sales Invoice`
Idempotent order sync stores the Mirakl order id and acceptance state — re-polling never creates duplicate Sales Orders
Offer publish and update from your ERPNext `Item` catalog through the Mirakl offer import feed, with async import-status tracking on a `Mirakl Offer` DocType
Two-way inventory sync — ERPNext `Stock Ledger Entry` changes push offer stock out; Mirakl-side stock reconciles back on schedule
Two-way price sync from an ERPNext `Price List` to per-operator offer pricing, with configurable markup/rounding rules
Shipping and tracking writeback fired on `Delivery Note` `on_submit` via a `hooks.py` doc event — pushes carrier and tracking number to Mirakl
Per-operator settlement reconciliation into a `Mirakl Settlement` DocType, matching commissions, refunds and payouts to ERPNext accounting entries
Whitelisted server methods (`@frappe.whitelist()`) for controlled actions like manual re-sync, offer re-publish and order re-poll
Dedicated role profiles and DocType permissions so marketplace operators only see and act on their own data
Structured sync logging with retry/backoff and error DocTypes so failed API calls are visible, replayable and alertable
Client scripts for in-form actions (re-sync this order, publish this offer) plus a connection health/test-credentials button
Built and tested for Frappe/ERPNext v15 with forward compatibility for v16, delivered as a clean Frappe app installable via bench
Über dieses Produkt
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.
Warum ERPNext Mirakl Marketplace Connector wählen
Operator-agnostic Mirakl API client — one connector serves any of the 400+ Mirakl-powered marketplaces via per-operator credentials, no per-marketplace rebuild
`Mirakl Operator Settings` DocType holds base URL, API key, warehouse, price list, currency and tax mapping so onboarding a new operator is configuration, not code
Scheduled order import polls Mirakl order endpoints on a `scheduler_events` cron and maps each line into ERPNext `Sales Order` / `Sales Invoice`
Idempotent order sync stores the Mirakl order id and acceptance state — re-polling never creates duplicate Sales Orders
Offer publish and update from your ERPNext `Item` catalog through the Mirakl offer import feed, with async import-status tracking on a `Mirakl Offer` DocType
Two-way inventory sync — ERPNext `Stock Ledger Entry` changes push offer stock out; Mirakl-side stock reconciles back on schedule
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 2-4 weeks 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.
Was Sie bekommen
- Installable Frappe app source code built for your exact ERPNext version (v15 or v16)
- Installation and configuration on your environment, including per-operator settings and warehouse/price-list mapping
- Technical documentation — DocType reference, hooks, scheduler jobs, whitelisted methods and configuration guide
- End-user guide plus a live training session for your operations and finance team
- UAT on a staging site with a documented rollback plan before any production cutover
- A defined post-go-live support window for defect fixes and adjustments
- Full git repository handover so your team owns and can extend the code
- Optional Mirakl operator onboarding runbook for adding further marketplaces yourself
Für wen das ist
Marketplace Operations Manager
Runs day-to-day selling across several Mirakl operators and needs orders to land in ERPNext automatically, stock to stay accurate across channels, and shipments to confirm back without rekeying seller portals.
ERPNext / Frappe Systems Owner
Owns the ERPNext instance and wants a clean, maintainable Frappe app with proper DocTypes, hooks and permissions — not brittle scripts — built against v15/v16 and handed over as source they control.
Finance & Reconciliation Lead
Responsible for matching marketplace payouts to the books and needs per-operator settlement, commission and refund data reconciled against ERPNext accounting instead of manual spreadsheets.
Head of E-commerce / D2C
Expanding a brand onto enterprise Mirakl marketplaces and needs one integration that scales to new operators as configuration, protecting margin and stock accuracy as order volume grows.
Installationsübersicht
Von ECOSIRE herunterladen
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei der ERPNext Mirakl Marketplace Connector-App von Ihrem Konto-Dashboard herunter.
Fügen Sie die App zu Ihrer Bank hinzu
Extrahieren Sie die ZIP-Datei in den Apps-Ordner Ihrer Bank oder führen Sie „bench get-app“ mit dem Pfad zur extrahierten App aus.
Installieren Sie es auf Ihrer Website
Führen Sie „bench --site SITE_NAME install-app APP_NAME“ gefolgt von „bench migrate“ aus, um ERPNext Mirakl Marketplace Connector zu installieren und sein Schema anzuwenden.
Aktivieren Sie Ihre Lizenz
Öffnen Sie die ECOSIRE-Lizenzeinstellungen auf Ihrer Website und aktivieren Sie Ihren Lizenzschlüssel. Erfordert die kostenlosen Apps ecosire_connect und ecosire_license_client.
Wie ERPNext Mirakl Marketplace Connector im Vergleich abschneidet
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| Mirakl operator coverage | One operator-agnostic connector; new operators added as configuration | Whatever you scope and code yourself, per operator | Often single-marketplace or a fixed operator list | |
| Order import | Scheduled, idempotent poll into Sales Order/Invoice with dedupe | Build and maintain your own polling and mapping logic | Basic import, dedup and mapping vary by vendor | |
| Offer & inventory/price sync | Two-way stock and price sync driven by ERPNext doc events | You design and own both directions of sync | Frequently one-way or push-only | |
| Shipping & tracking writeback | Auto push on Delivery Note submit via hooks.py | Custom hook you must build and test | Sometimes supported, often manual | |
| Settlement reconciliation | Per-operator settlements matched to ERPNext accounting | Bespoke reconciliation you build | Rarely included | |
| Fit to your ERPNext version | Built and tested for your v15/v16 site | Depends on your team's Frappe depth | Generic build; upgrade lag common | |
| Code ownership | Full git repo handover — you own it | You own it but carry all build cost | Usually licensed, closed or subscription | |
| Delivery model | Build-to-order, 2-4 weeks from confirmed scope, with UAT + support | Open-ended internal project timeline | Instant install but generic fit |
Häufig gestellte Fragen zu ERPNext Mirakl Marketplace Connector
+Is this an existing app I can download and install right now?
No. This is build-to-order. ECOSIRE builds the connector against your exact ERPNext version, operator list and workflow, then installs and supports it. You are not downloading a generic marketplace app — you get source tailored to your configuration and a git handover.
+How long does delivery take?
Typical delivery is 2-4 weeks from confirmed scope. We start with a short scoping call to lock the operators, order-to-invoice flow, warehouse and price-list mapping and settlement depth; the timeline runs from that confirmed scope. Larger multi-operator or heavily customized builds can run longer and we tell you upfront.
+Does one connector really cover all Mirakl marketplaces?
Yes. Mirakl operators share a common API surface, so we build an operator-agnostic client and store each marketplace's credentials and mapping in a `Mirakl Operator Settings` DocType. Adding Best Buy, Decathlon, Worten or any other Mirakl operator is configuration, not a code rewrite — subject to any operator-specific field requirements we confirm during scoping.
+Which ERPNext versions are supported?
We build and test primarily for Frappe/ERPNext v15, with forward compatibility for v16. Tell us your version at the scoping call and we build against it. Because it is delivered as a proper Frappe app, it installs cleanly via bench and upgrades with your site.
+How do updates and support work after go-live?
Every build includes a defined post-go-live support window for defect fixes and adjustments. Because you receive the full git repository, your team can maintain and extend the code independently, and ECOSIRE can provide ongoing support or Mirakl API-change updates under a separate arrangement.
+Will importing orders create duplicates if the scheduler runs repeatedly?
No. Order sync is idempotent — each Mirakl order id and its acceptance state are stored, so re-polling matches the existing ERPNext Sales Order instead of creating a new one. Failed API calls are logged with retry/backoff and can be safely replayed.
+Can we control who can see and act on each marketplace's data?
Yes. The app uses Frappe's permission model with dedicated role profiles and DocType permissions, so a given operator's team only sees and manages their own orders, offers and settlements. Sensitive server-side actions are exposed only through whitelisted methods.
Verwandte Module
Angebot anfordern
ERPNext Mirakl Marketplace Connector
A build-to-order Frappe app that connects ERPNext to any Mirakl-powered marketplace — importing orders, publishing offers, syncing inventory and price, writing back shipments, and reconciling per-operator settlements from one operator-agnostic connector. ECOSIRE scopes, builds, installs and supports it for you.
- Operator-agnostic Mirakl API client — one connector serves any of the 400+ Mirakl-powered marketplaces via per-operator credentials, no per-marketplace rebuild
- `Mirakl Operator Settings` DocType holds base URL, API key, warehouse, price list, currency and tax mapping so onboarding a new operator is configuration, not code
- Scheduled order import polls Mirakl order endpoints on a `scheduler_events` cron and maps each line into ERPNext `Sales Order` / `Sales Invoice`
- Idempotent order sync stores the Mirakl order id and acceptance state — re-polling never creates duplicate Sales Orders