Auchan

Auchan runs its marketplace on Mirakl, and this connector covers the seller side end to end. Agents accept orders inside the acceptance window, ship and refund them, push stock and price imports, answer customer messages, and reconcile payouts and accounting documents.

2 triggers 111 actions API key available

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

On Return Updated fires for a return that has moved into a new state

The agent reads the lines, quantities, reason codes and the order behind them

List Items To Return confirms each line is still inside its return window

Accept Or Refuse Returns answers the request, with a reason code when it is refused

Validate Returns As Received records the parcel arriving at the warehouse

The returns desk sees the parcel alongside the customer's stated reason and the order history

The person holding the goods records whether they came back in acceptable condition

What This Integration Enables

Selling on Auchan's marketplace means being graded continuously. The platform keeps a scorecard on every shop: approval rate and approval delay, cancelation rate, incident rate, refund and return rates, late shipment rate, valid tracking rate, message response delay and an overall grade. Every one of those numbers is the byproduct of an operational decision made or not made in time, which is why this connector is worth automating in a particular order. The metrics are not a report to read at month end. They are the queue.

FlowRunner agents work that queue. They answer the acceptance decision inside the window, because an unanswered order is refused for you and the delay is recorded. They build one parcel per shipment, attach tracking before validating so a method with mandatory tracking does not reject the confirmation, and watch the shipping deadline on every outstanding line. They run the returns desk from request to closure, close incidents with a resolution reason before the incident rate absorbs them, and reply to threads before the outstanding reply clock counts against the shop. And they pull the transaction ledger, the billing cycles and the invoice obligations so payouts reconcile without a monthly spreadsheet. The human-in-the-loop gate on this page sits where the marketplace asks the seller to make a judgment it cannot verify.

Without FlowRunner

The scorecard is read after the fact Approval delay, incident rate and message response time are reviewed monthly, once the damage is already in the number

Returns handled in batches Requests, receipts and compliance checks are worked through when the desk has time, which is rarely when the clock started

Money reconciled by hand Commissions, refunds, penalties and payouts are matched to invoices in a spreadsheet built once a month

With FlowRunner

The metrics drive the workflow Acceptance, incidents and unanswered threads are worked from the same fields the marketplace grades on

Returns move on their own states Each return advances through acceptance, receipt and closure as its state changes, with people involved where judgment is needed

The ledger reconciles continuously Transaction lines, billing cycles and issued documents are pulled on a schedule and matched as they arrive

Use Case Scenarios

The acceptance clock, answered by a workflow

Orders arrive at the marketplace's pace and not at the warehouse's. The agent polls for orders in the waiting acceptance state, reads the lines, and confirms stock and lead time for each. Lines it can fill are accepted through Accept Or Refuse Order Lines, which is the operation the approval rate and approval delay are measured from. Anything ambiguous is posted to Slack with the deadline attached so a person answers rather than the clock answering for them. Accepted orders flow into the packing queue, where List Items To Ship carries the shipping deadline that the late shipment rate is scored against.
Parcels, tracking and the order that ships in two boxes

A picked order goes out as two parcels. The agent calls Create Shipments to build a shipment per parcel over the right lines, buys each label through Sendcloud, records the carrier and tracking with Update Shipment Tracking, and only then calls Validate Shipments As Shipped. The order matters: some shipping methods refuse a shipment confirmation without a tracking number, and the marketplace also keeps a valid tracking rate. Click and collect parcels take the ready to pick up route instead. Where a warehouse fed the wrong lines into a shipment, Delete Shipments puts them back in the packing queue rather than leaving a parcel nobody can edit.
Payouts that explain themselves

On a schedule the agent pulls List Transaction Lines, or starts an asynchronous export when a whole cycle is in scope, and appends every order amount, commission, refund, fee and penalty into a reconciliation sheet in Google Sheets. List Seller Billing Cycles is read next to it, because a cycle showing a failed payout is what explains an invoice that was raised and never paid. Commission invoices are downloaded and archived. On the other side of the ledger, List Accounting Document Requests carries the invoices the marketplace expects the seller to issue, so obligations are worked from a queue rather than discovered late.

Human-in-Loop Highlight

