Carrefour

Carrefour's marketplace runs on Mirakl, and this connector covers the seller surface for each country instance. Agents accept and ship orders, handle returns and refunds, push offer, price and stock imports, message customers, and pull seller accounting documents.

3 triggers 109 actions API key available

Carrefour website Platform Documentation Capability data verified 2026-08-26

On New Order fires for an order sitting in the waiting acceptance state

The agent reads the lines, the customer, the shipping deadline and the channel off the order

Stock and lead time are confirmed line by line against the warehouse

Accept Or Refuse Order Lines answers inside the window, because an unanswered order is refused automatically

Create Shipments builds one shipment per parcel and Update Shipments Tracking records the carrier

The picking queue reaches the warehouse channel with the shipping deadline on every line

A person decides any line the agent cannot confirm, because a refusal is final and it is scored

What This Integration Enables

Carrefour does not run one marketplace. It runs a marketplace per country, each of them a separate Mirakl instance with its own host, its own API key and, more importantly, its own vocabulary. The carrier codes, reason codes, shipping methods, logistic classes, offer conditions, channels, currencies and locales are all defined by the operator of that instance. A workflow that copies a code from a sample response works on one national marketplace and silently fails on the next. This connector is built for that reality: the platform settings operations exist so an agent reads the marketplace's own vocabulary before it uses any of it.

Everything else follows from the seller's position on somebody else's platform. FlowRunner agents answer the acceptance queue inside the window, build one shipment per parcel and confirm each as shipped or ready for collection, run the returns desk from request through receipt and compliance, push offers, prices and stock through the bulk import routes, answer customer and operator threads before the reply clock counts against the shop, and pull the transaction log and billing cycles so payouts reconcile. The scorecard is watching all of it, which is why the human-in-the-loop gate here sits on the bulk writes that cannot be walked back rather than on the routine ones that can.

Without FlowRunner

Every country is its own project Each national marketplace is a separate instance with its own key and its own codes, so the same integration gets rebuilt per country

The acceptance clock runs unattended Orders arriving outside working hours sit in the queue until someone opens the back office, and silence is answered for you

Codes hard coded from a sample Carrier, reason, shipping method and channel codes are copied from one instance and quietly wrong on the next

With FlowRunner

One workflow, many instances The instance host, key and shop are configuration, so the same flow serves the French, Spanish or Italian marketplace

The clock is answered by a flow Acceptance runs on the order's own state and deadline, and the cases needing judgment are escalated rather than left

Vocabulary read from the platform Carriers, reasons, methods, zones and channels are read from the marketplace before they are used

Use Case Scenarios

The acceptance queue answered on time

An order lands in the waiting acceptance state and the trigger fires. The agent reads the lines and checks stock and lead time for each one, resolving the shipping method's own flags first because some methods refuse a shipment without a tracking number. Lines it can fill are accepted through Accept Or Refuse Order Lines. Lines it cannot are posted to Slack with the shipping deadline attached, and a person answers before the window closes. The order then moves into the picking queue, where List Items To Ship carries the deadline on every line so the warehouse works to the promise rather than to arrival order.
Multi parcel fulfillment written back correctly

The warehouse splits an order across two boxes. Rather than confirming the whole order shipped, the agent calls Create Shipments to build one shipment per parcel over the right lines, buys each label through Shippo, records carrier and tracking with Update Shipments Tracking, and only then calls Validate Shipments Shipped, which is what starts the customer debit for those parcels. Click and collect parcels take the ready for pick up route instead. If a shipment was built over the wrong lines, Delete Shipments releases them back into the queue, because a shipment's contents cannot be edited afterwards.
Marketplace money that reconciles itself

On a schedule the agent pulls the transaction log with List Transaction Lines, or starts an asynchronous export when a whole billing period is in scope, and appends every order amount, commission, refund, penalty and payment into a reconciliation sheet in Google Sheets. List Seller Billing Cycles is read alongside it, because a cycle in a failed state is what explains an invoice that was issued and never paid. Commission invoices are downloaded and archived, and the documents the marketplace asks the seller to issue are picked up from the request list so nothing sits waiting on a finance inbox.

