How Shopware supports the growth of international sales
International sales in e-commerce are not only about translating the store and adding another currency. The more markets, languages, domains, payment methods, deliveries, taxes, marketplaces and local sales scenarios, the more the platform's architecture matters. In this article we show how Shopware supports the growth of cross-border e-commerce thanks to sales channels, support for multiple languages and currencies, local payment and delivery methods, sales rules, international SEO, API-first integrations and B2B functions that make it possible to combine central control with local flexibility.
The growth of international sales in e-commerce very often starts from a simple assumption: since the company already has an online store in one market, it is enough to translate the site, add a few delivery methods, launch payments in another currency and start selling abroad. In practice, cross-border e-commerce is rarely that simple. The more markets, languages, currencies, sales channels, customer groups and local rules, the more the platform's architecture matters.
International e-commerce is not only about the user being able to switch the language of the site. It is a much broader ecosystem of decisions: how to manage many stores from one backend, how to run sales in different currencies, how to present local content, how to handle national payment and delivery methods, how to manage taxes, how to adapt the catalog to a specific market, how to take care of international SEO, how to connect online sales with marketplaces and how to maintain operational consistency when the company operates in several or a dozen countries at once.
From our perspective, the biggest mistake made by companies starting foreign expansion is treating international sales as a simple extension of the current store. If the platform was designed solely for one market, one currency, one language, one delivery model and one way of presenting the offer, every subsequent country starts to generate exceptions. First separate pricing logic appears. Then different tax rates. Then local promotions. Then separate content. Then different payment methods. Then different delivery terms. After a while, the company no longer manages scalable e-commerce, but a growing number of workarounds and local variants.
Shopware is a platform that responds to this problem very well, because international growth does not have to mean creating separate, hard-to-maintain stores for each market. What matters here are sales channels, support for multiple languages and currencies, the ability to configure domains, flexible management of taxes, rules, content, payments, deliveries, integrations and the API-first architecture, which allows the platform to be adapted to local requirements without losing central control.
International sales begin with architecture, not with translation
Translating the store into another language is important, but by itself it does not create international sales. A customer in a new market expects not only understandable content. They expect a price in their currency, familiar payment methods, clear delivery costs, correct taxes, local messaging, reliable lead times, culturally adapted content and a purchasing experience that does not feel like a store „translated in a hurry”.
That is why the first question before expansion should not be: „into which languages will we translate the store?”, but „how do we want to manage many markets in one ecosystem?”. Selling to two countries in a B2C model is designed differently, B2B sales to several markets with individual price lists differently, and a model in which the company combines its own store, marketplaces, wholesale sales, local promotions and different warehouses differently still.
Shopware supports such an approach above all through the ability to manage many country shops, currencies and languages in one backend. Each sales channel can have its own domain, assortment and pricing, which makes it possible to build local purchasing experiences without losing central control over the platform.
This is very important, because companies developing foreign sales often balance between two extreme models. The first consists of centralizing everything and showing customers in different markets an almost identical store. It is simpler operationally, but often weaker in sales terms. The second consists of creating separate stores for each country, which gives greater local flexibility but quickly increases maintenance costs, data problems, integrations and development. Shopware allows you to look for a sensible middle: to localize the experience where it matters to the customer, but to maintain a consistent technological and operational foundation.
Sales channels as the foundation of international expansion
One of the most important features of Shopware in the context of international sales are sales channels. It is precisely they that allow you to manage different sales channels, markets, domains, languages, currencies, payment methods, deliveries and configurations within one platform.
In practice this means that a company can build separate experiences for different countries without having to create completely separate systems. One market can operate on a Polish domain, a second on a German one, a third on a French one. Each can be assigned a language, currency, set of payment methods, shipping methods, tax settings and content tailored to local needs. At the same time, administration, product data, integrations and platform development can remain centrally managed.
This is especially important in companies that plan phased growth. At the beginning they launch sales in one foreign market, later add another language, then a new currency, later a separate domain, and then a marketplace or a B2B channel. If the platform does not have a well-designed sales channels model, every subsequent step starts to require an ever-greater number of compromises.
Shopware allows sales channels to be configured so that they correspond to specific markets and sales scenarios. In the channel settings you can define, among other things, the available payment methods, delivery methods, currencies and the way tax is calculated. For domains it is possible to assign a language, currency, snippet set and system of units to them. This gives very great flexibility when building local versions of the store.
From CREHLER's perspective, sales channels are one of those elements worth designing strategically right at the start of the project. It is not only about launching a second language. It is about thinking through how the company will manage markets in one, two and five years. Will each country be a separate channel? Will some markets be served jointly? Do the differences concern only language, or also assortment, price lists, taxes, warehouses and delivery logic? The answers to these questions influence the architecture of the entire implementation.
Multilingualism that does not end at translation
Shopware supports working in multiple languages, which is one of the basic conditions of international sales. In the administration you can configure languages, locales, ISO codes, language activity and translation inheritance. For companies operating in many markets this matters a great deal, because it allows local versions of the store to be managed in a more organized way than manually copying content between separate installations.
In practice, multilingualism in e-commerce covers far more than translating category names and product descriptions. Localization is required for system messages, the cart, checkout, transactional emails, consents, information pages, SEO content, URLs, promotion descriptions, delivery messages, brand content, banners, landing pages and customer service elements. If a company treats translation as a one-off project, inconsistencies will quickly appear.
That is why the content management process is so important in international sales. Shopware allows you to create local language versions and assign them to the appropriate sales channels and domains. In combination with a PIM, translation tools and a well-designed content workflow, this can significantly ease growth across many markets.
It is worth remembering, however, that a good translation does not always mean good localization. A local market may require a different tone of communication, different sales arguments, a different way of presenting categories, different promotional slogans, different trust icons, different payment methods and different delivery information. Shopware provides tools for managing multilingualism, but the localization strategy should stem from knowledge of the market, customers and sales model.
At CREHLER we often recommend that companies plan the model of working with languages already at the implementation stage. Who is responsible for translations? Does product data come from a PIM? How are descriptions updated across many markets? Are there local SEO contents? Are promotions translated centrally or locally? Does the team have a quality control process? Without these answers, multilingualism can become one of the most time-consuming areas of expansion.
Multi-currency and local prices
International sales require support for multiple currencies. The customer expects to see the price in a currency they understand and in which they make the purchasing decision. For a user from Germany, a price in euros is natural. For a customer from Poland, a price in zlotys builds greater transparency. For customers from markets outside the eurozone, currency can have a great impact on trust, comparability of the offer and the decision to buy.
Shopware makes it possible to manage currencies in the administration, create new currencies, edit existing ones and define their basic parameters, such as name, ISO code, abbreviation and symbol. Currencies can be assigned to sales channels and domains, so that a specific market can operate in its local currency.
In practice, however, multi-currency is not only a rate converter. The company must decide whether prices are to be automatically converted from the base currency or managed locally. In some models it is enough to convert the currency and round appropriately. In others, markets have their own pricing policy, different margin levels, different delivery costs, different customer expectations and different competition. In B2B there are also individual price lists, discounts, contractual terms and prices assigned to customer groups.
That is why implementing multiple currencies should be combined with a conversation about pricing. Is the price in euros a simple consequence of the price in zlotys? Does the German market have a separate price list? Should promotions be shared or local? Does the company want to show gross or net prices? How to handle rounding? What data will be the source of truth for prices? How is Shopware to communicate with the ERP in the context of currencies?
Shopware provides flexible possibilities for managing currencies, but the effectiveness of international sales is decided by the business model behind the price. At CREHLER we treat multi-currency not as a simple configuration, but as an element of the expansion strategy. The price is one of the most important market messages, so it should be consistent with local competition, costs, margin and customer expectations.
Taxes and compliance with local rules
One of the most difficult elements of international sales are taxes. Different countries can mean different VAT rates, different settlement rules, different documentation requirements and different transactional scenarios. In B2C, the rules of selling to consumers in the European Union are especially important, including mechanisms such as OSS. In B2B there are scenarios related to the EU VAT number, net sales, verification of the counterparty and settlements between companies.
Shopware indicates in its materials on internationalization that the system enables transactions in local currencies and offers flexible rules for calculating country-specific taxes, including support for the OSS scheme. In the sales channel configuration you can also define the way tax is calculated for orders in a given channel.
This is important, because international e-commerce requires not only an attractive frontend, but also correct transactional logic. The customer must see the right price, the right tax, the right invoice information and the right delivery terms. The company must be sure that orders reach the accounting and ERP systems in a way that complies with operational and legal requirements.
Of course, the platform itself does not replace tax advice. Every company should verify its obligations with its accounting department or a tax advisor, especially when selling to many markets. Shopware, however, provides the technological layer that allows different rules and configurations in international sales to be mapped.
At CREHLER we very strongly emphasize that taxes and pricing logic should be analyzed before launching a market, and not after the first problems in orders. If a company starts selling in a new market without the right tax model, later fixes may concern not only the frontend, but also the ERP, invoices, reporting and integrations.
Local payment and delivery methods
One of the most common reasons for cart abandonment in cross-border e-commerce is a lack of trust in the purchasing process. The customer may accept the product and price, but if they do not see a familiar payment method, do not understand the delivery or the shipping cost appears too late, the risk of resignation increases. International sales therefore require localization of the checkout, and not only localization of content.
Shopware allows you to define payment and delivery methods for specific sales channels. This means that a company can assign different payment and shipping options to the Polish market, different ones to the German, different ones to the Czech and different ones to the French market. Shopware also points to the possibility of supporting local payment methods, such as iDEAL, Blik or credit cards, in order to create a more native purchasing experience.
This is very important, because payment preferences are strongly local. In one market card payments will be popular, in another instant transfers, in another digital wallets, in another deferred payments, and in selected models cash on delivery may still be significant. A company that ignores local habits may have a problem with conversion despite a good product and good traffic.
Logistics works similarly. The customer wants to know how much they will pay for delivery, when they will receive the product, whether they have the option of pickup at a point, whether a local courier company is available, whether the return will be simple and whether the delivery is reliable. In the B2B model there are also other needs: pallet deliveries, lead times, minimum quantities, regional warehouses, shipping documents and integrations with logistics operators.
Shopware makes it possible to configure delivery methods at the sales channel level, but good international sales require designing the whole delivery experience. It is not only about the method being available at checkout. It is about the customer understanding the terms of purchase from the beginning and not having the feeling that they are ordering from a foreign store that only happens to serve their country.
Hreflang, local URLs and international SEO
International sales without international SEO very quickly become dependent on paid campaigns. If a company invests in local language versions, separate domains, content and categories, it should at the same time make sure that search engines understand the structure of the store. Otherwise, problems may appear with content duplication, incorrect routing of users to language versions or poor visibility in local markets.
Shopware indicates that with multiple language versions hreflang is important, because it helps to clearly assign content to the appropriate language and prevents different language versions from being treated as duplicates. In its materials on internationalization, Shopware also emphasizes automatic SEO signals, including setting hreflang and generating SEO-friendly URLs individually for each market.
This is of huge importance during expansion. The German site should be visible to German-speaking users. The French site to French-speaking ones. If the store operates on several domains or language paths, the URL architecture, hreflang, canonicals, sitemap, metadata, translations and internal linking must be designed in a consistent way.
At CREHLER we treat international SEO as an element of architecture, and not as a task performed only after implementation. Decisions about domains, category structure, URL names, translations, content and local landing pages influence organic visibility from day one. If a company launches markets quickly, without an SEO strategy, it may later have a problem with organizing indexation and recovering organic potential.
Shopware provides tools supporting international SEO, but their value depends on how the market structure is designed. Technology can generate correct signals, but the company must know which pages are to have organic value, which phrases are important locally, which content should be unique and how to build visibility in a given country.
Shopping Experiences and local content for markets
International sales require local communication. A merely translated catalog is not always enough, because users in different markets may have different needs, concerns, purchasing styles and expectations toward the brand. That is why an important element of Shopware are Shopping Experiences, that is, a tool for creating and managing content pages, landing pages, category pages and store layouts.
Thanks to Shopping Experiences, a company can create local landing pages, campaign pages, category layouts and content tailored to a specific market. Shopware indicates that with Shopping Experiences you can create, among other things, landing pages, shop pages and category layouts and manage them centrally. In the context of international sales this matters a great deal, because it allows a central system to be combined with local communication.
The example is simple. The same product can be sold in different markets with a different argument. In Poland the customer may respond to price and fast delivery. In Germany quality, warranty, certificates or trust in the manufacturer may matter more. In the Scandinavian countries aspects of sustainability may be more important. In B2B, on one market technical data will be key, and on another availability and integration with the customer's purchasing process.
Shopware makes it possible to create such differences without having to build separate pages from scratch. This is a big advantage for marketing and e-commerce teams that want to manage local campaigns faster and more flexibly.
At CREHLER we recommend that during foreign expansion you do not limit yourself to translating the homepage and categories. It is worth planning local landing pages, educational content, promotional pages, trust messaging, FAQs and sections that respond to the specific needs of a given market. Shopware provides the tools for this, but effectiveness depends on whether the company understands the local purchasing intent.
The Rule Builder as a tool for local sales scenarios
Every market has its rules. Different promotions, different delivery costs, different free-shipping thresholds, different payment methods, different customer groups, different purchasing terms, different restrictions and different campaigns. In international e-commerce the need very quickly arises to manage logic that should not be added each time as a customization.
In Shopware, an important role is played by the Rule Builder, which allows you to define rules used to adjust various settings and functions. From the perspective of international sales, this means the ability to build conditions dependent on the market, customer, cart, channel, delivery, payment or other elements of the process.
In practice, the Rule Builder can support local scenarios, for example different promotions for a specific country, different free-delivery thresholds, the availability of selected payment methods, cart conditions, restrictions for specific customer groups or special rules for B2B channels. Thanks to this, a company can create a more flexible sales model without designing every difference as a separate module.
This is especially important when a company develops many markets simultaneously. Without a rules tool, local exceptions very quickly start to create technical debt. The business team needs another promotion for Germany, different delivery for the Czech Republic, different terms for France, a different discount for B2B customers and a separate message for a chosen channel. If every such change requires development work, growth becomes slow and expensive.
The Rule Builder does not replace strategic process design, but it gives great flexibility in the daily management of sales. It is important to us that already at the implementation stage we distinguish rules that should be configurable by the business from those that should be an element of the system architecture. This allows the reaction time to market needs to be shortened and the number of unnecessary customizations to be limited.
API-first and integrations with the local ecosystem
International sales rarely operate solely within the e-commerce platform itself. The company needs integrations with ERP, PIM, WMS, CRM, payment operators, couriers, marketplaces, accounting systems, marketing automation tools, customer service systems and analytics. The more markets, the more the flexibility of integrations matters.
API-first architecture is one of the elements supporting the flexible adaptation of the system to regional requirements. This is very important, because each market may require different tools. In one market the company uses a local payment operator. In a second, a different courier system. In a third, a local marketplace. In a fourth, integration with a tax system. In B2B there are also integrations with customers' systems, procurement platforms, individual price lists and quoting processes.
API-first is therefore not a technical slogan. It is a condition of scalability. The platform must communicate with other systems in a stable, predictable and extensible way. If integrations are designed on a point basis, without architecture, every new market increases complexity. If they are designed strategically, they can become an advantage.
At CREHLER we especially strongly emphasize that integrations should be designed before the start of expansion, and not only when the first operational problem appears. You have to determine which systems are the source of truth, how data flows, how often it is updated, how errors are handled, what happens when there is no synchronization and who is responsible for maintaining the integration. In international sales, without this it is hard to speak of scaling.
Marketplaces as part of expansion, not a separate world
For many companies, international sales do not begin with their own store in a new market, but with a marketplace. Amazon, eBay, Kaufland, bol.com, Zalando, Otto, Allegro or local industry marketplaces can give faster access to customers and allow the market's potential to be tested without building a full local structure right away.
Shopware is also developing the multichannel and marketplace area. In its materials on Shopware Multichannel Connect it is indicated that the solution created with ChannelEngine makes it possible to connect Shopware 6 with a broad network of global marketplaces, centrally manage product listings, stock levels, prices and orders, and access more than 950 sales channels.
This is important, because marketplaces can be a very effective expansion tool, but at the same time they generate great operational complexity. Each channel has its own product requirements, categories, commissions, logistics models, pricing rules, customer expectations and requirements regarding order handling. If a company manages marketplaces manually, chaos in data, stock levels and prices appears very quickly.
Shopware can be the central element of an ecosystem in which the company's own store, marketplaces and other sales channels are connected to one model of data and processes. Thanks to this, marketplace expansion does not have to mean creating a separate operation alongside e-commerce. It can be part of a larger multichannel strategy.
From CREHLER's perspective, however, the most important thing is that the marketplace should not be a random add-on. The company should know which products it sells in a given market, what the margin terms are, how it will handle logistics, how it will synchronize stock, how it will manage descriptions, how it will handle returns and how it will avoid conflicts between channels. Technology helps, but the channel strategy must be conscious.
B2B internationalization: foreign sales in the business model
International sales in B2B are even more complex than in B2C. The business customer expects not only language and currency. They expect their commercial terms, individual prices, quoting, order history, quick reordering, user roles, approvals, documents, limits, availability and integration with the purchasing processes of their organization.
Shopware B2B Components support such scenarios through modular functionalities that can be tailored to the company's operational processes. Among them are, for example, quick order options, employee management, quote management, shopping lists and approval rules. For international B2B this matters a great deal, because it allows the platform to be designed not only as a product catalog, but as an environment of cooperation with the business customer.
Let us imagine a company that sells to distributors in several countries. Each market has different price lists, different delivery terms, different limits, different people responsible for orders and different approval processes. In the traditional model, a huge part of this work goes to salespeople. In well-designed B2B e-commerce, the platform can take over part of the repetitive activities: show the customer the right prices, allow quick orders, handle requests for quotation, manage users within the customer's company and reduce the number of emails.
This does not mean that the platform replaces relationship-based selling. It means that it gives salespeople and customers a shared working environment. In international B2B this is of particular importance, because language differences, time zones and local processes increase the cost of manual handling. The more can be moved to well-designed self-service, the easier it is to scale sales without a proportional increase in the team.
At CREHLER we see that B2B companies very often do not need an „online store” in the simple sense. They need a digital sales and customer service platform. Shopware provides the foundation for building such models, but success depends on whether the architecture takes into account real B2B processes in different markets.
Multiple warehouses and the logic of international deliveries
In foreign sales, logistics very quickly becomes one of the key areas. A company may have a good store, a local language and attractive prices, but if delivery is expensive, unpredictable or too slow, conversion will be limited. In international e-commerce it increasingly matters not only whether a product is available, but where it is available and from which warehouse it should be shipped.
In Shopware there is the possibility of managing warehouses and warehouse groups and using rules to select a warehouse in relation to the delivery address. An order can be shipped from warehouses closer to the shipping address in order to shorten delivery time, take taxes into account and avoid customs clearance.
This is very important in more advanced expansion models. At the beginning a company may ship all orders from one warehouse. Later a local warehouse appears, a fulfillment partner, a marketplace warehouse, a regional warehouse or separate handling for the B2B market. Then the platform must support not only information about availability, but also the logic of assigning the order to the appropriate fulfillment source.
In practice, multi-warehousing requires integration with WMS, ERP, logistics operators and order handling systems. Shopware can be part of such an ecosystem, but the key is to design the data flow. The customer should see reliable availability and a predictable delivery date, and the company should know from where the order will be fulfilled and how this will affect cost, time and the operational process.
Central control and local flexibility
The greatest value of Shopware in international sales is the ability to combine central control with local flexibility. A company can manage the platform, data, integrations and development from one place, but at the same time create differences where the market requires it.
Centralization is needed, because without it expansion quickly increases costs. If each market has a separate installation, a separate catalog, separate integrations, separate data and a separate development process, the organization loses control. Every change requires repetition in several places. Every update is harder. Every error can occur in a different variant. Every new market requires a large amount of work.
Local flexibility, however, is equally important. Customers in different markets do not behave identically. They need different content, payment methods, deliveries, currencies, campaigns, trust messaging and sometimes a different assortment. A company that centralizes everything without the possibility of local adaptation may have a platform that is easy to maintain but weak in sales terms.
Shopware allows you to build a model in which one does not exclude the other. Sales channels, domains, languages, currencies, rules, Shopping Experiences, payments, deliveries and integrations make it possible to create local experiences within one ecosystem. This approach works especially well in companies that want to develop sales gradually, test markets and scale channels without rebuilding the platform after each subsequent country.
Implementing Shopware for international sales
At CREHLER we do not treat international expansion as a simple extension of the current store with more languages. We look at it as a sales-architecture project. Before we start the configuration, we analyze the business model, markets, channels, languages, currencies, product data, prices, taxes, logistics, integrations, marketplaces, SEO, B2B and the organization of the team's work.
This makes it possible to avoid a situation in which a company launches another market but, after a few months, discovers that it has no control over translations, promotions, stock levels, prices, logistics or reporting. International sales require pace, but should not be designed chaotically.
In Shopware projects it is especially important to us to design the sales channels, the model of domains, languages, currencies and rules. We analyze which elements should be shared across all markets and which should be local. We check whether product data is ready for translations and local variants. We design integrations with ERP, PIM, WMS, CRM, payments, deliveries and marketplaces. We make sure that the platform not only works at launch, but is ready for further countries and channels.
The roadmap is also an important element. Not every company has to launch ten markets right away. Often a better approach is to choose the first market, a well-designed expansion model, test the processes, organize the data and only later scale to further countries. Shopware provides the appropriate flexibility for this, but success depends on the quality of the implementation decisions.
Shopware as a platform for companies that want to grow beyond one market
The growth of international sales requires technology that does not treat every market as an exception. This is precisely why Shopware is a good choice for companies that want to develop cross-border e-commerce, B2B sales, marketplaces, local language versions, different currencies and complex integrations in one scalable ecosystem.
The greatest value of Shopware is not a single feature. It is not only multilingualism, multi-currency, sales channels, the Rule Builder, Shopping Experiences, B2B Components or API-first. The greatest value is that these elements can together create a coherent architecture for international growth. The platform can handle local differences but at the same time remain the central sales system.
For companies thinking about expansion, this is crucial. The first foreign market can often be handled with simple solutions. The second and third already reveal problems. The fifth shows whether the platform was really designed for scale. If the system does not handle languages, currencies, taxes, domains, local content, payments, deliveries, integrations and rules well, international growth starts to become ever more expensive.
At CREHLER we help companies design and implement Shopware so that foreign expansion is not a collection of local workarounds, but a controlled model of sales growth. If a company wants to enter new markets, it is worth starting not with translating the store itself, but with a conversation about architecture: sales channels, data, integrations, currencies, taxes, SEO, logistics and processes. That is precisely where the difference begins between a store available abroad and e-commerce really ready for international sales.