Cross-Border Ecommerce with Magento: Stores, Currencies, Tax and Languages

Cross-border ecommerce means selling online to customers in other countries, with the right language, currency, prices, tax, shipping and payment options for each market. In Magento and Adobe Commerce, most of that comes down to one early decision: how you map markets onto websites, stores and store views. Get that structure right and the rest is configuration; get it wrong and you will fight it on every price change, tax update and SEO fix.

This guide explains the hierarchy, gives a planning table you can use in a workshop, and covers currency, tax, languages, SEO and operations.

How Magento's website, store and store view hierarchy works

Every Adobe Commerce and Magento Open Source installation has a hierarchy of websites, stores and store views. Adobe's documentation describes a cascading configuration model: global, then website, then store, then store view. Each level has a main job:

• Website: top-level configuration. Price scope, base currency (when price scope is set to website), payment and shipping methods, and whether customer accounts are shared are typically decided here.
• Store: root category configuration. Stores under one website share the checkout and can show a different catalog tree.
• Store view: language and display currency. Each store view can have its own base URL and translated content.

The key detail for currency: base currency scope is global by default. If you set Catalog Price Scope to "Website", each website can have its own base currency and its own prices. Store views can show different display currencies, but transactions are processed in the website's base currency.

Website, store and store view planning table

Use this table to decide what each market needs. If a market needs a different value in a "website-level" row, it usually needs its own website.

Three common patterns

• One website, several store views: one currency, several languages. Works for a single market with more than one language, or when converted display prices are acceptable.
• One website per currency region: for example, EU (EUR), UK (GBP) and US (USD), each with language store views as needed. This is the most common setup for real local pricing.
• One website per brand or business entity: when legal entities, payment accounts or customer bases are separate. B2B and B2C on the same platform often fit this pattern; our B2B ecommerce guide covers the B2B side.

More websites mean more configuration, more indexing work and more testing. Add one only when a setting truly has to differ.

Currency and pricing

• Converted versus local prices: converted prices change with exchange rates and end in odd numbers. Local prices need website price scope and a process for maintaining them, usually in your PIM or ERP.
• Promotions: Adobe's documentation advises website price scope with a base currency per site if you want fixed-amount discounts that are not converted from a global base currency.
• Rounding and tax display: decide whether prices include tax per market. EU and UK shoppers expect tax-inclusive prices; US shoppers usually see tax at checkout.
• Payment settlement: check your payment provider can accept and settle each currency, and which local methods it supports.

Tax and duties

Tax rules drive both configuration and paperwork, so involve your accountant early. A few common points:

• EU VAT One Stop Shop (OSS): since 1 July 2021, B2C distance sales of goods within the EU are taxed in the customer's country once your EU-wide cross-border sales exceed EUR 10,000 a year (the threshold applies to sellers established in a single Member State). OSS lets you declare that VAT through one Member State.
• Import One Stop Shop (IOSS): covers VAT on imported goods in consignments up to EUR 150, so customers are not surprised by charges at delivery. Non-EU sellers generally need an EU intermediary to use it.
• Configuration: Magento supports tax rates by country and region, tax classes and display settings. Larger catalogs and many jurisdictions often use a tax calculation service instead of manual rate tables.
• Duties: decide whether you charge duties at checkout (delivered duty paid) or leave them to the customer. This affects carriers, pricing and returns.

This is general information, not tax or legal advice. Rules change, so confirm your obligations with an adviser for each market.

Languages and content

• Translate product content, CMS pages, emails and transactional texts, not only the theme.
• Use real translations for key pages; machine translation plus human review is a practical middle ground for long catalogs.
• Localize sizes, units, date formats, address forms and phone formats.
• Localize legal pages: returns, terms, privacy and accessibility statements. EU markets also bring accessibility obligations; see our guide to ecommerce accessibility and the European Accessibility Act.

International SEO

Each language or regional version should have its own URL, and you should tell Google how they relate. Google's documentation on localized versions recommends hreflang annotations (in HTML, HTTP headers or the XML sitemap), with each version listing itself and every other version, plus an x-default for a fallback or country selector page. Google also notes its crawler usually does not send an Accept-Language header, so do not rely on automatic redirects by IP or browser language to show the right version.

• Pick one hreflang method and use it consistently.
• Do not force-redirect visitors by IP; offer a country or language selector instead.
• Keep canonical tags pointing to the same-language version, not across languages.
• Translate URL keys and metadata per store view.

Mistri's Magento SEO service covers hreflang, canonical setup and international URL structure.

Operations checklist before launch

1. Confirm entities, VAT registrations and payment accounts per market.
2. Agree the website, store and store view map using the table above.
3. Set up pricing ownership (who maintains local prices, and in which system).
4. Configure tax, shipping, payment methods and currencies per website.
5. Translate and localize content, emails and legal pages.
6. Set up hreflang, sitemaps per store view and a country selector.
7. Test checkout end to end in each market, including refunds and returns.
8. Check customer service coverage for time zones and languages.

FAQ

Do I need a separate Magento installation per country?

Usually not. One installation can run many websites and store views. Separate installations make sense only when businesses are fully independent.

Can one website show prices in several currencies?

Yes, as display currencies per store view, but orders are processed in the website's base currency. For true local pricing, use separate websites with website price scope.

Should I use country domains or subfolders?

Both work with hreflang. Country domains signal locality clearly but cost more to run and build authority for; subfolders are simpler to maintain.

Next steps

Run the planning table with your finance, operations and marketing leads before any build work. If you want help mapping markets to a Magento structure or implementing it, Mistri's Adobe Commerce development service handles multi-store setup and configuration.

Sources: Adobe Experience League: Websites, stores and views; Adobe Experience League: Currency configuration; European Commission: VAT One Stop Shop; Google Search Central: Localized versions of your pages.