Leroy Merlin

Leroy Merlin's marketplace runs on Mirakl, and this connector covers the whole seller workflow. Agents accept orders as they arrive, push shipment confirmations and tracking from a warehouse system, handle returns and refunds, manage offers, prices and stock, and reconcile settlements.

1 trigger 115 actions API key available

Leroy Merlin website Platform Documentation Capability data verified 2026-08-26

On Order Created Or Updated reports an order sitting in Waiting Acceptance

Agent reads the order lines with their SKUs, quantities, and shipping origin

Live stock for each SKU is read from the warehouse system of record

Accept Or Refuse Order Lines answers line by line rather than accepting the order whole

Create Shipments and Update Shipment Tracking push the carrier detail back to the marketplace

The fulfillment channel gets the accepted order and the lines that were refused

Lines the stock check cannot cover go to a person, who decides between refusing and sourcing

What This Integration Enables

Selling on Leroy Merlin is not running a store. It is trading inside somebody else's, under rules the operator sets and against a scorecard the operator keeps. Acceptance rate, cancellation rate, and shipping performance are not internal metrics here, they are the terms of your continued presence on the marketplace. That is the frame this integration is built for, and it is why the operations worth automating are the time-sensitive ones: accepting order lines while the clock is running, pushing tracking the moment the parcel leaves, and answering messages before a thread ages.

The marketplace runs on Mirakl, so every operation carries its Mirakl operation code in its description, which is the identifier Leroy Merlin's seller support and every Mirakl integration guide actually use. The connector covers the whole seller workflow: orders and their documents, shipments, customer returns and return labels, offers with their price and stock imports, product imports into the operator catalog, the messaging inbox, settlement and accounting documents, promotions, and the reference data all of it depends on. FlowRunner's connectors are built and verified against each vendor's official API, and Mirakl's own per-operation call frequency guidance is repeated on each action, because on this platform polling too fast is a compliance question rather than a performance one.

Without FlowRunner

Acceptance runs on someone's attention Orders wait in the seller portal until a person opens it, and the acceptance clock keeps running

Tracking retyped between systems A carrier number lives in the warehouse system and gets copied into the portal by hand

Settlement reconciled at month end Commission and refund lines are matched against invoices long after anything can be queried

With FlowRunner

Acceptance follows live stock Each line is answered against what the warehouse actually holds, within the operator's cadence

The warehouse writes to the marketplace Shipments, tracking, and validation are pushed from the system that already knows them

Settlement reconciles continuously Transaction lines are pulled per billing cycle and unmatched lines surface while they still matter

Use Case Scenarios

Acceptance decided by stock, not by whoever is at the desk

The trigger polls for orders in Waiting Acceptance. For each one the agent reads the lines, checks live availability per SKU against the warehouse system, and answers with Accept Or Refuse Order Lines, which works line by line rather than forcing an all-or-nothing call on the order. Accepted lines move straight into fulfillment. Refused lines carry a reason code pulled from List Reasons rather than a guess, because reason codes are per-marketplace and per-role. The result is that acceptance happens at the speed of the stock check, and a person is only involved when the stock check is inconclusive.
Settlement that reconciles while it still matters

On a schedule the agent pulls List Transaction Lines for the current billing cycle and matches each commission, refund, and adjustment line against the accounting system through Xero. Lines that match are logged. Lines that do not are posted to the finance channel in Slack with the order reference and the amount, while the order is still recent enough for support to answer a question about it. The reconciliation stops being a month-end archaeology exercise.
The returns queue, worked end to end

List Items To Return gives the agent the queue on a schedule. For each return it applies the policy: accept or refuse, then validate as received when the warehouse scans it in, set compliance where the item came back damaged, and close it out. Create Return Labels is asynchronous, so the agent polls List Return Labels until the label leaves its pending state rather than assuming it exists. Returns that fall outside policy, or where the customer's message contradicts the warehouse's inspection, are handed to a person with both accounts side by side.

Human-in-Loop Highlight

Import Offers File carries a mode, and the mode decides whether the file is an update or a replacement for your entire catalog. In Replace mode Mirakl treats the file as the complete set of offers and deletes every offer missing from it. Nothing about the call looks different: same operation, same file, one flag. The import is asynchronous too, so the error report that would tell you what happened arrives after the deletions have already been applied, and on a marketplace where your listings are your presence, a catalog that silently shrinks is not a data problem, it is a revenue outage that also moves your scorecard. So a catalog agent never chooses that flag on its own. It prepares the file, compares its contents against List Offers, and stops: "Offer file ready, 2,140 rows. Your live catalog holds 2,489 offers. Replace mode would delete the 349 offers not in this file, listed below by SKU. Import in Normal mode, import in Replace mode, or cancel?" The catalog owner answers. The agent is entirely capable of building the file. Deciding that the absence of a row means the offer should die is a different kind of decision, and it belongs to a person.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

115 actions

Orders