Set Return Compliance is the operation that decides whether a customer gets their money back. It records, line by line, whether returned goods came back in acceptable condition, with a non compliance reason where they did not. An agent can see the return request, the stated reason, the order history and the tracking that proves a parcel arrived. What it cannot see is the item. Nothing in the seller API reverses a compliance verdict once written, and a wrong one either takes a refund from a customer who deserved it or pays out on goods that came back broken. So the returns workflow drives everything up to that point and stops. The agent posts to the desk: "Return RMA 88214 received today against order 4193021. Customer reason: item does not match description. Two lines, quantity one each. The order shipped nine days ago and the return window closes in four. Photos from the customer thread are attached. Record both lines compliant, or name a non compliance reason?" The person with the goods in their hands answers. The agent did the receiving, the deadline arithmetic and the evidence gathering, and it left the one judgment that requires eyes on the item 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

111 actions

Shop

Get Shop Information Returns your shop's full record: contact and billing details, channels, currency, approval rate and delay, offer and order counts, shipping settings and compliance status.
Update Shop Information Updates the shop record. It answers success even when individual fields were rejected, carrying an errors array beside whatever was applied, so read the response rather than the status code.
Get Shop Statistics Returns the shop's performance metrics per period: approval rate and delay, cancelation, incident, refund and return rates, late shipment rate, valid tracking rate, grade and average cart. This is the scorecard the marketplace judges the shop on.
List Shop Documents Lists the business documents attached to the shop, each with its id, type, file name and upload date. The marketplace requires either shop ids or an update window and refuses a call with neither.
Upload Shop Document Uploads one business document to the shop, such as a registration certificate or an insurance policy. Only the failures are reported, so anything missing from the response was accepted.
Download Shop Documents Downloads the shop's business documents into FlowRunner file storage. One document id returns that file directly, and more than one comes back as an archive.
Delete Shop Document Permanently removes one business document from the shop. The marketplace answers with no body, so this operation returns the deleted id for the workflow to carry forward.
List Shop Roles Returns the user roles available on the shop account, each with its code and description. These are the permission sets the marketplace grants to people in your organization.
Check Platform Health Checks that the marketplace platform is up. The cheapest call in the API and the only one needing nothing but the instance URL, so it separates a wrong host from a wrong key.

Platform Settings

List Custom Fields Returns the marketplace's custom field definitions with each field's code, label, entity, type, requirement, editability, accepted values and validation pattern.
List Channels Returns the sales channels enabled on the marketplace, each with its code, label and description. Channel codes appear on per channel offer prices, order filters and promotions.
List Currencies Returns the currency codes activated on the marketplace, flagging the platform default. Use these codes on refunds, cancelations and offer prices where a shop trades in more than one.
List Document Types Returns the document type codes the marketplace defines, with the entity each applies to and the file types it accepts. The document upload operations require one of these codes.
List Locales Returns the locale codes enabled on the marketplace, flagging the platform default. These are the only values the locale parameter on localized operations accepts.
List Offer Conditions Returns the offer condition codes the marketplace accepts, such as new or refurbished, in the order set in the back office. An offer write requires one of these.
List Reasons Returns every reason code the marketplace defines, keyed by type across cancelation, refund, incident opening and closing, returns and messaging, flagging which ones a shop may use. One call covers every reason list in the API.
List Shipping Zones Returns the active shipping zones, each with its code, label and description. Shipping charges and offer shipping prices are expressed per zone.
List Shipping Methods Returns the active shipping methods, each flagged for click and collect, delivery by the operator, whether tracking is mandatory and whether it ignores the lead time. Those flags change how a fulfillment workflow must behave.
List Carriers Returns the carriers registered on the marketplace, each with its code, label, standard code and tracking URL template. A registered carrier is identified by code alone on the tracking operations.
List Logistic Classes Returns the logistic classes defined on the marketplace. A logistic class groups offers that ship the same way and drives the shipping charge that applies.
Get Shop Shipping Configuration Returns the shop's shipping configuration: lead time to ship with both the platform default and the shop's own value, delivery times per zone and method, and order cut off times.
Get Shop Shipping Charges Returns the shipping charges configured for the shop per logistic class, zone and method, with a flag showing where the shop has overridden the platform value.
Get Platform Configuration Returns which modules and features the marketplace has enabled, including catalog manager, promotions, returns, shipments, warehouses, multi currency and tax collection. Read this before building anything, because much of the API's behavior depends on it.

Offers

