E-commerce
June 28, 2026
Selling on Shopify and on Amazon, Fnac or Cdiscount is not just about synchronizing your catalog and inventory. Each channel opens a separate inbox: seller messaging, support@ email, site chat, Instagram DM. Without centralization, marketplace SLAs slip, the customer repeats their order number three times, and the customer service team gets exhausted switching between tabs.
The right approach is not "reading everything in Gmail". It is a unified inbox connected to Shopify and marketplaces, with channel tags, tailored macros, priority routing, and comparable KPIs. Articles on marketplace integration cover product synchronization; here, the focus is operational: daily customer messages and customer service.
This guide details channel audits, target architecture, tool selection, SLA rules, Amazon and French marketplace constraints, order matching, templates, and weekly organization. It complements the marketplace integration and the multichannel.
Summary
Why do marketplace and Shopify messages turn into customer service chaos?
Selling on Shopify and on one or more marketplaces multiplies touchpoints. Each agent juggles between Seller Central, the Fnac portal, Gmail, and site chat. Without a single stream, SLAs skyrocket and the customer repeats his request on three platforms.
Symptoms of chaos
Forgotten messages: secondary marketplace inbox not checked
Double responses: two agents handle the same customer without visibility
Inconsistent policies: DTC return applied to an Amazon ticket
Blind KPIs: impossible to measure overall support volume
Peak stress: BFCM or marketplace sales without on-call coverage
Business cost
On Amazon, Feedvisor points out in 2026 that the Contact Response Time (CRT) requires 90% of responses within 24 hours, weekends included. Dropping below 80% degrades Account Health and can impact the Buy Box (Feedvisor, Buyer-Seller Messaging 2026). On DTC, it results in a negative review and a loss of LTV.
Goal of centralization
A single flow: all conversations enter a unified inbox, enriched with order, channel, and SLA data, processed with the same internal procedures, and measured in a dashboard.
Multichannel vs omnichannnel support
Multichannel: you reply to each channel from a single inbox. Omnichannel: the customer continues a conversation between Instagram and email without repeating themselves. Centralization is the first step; a unified history per customer is the second.
Concrete example
DTC store + Amazon FBM: 40% Amazon tickets, 35% site email, 15% chat, 10% Instagram. Before centralization, two agents spent 2 hours/day copying and pasting tracking from Seller Central. After helpdesk + Amazon connector: tracking injected in one click, Amazon FRT dropped from 18h to 6h.
How to map all of your customer contact channels?
Before buying a tool, list each incoming message and who handles it today.
Frequent channels
Shopify DTC : email, chat widget, contact form
Amazon : Buyer-Seller Messaging, A-to-z Guarantee claims
FR Marketplaces : Fnac Darty, Cdiscount, Rakuten, ManoMano, Mirakl white-label
Social media : Instagram DM, Facebook Messenger
Others : eBay, Etsy, TikTok Shop if active
One-week audit
Simple table: channel, daily volume, average response time, current tool, owner, contractual marketplace SLA, duplicates with other channels. Document how many minutes per day each agent spends switching tabs. This figure alone often justifies the helpdesk budget.
Volume vs criticality
A low-volume channel with a strict SLA (Amazon 24 hours) can take priority over a noisy DTC chat. See prioritizing support requests.
Cross-channel customer duplicates
The same customer orders on Amazon and on the website: two identities until manually merged. eDesk describes agent collision detection and thread merging when the same email appears on two platforms (eDesk, avoid duplicate replies FR).
Which unified inbox architecture should you adopt with Shopify?
The winning model in 2026: a multi-channel helpdesk connected to Shopify admin and native marketplace connectors or API bridges.
Three layers
Collection: Marketplace API + email + chat + social to tickets
Enrichment: Order, status, tracking, sales channel, tags
Resolution: Macros, refund actions, escalation, closing
Compare the stack in helpdesk, chatbot and KB.
Shopify as the DTC source of truth
Site orders, customers, inventory: Shopify admin. Marketplaces have their own reference; the ticket must display both numbers.
Shopify Inbox alone is not enough
Native Inbox = basic site chat. As soon as Amazon or high-volume email comes into play, migration to a helpdesk is needed. See Is Shopify Inbox enough?
Shopify Flow and helpdesk
Shopify Flow can tag high-risk orders or large carts; webhook to helpdesk for proactive tickets. Combined with marketplace rules, you anticipate messages before they arrive.
Selection criteria
Prioritize: native Amazon connector (not just email parsing), Shopify order sidebar, SLA rules by channel tag, open API for BI, cost per ticket at real volume. Request a demo with a real Amazon ticket and a real Shopify ticket side by side.
How to choose the tool for a multichannel store?
Gorgias, eDesk, Zendesk, Freshdesk, Re:amaze: all promise unification. Compare on your actual channels, not on the marketing list.
Non-negotiable criteria
Marketplace connector you use (Amazon SP-API messaging, Fnac, Cdiscount)
Shopify Sync: order visible, refund/cancel actions if authorized
Automation rules by channel and intent
Variable macros: name, order number, tracking
Reporting by channel and agent
Mobile app for marketplace emergencies
Gorgias vs generalist
Gorgias excels at native Shopify (order actions inside ticket). Zendesk scales for large multi-brand teams but has a less deep e-commerce integration. For marketplaces without a native Gorgias connector, Juble.io bridges the gap to Amazon, Mirakl, Fnac, and Cdiscount (Juble.io, Gorgias).
eDesk and French marketplaces
eDesk explicitly targets marketplace + webstore consolidation with native connections to Amazon.fr, Cdiscount, Fnac Darty, and Rakuten France (eDesk, France helpdesk platform 2026).
Migration from Gmail
Transition phase: automatically forward support@ and Amazon aliases to the helpdesk. Disable replies from Gmail after 2 stable weeks to avoid double threads.
Test before committing
Trial period: connect one marketplace channel + Shopify, simulate 20 tickets, measure resolution time vs current process. Check the helpdesk app on Shopify and refund permissions.
Which routing rules, tags, and SLAs should be applied per channel?
Centralizing without sorting recreates a catch-all inbox.
Mandatory Tags
channel : amazon, shopify, instagram
intent : wismo, return, pre-purchase, dispute
marketplace_sla : if platform deadline
priority : P1 to P4 aligned internally
Automation Rules Examples
Instagram pre-purchase: AI bot if frequent question, otherwise human. A-to-Z dispute: assignment to trained agent + P1.
Differentiated SLAs
Amazon: 24 calendar hours, internal target 12 hours for margin. DTC email: 12 business hours. Display the countdown in the helpdesk. Feedvisor recommends 95% CRT, not just 90% (Feedvisor, CRT 2026).
Weekends and On-Call
Marketplace is continuous; plan on-call coverage or auto-reply with a realistic timeframe. An FBM seller with no response on Sunday accumulates penalties on Monday.
Agent Notifications
Mobile push on Amazon P1 ticket, email digest on low-priority DTC queue. Round-robin on DTC; Amazon assigned to the agent most trained in disputes.
What are the specific constraints for marketplaces (Amazon and others)?
Each marketplace imposes messaging rules that differ from DTC.
Amazon Buyer-Seller Messaging
Templates are sometimes mandatory, review soliciting is prohibited, external links are limited. Since April 2025, the [Important] tag no longer bypasses buyer opt-outs: use the Seller Central templated messaging system for shipping, returns, and delivery (eDesk, 24 h deadline 2026).
Do not mix policies
Amazon A-to-Z returns ≠ 30-day website returns. Macros separated by channel with the suffix _amazon, _shopify. Common mistake: copying and pasting the DTC policy on an Amazon ticket.
Marketplace disputes
Documented process: screenshot, tracking, proof of shipment, short deadline, P1 priority. Archive every response in the helpdesk ticket: timestamped history protects the seller rating.
Inventory and message synchronization
Out of stock on marketplace while website indicates stock: "cancel my order" tickets. Align ops and support. See Amazon Shopify integrations.
Fnac, Cdiscount, Mirakl
Distinct seller interfaces, similar contractual response times. Centralize via native connector or email parsing with explicit marketplace tags. Fnac Darty saw its online sales grow in 2025: buyers expect fast responses (eDesk, Fnac sellers 2026).
How to identify the customer and the order regardless of the channel?
A ticket without a linked order = three back-and-forth messages.
Automatic matching
Customer email = primary key. Marketplace order ID mapped via connector. Name + postal code as backup.
Multiple orders
Ask for order number confirmation if ambiguous. Polite macro: "To help you, please provide the marketplace or website order number".
Cross-channel profile merging
Helpdesk merge when the same email is detected. Amazon + Shopify history visible before replying. eDesk groups threads from the same buyer across multiple platforms.
Marketplace WISMO
Marketplace tracking is sometimes distinct from the final carrier. WISMO macros by channel. Learn more about reducing WISMOs on DTC.
GDPR and marketplace data
Do not copy Amazon customer data into internal notes outside of a compliant helpdesk. Respect the buyer terms of service for each platform.
How to build consistent macros and templates per channel?
Centralization is only effective if the tone and policy remain consistent.
Library by channel
Macro suffix: _amazon, _shopify, _generic. Same factual basis, phrasing adapted to platform constraints.
Dynamic variables
Order number, tracking URL, marketplace name, return window. See support response templates.
Legal/ops review
Any return/refund macro validated once by legal and ops, reused everywhere. Date of last review in the macro title.
Agent training
Internal week 1 quiz: "Which macro for Amazon vs website return?" Marketplace tone: neutral, factual. DTC Instagram: warmer. Two tone guides in Notion.
Concrete examples
Amazon WISMO: "Hello, your order [ID] was shipped on [date]. Tracking: [link]. Estimated time [X] business days." Return site: "You have 30 days after receipt..." Never swap them.
Where to place chatbot and AI in a multichannel context?
The onsite bot does not see Amazon; it remains useful on DTC and sometimes connected social channels.
Where to automate
Shopify Chat : WISMO, site return policy, preorder status
DTC Email : auto-reply acknowledgment + self-service portal link
Pre-purchase Social : hours, sizing, site stock
Where not to automate
Amazon disputes, exception negotiations, 1-star review threats, complex GDPR requests. Generic auto-responses do not count towards Amazon's CRT: a substantial human response is required.
Handoff with source channel
Escalated ticket indicates: source channel, remaining SLA, bot history. Avoid support automation mistakes: a bot unaware that a customer is talking about an Amazon order from Instagram.
Lightweight DTC self-service
Site order tracking portal reduces Shopify email tickets; the team focuses on the marketplace. See customer self-service.
How do you organize daily operations and measure multichannel KPIs?
Centralizing is a project; maintaining it is a discipline.
15-minute daily ritual
Backlog of SLA tickets under 4 hours, Amazon queue, overnight escalations, out-of-stock items reported by support.
KPIs per channel
Ticket volume / channel
First response time (FRT)
Resolution time
CSAT if measurable
Marketplace dispute rate
Bot auto-resolved rate (DTC)
Support cost comparison
Support cost per order Shopify vs Amazon vs other. See omnicanal vs multicanal ROI.
Weekly review
Top 5 ticket reasons, most used macros, tickets without linked orders (matching signal to be corrected). BFCM post-mortem: which channels broke, which SLAs were missed.
Executive dashboard
One monthly slide: volume per channel, estimated support cost, evolution of Amazon disputes, DTC CSAT. Justifies headcount and tool.
How Qstomy lightens DTC customer service while the helpdesk manages marketplaces?
Qstomy absorbs pre-purchase and WISMO enquiries on the Shopify site. The helpdesk unifies marketplaces and emails. Both systems complement each other without duplication if the customer email merges threads.
Role Allocation
Helpdesk: Amazon, Fnac, Cdiscount, support@ email, disputes. Qstomy: site chat, product questions, DTC return policy, Shopify order tracking connected to the catalog.
DTC Scenario in Figures
DTC beauty brand + Amazon FBM, 320 tickets/week before centralization. After helpdesk (Amazon + email) + Qstomy on site: email tickets −38%, Amazon FRT 6 hours (CRT 97%), chat resolved without human interaction 52%, agent time −2.4 hours/day. The team of 3 agents handles marketplaces without sacrificing DTC.
Explore Shopify integration, customer support, AI sales agent and request a demo.
Which playbooks should be launched this week?
Playbook 1: Channel audit in 90 minutes
List every channel, estimated volume, owner, contractual SLA, and minutes/day spent switching tabs. Classify by SLA criticality, not by volume.
Playbook 2: Connect Shopify + marketplace #1
Week 1: helpdesk + Shopify + Amazon (or Fnac if it is your main channel). Forward support@ to the inbox. Test 10 real tickets with the order sidebar.
Playbook 3: 10 macros per channel
Draft WISMO, return, cancellation, pre-purchase, and dispute for _amazon and _shopify. Ops review mandatory. Quiz agents before go-live.
Playbook 4: P1 routing rules
Amazon dispute + WISMO D+7 without delivery: P1, mobile push, assignment to a trained agent. Instagram pre-purchase: bot or low priority queue.
Playbook 5: Weekly dashboard
Helpdesk export: FRT by channel, Amazon CRT, tickets without linked orders, top 5 motives. Friday share in 15 min. Adjust macros the following week.
Useful links
Prioritization: prioritize requests
Native Inbox: Shopify Inbox
Templates: support templates
Self-service: self-service
Enzo
June 28, 2026