Human-in-Loop Highlight

Import Price File runs in delete and replace mode. Every price already sitting on an offer that the uploaded file does not restate is deleted, which means a file listing one channel's price silently removes the volume prices, the discount prices and the other channels' prices from every offer it touches. Save Offers behaves the same way at the offer level: it is a full replace, so any field the payload omits is reset. Neither has an undo, and the error report only tells you which rows were rejected, not which prices quietly disappeared. So the repricing agent stops before it uploads. It posts: "The price file covers 2,140 offers and restates one channel price per offer. 386 of those offers currently carry additional channel or volume prices that this file does not include, and those will be deleted. The affected offer SKUs are attached. Upload as prepared, or restate the missing prices first?" A person answers. The agent built the file, matched it against what the marketplace already holds and named the difference. Deciding to overwrite a national catalog's pricing structure is not a call it makes on its own.

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

109 actions

Shop

Check Platform Health Calls the marketplace's own health check on the configured instance, which is the cheapest way to confirm that the instance URL and the API key are both correct. Needs no identifiers and touches no data.
Get Shop Information Returns the seller's full shop record: contact and address details, channels, currency, applicable taxes, billing and payment information, shipping country, return and recycling policies, and custom fields.
Update Shop Information Updates the shop record, including name, description, email, address, channels, policies and custom fields. It answers success even when individual fields were rejected, listing each rejection, so read the response rather than the status code.
Get Shop Statistics Returns the marketplace's own scorecard for the shop: approval rate and delay, automatic refusal rate, average cart, cancelation and incident rates, late shipment rate, offer count, message response delay and evaluation counts.
List Shop Documents Lists the business documents the marketplace holds about the seller, with each document's identifier, file name, type code and upload date. These are the compliance files, not order documents.
Download Shop Documents Downloads the shop's business documents and stores the result as a FlowRunner file. A single document identifier returns that file directly, and any other combination returns an archive.
Upload Shop Documents Uploads business documents to the shop from FlowRunner files. File names must be distinct, there is one file per document type, and the marketplace caps how many a shop can hold.
Delete Shop Document Permanently removes one business document from the shop. This is irreversible and the file would have to be uploaded again.
List Shop Roles Returns the roles that can be granted to users of this shop, each with its code and description. Used to see which permissions the marketplace exposes before deciding what a back office user or an API key may do.

Offers

List Offers Lists the shop's own offers with price, stock, state, logistic class, lead time to ship, channels, shipping minimums and product details. Filter by condition, by offer or product SKU, or to favorites only.
Get Offer Returns one offer by its marketplace identifier, including the full pricing block: every channel and volume price, the applicable price after discounts, eco contributions, fulfillment center, logistic class and stock.
Save Offers Creates, updates or deletes offers as structured data, and is the synchronous write most workflows should use. It is a full replace rather than a patch, so every field the payload omits is reset.
Import Offers File Uploads a bulk offer file for creation, update or deletion, optionally carrying product information in the same file. The response is a tracking identifier rather than a result, so poll the import status afterwards.
Get Offer Import Returns the progress and line counts of one offer import: lines read, in success, in error and pending, offers inserted, updated and deleted, and whether an error report exists.
List Offer Imports Lists the shop's offer imports with their statistics, filterable by creation date, status, mode and origin. This route pages by token, so pass the previous response's token to continue.
Download Offer Import Error Report Downloads the error report for a failed or partially failed offer import and stores it as a FlowRunner file, in whatever format the import was submitted in.
Export Offers Starts an asynchronous export of the shop's offers and returns a tracking identifier. This is the right way to read a whole catalog, where listing offers is for a page at a time.
Get Offer Export Status Polls an asynchronous offer export and, once complete, returns the URLs holding the generated chunks. A failure carries an error block with a code and detail.
Download Export Chunk Fetches one chunk of a completed asynchronous export from the URL the status call returned and stores it as a FlowRunner file. One operation covers the offer, order and transaction exports, which differ only in which export they belong to.
Import Price File Uploads a price file for the shop's offers and returns an import identifier. The mode is delete and replace, so any price already on an offer that the file does not restate is removed. The operation this page's human gate exists for.
List Price Imports Lists the shop's price file imports with their statistics. This route pages by token, and the marketplace ignores other parameters once a page token is present.
Download Price Import Error Report Downloads the error report for a price file import and stores it as a FlowRunner file. Each row names the rejected offer SKU and the reason, which is the only place a per line price rejection is explained.
Import Stock File Uploads a stock file for the shop's offers and returns an import identifier. This is the lightest way to keep quantities in step with a warehouse system, because it touches only the stock column rather than rewriting whole offers.
Get Stock Import Returns the status and line counts of one stock file import, including how many lines succeeded, how many failed and whether an error report is available.
Download Stock Import Error Report Downloads the error report for a stock file import and stores it as a FlowRunner file, naming each rejected offer SKU and the reason.
List Product Offers Returns every seller's offers on the given marketplace products, which is how a seller sees the competition on a product page: each rival offer's price, shipping, condition, shop grade and premium status.

