Anyone selling abroad with their Shopware shop soon faces a simple but consequential question: which currency does the customer see? Multi-currency means far more than layering an exchange rate over your prices. It is about local prices that feel right, maintained exchange rates, clean price rounding and the correct VAT per country. Around 94% (PYMNTS) of cross-border shoppers expect prices in their own currency, and about 33% (Capital One Shopping) abandon the purchase when only a foreign currency is shown. This article shows how to implement multi-currency in Shopware thoughtfully - technically, fiscally and psychologically.

Why Local Prices Decide Cart Abandonment

There is also a trust aspect that is often underestimated: a price in the customer's own currency signals that the shop is prepared for that market. A shopper in Sweden who suddenly sees euro amounts unconsciously concludes that shipping, returns and support may not be thought through locally either. Local prices are therefore also a signal of market proximity - they reduce the perceived distance between shop and buyer and take away part of the uncertainty that accompanies every cross-border purchase.

This effect intensifies on the smartphone. A large share of cross-border trade happens on mobile, where the screen is small and attention is scarce. If the customer must also interpret a foreign currency here, cognitive load rises at exactly the moment the buying decision is made. A price clearly shown in local currency and cleanly rounded removes that hurdle - which is precisely why the currency question belongs at the start of every internationalization project, not at the end.

International trade is growing fast: the European cross-border market was around USD 370 billion in 2024 and is expected to reach roughly USD 437 billion in 2025 (Research and Markets). More than 70% (Eurostat) of European consumers now buy from foreign online retailers. Yet the currency question often decides whether interest turns into a purchase. If the price is shown only in a foreign currency, the customer must convert it mentally, estimate the difference on the card statement and muster trust - three friction points that cost conversions.

The numbers are clear: about 92% (Capital One Shopping) of shoppers prefer shops that price in their local currency, and roughly 98% (Worldpay) would ideally browse and pay in their own currency. On top of that, around 99% (PYMNTS) of cross-border shoppers expect their customary payment method, so local currency and the right payment option together are a strong lever against cart abandonment. Local prices are therefore not a cosmetic detail but a direct lever on revenue in cross-border business.

Currency and Payment Method Belong Together

Nearly 99% (PYMNTS) of cross-border shoppers want to pay with their preferred local method. Local prices only take full effect once the matching payment options per market are available too - the currency in the storefront and the payment method at checkout must match.

How Multi-Currency Works in Shopware

It is also worth noting that not only product prices are affected by currency, but also shipping costs, minimum order values, free-shipping thresholds and discounts. A EUR 50 threshold for free shipping, converted into another currency, yields an awkward value that should likewise be rounded to a clean amount. Multi-currency is therefore not purely a product-price question but concerns all price-related rules in the shop.

In practice it pays to decide early which currency serves as the internal calculation base. The euro is commonly used as the default currency against which all factors are defined. All prices, discounts and tiers are maintained in that base; the foreign currencies derive from it. This keeps data maintenance lean, because a price change on the base product automatically flows into all currencies - as long as you rely on automatic conversion rather than fixing each foreign-currency price by hand.

Base Currency as the Anchor

A clearly defined base currency keeps the pricing model maintainable: maintain the EUR base price, derive via factors, and use targeted fixed prices only where the psychological price point matters. This avoids a sprawling scenario in which hundreds of foreign-currency prices have to be updated one by one.

Shopware ships multi-currency out of the box. Each currency is defined via an exchange-rate factor relative to the default currency (EUR = 1, USD = e.g. 1.08). Prices are converted using that factor and displayed in the respective currency in the storefront (Shopware documentation). In addition, you can define per sales channel which currencies are available - so an international channel can offer several currencies while a purely German channel stays in EUR.

Two paths lead to a foreign-currency price: automatic conversion via the factor, or a fixed price per currency. The factor is quick to set up but produces awkward amounts. Fixed prices per currency are more work to maintain but allow psychologically clean price points. In practice, a mix often works best: the factor as a baseline, fixed prices for key products and markets.

AspectFixed Price Per CurrencyAutomatic Conversion
Price appearanceclean price points (e.g. 99)awkward amounts (e.g. 107.84)
Maintenance efforthigher, per productlow, central via factor
Rate riskmaintained manuallyfollows the factor
Best fortop sellers, core marketsbroad range, secondary markets

Maintaining Exchange Rates Without a Margin Trap

The safety margin is not a trick at the customer's expense but a commercial necessity: between two rate updates the exchange rate can move, and especially with volatile currencies a factor calculated too tightly can eat into the already thin margins of distance selling. A small, transparently calculated buffer cushions that swing. It is important to apply it consistently across all currencies and to review it regularly, rather than varying it arbitrarily per market.

Exchange rates are not a settings field you fill in once but an ongoing process. Those who fail to define it leave their cross-border margin to the chance of the daily rate.

XICTRON development team

