E-commerce
June 28, 2026
"Where is my Amazon order?" answered in 36 h. A-to-z claim opened. "Cdiscount damaged package" handled by an agent with DTC return policy. Forced refund by the platform. Two errors, two seller account penalties.
Feedvisor reminds us that Amazon requires 90% of buyer message responses within 24 hours, weekends included, and that a 48-hour silence paves the way for A-to-z claims (Feedvisor, messaging Amazon 2026). Cdiscount imposes 2 business days and rejects "we will get back to you" responses (Cdiscount, responding to customers 2026).
This guide #190 covers marketplace customer support: imposed rules, SLAs, platform disputes. It completes message centralization through the lens of compliance and defense, not inbox architecture.
Summary
Why does marketplace customer service follow different rules than DTC?
Marketplace customer support is not managed like a Shopify email: the platform sets deadlines, authorized channels, and account penalties.
Three structural differences
Contractual SLA: exceeding it = automatic penalty or forced refund
Single channel: platform messaging, no website or WhatsApp redirection
Platform dispute: arbitration in case of a deadlock, evidence required within a short timeframe
Seller vs. host liability
Amazon.fr reminds: the sales contract binds the seller and the buyer. The marketplace facilitates the transaction but the seller remains responsible for customer service, except in FBA cases where Amazon manages part of the service (Amazon, FR marketplace).
Cost of non-compliance
Amazon: Order Defect Rate (ODR) must remain below 1%. Cdiscount: refund charged back to the seller if there is no response within 48 business hours. eDesk estimates that a late response multiplies the risk of an A-to-z claim and negative review by 3 (eDesk, FBM 2026).
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
How does it differ from message centralization?
#190 covers rules and disputes, not the inbox tool.
Message centralization (dedicated article)
Centralize messages: helpdesk architecture, connectors, routing. #190: what to answer, within what timeframe, how to defend a dispute.
Three-channel service (#134)
Social commerce (#134): TikTok, Instagram, Shopify. Here: third-party marketplaces with imposed SLAs.
Marketplace + Instagram + Amazon
Three-channel marketplace service: general overview. #190: platform-by-platform SLA matrix and dispute procedures.
Promise #190
SLA table, prohibited actions by channel, A-to-z workflow, Cdiscount claim, P2B account defense.
What are the SLAs and rules for each major marketplace?
Map your marketplace SLA matrix before unifying DTC macros.
Amazon (FBM and Seller Central)
Message response: 24 hours, weekends and holidays included
CRT Target: 90%+ under 24 hours
Buyer escalation: A-to-z eligible if not resolved within 48 hours
A-to-z Claim: 72 hours to submit proof, otherwise auto-loss
Prohibitions: external links, marketing, review solicitation, direct contact details
Cdiscount Marketplace
Response: 2 business days max
Prohibitions: placeholder-only response, off-platform contact, website URL
Dispute: platform can refund and pass the cost to the seller
Fnac Darty / Mirakl / ManoMano
Fnac Darty via Octopia: often 8 business hours, 24 hours if message is outside hours. Mirakl white-label: 48 calendar hours frequent, auto-closure in favor of the customer if silent. ManoMano: 4 business hours on certain pro flows. Consult the seller T&C of each portal, they take precedence over your DTC habits.
Ops Document
Notion table: platform | response SLA | authorized channel | platform return policy | dispute deadline | weekend on-call owner.
How to prioritize marketplace tickets in the customer service queue?
Urgent marketplace tickets take precedence over DTC when the platform SLA is stricter.
Priority Matrix
P0: A-to-z claim / dispute open, 72h countdown
P1: Amazon message < 6h remaining on 24h SLA
P2: Cdiscount claim next business day
P3: Marketplace pre-purchase question
P4: Standard DTC email
Amazon Weekend On-Call
Amazon's 24h SLA does not pause on Saturday. Plan for rotation or auto-acknowledgment macros + human processing within 12h. Feedvisor notes that the [Important] tag was deprecated in April 2025: only Contact Buyer templates guarantee delivery (eDesk, 24h deadline 2026).
Helpdesk Tags
mp_amazon, mp_cdiscount, mp_fnac, dispute_open, sla_critical. See support prioritization (#26).
What response rules should be followed on each platform?
Marketplace response rules limit tone, content, and channel more than your DTC policy.
Amazon: what goes through and what is blocked
Allowed: order status, tracking, return, replacement, sincere apology
Blocked since 2026: AI-filtered messages if marketing, external link, review request
Mandatory template: certain post-purchase communications via Contact Buyer
Cdiscount: golden rule
One discussion = quick response + concrete solution + zero platform bypass. Offer return, exchange, refund, or repair according to law. Never "we are processing your request" without action.
Frequent multichannel errors
Copying DTC macro "visit our return portal on [site]" on an Amazon ticket. Mentioning WhatsApp or personal email on Cdiscount. Promising a refund period outside the platform's policy (often 14 days max on the buyer's side).
Tone
Factual, short, without excessive emojis. Personalize name + order #. Offer a clear next step: "refund initiated within 24 hours" or "return label attached."
How to handle an Amazon A-to-z claim step-by-step?
The Amazon A-to-z Guarantee claim must be defended within 72 hours with evidence, not with emotion.
Timeline
Buyer message: reply within 24 hours with a concrete solution
If not resolved: buyer becomes eligible for A-to-z after 48 hours
Claim notification: 72 hours to respond in Seller Central
Amazon decision: 7-10 business days
Appeal: 30 calendar days if denied
Standard Evidence File
Tracking with POD (Proof of Delivery) if item not received
Product + packaging photos if damaged / not as described
Complete buyer-seller message history
Return policy applied + refund already processed if legitimate
When to Accept Immediately
Proven seller error (wrong SKU, not shipped): proactive refund before Amazon's decision limits ODR impact. Titan Network estimates that replying to the buyer within 48 hours with a solution reduces A-to-z filings by 40% (Titan Network, A-to-z 2026).
Related Cases
See different product received (#186) and partial returns (#185).
How to manage a Cdiscount or Mirakl claim?
France marketplace disputes go through the seller messaging system, not through your Gmail.
Cdiscount Workflow (5 steps)
Read the claim in the seller area within 24 hours
Propose a complete solution within 48 business hours (no holding messages)
Attach evidence via the dedicated attachments space
Confirm resolution in writing on the platform
If platform arbitration is triggered: accept or challenge with a factual file
Failure and warranty
Cdiscount CGMAD: confirmation of taking charge within 2 business days, repair or replacement within 30 calendar days. Defect = refund possible by the platform to the seller.
Mirakl / Markette
Markette requires a seller response within 72 hours to platform requests regarding claims. Indicative review time of 5 business days. Seller must cooperate, otherwise a decision is made based on available elements (Markette, T&Cs 2026).
Which customer service macros per marketplace?
Marketplace-specific macros support separate from DTC macros, prefixed by channel.
AMZ-WISMO-01 (Amazon tracking)
"Hello [First Name], order #[Amazon]. Shipped on [date], carrier [X], tracking [link]. Estimated delivery [date]. If not received by this date, contact us here for investigation."
AMZ-RETURN-01
"Return accepted order #[X]. Prepaid label attached / Amazon return procedure followed. Refund within 14 days after warehouse receipt."
CDS-CLAIM-01 (Cdiscount claim)
"Hello, we have received your claim for order #[X]. Proposed solution: [refund / exchange / resend]. Deadline: [date]. Confirm your agreement by replying to this message."
MP-DAMAGE-01 (multi-platform)
"Sorry for the damage found. Please attach 3 photos (product, packaging, label). We will initiate a replacement or refund within 24 hours of receiving the photos."
Team rule
Before sending: check channel, no website link, no direct email, solution = action not vague promise.
How to dispute a seller account sanction (P2B)?
Marketplace account suspension or restriction: the P2B regulation now governs the seller's response.
Immediate verifications
Written notification: specific grounds, cited T&C clause
Notice period: 30 days in principle (except for fraud or legal urgency)
Internal remedy channel: mandatory platform complaint system
Structure of the dispute response
Reference the notification and date
Dispute inaccurate facts with evidence (customer service logs, tracking)
Invoke the T&C clause and proportionality
Request the review or P2B independent mediation
Atias Avocats reminds: DSA and P2B impose written justification and internal remedy for any seller restriction (Atias, marketplace 2026).
Which KPIs should be monitored per marketplace?
Measure marketplace customer service per platform, not as a global aggregate.
Amazon KPIs
Contact Response Time: target 90%+
ODR: < 1%
A-to-z claims granted: monthly trend
Negative feedback rate
French marketplaces KPIs
Response rate under contractual SLA. Platform-arbitrated claims. Forced refunds / turnover. Seller rating if applicable.
Weekly ops review
15 min: messages < SLA, open disputes, 1 root cause. Tag conversations (#54) with mp_* for reporting.
Chargeback
See chargeback prevention: platform dispute ≠ bank chargeback, two parallel flows.
How does Qstomy help with multichannel marketplace support?
Qstomy routes conversations according to the marketplace channel and alerts before a SLA breach.
Features
Detect channel mp_*: macros and policy by platform
SLA countdown: Amazon alert < 8 h
Dispute workflow: A-to-z evidence file
Forbidden link scan: blocks website URLs in Cdiscount drafts
CRT / ODR Dashboard: KPIs by marketplace
Encrypted DTC Scenario
Sports equipment brand, Shopify + Amazon FBM + Cdiscount, Amazon CRT 78%, 4 A-to-z granted/month, 2 forced Cdiscount refunds. Deployment of Qstomy mp routing + weekend on-call + AMZ/CDS macros. After 10 weeks: CRT 94%, A-to-z granted 1/month, forced refunds 0, ODR 0.6%, median Cdiscount first response 18 h.
Explore AI customer support, Shopify, request a demo.
Which operational playbooks should be deployed this week?
Playbook 1: SLA matrix (2 h)
List each active marketplace. SLA, restrictions, owner, weekend on-call. Share with the customer service team.
Playbook 2: MP macros (3 h)
6 section 8 macros in helpdesk. Prefix AMZ-, CDS-, MP-. Test without external links on Cdiscount.
Playbook 3: standard A-to-z file (1 h)
Google Drive folder: tracking template, message screenshots, 72 h procedure. Seller Central alerts directed to Slack.
Playbook 4: message compliance audit (45 min)
Review the last 20 marketplace responses. Count website links, holding replies, SLA breaches.
Playbook 5: Monday marketplace ritual (20 min)
CRT, open disputes, forced refunds, 1 corrective action.
Useful links
On marketplaces, a good response is not the one that pleases the customer: it is the one that respects the SLA, resolves the case, and protects your seller account.
Enzo
June 28, 2026