List Offers Lists the shop's offers with price, discount, quantity, condition, lead time to ship, logistic class, channels, availability window and the product each is attached to. This route pages by offset.
Get Offer Returns one offer in full, including every channel price, the volume price ranges, the applicable price after discounts, eco contributions, custom fields and the fulfillment center.
Create Or Update Offers Creates, updates or deletes offers synchronously, and is the write most workflows should use rather than building a file. Send every field an offer should keep, because omitted fields are not preserved.
Import Offers File Uploads a bulk offer file for creation, update or deletion and returns an import id to poll. The response is a tracking id and not a result, so nothing has been imported when it returns.
List Offer Imports Lists the shop's offer imports with their statistics: lines read, in success, in error and pending, offers inserted, updated and deleted, the origin, the status and whether an error report exists.
Get Offer Import Returns one offer import's status and statistics. This is the poll that turns a submitted file into a known result.
Download Offer Import Error Report Downloads the error report for an offer import into FlowRunner file storage. The report holds the rejected lines with their reasons, ready to be corrected and resubmitted.
Export Offers Starts an asynchronous export of the shop's offers and returns a tracking id. Use it rather than listing for a full catalog, and set a change window for a differential export.
Get Offer Export Status Returns the status of an asynchronous offer export and, once complete, the URLs of the chunk files. The second leg of a three part export.
Download Offer Export File Downloads one chunk of a completed offer export into FlowRunner file storage. Called once per URL the status operation returned.
Import Price File Uploads a price file for the shop's offers and returns an import id to poll. The mode is delete and replace, so any price on an offer that the file does not restate is removed.
List Price Imports Lists the shop's price imports with their statistics. A complete import can still hold rejected offers, so read the counts rather than the status alone.
Download Price Import Error Report Downloads the error report for a price import into FlowRunner file storage. It contains only the offers with at least one price in error, with the reason for each.
Import Stock File Uploads a file to update offer quantities, globally or per warehouse, and returns an import id to poll. This is the cheap way to keep stock in step, because it touches only quantities rather than rewriting offers.
Get Stock Import Status Returns a stock import's status and statistics. A complete status does not mean every line landed, so check the error counts.
Download Stock Import Error Report Downloads the error report for a stock import into FlowRunner file storage, holding only the failing lines with their line numbers and reasons.
List Product Offers Lists every offer on the marketplace for the given products, yours and your competitors', with prices, conditions, shop grades and shipping. This is the competitive pricing read.

Orders

List Orders Lists the shop's orders with lines, customer, shipping address, prices, taxes, refunds, promotions, custom fields and state. The central read of the whole API, and filtering by state is how each queue is built.
Patch Orders Updates orders field by field, which is how your own system's reference lands on a marketplace order. Errors are nested per order inside a success response, so read the body rather than the status.
Accept Or Refuse Order Lines Accepts or refuses the lines of an order waiting for a decision. This is the clock the marketplace judges the shop on, since approval rate and delay are both measured from it and silence is answered as a refusal.
Update Order Tracking Sets or replaces the carrier and tracking information on a whole order. Call it before validating the shipment when the shipping method makes tracking mandatory.
Validate Order Shipment Marks a whole order as shipped, which starts the customer debit on payment workflows that settle on shipment. This is the single parcel path, so a split order uses the shipment operations instead.
Cancel Order Cancels an entire order, every line at once. This is irreversible and counts toward the cancelation rate on the scorecard, so partial problems belong in the line level operation.
Update Order Line Shipping Origin Records where each order line actually ships from, by warehouse or by address. The origin decides the tax treatment on a cross border order, so this is a compliance field.
Refund Order Lines Refunds money on order lines, partially or in full, with an explicit amount, shipping amount and reason code. Amount and shipping amount are separate and both are required, and a refund cannot be undone.
Cancel Order Lines Cancels specific quantities on specific order lines with an amount and a reason code. The partial counterpart to canceling a whole order, and the right choice when only part 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 send are touched, and sending an empty value clears one.
Adjust Order Lines Corrects the actual measurement of order lines sold by weight or length, up or down within the marketplace's limit. The platform creates the matching refund or cancelation itself.
Get Order Evaluation Returns the customer's evaluation of an order: the grade, the comment, the individual assessments, whether it is public and any reply already published. The raw material for a review response workflow.
Export Orders Starts an asynchronous order export and returns a tracking id. The marketplace recommends this over listing for anything large, because it handles volumes the paginated read cannot.
Get Order Export Status Returns the status of an asynchronous order export and, once complete, the URLs of the chunk files. Poll until it settles rather than assuming a result.
Download Order Export File Downloads one chunk of a completed order export into FlowRunner file storage, called once per URL the status operation returned.
List Order Documents Lists the documents attached to the given orders, each with its id, type, file name, size, order and upload date. This is the index needed before downloading or deleting one.
Download Order Documents Downloads documents attached to orders into FlowRunner file storage. Exactly one document id returns that file directly, and any other combination returns an archive.
Upload Order Document Attaches one document to an order, such as a customer invoice or a delivery bill. Only the failures are reported, so anything absent from the response was accepted.
Delete Order Document Permanently removes one document from an order. The marketplace answers with no body, so this operation returns the deleted id for the workflow to carry forward.
List Order Taxes Returns every order tax code the marketplace defines, each with its label and calculation rule. The refund and cancelation operations require these codes on their tax entries.
Resolve Incident Closes an open incident on an order line with a resolution reason. Open incidents drive the incident rate on the scorecard and hold up the order, so a workflow that finds and closes them protects both.