List Orders Lists orders with filters on state, date, and channel (OR11). Mirakl asks that this be polled no more than once a minute.
Get Order Retrieves one order with its lines, customer, and totals (OR12).
Accept Or Refuse Order Lines Answers a Waiting Acceptance order line by line, which is where an auto-acceptance rule actually lands.
Update Order Tracking Writes the carrier and tracking number onto an order.
Validate Order Shipment Confirms the order as shipped (OR24), which is the call that stops the shipping clock on the operator's scorecard.
Cancel Order Cancels an order (OR29). Published as a PUT, but not idempotent and not reversible.
Cancel Order Lines Cancels individual lines across orders.
Refund Order Lines Refunds lines, spanning several orders in one call (OR28). Taxes and shipping taxes must be carried where the order has them.
Update Orders Updates several orders in one call, each with its own error entry in the response.
Update Order Line Shipping Origin Changes the origin a line ships from, which affects delivery promise and duties.
Update Order Custom Fields Writes the operator's custom fields onto orders.
Adjust Order Lines Adjusts line quantities or amounts within the operator's rules.
Resolve Order Incident Closes an incident the operator or customer raised against an order.
Get Order Evaluation Reads the customer's evaluation of an order.
List Order Taxes Returns the tax codes an order carries, which refunds and cancellations must include.
Export Orders Starts an asynchronous order export and returns a job to poll.
Get Order Export Status Polls an order export until it completes and hands back the URLs to fetch.
List Order Documents Lists the documents attached to orders, such as invoices.
Download Order Documents Fetches order documents into FlowRunner file storage. Anything naming more than one document comes back as a ZIP archive.
Upload Order Document Attaches a document to an order. An order holds at most fifty, with distinct file names.
Delete Order Document Permanently deletes a document from an order.
Download Export File Fetches a completed export chunk from the URL an export status response supplied, sending the API key with the request.

Shipments

List Shipments Lists shipments with seek pagination.
List Items To Ship Lists the lines still waiting to be shipped, which is the queue a fulfillment flow drains.
Create Shipments Creates shipments in bulk. The response carries a success list and an error list, so read the body rather than the status.
Update Shipment Tracking Writes carrier and tracking onto existing shipments in bulk.
Validate Shipments As Shipped Confirms shipments as dispatched.
Validate Shipments As Ready For Pickup Confirms shipments as ready for collection on click-and-collect orders.
Delete Shipments Deletes shipments and returns their lines to the pool still to ship. Published as a PUT, and not reversible.
Update Shipment Shipping Origin Changes the origin recorded on shipments.
Update Shipment Additional Information Writes the operator's additional information fields onto shipments.

Returns

List Returns Lists customer returns with seek pagination.
List Items To Return Lists the items customers are returning, which is the queue a returns flow starts from.
Create Returns Creates returns in bulk, up to two hundred per call.
Update Returns Updates existing returns.
Accept Or Refuse Returns Answers return requests with a reason code the shop's role is allowed to use.
Validate Returns As Received Marks returns as received once the warehouse scans them in.
Close Returns Closes returns once the outcome is settled.
Cancel Returns Cancels returns. Published as a PUT, and not reversible.
Set Return Compliance Records whether a returned item came back in the condition the policy requires.
Create Return Labels Requests carrier return labels. Asynchronous, so poll rather than assuming the label exists.
List Return Labels Lists return labels and their state, which is how a pending label request is followed to completion.

Offers, Prices and Stock

List Offers Lists the shop's offers with their price, stock, and state.
Get Offer Retrieves one offer by its numeric Mirakl offer id.
Get Offer Stock Reads an offer's stock. A zero here means either genuinely empty or unavailable, so it is not proof of an empty shelf on its own.
Create Update Or Delete Offers Writes offers, with an action per offer choosing between writing and deleting. A full replace rather than a patch: fields not sent are reset, so omitting quantity sets stock to zero.
Import Offers File Imports an offer file asynchronously. Normal mode updates; Replace mode treats the file as the entire catalog and deletes every offer missing from it. The operation this page's human gate exists for.
List Offer Imports Lists offer import jobs and their state.
Get Offer Import Reads one offer import's progress and counts.
Get Offer Import Error Report Fetches the rejected rows from an offer import, which is where a silent partial failure becomes visible.
Import Prices File Imports a price file. Delete-and-replace per offer, so send the complete price set for each offer rather than only the price that changed.
Import Stock File Imports a stock file for the shop's offers.
List Price Imports Lists price import jobs.
Get Price Import Error Report Fetches the rejected rows from a price import.
Get Stock Import Status Polls a stock import, at the fastest cadence Mirakl allows on any of these.
Get Stock Import Error Report Fetches the rejected rows from a stock import.
Export Offers Starts an asynchronous export of the shop's offers.
Get Offer Export Status Polls an offer export until it completes and hands back the URLs to fetch.
List Product Offers Lists the offers attached to given products, up to one hundred references per call.

Products

Get Products Reads operator catalog products by reference. Shop SKUs are rejected here, so use an operator reference type such as EAN.
Import Products File Submits new products into the operator's catalog for review.
List Product Imports Lists product import jobs.
Get Product Import Reads one product import's progress and counts.
Get Product Import Error Report Fetches the rows the operator rejected.
Get Product Import Added Products Report Fetches the products the operator accepted into its catalog.
Get Product Import Transformed File Fetches the file after the operator's transformation rules were applied.
Get Product Import Transformation Error Report Fetches the rows that failed transformation rather than validation.

