E-commerce
June 28, 2026
"Do you deliver to Switzerland? Is the price in euros or francs? Will there be customs duties?" These three questions often arrive in the same chat, while your bot responds from the France policy and a single catalog.
Shopify Markets centralizes languages, currencies, catalogs, and duties per market from a single store (Shopify, Markets 2026).
This guide #157 covers the Markets-aligned AI chatbot: country detection, currency responses, SKU availability, customs duties, and multilingual support. An international use case focused on Shopify, distinct from generic delivery guides.
Summary
Why does the chatbot need to understand Shopify Markets?
Without a Shopify Markets chatbot, the bot responds as if all customers were buying in the primary market: wrong currency, unavailable SKU, outdated shipping policy.
What Markets changes
Per market: catalog, displayed prices, language, domain, taxes and duties, shipping options (Shopify Dev, Markets).
International support volume
Shoply AI estimates that Shopify US, NL, UK, and DE installations concentrate a major share of multilingual traffic: 5 to 15 languages often cover 95% of EU conversations (Shoply AI, multilingual 2026).
Cost of mistakes
A "3-5 day delivery" promise valid in FR only, told to a CA customer: chargeback and a 1-star review. The bot must read the market before discussing lead times or prices. A monthly audit per active market prevents drift when you open a new country.
Which Markets customer questions should the bot handle?
Map the international Markets intents before configuring the corpus.
Top 10 verbatims
"Do you deliver to [country]?"
"What currency are the prices on your site in?"
"Customs fees / VAT upon arrival?"
"Is this product available in my country?"
"Delivery time [country]?"
"Returns from abroad: who pays?"
"Can I pay in [local currency]?"
"Site in English but I am in France"
"Order blocked in customs"
"Difference .com vs .fr?"
Bot prioritization
Country availability + currency + duties = pre-purchase. International WISMO = post-purchase with the order's market, not the browsing country's market.
Intent routing
The `market_shipping` and `market_duties` intents are distinct from generic `wismo`: the bot loads the policy chunk of the correct market before responding, even if the customer's phrasing is vague.
How does it differ from the existing delivery and wholesale guides?
Three neighboring pieces of content, three focal points.
Delay communication (#delivery)
Delivery times and dynamic ETA: general timing copy. Here: configured regional Markets logic.
Wholesale B2B (#144)
Wholesale support (#144): reseller rates, MOQ. Markets B2B Plus shares the same market mechanics, but this guide #157 targets DTC international.
Generic multilingual
Translating the widget ≠ responding with the correct market catalog. The bot must read the price and stock in the presentment currency of the detected market.
How to detect the market and the language in conversation?
The chatbot market detection combines Shopify signals and conversation.
Technical signals
Shopify Market context: storefront session country
Domain / subfolder: .fr, /de, /en-ca
Presentment currency displayed on PDP
Browser locale: fallback if market is ambiguous
Conversational signals
Customer says "I am ordering from Tokyo": override JP market if configured. Shopify Dev: fallback language/country if localized content is missing.
Required slot
`market_id` or `country_code` stored in chat session before delivery, price, or duty response. See Shopify customer data.
Ambiguous case
Customer on US VPN, FR delivery: the bot asks "Which country would you like to be delivered to?" before making any promise. A single question, not a five-field interrogation.
How to answer currency and price questions?
The Markets chatbot currency answers must quote the currency presented, not the admin's.
Editorial rules
"Prices on your [country] market are displayed in [currency]"
Auto-conversion vs. fixed rate: aligned with Markets settings
No bot mental conversion ("around $X") without rate API
Checkout vs. navigation
Shopify Help: the order currency follows the shipping address and the associated market. Customer browses in USD, ships to Canada: the bot explains the switch to CAD at checkout if local currency is enabled.
Managed Markets
If you are using Managed Markets (merchant of record US), mention that duties and taxes can be integrated into the displayed price (Shopify International).
How to manage product availability by market?
The Markets chatbot catalog can exclude SKUs by region (restrictions, stock, regulation).
Bot verifications
SKU published in the customer's market?
Stock shippable to the destination country?
Regulated product excluded (e.g., prohibited supplement)?
Phrasing
"This product is not available for delivery to [country] in our current store. Alternatives: [market substitute SKU]." Never state "global stockout" if only one market is affected.
Corpus
Policy chunks per market: `market:EU`, `market:NA`, `market:CH`. See maintain knowledge base and regulated products.
How do you explain customs duties and international taxes?
Markets chatbot customs duties are a major source of tickets if poorly explained.
DDP vs DAP
Shopify 2026: DDP (Delivered Duty Paid) = duties collected at checkout, no surprises upon delivery. DAP = customer pays upon receipt, risk of package abandonment (Shopify, import shipping 2026).
What the bot can say
"For [country], estimated duties visible at checkout if enabled"
"HS code required for precise calculation; otherwise estimation"
"We ship DDP: nothing to pay to the delivery courier"
What the bot must not invent
Exact customs amount without live checkout = escalation or cart link. Never "zero fees" without checking market settings.
HS codes and admin
Shopify Help reminds: without HS code and product country of origin, the checkout customs estimate is approximate (Shopify, checkout duties). The bot directs to checkout for the exact amount, not to an invented range.
How to adapt delivery times and returns by market?
The Markets delivery & return policies vary by warehouse and regional carrier.
Timescales
Spreadsheet table: market | warehouse | carrier | min-max delivery time | notes. Bot reads the row of the session `country_code`. e.g., EU 4-7 business days, UK post-Brexit 5-10 days, US 3-5 days.
International return shipping fees
Who pays for returns from [country]? Local return portal vs. prepaid label? Dedicated chunk per market, not a generalized FR return policy.
Cross-border WISMO
Tracking + possible mention of customs delay. Escalate if package is stuck in customs > 7 days. See handoff (#12).
UK delivery response example
« For the United Kingdom, allow 5 to 10 business days from our EU warehouse, duties included at checkout if you see the "import fees" line. Tracking available as soon as shipped. » Calibrated phrasing for the market, not copied from the France policy.
How do you set up multilingual support without using simple translation?
A multilingual Markets bot responds in the customer's language with the localized market content, not a Google translation of the FR corpus.
Best Practices
RAG per locale: native FR, EN, DE chunks
Shopify Translate & Adapt for PDP; bot quotes local version
Auto language detection + explicit switch proposed
Legal terms (right of withdrawal): local legal chunk
Quality Test
Shoply AI: test 5 catalog questions per active language on real SKUs, not generic phrases. Common error: correct price in EN, shipping policy still in FR.
Multilingual Human Agents
The handoff transmits `locale` and `market_id` to route to a FR, EN, or DE agent. See context transfer (#155).
Privacy
Mention of language and market in the welcome message. See privacy (#154).
How should the corpus be structured and the Markets bot audited?
The Markets chatbot audit verifies market by market, not in aggregate.
Corpus structure
Metadata chunk: `market`, `locale`, `topic`, `last_updated`. Retrieval priority: exact market > market region > default.
Regression test suite
Per active market, 10 questions: delivery, currency, duties, SKU availability, returns. Audit #143 already cites the "DE Markets return policy" errors as a typical regression case (bot audit (#143)).
Quarterly review
With each new Shopify market: duplicate test suite, add chunks, train agents on country specificities.
How does Qstomy handle Shopify Markets international support?
Qstomy reads the Shopify Markets context (country, currency, catalog) to customize bot responses and agent handoffs.
Markets Features
Market detection: session + conversation override
Price presentment: displayed currency is quoted correctly
Filtered catalog: SKU availability by country
Multi-locale corpus: FR/EN/DE RAG
Duties/shipping chunks by market tag
Handoff context: market_id + language in ticket
Encrypted DTC Scenario
FR skincare brand, EU + UK + CH Markets. Qstomy bot syncs catalog and policies per market. After 12 weeks: "country shipping" tickets -41%, chat currency errors -89%, international bot-assisted session conversion +17%, customs escalations -28% thanks to DDP explanation at checkout.
Explore AI support, Shopify, request a demo.
Which operational playbooks for launching the Markets bot?
Playbook 1: market inventory (1 h)
List active Shopify markets: country, currency, languages, DDP/DAP, shipping warehouse.
Playbook 2: policy chunks (3 h)
Per market: shipping, returns, duties, currency. Market + locale metadata. Upload bot corpus.
Playbook 3: 10 tests / market (2 h)
Section 10. Correct price and delivery time hallucinations.
Playbook 4: multilingual welcome (30 min)
Language detection + mention of detected market. Link to international policy.
Playbook 5: post-launch market review (1 h)
30 days after country opening: top 5 bot questions, 3 corpus corrections, 1 agent macro.
Useful links
Selling internationally without a Markets-aware bot is like responding from Paris to a customer in Zurich with the wrong rules: the chatbot must travel with the customer, not stay at the domestic warehouse.
Enzo
June 28, 2026
