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 one working week 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.