Orders

List Orders Lists the shop's orders with lines, customer, shipping address, prices, taxes, promotions and current state. Filter on the update window rather than the creation window when synchronizing, because the marketplace widens that window deliberately so nothing is lost to latency.
Accept Or Refuse Order Lines Accepts or refuses the lines of an order waiting for acceptance. This is the most time sensitive operation in the API, because the marketplace measures acceptance rate and delay and an unanswered order is refused for you.
Update Order Tracking Records the carrier and tracking details for one whole order. Supply a carrier code the marketplace knows and it builds the tracking URL itself, or supply a name and URL for one it does not.
Validate Order Shipment Marks a whole order as shipped, which is what starts the customer debit on most payment workflows. This is the single parcel route, so a split order uses the shipment operations instead.
Cancel Order Cancels an order in full. This is irreversible and cancelation rate is one of the scorecard metrics, so partial problems belong in the line level cancelation instead.
Patch Update Orders Updates fields on a batch of orders field by field, leaving what you do not send alone and clearing an optional field when you send an empty value. Carries the seller's own order reference and per line eco contributions.
Update Order Line Shipping Origin Sets where order lines are being shipped from, as a country and address or as a warehouse code. Marketplaces use this for cross border tax and duty, so a wrong origin surfaces later as a tax problem.
Refund Order Lines Creates refunds on order lines, each with the product amount, the shipping amount, an optional fee breakdown and a reason code. A refund moves money and cannot be undone, and tax amounts must match the order's own tax rules.
Cancel Order Lines Cancels part of an order line by line, each with amount, quantity, shipping amount and reason code. This is what to use when only some of an order cannot be fulfilled.
Update Order Custom Fields Writes the operator defined custom fields on an order and its lines. Only the fields you name are touched, and an empty value clears one unless the field is required.
Adjust Order Lines Corrects the actual measurement of order lines upwards or downwards, which is how a seller of weighed or measured goods bills what was really supplied. The marketplace creates the matching refunds or cancelations itself.
Get Order Evaluation Returns the customer's evaluation of one order: the grade, the comment, each individual assessment, whether it is public, and any reply already posted. This is the raw material for a review response workflow.
Resolve Order Incident Marks an open incident on an order line as resolved, with the reason code explaining how it was settled. Incident rate is a scorecard metric, so open incidents are expensive.
Export Orders Starts an asynchronous export of orders and returns a tracking identifier. The marketplace recommends this over listing for anything large, because it handles high volumes and chunks the result.
Get Order Export Status Polls an asynchronous order export until it completes, then returns the URLs holding every generated chunk, or reports a failure or cancelation.
List Order Documents Lists every document attached to the given orders, with identifier, file name, size, type code and upload date. This is the index needed before downloading or deleting one.
Download Order Documents Downloads documents attached to orders and stores the result as a FlowRunner file. Exactly one document identifier returns that file directly, and any other combination returns an archive.
Upload Order Documents Attaches documents to one order from FlowRunner files, which is how a seller delivers an invoice or delivery note through the marketplace. File names must be distinct and the marketplace caps how many an order can hold.
Delete Order Document Permanently removes one document from an order. This is irreversible, and a document the marketplace generated itself cannot be replaced by uploading it again.
List Order Taxes Returns every order tax code the marketplace defines, each with its label and the rule saying whether the marketplace recalculates that tax on a partial refund or expects the seller to supply it.

