E-commerce
June 28, 2026
Selling internationally is not just a matter of activating Shopify Markets and translating the menu. A customer in Tokyo, Montreal, or Berlin asks questions that your French help center doesn't cover: checkout currency, customs duties, shipping times to APAC, returns from Australia, VAT invoices.
Ecommerce Times points out that cross-border returns from Europe to a US warehouse often cost $18 to $40 per unit in transport alone, before restocking (Ecommerce Times, cross-border 2026).
This guide #100 covers language, currency, shipping, returns, payments, agent workflows, and multilingual bots. It complements customs questions (#65) and multilingual chatbots (#16) with a focus on global international customer service, which is distinct from international marketplace support (#266).
Summary
Why is international support a profession in its own right?
International e-commerce customer support multiplies languages, time zones, regulations, and logistical expectations.
Complexity vs domestic market
Languages: FR, EN, ES, DE depending on active markets.
Currencies: EUR, USD, GBP, CAD, refund discrepancies.
Delivery times: 5 days France vs 20 days Canada vs 30 days APAC.
Customs: DDP vs DDU, surprise fees upon delivery.
Returns: prohibitive reverse logistics cost.
Payments: iDEAL NL, Klarna DE, Pix BR.
Export = 20 to 40% of mature DTC turnover. International tickets = 25 to 35% of support volume, average basket often +30%. Badly handled: "not received" or "surprise customs" chargebacks and reviews on target markets. Logistics ships; support explains, reassures, resolves. Both must announce the same delivery times. See support strategy.
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
Which international customer profiles and which questions come up most often?
Mapping international support personas guides knowledge base and bot routing.
Common profiles
Cross-border shopper: buys on FR site, delivery to BE/CH/UK.
Expat / diaspora: family gift, country A card, ship to country B.
B2B export: invoice, VAT number, Incoterms.
APAC / Americas: long delivery times, local payment methods.
Top questions by topic
Language: "Do you speak Spanish?" Currency: "Why billed in USD on EUR site?" Delivery: country delivery time, local carrier tracking. Customs: fees to pay, DDP included? Return: international label, refund timeframe. Payment: declined card, PayPal available? EU vs US size, cross-border gift, ERASMUS student split payment. See intent segmentation.
How to structure the language strategy without a polyglot team?
The multilingual support strategy combines a localized site, an AI bot, and targeted human escalation.
Four levels of coverage
Site + help center in local language per Shopify market.
24/7 multilingual AI chatbot (tier 1 WISMO, returns, delivery times).
Native agents in the top 3 export markets by revenue.
BPO partner in local time zones if volume is insufficient.
Digital Applied: machine translation alone on technical datasheets or INCI creates conversion and compliance errors. Lean approach: MT catalog + native proofreading of top 20% revenue-generating SKUs. Prioritize languages by export revenue + ticket volume: EN is often #1 post-FR. Transactional emails: checkout language, not browse language. Dedicated bot angle: multilingual chatbot support (#16). Handoff: bot-to-human handoff.
How do I manage currency, checkout, and multi-currency refunds?
Currency support tickets skyrocket when the displayed price ≠ the billed amount.
Recurring questions
Why does my bank display a different amount? Exchange rate + card issuer fees.
Refund in which currency? Same currency as the order, processing time 5-10 days.
Refund vs. debit gap: exchange rate fluctuation between purchase and refund.
VAT invoice: country-specific format, B2B customer VAT number.
Best practices
Shopify Markets: price and currency per market, mention "payment may be converted by your bank" if multi-currency checkout is used. Managed Markets can guarantee exchange rates on returns (Shopify Enterprise). Intl refund macro: explain bank processing time + possible exchange rate gap. Never promise an exact refund amount in the local currency if the original charge was USD and the processor refund is EUR.
How do I handle delivery, lead times, and customs in support?
International delivery tickets dominate export after-sales service: delivery times, customs, tracking.
Procedures by case
Country X delivery times: zone table on /pages/livraison, PDP dynamic ETA.
Parcel blocked in customs: DDP = contact support; DDU = customer pays, explain before purchase.
Frozen international tracking: transit + customs, alert threshold D+21.
Post-Brexit UK: distinct rules from the EU, dedicated article if > 5% of turnover.
ESW notes that agents without cross-border context (customs, regional delays) resolve issues more slowly. Your support team must know the Markets configuration by country. See customs questions (#65), delivery time communication (#84), dynamic ETA (#85), international delivery.
How to organize cross-border returns without ruining the margin?
International returns are the highest deficit support+logistics cost center if copied directly from domestic operations.
Operational Models
Returnless refund: item < €45 landed cost, customer keeps the product.
Regional return hub: EU 3PL accepts consolidated returns, no US return shipment.
Localized portal: Loop, Narvar, AfterShip Returns, instructions by country.
Customer return fees: transparent on PDP if no prepaid label is provided.
Online Store News: EU 30-day return window (2026) extends the inbound flow. DHL "Returns by Destination": regional consolidation −30% unit cost (with sufficient volume). Support: explain process before purchase, automatic return statuses (received, inspected, refund issued). See return policy and returns bot.
How to manage local payments and card declines abroad?
International payment issues affect checkout conversion and post-rejection tickets.
Common Cases
Card declined in country X: 3DS, cross-border anti-fraud bank, offer PayPal/Shop Pay.
Missing local method: iDEAL, Klarna, Bancontact depending on the market.
Unknown descriptor: bank statement name = store name.
Temporary double charge: auth + capture, explain the delay.
Digital Applied: local currency pricing + familiar payment methods reduce checkout abandonment. WhatsApp is the dominant support channel in BR, IN, MENA for payment/delivery questions. Germany, France, Japan: phone support is expected for high-value carts. See declined payment, BNPL support.
Which agent workflows, macros, and routing by market?
Standardizing international ops support prevents each agent from improvising by country.
Gorgias macro examples
INTL-001 delay: zone delay + tracking link + customs if applicable.
INTL-002 customs DDU: explaining customer fees + proof of DDP if included.
INTL-003 refund FX: bank delay + exchange rate difference.
INTL-004 return intl: portal + returnless if eligible.
INTL-005 language: template EN/ES response + native escalation.
Routing and tags
Tags: `market_UK`, `market_US`, `customs_issue`, `intl_return`. Route by market if agents are specialized. 1-page cheat sheet of key EN/ES phrases for the FR team. Omnichannel consistency: same delay on site, emails, bot, agents. See support templates, omnichannel support.
How to deploy a multilingual chatbot for export?
The international chatbot covers time zones and languages on tier 1 before hiring native agents.
Priority intents by market
shipping_country: delivery time + fees + regional carrier.
customs_fees: DDP/DDU policy by market.
return_international: portal + returnless threshold.
currency_refund: timeframe + exchange rate.
wismo_intl: lookup + customs transit explanation.
Bot sources by market: localized help center articles, not raw translation of FR policy. Browser language detection + customer message. Zendesk AI / Intercom Fin: 60-70% tier 1 multilingual (Digital Applied). Escalation for disputes, chargebacks, VIP, legal liabilities: native human or 24h async. Training: Shopify chatbot.
How to measure CSAT and tickets by market?
Measure the international KPI support by market, investment guide, language, and returns.
Essential KPIs
Export ticket rate: tickets / orders per country.
CSAT by market: deviation > 10 pts vs domestic = alert.
First response time: client time zone vs office hours.
Top intl themes: customs, shipping time, return, currency.
Export chargeback rate: vs domestic.
Cost per intl return: vs product margin.
Monthly review: market with ticket rate ↑ and CSAT ↓ → audit help center, PDP lead times, return policy. See chargebacks, analytics conversations.
How does Qstomy unify Shopify international support?
Qstomy handles multilingual international support with Shopify order + market context, via Shopify integration.
Key Capabilities
Language detection: FR/EN/ES/DE response based on the customer.
Market context: lead time, customs, order currency.
Intl intents: shipping_country, customs, return_intl, refund_fx.
Cross-border WISMO: tracking + customs phase explained.
Handoff: customer language transcript for the agent.
Quantified DTC Scenario
FR beauty brand, 35% export revenue (UK, US, BE), 28% of tickets = international, export CSAT 3.6 vs 4.2 domestic, median intl first response time of 18 hours.
Qstomy deployment: multilingual bot + help center per market + INTL macros. 12-week result: intl first response time 18 hrs → 4 mins (bot), export CSAT 3.6 → 4.1, customs tickets −35%, export chargebacks −22%. 2 native EN agents recruited solely for disputes scoring > 80.
Explore AI support and request a demo.
Which operational playbooks should be launched this week?
Playbook 1: delivery page by export zone
Country table: delivery time, cost, carrier, customs DDP/DDU. Link from PDP and emails. Measure "delivery country X" tickets over 30 days.
Playbook 2: 5 INTL macros + market tags
Create INTL-001 to 005 under section 8. Mandatory `market_XX` tag upon closing. Ticket dashboard by country.
Playbook 3: returnless threshold by landed cost
Define threshold (e.g. €45) per zone. Document in bot + return policy. Calculate savings vs international return label.
Playbook 4: audit top 3 export markets
UK, US, BE: full mystery shop on checkout language, confirmation email, test chat question. Correct inconsistencies within 7 days.
Playbook 5: separate CSAT domestic vs export
Post-ticket survey tagged international. Monthly review: market under 4.0 = content priority + bot intents.
Useful linking
Selling globally without global support means exporting your customer service issues: treat every market like a customer who deserves the same clarity as your domestic market.
Enzo
June 28, 2026