Exchange rates move daily. Setting the conversion factor once and then forgetting it risks two mistakes: prices too high that drive customers away, or prices too low that cost margin. A defined process therefore makes sense - manual at fixed intervals or automated via a rate source connected through an interface. We implement such rate updates as part of programming and development individually, including a safety margin that cushions rate fluctuations between two updates.

  • Define the rate source: your bank, public reference rates or a payment provider as the basis.
  • Update interval: daily, weekly or event-based on larger swings.
  • Safety margin: a small buffer so rate fluctuations do not cut into the margin.
  • Round afterwards: convert first, then round to a clean price point.
The Rate Is Not the Final Price

The raw daily rate rarely yields a sellable price. 107.84 instead of 99 looks random and erodes trust. Between conversion and display there should consistently sit deliberate rounding logic - otherwise you forfeit the psychological effect of clean prices.

Price Rounding: Why 99 Sells More Than 107.84

In practice it helps to define a few representative price points for each target market and align the rounding to them. This creates a consistent price image across the entire range, rather than a patchwork of awkward individual amounts. The same logic applies to promotional and discount prices: a reduced price should be as cleanly rounded as the regular price, otherwise the reduction looks arbitrary and the psychological effect fizzles out.

Technically, rounding in Shopware is controlled via decimal places and a rounding interval. An interval of 0.05, for example, rounds every amount to the nearest multiple of five centimes - the solution for the Swiss market, where the smallest coin differs from the smallest unit of account. For markets where decimals are uncommon, you can round to whole amounts, turning a converted figure into a sellable price without distracting decimals.

rounding-per-currency.json
{
  "CHF": { "decimals": 2, "interval": 0.05 },
  "SEK": { "decimals": 0, "interval": 1.00 },
  "USD": { "decimals": 2, "interval": 0.01, "ending": 0.99 },
  "GBP": { "decimals": 2, "interval": 0.01, "ending": 0.95 }
}

Whether a 9-ending or a round price makes sense depends on product and market. In the entry-price segment, endings like 9.99 act as a bargain signal, while round prices like 100 convey quality for premium or explanation-heavy products. This decision should be made deliberately per product area - a blanket 9-ending across the entire range can even be counterproductive in the premium segment.

Price rounding is the underrated part of multi-currency. The left-digit effect makes customers weight the left-most digit disproportionately: 9.99 is perceived as noticeably cheaper than 10. A widely cited analysis found around 24% (University study, 2011) higher sales from prices ending in 9, and an experiment by MIT and the University of Chicago even 35% (MIT/University of Chicago) more demand. This effect is lost when conversion produces awkward amounts like 107.84.

Shopware therefore allows a differentiated rounding configuration per currency and even per country: you set the decimal places and the rounding interval (Shopware documentation). This covers markets where the smallest unit of account differs from the smallest coin - such as Switzerland, where prices round to CHF 0.05. The order matters: convert to the foreign currency first, then round to the desired price point.

Market-Specific Endings

9.99 in EUR, .95 in GBP, round hundreds in SEK - every market has its own conventions.

Rounding Interval

Switzerland to CHF 0.05, Scandinavian markets often to round amounts without decimals.

Premium vs. Entry Price

Round prices (100) signal quality, 9-endings read as a bargain - choose deliberately.

Tax Per Country: OSS Instead of a Flat 19%

From an accounting perspective it is also important that foreign-currency sales are documented cleanly. Every order should record the exchange rate used, the amount in foreign currency and the converted value in the base currency, so that documents remain traceable and audit-proof later. This traceability matters not only for the tax authority but also for your own analysis: only when it is clear which rate applied at which point in time can margins per market be assessed reliably and rate losses be distinguished from genuine assortment effects.

A further distinction is between B2C and B2B. In B2B trade within the EU, the reverse-charge mechanism often applies with a valid VAT identification number, shifting the tax liability to the recipient and letting the shop invoice net. In B2C trade, by contrast, the destination country's tax rate applies once the distance-selling threshold is exceeded. An internationally oriented shop must keep these cases cleanly apart and map the tax logic accordingly - ideally automated based on customer group, country of delivery and VAT ID.

Local prices are not the end of the job - VAT must be correct per country. For cross-border B2C sales within the EU, a combined distance-selling threshold of EUR 10,000 (EU Commission) per year applies, cumulative across all EU countries. Below that threshold you may apply your domestic rate; above it, VAT is due in the customer's country (VATupdate). Instead of registering separately in every EU country, merchants can use the One-Stop-Shop scheme (OSS) and report all EU sales centrally through a single return.

For the shop this means: the tax rate must not be a flat 19% but must follow the country of delivery - 20% in Austria and France, 25% in Sweden, and no EU VAT for deliveries to third countries like Switzerland or the USA. Shopware maps country-specific tax rates; the correct assignment and a clean link to accounting are something we implement together with the matching DATEV integration. If you invoice cross-border anyway, also keep the requirements for ZUGFeRD and XRechnung in view.

Do Not Underestimate Tax Logic

Incorrectly stated VAT in cross-border business can lead to back payments and corrections. The thresholds and rates mentioned here are an overview and do not replace tax advice. Be sure to coordinate the specific situation - OSS registration, B2B reverse charge, third-country deliveries - with your tax advisor.