Shipments

List Picklists Lists the picklists the marketplace generated for the shop's orders, with their state, pickup date, pick run code, order lines and picklist lines. This is the warehouse view of what to pick.
Create Shipments Creates parcels against orders, each carrying its own lines, quantities, tracking and origin. This is the multi parcel path and a different model from validating a whole order as shipped.
List Shipments Lists the shop's shipments with lines, tracking, shipping origin, status, customer debit status and payment details. This route pages by token while orders page by offset.
List Items To Ship Lists the order lines still waiting to be put in a parcel, with the outstanding quantity, shipping address, method, deadline and fulfillment center. The shipping deadline here is what the late shipment rate measures against.
Delete Shipments Deletes shipments that have not yet gone out, putting their items back into the packing queue. Per shipment failures are reported inside a success response.
Validate Shipments As Shipped Marks shipments as shipped, the multi parcel equivalent of validating a whole order, and what starts the customer debit on workflows that settle on shipment. Set tracking first.
Validate Shipments As Ready To Pick Up Marks shipments as ready for the customer to collect, which is the click and collect path rather than the delivery one.
Update Shipment Tracking Sets the carrier and tracking number on individual parcels. The per parcel counterpart of the order level tracking write, and the one a multi parcel seller needs because each box has its own number.
Update Shipment Shipping Origin Records which warehouse a parcel actually left from, which drives the tax treatment on cross border orders. Per shipment failures are reported inside a success response.
Update Shipment Additional Information Writes the operator defined extra fields on shipments, such as a pallet reference or a customs declaration date. Per shipment failures are reported inside a success response.

Returns

Create Returns Opens return requests against orders, each with its method, reason and lines. Marking an entry accepted skips the acceptance step for a return already agreed to.
Patch Returns Updates returns field by field: the authorization number, the label URL, the return address, the carrier tracking and, where the operator allows it, the return method.
List Returns Lists the shop's customer returns with state, method, reason, authorization number, return address, tracking, documents and lines. Filtering on the waiting acceptance state gives the queue that needs a decision.
List Items To Return Lists what is still returnable on an order: the returnable quantity per line, the return window with its dates, and the methods and reasons the marketplace will accept. Read it before opening a return.
Accept Or Refuse Returns Answers customer return requests waiting for a decision. A refusal needs a rejection reason code and accepting needs none, and per return failures are reported inside a success response.
Validate Returns As Received Marks returns as physically received at the warehouse, which is the step before the compliance check.
Set Return Compliance Records, per returned line, whether the goods came back in acceptable condition, with a non compliance reason where they did not. This is what decides whether the customer is refunded, and the operation this page's human gate exists for.
Close Returns Marks returns as closed, the final state once the goods are back and the refund has been settled.
Cancel Returns Marks returns as canceled, for a request the customer withdrew or that was raised in error. Canceling is not the same as refusing, which records a decision on a valid request.
Create Return Labels Asks the marketplace to generate carrier return labels for the given returns. Generation is asynchronous, so the label is not ready when the call returns.
List Return Labels Lists return label requests with their state, estimated cost, generated files, tracking and any errors. This is the polling half of label creation.

Products

Get Products Looks up marketplace catalog products by identifier, returning each product's SKU, title, category and identifier type. This is how a workflow learns whether a product it wants to sell already exists.
Import Products Uploads a product file so the operator can add products the catalog does not yet hold. This is a request rather than a publication, because the operator decides what enters their catalog.
List Product Imports Lists the shop's product imports with status, transformation statistics and integration details covering products synchronized, rejected, invalid, reimported and not accepted.
Get Product Import Returns one product import's status, transformation statistics and integration details, with flags saying which reports exist. Read those flags before asking for a report.
Download Product Import Report Downloads one of the reports a product import produces into FlowRunner file storage. Several marketplace routes are folded into one operation that differs only in which report it returns.
Get Product Attribute Configuration Returns the attribute definitions the marketplace expects on products: each attribute's code, label, type, requirement level, default, example, validations and roles.
List Value Lists Returns the operator's controlled vocabularies with each list's code, label, translations and permitted values. An attribute typed as a list draws its legal values from one of these.
List Catalog Categories Returns the marketplace's catalog category tree, each entry carrying its code, label, translations, level and parent. The category decides which product attributes apply.