Messaging

List Message Threads Lists inbox threads with customers and the operator, seek paginated at fifty by default.
Get Message Thread Reads one thread with its messages and attachments.
Reply To Message Thread Posts a reply into an existing thread.
Create Operator Thread Opens a new thread with the marketplace operator.
Create Order Thread Opens a new thread against an order, which is how a customer question about a specific order is started.
Download Message Attachment Fetches an attachment from a thread into FlowRunner file storage.

Settlement and Accounting

List Accounting Documents Lists the settlement documents the operator has issued.
Download Accounting Document Fetches one accounting document into FlowRunner file storage.
List Seller Billing Cycles Lists the shop's billing cycles, which is what settlement is grouped by.
List Transaction Lines Lists individual commission, refund, and adjustment lines, seek paginated with a high ceiling.
Export Transaction Lines Starts an asynchronous export of transaction lines. Once per day at most.
Get Transaction Log Export Status Polls a transaction log export until it completes.
List Accounting Document Requests Lists the documents the operator is asking the shop to supply.
List Accounting Document Request Lines Reads the lines of a document request, including which formats are demanded.
Download Accounting Document Request Files Fetches the files attached to a document request.
Upload Accounting Document Uploads accounting documents, up to fifty per call. When a request demands several formats they must all go in the same call.
Confirm Accounting Document Issuance Confirms that documents have been issued, up to one hundred confirmations per call.

Shop

Get Shop Information Reads the shop's own configuration. Once per day at most.
Update Shop Information Updates shop details. The response carries both an updated block and a field-level error array.
Get Shop Statistics Reads the scorecard: acceptance rate, cancellation rate, average cart, and the rest. Once per day at most.
List Shop Documents Lists the shop's business documents. Requires at least one of shop ids or an updated-since filter (S30).
Download Shop Documents Fetches shop documents into FlowRunner file storage.
Upload Shop Document Uploads a business document. A shop holds at most fifty, one file per document type.
Delete Shop Document Permanently deletes a shop document. Removing a compliance document the operator requires can put the shop back into a pending state.
Get Shop Shipping Configuration Reads how the shop's shipping is configured on the marketplace.
Get Shop Shipping Charges Reads the shipping charges the shop applies per zone and method.

Promotions and Picking

List Promotions Lists the shop's promotions and their state.
Create Promotion Creates a promotion. Depending on the operator's configuration it may start in pending approval rather than going live.
Update Promotion Updates a promotion. Its promo code and start date become uneditable once it is running.
List Picklists Lists picklists for warehouse preparation.

Platform and Reference Data

Check Platform Version Reads the Mirakl platform version. It sits above the authentication filter, so it proves the host is right before the key is checked.
Get Platform Configuration Reads the operator's platform configuration.
List Carriers Lists the carriers the marketplace recognizes.
List Shipping Zones Lists the operator's shipping zones.
List Shipping Methods Lists the shipping methods available to the shop.
List Logistic Classes Lists the logistic classes offers are categorized by.
List Channels Lists the sales channels the operator runs.
List Currencies Lists supported currencies.
List Locales Lists supported locales.
List Document Types Lists the document types the operator defines, including which are reserved to the operator.
List Custom Fields Lists the operator's custom field definitions.
List Offer Conditions Lists the conditions an offer may declare, such as new or refurbished.
List Reasons Returns every reason code in one call with its type, and an indicator of whether the key's role may use it (RE01).
List Reasons By Type Returns reason codes filtered to one type, which is still useful even though the unfiltered call covers it (RE02).
List Category Hierarchies Lists the operator's category tree.
List Product Attributes Lists the attributes the operator's catalog expects on products.
List Value Lists Lists the operator's controlled value lists for attributes.
List Shop Roles Lists the roles a shop user may hold, which is what decides why a valid key is refused on one operation.

Triggers

1 triggers

Event Triggers

On Order Created Or Updated Polls Mirakl for orders created or changed since the last run, using the platform's own update-date filter. Mirakl subtracts a safety delta so no order is missed, which means an order can arrive twice around a poll boundary, so make the downstream flow idempotent on the order id. The first poll records a baseline and emits nothing, each poll fetches at most one hundred orders, and restricting the trigger to Waiting Acceptance is what turns it into an auto-acceptance flow. Mirakl publishes no webhooks to sellers, so polling is the honest mechanism rather than a fallback.

Frequently Asked Questions

What can FlowRunner do with Leroy Merlin?

FlowRunner agents can run List Orders, Get Order, and Accept Or Refuse Order Lines in Leroy Merlin, plus 112 more actions.

Does connecting Leroy Merlin to FlowRunner require OAuth?

No. Leroy Merlin connects to FlowRunner with an API key, no OAuth flow required.

Can Leroy Merlin trigger a FlowRunner workflow automatically?

Yes. Leroy Merlin supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Leroy Merlin

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us