B2B internationalisation: country-specific shops

The obvious solution -- translating the existing shop into English and serving it on a .com domain -- falls short in B2B. Business customers expect a purchasing environment in every market that feels like a local provider: in their language, with their currency, with correctly displayed tax and with an assortment that matches local requirements. 75 percent of international buyers want to purchase products in their native language (Branchendaten), and 40 percent generally do not buy from websites that are not available in their language (Branchendaten).

The widely cited "Can't Read, Won't Buy" study by CSA Research has confirmed this finding for years: a large share of consumers spend most or all of their time on websites in their own language, and the majority prefer to buy products offered in their preferred language (CSA Research). In B2B this effect intensifies, because buying committees are often involved, technical data sheets are reviewed and legal documents must be binding. An inaccurate translation of a safety specification can cause a deal to fail.

A country-specific shop strategy rests on four pillars that together shape the purchasing experience. Each pillar has its own technical and organisational complexity -- and none can be considered in isolation.

Linguistic localisation begins with the user interface, but does not end there by any means. In the B2B context, the most demanding areas are the product data: technical attributes, units of measure, standard designations and certifications differ from market to market. Professional product data management via a PIM system is therefore the foundation of any multilingual strategy. Without central data management, the maintenance effort multiplies with each new language.

The business relevance is considerable: localised checkout language typically increases conversion by 20 to 30 percent (Branchendaten), and localisation is consistently regarded as one of the central conversion drivers in cross-border trade (Market Data Forecast). In Shopware Open Source, multilingualism is mapped via language layers and sales channels: a single sales channel can carry several languages, or each country receives its own channel with its own domain. Which variant fits depends on the market strategy.

For multilingual visibility in search engines, correct annotation with hreflang is decisive. It signals to search engines which page is intended for which language-country combination and prevents duplicate content problems between similar language versions. How SEO visibility towards business customers is built systematically requires its own consideration for each target market.

Displaying prices in the local currency is not a comfort feature in international trade but a trust factor. Studies show that a considerable share of buyers expect a price stated in their own currency, and the absence of local currencies noticeably lowers purchase intent (Filuet). Naive conversion via a daily exchange rate is rarely sufficient in B2B: business customers work with fixed terms, annual prices and framework contracts that must not fluctuate with every rate swing.

The clean solution is independent price lists per market. Instead of converting prices, dedicated prices are stored for each target market -- aligned with local market conditions, competition and margin strategy. In Shopware this can be mapped via currency-specific prices and customer groups. As a result, the same article can appear in Germany in euros, in Switzerland in francs and in the USA in dollars with market-appropriate values in each case. The customer-specific pricing that is standard in B2B remains fully intact.

No other pillar of internationalisation carries as much potential for error as tax and legal logic. In B2B trade within the EU, the reverse charge procedure usually applies: for intra-community supplies between businesses, the seller invoices without VAT, and the buyer self-assesses the transaction in their own country (PwC). The prerequisite is a valid VAT identification number that the shop should verify in real time.

For sales to end consumers, the EU-wide One-Stop-Shop scheme with a uniform delivery threshold of 10,000 euros has applied since July 2021 (KPMG). If this threshold is exceeded across all EU countries, the VAT of the destination country must be applied and can be reported centrally via the OSS scheme (PwC). Since B2B shops often serve both business and end customers, the architecture must handle both logics in parallel and distinguish cleanly by customer type.

For deliveries to third countries such as Switzerland, the United Kingdom or the USA, customs, import VAT and country-specific tax systems are added. In the USA, for example, sales tax is levied at state and partly municipal level, which leads to thousands of possible tax rates. A country-specific architecture encapsulates this complexity so that the buyer in the frontend only sees a correct, comprehensible result. The connection between tax logic and financial accounting usually runs via the ERP integration of the B2B shop, which serves as the leading system for tax rates and terms.

A frequently underestimated aspect of internationalisation is assortment control. Not every product may or should be sold in every country: approvals, standards, hazardous material rules or simply the market strategy mean that assortments vary by country. A technical product certified to a DIN standard in Germany may require a different certification for the French market -- or may not be offered there at all.

In a cleanly set up Shopware architecture, assortment assignment is controlled via sales channels and category assignments. Each country sales channel receives exactly the products approved for that market. Central product maintenance remains unaffected: a product is created and maintained once, and its visibility per market is controlled separately. This prevents data duplicates and keeps the maintenance effort manageable.

The guiding principle of scalable B2B internationalisation is: manage centrally, deliver locally. Master data, product information, stock and business logic live in central systems -- ERP for prices, taxes and stock, PIM for product data. The country-specific expression arises in the presentation layer via sales channels, language layers and currency-specific prices. This keeps data management lean while the frontend appears fully local in each market.

Technically, this model rests on a well-considered interface and integration architecture that connects shop, ERP and PIM. The synchronisation of prices, stock and tax rates must be reliable, idempotent and traceable -- especially when several countries are served in parallel. A central question is whether several countries are mapped in one Shopware instance with multiple sales channels or whether separate instances are more sensible.

For most mid-market B2B traders, the multi-channel architecture in one instance is the more economical choice: it keeps the maintenance effort low and enables central updates, while each country receives its own expression. How this results in a consistent self-service experience is particularly evident with B2B customer portals, in which international customers manage their orders, terms and documents across countries.

The shift in purchasing behaviour intensifies the pressure to internationalise: according to Gartner, 67 percent of B2B buyers prefer a largely rep-free buying experience (Gartner), and more than 75 percent of buyers and sellers prefer digital self-service and remote interactions over in-person meetings (McKinsey). For internationally active traders this means: in many markets the shop is the first and often decisive point of contact -- and must feel like a local provider everywhere.

Internationalisation tends to succeed better in waves than in one big move. It makes sense to start with a target market that is structurally similar to the home market -- same currency, comparable tax system, similar assortment requirements. This allows architecture, processes and maintenance routines to be tested on a manageable case before more complex markets with their own currency and third-country logic follow.

This incremental approach reduces risk and allows lessons to be learned from the experience of the first market. At the same time, every clean piece of preparatory work -- central PIM, clean ERP mapping, well-considered channel structure -- directly pays into the speed of future market entries. A well set-up architecture makes the second and third market considerably cheaper than the first.