Taking an E-Commerce Business International
Your store works in Britain. What changes when the customer doesn’t live here? Not the shipping settings — the expectations. How people pay, how they read, what tax they see, and what happens when they want to send something back.
Does this sound familiar?
Overseas orders arrive, but the checkout was clearly not built for them.
You are quoting in one currency and settling in another, and margin is disappearing between the two.
A market you want uses payment methods your platform has never heard of.
Translating the product descriptions did not produce a store that feels local.
Returns from abroad cost more to handle than the order was worth.
You know which country you want next. You do not know what it will require.
Selling abroad is not a setting you switch on
Most platforms will happily accept an overseas order today. That is not the same as being able to sell in that country, and the difference only becomes visible after the money starts moving.
Each market brings its own expectations about payment, language, currency, tax, delivery, address format, returns, fraud and support. Individually none is hard. Together they decide whether a customer in Riyadh or Shanghai completes a purchase or closes the tab, and a British checkout quietly fails most of those tests without ever reporting an error.
Don’t launch everywhere at once
The most useful advice we give about international e-commerce is usually to do less of it at once. Choose one commercially attractive market and make the whole customer journey work — browsing, paying, delivery, tax, returns and support — before adding a second.
Launching into five countries simultaneously produces five half-finished experiences and no clear read on which market was actually worth the effort. One finished market tells you what the next one costs.
And if your existing platform can already be extended to do this, we would rather extend it than replatform you.
Currency is more than conversion
There is a difference between the currency a customer sees, the currency you settle in, and the rate between them on the day. Display, rounding, pricing strategy and exchange-rate handling are commercial decisions before they are technical ones — a price that converts to 41.37 does not belong on a luxury product page.
Payment is local in a way British merchants routinely underestimate. A market may expect methods your current gateway does not offer at all, and a checkout without the method people trust is a checkout they leave. That is a question about the target market first and your platform second.
Arabic is not translated English
A right-to-left language changes the page, not just the words. Navigation, components, product presentation, form behaviour and the direction the eye travels all move. Running English through translation and switching the text direction produces something that reads as foreign to the people it was meant for.
Behind the storefront, the same applies to operations: stock, warehousing, shipping, duties, returns, order management and CRM all have to work for an order that did not originate here. That is usually where expansion actually stalls, and it is an integration problem rather than a storefront one.
How we approach it
Understand
Start with the market. What does a customer in that country expect at each step?
Decide
Pick one market, and decide what your current platform can be extended to do.
Build
Localise properly — currency, payment, language, tax and the operations behind them.
Move
Launch the one market, measure the whole journey, then use what you learn on the next.
Stay
Run it. Payment methods, tax rules and carrier arrangements all change without asking you.
We’ve solved this before
GINA — luxury footwear
GINA sell luxury footwear from Britain to customers who mostly do not live here. What makes them useful as an example is not the feature list — it is how many decisions had to agree with each other before a single order could complete. Which language, in which reading direction. Which currency to show, and which to settle in. Which payment method a customer in that country actually trusts. What the price should look like once converted. Get any one of those wrong and the others do not save you.
The store runs in English, Arabic and Chinese, detects the visitor’s country and currency, and accepts the payment methods each market actually uses — Apple Pay and PayPal alongside WeChat Pay and Alipay. We built it, and we continue to run it as the markets change.
What this usually involves
International E-Commerce
The detailed capability page: currencies, languages, tax and cross-border operations.
Questions we get asked
Do we need a separate website for each country?
Usually not. One platform with proper localisation is easier to run than several sites that drift apart. Where a market genuinely requires its own presence, that is a specific decision rather than a default.
Can you work with our existing platform?
Often yes. Extending what you have is cheaper and less risky than replatforming, and we would rather establish whether that is possible before proposing anything larger.
Which market should we start with?
The one where you already see demand, or where the commercial case is clearest. We would rather help you finish one market than start four.
What about tax and duties?
They have to be handled in the storefront and in the operations behind it, and the right answer differs by market and by what you sell. It is part of the scope, not an afterthought.
Will you support it once it is live?
Yes. Payment methods, tax rules and carrier arrangements change without consulting you, which is the main reason an international store needs someone running it.
Which market are you trying to reach?
You don’t need to know the technical answer yet. Tell us what is causing the problem. We’ll start there.
Building and running business systems since 2000. The same team that builds it stays to run it.
Start a Conversation