Leroy Merlin Marketplace Connector

Key Features

Mirakl Seller API integration for the Leroy Merlin marketplace, implemented in AL codeunits with `HttpClient`, credentials held in isolated storage rather than plain setup fields

Order import across Mirakl order states (WAITING_ACCEPTANCE, SHIPPING, SHIPPED, RECEIVED, CLOSED) into a staging table, with a configurable state-to-Business-Central document status mapping

Automatic sales order creation using customer templates, marketplace bill-to/ship-to handling, shipping agent and service code mapping, and default dimension assignment per channel

Delta-based stock synchronisation from item ledger quantity, calculated availability or a nominated location and bin set, with per-item safety-stock buffers so marketplace availability never oversells physical stock

Price synchronisation from a nominated price list or sales price group, including discount and promotional windows pushed as Mirakl offer price periods

Offer export with category and attribute mapping: a mapping table translates Business Central item categories, item attributes and variant dimensions into the Leroy Merlin category tree and its required attribute values

Shipment confirmation and tracking push-back via an event subscriber on sales document posting, so posting a warehouse shipment or invoice notifies the marketplace with carrier and tracking number

Settlement and fee reconciliation: import of Mirakl transaction and settlement files, matching to originating orders, and generation of general journal lines for commission, shipping and adjustment fees against configurable G/L accounts

Independent job queue entries per sync direction (offers, stock, prices, orders, shipments, settlements) so a fifteen-minute stock push coexists with a nightly catalogue export

Sync log table and page recording request, response, HTTP status, correlation ID and error text per call, with a re-run action for individual failed records

Retry with exponential backoff and rate-limit awareness on marketplace API calls, so a Mirakl outage produces queued retries rather than a stalled job queue and lost orders

API pages (REST API v2.0 / OData v4) exposing offer state, order sync status and settlement lines for Power BI, Power Automate and Dataverse consumption

Dedicated permission sets separating marketplace administrators, order processors and read-only observers, with no SUPER requirement for day-to-day operation

Application Insights telemetry via `Session.LogMessage` on every sync run, plus optional failure notifications so operations hears about a broken feed before the marketplace does

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Selling on Leroy Merlin's Mirakl-operated marketplace means running a second operational system beside Business Central. Offers are maintained in the Mirakl seller portal, orders arrive there, shipments are confirmed there, and the settlement statement arrives as a file that nobody can tie back to a posted document without a spreadsheet. Business Central out of the box has no concept of a marketplace offer, a Mirakl order state, a commission fee line or a marketplace payout — it has items, sales orders, warehouse shipments and general journals. The gap is not a missing button; it is a missing translation layer, and the usual fallback is somebody re-keying orders every morning and reconciling fees at month end.

We build that translation layer as a proper AL extension for your tenant. The connector talks to the Mirakl Seller API over HTTPS from codeunits using HttpClient, with credentials held in isolated storage rather than in a setup field, and stores its own state in new tables: a marketplace channel setup, an offer register keyed to Item No. and variant, an order staging table, and settlement lines. Table and page extensions add the marketplace fields where your users already work — a marketplace order reference and channel on the Sales Header, an offer state and marketplace SKU FactBox on the Item Card. Nothing is bolted onto a separate console; the Sales Order List you already use is where marketplace orders land.

Technically the flow is event-driven where Business Central gives us events and scheduled where it does not. Offer publication and price/stock updates run as job queue entries at the cadence you choose, sending only deltas so you are not pushing the whole catalogue every fifteen minutes. Inbound orders are pulled, staged, validated against your item and customer master, then converted to sales orders with a configurable customer template, dimension defaults and shipping-agent mapping; anything that fails validation stays in staging with a readable error rather than silently disappearing. Shipment confirmation and tracking numbers are pushed back through an event subscriber on sales document posting, so posting a warehouse shipment in Business Central is what tells Leroy Merlin the parcel is on its way. Settlement files are imported and matched to their originating orders, with commission and shipping fees posted as configurable G/L entries so marketplace revenue reconciles without a spreadsheet. API pages (REST API v2.0 / OData v4) expose the sync log and offer state, so Power BI, Power Automate or a Dataverse flow can read status without anyone opening the client.

Everything ships with dedicated permission sets, telemetry to Application Insights via Session.LogMessage, and retry-with-backoff on API failures so a marketplace outage produces a queued retry rather than a stuck job queue and a lost order. We target the Business Central release wave you are actually running, and support both online (SaaS, per-tenant extension or AppSource-format app) and on-premises deployments.

This is build-to-order, not a download. You request a quotation, we run a scoping call to confirm your Mirakl shop configuration, item and variant model, tax and dimension setup, fulfilment process and settlement posting rules, then we quote a fixed scope. Typical delivery is 2-4 weeks from confirmed scope. You get the AL source code compiled for your version, installation and configuration on your sandbox first, UAT against Mirakl test credentials, and a documented rollback plan before we touch production.

What you get

Installable AL extension source code compiled for your exact Business Central version and deployment type (SaaS per-tenant extension or on-premises app)

Installation and configuration on your sandbox environment, including Mirakl credential setup, category and attribute mapping, and job queue scheduling

Technical documentation: object range, table and page extension inventory, event subscribers, API endpoint reference and integration architecture diagram

End-user guide plus a live training session for your order-processing and finance teams, recorded for later onboarding

UAT on a staging environment against Mirakl test credentials, with a signed-off test script and a documented rollback plan before the production install

Post-go-live support window for defect fixes on the delivered scope, with an agreed response window

Git repository handover with full commit history, branch structure and build pipeline configuration, so your team or another partner can take it forward