Shipments

List Picklists Lists the shop's picklists: the pick runs a fulfillment operation works from, each with its pickup date, state, order lines and picklist lines.
Create Shipments Creates shipments over order lines in bulk, each with its lines, quantities, optional tracking and shipping origin. This is the multi parcel workflow, and it is a different concept from validating a whole order as shipped.
List Shipments Lists the shop's shipments with status, customer debit status, lines, tracking, shipping origin and payment details, filterable by order, state, debit state and update window. This route pages by token.
List Items To Ship Lists the order lines waiting to be shipped, each with its shipping address, shipping date, deadline, method and fulfillment information. This is the warehouse work queue, and the deadline is what a late shipment is measured against.
Update Shipments Tracking Records carrier and tracking details on existing shipments in bulk. Supply a carrier code the marketplace knows and it builds the tracking URL, or supply a name and URL for one it does not.
Validate Shipments Shipped Marks shipments as shipped in bulk, which is the multi parcel equivalent of validating a whole order and is what starts the customer debit for those parcels. Send tracking details first.
Validate Shipments Ready For Pick Up Marks shipments as ready to be collected, which is the click and collect counterpart of marking them shipped. Used for methods where the customer collects rather than receives.
Delete Shipments Deletes shipments in bulk, releasing their lines back into the items still to ship. This is irreversible, and it is the correct fix for a shipment built over the wrong lines, because a shipment's contents cannot be edited.
Update Shipment Shipping Origin Sets the warehouse shipments are dispatched from. The origin drives cross border tax and duty, so this is a compliance field rather than a cosmetic one, and per shipment failures are reported inside a success response.
Update Shipment Additional Information Writes the operator defined additional information on shipments, each entry a code, a type and a value. Marketplaces use these for logistics data collected beyond the standard shipment fields.

Returns

Create Returns Opens returns on behalf of customers in bulk, each against an order reference with its lines, quantities, reasons and return method. Marking an entry accepted accepts it immediately rather than leaving it for a decision.
List Returns Lists the shop's returns with state, method, reason, authorization number, return address, tracking, documents and lines. The update window is what an incremental returns sync filters on.
List Items To Return Lists the order lines a customer is still entitled to return, each with the returnable quantity, the return window and its dates, and the methods and reasons available for that line. Read this before opening a return.
Accept Or Refuse Returns Answers return requests waiting for acceptance in bulk. A refusal needs a rejection reason, and both decisions are final.
Patch Update Returns Updates existing returns field by field: the authorization reference, the return address, the carrier tracking and the label URL. The return method can only be changed where the operator allows sellers to do so.
Validate Returns Received Marks returns as physically received at the warehouse, which moves them out of progress and starts the compliance check. Per return failures are reported inside a success response.
Close Returns Marks returns as closed, which is the end of the return lifecycle once the goods have been inspected and any refund issued. Per return failures are reported inside a success response.
Cancel Returns Marks returns as canceled, which is what to use when a customer changes their mind or the request was raised in error.
Set Return Compliance Records whether the goods in a return came back in acceptable condition, line by line, with a non compliance reason and free text when they did not. This is what decides whether a refund is owed.
Create Return Labels Asks the marketplace's connected carriers to generate return labels for existing returns, with package weight and dimensions and either an explicit carrier or automatic selection. Generation is asynchronous.
List Return Labels Lists return label requests with their state, generated files, estimated carrier cost and tracking. This is the polling half of label creation, and a failed request carries the carrier's reason.

Products