Invoicing and Accounting

List Accounting Documents Lists the invoices and credit notes on the seller account with totals, taxes, payment state, due date, billing cycle and issuer. Check the type filter, because it does not default to everything.
Download Accounting Document Downloads one invoice or credit note into FlowRunner file storage. This is what an accounting workflow archives alongside the listing that found it.
List Seller Billing Cycles Lists the shop's billing cycles with the amounts transferred to the seller and to the operator, the payout state and provider, the voucher number and the cycle summary. This is where a missing payout is diagnosed.
List Transaction Lines Lists the individual money movements on the seller account: order amounts, commissions, refunds, taxes, one off fees and manual documents, each with its amount, balance and payment state.
Export Transaction Lines Starts an asynchronous export of the transaction ledger and returns a tracking id. Nothing is exported when it returns, so poll the status next.
Get Transaction Export Status Returns the status of an asynchronous transaction log export and, once complete, the URLs of the chunk files. Read the error object rather than assuming an incomplete status means waiting.
Download Transaction Export File Downloads one chunk of a completed transaction log export into FlowRunner file storage. The third leg of the export sequence.
List Accounting Document Requests Lists the accounting documents the marketplace expects the seller to issue, with amounts, taxes, due dates, recipients, payment terms and state. This is the invoice obligation list.
List Document Request Lines Returns the individual lines of one accounting document request: product, quantity, unit and total prices, taxes, eco contributions, shipping charges and the order line each belongs to.
Download Accounting Documents Downloads the documents attached to accounting document requests into FlowRunner file storage. More than one document comes back as an archive.
Upload Accounting Document Uploads the seller's own invoice or credit note against an accounting document request, closing an obligation the marketplace raised. Per request errors are reported inside a success response.
Confirm Accounting Document Issuance Tells the marketplace that a fees document was issued outside the platform, recording its number and amounts without uploading a file. The marketplace allows this only for specific document types.

Messaging

List Threads Lists the shop's message threads with customers and the operator, each with participants, topic, related entities and metadata including how long a shop reply has been outstanding. That outstanding field is what a support workflow should watch.
Get Thread Returns one thread in full: every message with body, sender, recipients and attachments, the participants, the topic, the related entities and the reply metadata.
Create Operator Thread Opens a new thread with the marketplace operator and sends the first message, optionally with an attachment. This is how a workflow escalates something to the marketplace itself.
Create Order Thread Opens a thread on a specific order and sends the first message, optionally with an attachment. This is how a seller contacts a customer, with the marketplace intermediating.
Reply To Thread Posts a reply into an existing thread, optionally with an attachment and optionally changing the topic. Replying is what clears the outstanding reply clock that feeds the message response metric.
Download Message Attachment Downloads a file a customer or the operator attached to a message into FlowRunner file storage. The route takes the attachment id rather than the message id.

Promotions

List Promotions Lists the shop's promotions with type, triggers, rewards, channels, customer groups, public descriptions, media, activity dates and state. The state filter does not default to everything, so set it deliberately.
Create Promotion Creates a shop promotion with its trigger, reward, dates, channels and customer targeting. The discount amount is not a single named field, because the platform uses a different property per reward type.
Update Promotion Updates an existing promotion. This is a full replacement rather than a patch, so required fields must be resent even when only one value is changing, and anything omitted is lost.

Triggers

2 triggers

Event Triggers

On Order Updated Fires for each order created or updated on the marketplace, optionally narrowed to given states so a workflow can watch only the orders waiting for acceptance or only those ready to ship. This polls rather than subscribes, because the platform publishes no seller webhooks, so an order arrives on the next poll rather than instantly. The first poll records the position without emitting the backlog, and the marketplace asks for no more than one order read per minute.
On Return Updated Fires for each customer return created or updated, optionally narrowed to given states so a workflow can watch only the returns waiting for a decision or only those received at the warehouse. Also a poll rather than a subscription. The first poll records the position without emitting the backlog, and the marketplace asks for a slower cadence on returns than on orders.

Frequently Asked Questions

What can FlowRunner do with Auchan?

FlowRunner agents can run Get Shop Information, Update Shop Information, and Get Shop Statistics in Auchan, plus 108 more actions.

Does connecting Auchan to FlowRunner require OAuth?

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

Can Auchan trigger a FlowRunner workflow automatically?

Yes. Auchan supports 2 triggers that can start a FlowRunner workflow automatically.

Start building with Auchan

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us