What is a Mirakl marketplace, and why do its customer messages behave differently?

What Mirakl is

Mirakl is the software that lets a retailer open its own website to third-party sellers, the way Amazon opened its site to sellers twenty years ago. The retailer keeps the storefront, the checkout and the customer relationship. The seller lists products, ships orders and answers questions. In the UK that is how B&Q, Argos, Debenhams, Tesco Marketplace and The Range sell far more than they stock; in Europe it is Home24, Leroy Merlin, XXXLutz, Vente-Unique and hundreds of others.

For a seller this is attractive: one product feed, several storefronts with millions of visitors each. It also means several back offices, several sets of rules, and several inboxes that all expect a reply inside a deadline the operator sets.

Three parties in every thread

On your own website a customer message has two sides. On a Mirakl marketplace it has three. The operator sits in the middle: it can read the thread, post into it, answer on your behalf, and grade you on how fast you replied.

1. 1Customer writesFrom the order page on the retailer's site. They never see your e-mail address.
2. 2Operator relaysThe message lands in your seller inbox. On some operators it arrives via the operator's support team instead of directly.
3. 3You replyThrough the back office or the API, choosing the customer or the operator as recipient. Links and contact details are usually forbidden.
4. 4Operator measuresFirst reply time, in the operator's clock, feeds your seller score and your visibility.

Five ways the messages behave differently

1. The operator can write in your thread. “Supplier must contact the customer to arrange a scheduled delivery” looks like a customer message, is written by the operator’s system, and needs a different response from a genuine complaint. An inbox that cannot tell them apart shows the wrong numbers and wakes the wrong people.
2. The clock is the operator’s, not yours. B&Q and Argos measure 24 business hours, some operators count calendar hours, Amazon a 24-hour wall clock. Details here.
3. The reply is policed. Most operators reject or flag messages containing links, e-mail addresses or phone numbers. That rules out most help-desk templates, and it is why an out-of-hours note has to be written with care.
4. The order is the context. Every thread hangs off an order. A reply that does not know the carrier, the delivery date and the line items is a guess.
5. Refunds and returns happen in the operator’s system. The customer can be refunded without ever writing to you, and the reason code is the operator’s wording, which differs per marketplace.

One API, many operators

The good news: every Mirakl operator exposes the same Seller API, so one integration reads threads, messages, orders and refunds on all of them. The bad news: the same endpoint behaves slightly differently on each. Some honour one date filter and silently ignore another; one paginates with a cursor that breaks after twelve pages; one rate-limits aggressively enough that a naive hourly sync gets locked out; attachments arrive as generic binary whatever their type. None of that is documented in one place.

What this means for a seller

If you sell on one marketplace, the back office is fine. From the second one on, the work is not answering messages; it is knowing which of the nine inboxes has a message that is about to breach, which of those are real customers rather than operator notices, and what the order says. That is the problem Growstall is built for: one inbox, each marketplace’s own clock, the order beside the thread, and a refund report that reads the operator’s reason codes for you.