Get Products Looks marketplace products up by typed reference, returning SKU, title and category for each. This is the lookup that comes before creating an offer, because an offer must point at a product the operator's catalog already holds.
Import Products Uploads a product file to contribute new products to the operator's catalog, optionally through the marketplace's own transformation and enrichment pipeline. The response is a tracking identifier rather than a result.
Get Product Import Returns the status of one product import with its transformation line counts and, once the operator's system has answered, a breakdown of how many products were synchronized, rejected or carried forward.
List Product Imports Lists the shop's product imports with statuses and line counts, filterable by status, change date and whether a transformed file was produced. This route pages by offset rather than by token.
Download Product Import Report Downloads one of the report files a product import produces and stores it as a FlowRunner file. One operation covers all of them, since they differ only in which file they return.
Get Product Attributes Returns the operator's product attribute configuration for a catalog category and its children: each attribute's code, type, requirement level, example, default, allowed values, roles and transformations.
List Value Lists Returns the operator's value lists, each with its code, label, translations and permitted values. These are the closed vocabularies that list type product attributes draw on.
List Catalog Categories Returns the operator's catalog category tree, each node with its code, label, level, parent and translations. Start from a code to walk a branch, or leave it empty for the whole tree.

Messaging

List Threads Lists the shop's message threads with participants, topic, entities and metadata, optionally including recent messages. The metadata carries how long a seller reply has been outstanding, which is the field a support workflow should watch.
Get Thread Returns one thread in full: every message with sender, recipients, attachments and date, the participants, the topic, the linked entities and the reply metadata.
Reply To Thread Posts a reply into an existing thread, addressed to the operator, the shop or the customer, with optional file attachments and an optional new topic. Recipients are required.
Create Operator Thread Opens a new thread with the marketplace operator and sends its first message. This is the seller to operator channel, for questions about fees, catalog rejections or account setup.
Create Order Thread Opens a thread on one order and sends its first message to the customer, the operator or both. This is how a seller contacts a buyer, with the marketplace intermediating the conversation.
Download Thread Attachment Downloads one attachment from a message thread and stores it as a FlowRunner file. The identifier comes from the attachments block of a message.

Promotions

List Promotions Lists the shop's promotions with type, state, activity window, triggers, rewards, promo codes, channels, customer groups and public descriptions. This route pages by offset.
Create Promotion Creates a seller promotion: a trigger describing what a customer must buy, a reward describing the discount, the activity window, an internal description and an identifier the seller chooses.
Update Promotion Updates an existing promotion, including its window, trigger, reward, channels, audiences and promo codes. The start date and the codes can only be changed while the promotion has not started.

Invoicing and Accounting

List Accounting Documents Lists the accounting documents the marketplace has issued to the shop: invoices and credit notes with totals, taxes, payment state, due date, billing cycle and issuing user.
Download Accounting Document Downloads one accounting document issued by the marketplace and stores it as a FlowRunner file, which is how a commission invoice reaches an accounting system.
List Seller Billing Cycles Lists the periods the marketplace settles the seller over, each with its payout state and provider. This is where a missing payout is diagnosed, because a failed cycle explains an invoice that was never paid.
List Transaction Lines Lists the shop's transaction log: every movement on the seller's marketplace account, including order amounts, shipping, commission fees, tax, refunds, subscription fees, penalties, reserves and payments.
Export Transaction Lines Starts an asynchronous export of the transaction log and returns a tracking identifier. Use it instead of listing when a whole billing period is being pulled into an accounting system.
Get Transaction Log Export Status Polls an asynchronous transaction log export until it completes, then returns the URLs holding every generated chunk, or reports a failure with its error block.
List Document Requests Lists the accounting documents the marketplace is asking the seller to issue, each with type, state, issuer, recipient, entity, amounts, taxes, due date and payment terms. This is the opposite direction from the documents the marketplace issues.
List Document Request Lines Returns the individual lines of one accounting document request, each tied to an order, an order line, a fee or an eco contribution, with unit price and delivery bill information.
Download Accounting Document Requests Downloads the documents attached to accounting document requests and stores the result as a FlowRunner file.
Upload Accounting Documents Uploads the seller's own invoices or credit notes against accounting document requests, from FlowRunner files. Where a request needs several formats they must all be uploaded in the same call.
Confirm Accounting Document Issuance Tells the marketplace that a fees document was issued externally, confirming its number, dates and amounts without uploading a file, and closes out the request.

