Selling in several countries needs more than translated text
Language, delivery country, currency and payment are separate settings. A fictional country switch shows what needs to be checked together.

I would treat a new country version as a change to the shop configuration. Translated product text addresses only part of the task. What matters is whether the application preserves the agreed offer for the selected destination through to the processed order.
Language does not determine the delivery country
Shopify describes market matching that can change at checkout with the shipping address. Shopware includes language, currency, countries and payment and shipping methods in its sales-channel context. Implementations differ; a language selector alone does not describe this context.
Our own fictional shop plans French text for deliveries to France and Switzerland. The following values are freely chosen test requirements, not pricing advice, currency conversion or statements about national regulations.
Test configuration | Planned state for item |
|---|---|
| Test price 50 EUR; assigned test payment and test shipping method A |
| Test price 55 CHF; assigned test payment and test shipping method B |
The language stays the same while the configuration changes. If the tester switches destination with a filled cart, the team must be able to trace which prices and available options apply afterwards. The table does not claim a test has already been run.
Reconcile display and actual processing
Shopify specifies prerequisites for payments in local currencies. A displayed currency therefore does not prove that every provider combination will charge in that currency. Using suitable test access, check the amount and currency of the display, test payment and transferred order together.
Also check address fields, allowed shipping options and messages for an unsupported destination. Missing mappings must not silently use another country configuration.
Deliberately define the limits of shared configurations
Several countries do not automatically require separate shops. If they share the same confirmed business rules, a common configuration may fit. Different rules must be explicitly represented and tested. Applicable tax or legal requirements need separate specialist clarification; the technical table does not replace that assessment.
Sources
Written by
- Anna NeumannEditor for Content and Digital MarketingAnna Neumann plans and writes content on digital marketing at ASES. Her topics include search engine optimisation, content strategy and web analytics, with a focus on evaluating marketing activities and their results in a transparent way.
Read more
All articles






E-Commerce with ASES
Online shops, marketplaces and B2B portals