Deployment runbook covering the production install, permission set assignment, first full catalogue export and settlement cut-over

Who this is for

Marketplace / E-commerce Manager

Owns the Leroy Merlin shop and its commercial performance. Needs offers published with correct categories and attributes, prices and stock accurate within minutes, and no manual re-listing when the catalogue changes in Business Central.

Order Fulfilment / Operations Lead

Processes marketplace orders alongside every other channel. Wants marketplace orders to appear as ordinary Business Central sales orders with the right customer, dimensions and shipping agent, and wants posting a shipment to be the only action needed to notify the marketplace.

Finance Manager / Controller

Has to reconcile marketplace payouts to revenue. Needs commission, shipping and adjustment fees posted to the correct G/L accounts and matched to their originating orders, so the settlement statement ties to the trial balance without a spreadsheet.

IT Manager or Business Central Partner

Accountable for the tenant's extension estate and upgrade path. Needs a clean AL extension with its own object range, permission sets, telemetry and source code in a repository they can maintain — not an opaque black box with no exit route.

How Leroy Merlin Marketplace Connector Compares

Criterion	ECOSIRE	Custom Build	Competitor	Dynamics 365 Business Central Native
Fit to your Mirakl shop configuration	Built against your actual category tree, attributes and variant model, confirmed during scoping	Same fit achievable, but you carry the discovery and design effort in-house	Generic mapping layer; unusual attributes often need workarounds or manual upkeep	No marketplace concept exists — offers, orders and fees have no counterpart
Order import and status mapping	Staged import with configurable Mirakl-state mapping and readable validation errors	Whatever your team builds and then maintains, error handling included	Usually present, with a fixed state model you adapt your process to	Manual re-keying from the Mirakl seller portal
Settlement and fee reconciliation	Settlement import matched to orders, with configurable G/L posting for commission and shipping fees	Often the first thing descoped when timelines tighten, leaving month-end spreadsheets	Varies widely; many apps import orders but stop short of finance posting	Spreadsheet reconciliation against the marketplace statement
Source code ownership	Full AL source in your git repository, yours to maintain or reassign	You own it — and every future fix and release-wave regression too	Closed source; behaviour changes when the vendor ships an update	Not applicable
Ongoing cost model	Fixed build price plus an optional annual maintenance agreement	Developer time indefinitely, including release-wave compatibility work	Per-user or per-order subscription that scales with your success	No licence cost, paid instead in operations headcount
Time to a working system	2-4 weeks from confirmed scope, sandbox first with UAT and rollback	Typically several months across discovery, build and stabilisation	Fast to install, then weeks of configuration and process compromise	Immediate — because nothing is automated
Upgrade and release-wave safety	Extension-only design with a dedicated object range, no base app modification, tested per release wave	Depends entirely on the discipline of whoever wrote it	Vendor-controlled; you wait for their compatibility release	Nothing to break, nothing to gain
Observability when a sync fails	Sync log with request, response, correlation ID, re-run action and Application Insights telemetry	Frequently the last feature built, if it is built at all	Basic error list; root-cause detail often not exposed to you	Failure surfaces as a customer complaint

Frequently Asked Questions about Leroy Merlin Marketplace Connector

How long does delivery take?

This is a build-to-order product, not an AppSource download. After you request a quotation we run a scoping call (about 30 minutes) to confirm your Mirakl shop setup, item and variant model, tax, dimension and fulfilment rules, and settlement posting expectations. From confirmed scope, typical delivery is 2-4 weeks. Wider scope — unusual variant structures, multi-company or multi-shop setups, custom fee posting rules — can extend that, and we tell you before you commit, not after.

Is this an existing app I can install today from Microsoft AppSource?

No. We build it for your tenant and your Business Central version. That is deliberate: Mirakl marketplace configurations differ per seller — category trees, required attributes, fulfilment models and settlement structures are not uniform — and a generic app forces you to bend your data to fit it. You receive the AL source code, so the result is yours to maintain, extend or hand to another partner.

Which Business Central versions and deployment types are supported?

We target the release wave you are actually running and support both Business Central online (SaaS) and on-premises. For SaaS we deliver a per-tenant extension by default, or build to AppSource technical standards if you plan to publish it yourself. For on-premises we deliver the compiled app plus a deployment runbook. We ask for your exact version and localisation during scoping so the build targets it from day one.

What happens with support, bug fixes and Business Central updates?

The delivered scope comes with a post-go-live support window for defect fixes at no extra cost. Beyond that we offer an annual maintenance agreement covering compatibility with new Business Central release waves and changes to the Mirakl Seller API — marketplaces do change their APIs, and an unmaintained connector eventually stops importing orders quietly. Because you hold the source code in your own git repository, you are never locked into us for that maintenance.

Will marketplace orders behave like normal Business Central sales orders?

Yes. Imported orders are real sales orders in the standard tables, created through the standard posting routines, with marketplace-specific fields added via table and page extensions. Your existing workflows, approvals, warehouse processes, reports and Power BI models keep working. We do not create a parallel document universe, and we do not modify base application objects.

How does stock synchronisation avoid overselling?

You choose the availability source — item ledger quantity, calculated availability net of open orders, or a nominated location and bin set — and set a per-item or per-category safety-stock buffer that is withheld from the marketplace figure. Stock pushes run on their own job queue schedule, independent of the catalogue export, and send only changed quantities, so a fifteen-minute cadence stays practical even with a large catalogue.

What do you need from us to start?

For scoping: your Business Central version and deployment type, sandbox access, Mirakl seller API credentials for a test shop, a sample of your item and variant data, and a recent settlement statement. For the build we work on your sandbox first — production is never touched until UAT is signed off and the rollback plan is documented.