Platform Settings

Get Platform Configuration Returns the marketplace's high level configuration: its name, tenant, timezone, and the modules and features the operator has switched on. Read this before building anything, because half of this API's behavior depends on it.
List Channels Returns the sales channels enabled on the marketplace. Channels are how one instance serves several storefronts or countries, and their codes appear on offers, orders, promotions and prices.
List Currencies Returns the currency codes activated on the marketplace, each with its label and whether it is the platform default. Used to validate a currency before sending it on a refund or a cancelation.
List Locales Returns the locale codes activated on the marketplace. Every operation here that takes a locale accepts only these values, so this is what to check when a locale is refused.
List Custom Fields Returns the operator defined custom fields for offers, shops, orders and order lines, each with its code, type, label, requirement, whether the seller may edit it and what it validates against.
List Document Types Returns the document types the marketplace defines for orders and for shops, each with its code, label, description and accepted file types. These codes are what the document upload operations require.
List Offer Conditions Returns the offer conditions the marketplace defines, each with its code and label. These are operator specific, so a code from one marketplace is not safe to assume on another.
List Reasons Returns every reason code the marketplace defines in one call, keyed by type: incident, refund, cancelation, return, return rejection, non compliance and the messaging types. Each says whether a seller may use it.
List Shipping Zones Returns the active shipping zones of the marketplace, each with its code, label and description. Zone codes appear on offer shipping prices and are operator specific.
List Shipping Methods Returns the active shipping methods, each with its code, label and the flags that change how a workflow must behave, including whether a shipment can be confirmed without a tracking number.
List Carriers Returns the carriers registered on the marketplace, each with its code, label, standard code and tracking URL template. A carrier in this list needs only a code and a tracking number on the tracking operations.
List Logistic Classes Returns the logistic classes of the marketplace, each with its code, label and description. A logistic class groups products by how they ship, such as bulky, fragile or hazardous.
Get Shop Shipping Configuration Returns the shop's shipping configuration: lead time to ship, delivery times per method and zone, order cut off times, and whether free shipping or operator collected charges apply.
Get Shop Shipping Charges Returns the shipping charges configured for the shop per method, zone and logistic class, with the currency and the date they last changed. Filter to seller overrides to see only what the shop has customized.

Triggers

3 triggers

Event Triggers

On New Order Fires once for each new order placed with the shop, emitting the whole order with its lines, customer and shipping address. This polls rather than subscribes, because the marketplace publishes no seller webhook at all. Watch the waiting acceptance state to drive an acceptance workflow, since an unanswered order is refused automatically and counts against the shop. The first poll records a baseline without firing, so existing orders are not replayed.
On Order Updated Fires when an existing order changes, emitting the whole order. It filters on the marketplace's update date, which the platform deliberately widens by a small delta so an order changed during the previous poll is not lost to latency, and compares timestamps between cycles so an unchanged order does not fire twice. Use it to mirror state changes such as a shipment being received or an incident being opened.
On New Return Fires once for each new return raised against the shop, emitting the whole return with its lines, reason, method and return address. Also a poll rather than a subscription. Watch the waiting acceptance state to drive a return approval workflow, and note that the marketplace asks for a slower cadence on returns than on orders.

Frequently Asked Questions

What can FlowRunner do with Carrefour?

FlowRunner agents can run Check Platform Health, Get Shop Information, and Update Shop Information in Carrefour, plus 106 more actions.

Does connecting Carrefour to FlowRunner require OAuth?

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

Can Carrefour trigger a FlowRunner workflow automatically?

Yes. Carrefour supports 3 triggers that can start a FlowRunner workflow automatically.

Start building with Carrefour

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us