Language, Shipping and Payment as One Package

Another building block is how shipping and customs costs are displayed. For deliveries to third countries, import duties may apply that the customer ultimately bears. Communicating these costs transparently and as early as possible in the order process - ideally as a total price including all charges in local currency - avoids nasty surprises at the doorstep and therefore returns and complaints. The currency logic does not end at the product price but runs through the entire basket to the final order confirmation.

In international business it is also worth looking at display conventions: thousands separators, the position of the currency symbol and the decimal separator differ from country to country. 1.299,00 EUR in Germany corresponds to 1,299.00 in English-speaking markets, and the symbol sometimes precedes and sometimes follows the amount. These details seem small but add up to the impression that a shop truly understands the respective market.

Multi-currency is most effective as part of a coherent international presence. That includes translated content, market-appropriate shipping options and local payment methods. Studies show that 24% (Baymard) of shoppers abandon when delivery is too slow, and 16% (Baymard) when the return policy is unconvincing. Currency, shipping and payment are therefore not separate projects but one connected experience.

The checkout itself should stay fair and transparent: hidden conversion or foreign fees that appear late destroy trust. What a clear, honest payment process looks like is described in our article on how to avoid dark patterns in checkout. Those selling internationally also benefit from features that raise basket value - such as product bundles and set articles, which must be calculated cleanly in every currency.

  • Local currency activated per target market and assigned to the sales channel
  • Exchange rates maintained with a defined interval and safety margin
  • Price rounding per currency and country set to market-typical price points
  • VAT correct per country of delivery (OSS scheme reviewed)
  • Local payment methods and market-appropriate shipping options added
  • Language and content translated for the target market

Internationalization as a Plannable Project

Planning multi-currency as part of the overall architecture from the start saves costly rework later. Even when designing an international shop, the data model, pricing logic and tax rules should be set up so that adding further markets and currencies is anticipated. This includes the question of whether prices are maintained centrally or per market, how discounts and promotions work across currencies and how the connection to inventory management and accounting scales along. A well-considered foundation turns every expansion into a plannable step rather than a technical hurdle.

In practice a step-by-step approach is advisable: first set up one or two core markets completely correctly - including currency, rounding, tax and payment - and then transfer the insights to further markets. This keeps complexity manageable, and each new market benefits from a proven logic rather than a reinvention. Adding a currency later then becomes routine rather than a special project.

Multi-currency is technically manageable once exchange rates, rounding and tax are thought of as one connected system rather than three loose settings. The biggest lever is not the individual factor but the end-to-end logic: from the EUR base price through the maintained rate and clean rounding to the correct tax rate and the right payment method. As a Shopware agency we support internationalization projects from concept to go-live - including the connection to inventory management and accounting through the available integrations.

Sources and Studies

This article draws on data and sources from: PYMNTS (Cross-Border Local Currency, 2025), Capital One Shopping (Cross-Border Online Shopping Statistics, 2026), Worldpay (Local Currency Preferences), Baymard (Cart Abandonment Rate Statistics, 2025/2026), Research and Markets (Europe Cross-Border E-Commerce Market), Eurostat (cross-border share in Europe), the EU Commission and VATupdate (OSS scheme and EUR 10,000 threshold), Shopware documentation (currencies and price rounding) and analyses of the left-digit effect by MIT and the University of Chicago. The figures, rates and tax rates mentioned can vary by point in time, market and legal situation and do not replace tax advice.

Showcase

Here is how your international shop could look:

D2C FashionDemo

Fashion & Lifestyle Shop

Multi-LanguageMulti-CurrencyInternationalizationPWA
Corporate WebsiteDemo

Maschinenbau-Unternehmen

Multi-LanguageInternational MarketsResponsiveSEO
Hotel-WebsiteDemo

Luxushotel mit Buchungssystem

Multi-LanguageLocal PricesBookingSEO
Demo

Usually not. Shopware maps several currencies within one shop and assigns them per sales channel. A separate shop per country typically only makes sense with strongly differing ranges, legal entities or brands.

Both are possible. Automatic updates via a rate source reduce effort, manual maintenance gives more control. Experience suggests a defined interval with a small safety margin works well, so rate fluctuations do not cut into the margin.

Because raw rate conversion produces amounts like 107.84. With per-currency rounding configuration or fixed prices per currency you can reach clean price points like 99 or 109.99, which typically convert better.

For B2C distance sales an EU-wide cumulative threshold of EUR 10,000 per year applies (EU Commission). Below it your domestic rate may apply; above it, tax is due in the customer's country - reportable centrally via the OSS scheme. Be sure to coordinate the specific implementation with your tax advisor.

Usually yes. Nearly all cross-border shoppers expect their preferred local payment method (PYMNTS). Local prices and local payment methods belong together - the currency in the storefront and the payment options at checkout should match the target market.

It depends on the range, the number of markets and the tax logic. A basic setup with a few currencies is comparatively quick, while a full international presence with rate maintenance, OSS logic and local payment methods is a plannable project. We are happy to give you an individual assessment.