Updated September 2026
Introduction
Every major platform can sell to another country. What separates them is whether they can quote duty and tax at checkout, accept the payment methods buyers in that market actually use, serve the right language and currency at the right URL, and handle a return from a country you have no presence in.
Selecting an e commerce platform is a consequential decision for online retailers. The right ecommerce solution scales with business growth, integrates with systems, and delivers shopping experience without engineering overhead. Businesses seeking to launch an online store, expand online sales, or move to online selling need clear guidance. This guide evaluates solutions across architecture, cost, and operational reality, from online stores to ecommerce marketplaces and full online stores.
Start from the markets rather than the shortlist. The platform is the last decision in this sequence, not the first, and treating it as the first is what makes it expensive.
Quick Shortlist: Best eCommerce Solutions
Clarity Ventures builds custom ecommerce sites integrated with enterprise systems, avoiding hosted constraints. Businesses needing multiple brands, legacy ERP, or custom workflows require ownership and flexibility off-the-shelf cannot match. For current site migration or launching ecommerce websites with features and advanced features, Clarity builds online stores integrating processing, shipping, and inventory management without lock-in. The platform supports SaaS alternatives for retailers seeking online store ownership.
Key vendor options across buyer profiles include leading e commerce platforms and ecommerce solutions for different scales:
- Clarity Ventures - Custom web store for ERP connectivity and operational control
- Shopify Plus - Hosted e commerce platforms with scaling and payment gateways
- Adobe Commerce - Self hosted ecommerce solution for customization and responsive themes
- WooCommerce - WordPress plugin with builder for current site
- BigCommerce - Mid-market SaaS with strong SEO and scalable solution
- Headless Ecommerce - Decoupled architecture for multi-platform storefronts
What actually changes when you sell across borders
A domestic store and a cross-border one look identical and are not the same system. Five things change, and each of them constrains which platforms are genuinely available to you.
Tax and duty, which is the one that hurts
Domestically you charge one tax at one rate. Cross-border you are dealing with import VAT, customs duty and thresholds that differ per destination. Two acronyms carry most of the weight in Europe: IOSS lets you collect VAT at checkout on consignments under €150 and remit it through a single registration, rather than leaving the buyer to pay it at the door. OSS covers distance selling within the EU once you are registered there. Above that threshold, or outside the EU, duty enters and the question becomes whether you quote delivered duty paid or delivered duty unpaid.
That choice is the single largest determinant of whether a first international market succeeds. DDP means you calculate duty and tax at checkout and the customer pays once. DDU means they get an unexpected invoice from the courier before delivery, and a meaningful share simply refuse the parcel, at which point you pay outbound shipping, return shipping and the refund, on an order that generated nothing. A platform that cannot compute landed cost at checkout is choosing DDU for you.
Payment methods, which are local
Card penetration is a British and American assumption. Buyers in the Netherlands expect iDEAL, in Brazil Pix and instalments, in India UPI, in Germany bank transfer or payment on invoice, in China Alipay or WeChat Pay. Offering cards alone in those markets does not reduce conversion slightly. It removes most of the market. The platform question is which local methods its payment integrations reach, and whether you can settle in the currency you sell in or are taking an FX spread on every order.
Language, currency and where each lives
Serving a translated page is the easy part. The structural decision is where international versions live: separate country domains, subdomains, or subfolders on one domain. Subfolders concentrate authority and are usually right for a business with one brand. Country domains suit businesses with genuinely separate operations and split your SEO effort several ways. Whichever you choose, hreflang annotations tell search engines which version belongs to which market, and getting them wrong is a common and quiet way to have the wrong page rank in the wrong country. Currency display matters too: showing a converted price is not the same as charging in local currency, and buyers notice at checkout.
Shipping, and the returns nobody plans
Rates by zone, carrier coverage that varies enormously by destination, and delivery estimates that have to account for customs clearance rather than transit time alone. Returns are the part that gets skipped: a customer in another country needs somewhere to send an item back to, and paying international return postage on a modest order usually costs more than the item. The workable answers are a returns address in-market through a third-party logistics provider, or a policy that refunds without requiring the return on low-value goods, and both need deciding before launch rather than after the first request.
Compliance that follows the customer
Selling into a market brings its rules with it. GDPR applies to EU customers regardless of where you are established, which affects consent, data handling and sometimes where data may be stored. Extended producer responsibility schemes for packaging and electricals require registration in several EU countries before you may sell there at all. Product rules vary: cosmetics, electricals, food and children's goods each carry their own labelling and registration requirements. None of this is a platform feature, and all of it is a reason the platform decision is smaller than it looks.
Choose the platform last. Establish which markets, under which tax treatment, with which payment methods, and the shortlist narrows itself.
None of these five are things a platform demo will raise with you. All five decide whether the market works.
Duty is the one to settle first. Every other decision on this page is easier once you know whether the customer pays at checkout or at the door.
If it cannot, you are shipping delivered-duty-unpaid whether you decided to or not, and a share of your parcels will be refused at the door. We build landed-cost integration into the checkout.
Fraud, which behaves differently across a border
Cross-border fraud behaves differently from domestic fraud and most fraud tooling is tuned for the domestic case. Address verification is the clearest example: the checks that compare a billing postcode against the card issuer's records work in the US and UK and return nothing useful across much of Europe and Asia, so a rule that declines on a failed address check will decline a large share of perfectly good international orders. Chargeback rates run higher on cross-border transactions, partly through genuine fraud and substantially through customers not recognising a foreign merchant name on a statement. Two practical mitigations cost little: use a descriptor the customer will recognise from your storefront rather than your legal entity, and review your decline rules per market rather than globally, because the same rule set produces very different outcomes in Amsterdam and Atlanta.
Pricing per market, not converting from home
Showing a converted price is not the same as setting one, and the difference is worth money. A converted price produces figures nobody would choose: a £49 product becomes €57.34, which reads as an import rather than a local offer and loses the psychological rounding that domestic pricing takes for granted. Setting a local price per market lets you round sensibly, absorb or pass on the duty and shipping differential deliberately, and price against local competitors rather than against your own home market. It also decouples you from daily exchange-rate movement, which otherwise means your prices change without anyone deciding they should. The cost is that somebody now owns a price list per market, and that is a real operational commitment rather than a setting.
Check whether your platform can hold a genuine price per market or only a conversion rate. It is a small question with a large consequence, and it belongs on the shortlist criteria rather than being discovered afterwards.
What Defines the Best eCommerce Solutions
Platform Fit over Feature Count
Best ecommerce solutions match capacity with requirements, not feature count. Technical capacity, integration requirements, and timeline determine fit. Many mid-market businesses find self hosted solutions offer better control and lower total cost than vendor platforms. Small e commerce businesses and small business owners often overestimate customization needs. A website builder with builder functionality typically suffices for basic online shopping. Reliable features and premium features matter less than essential features and built in features aligned with actual operational needs.
Three Core Decision Factors
Three core factors determine selection: Architecture, operational overhead, and vendor integration. Architecture determines ownership vs. licensing. Operational overhead reflects maintenance costs. Vendor integration determines whether solution connects existing systems. Key considerations include payment gateways, advanced features, flexible theme options, customization options, and SEO tools alignment. Some platforms offer complete features, others specialize.
Comparison Table: E Commerce and Adobe Commerce eCommerce Marketplaces
| Platform | Architecture | Best Fit | Strength | Critical Tradeoff | Hosting |
|---|---|---|---|---|---|
| Clarity Ventures | Custom-built | Business needing ERP | Ownership, workflows, integration | Development required | Self hosted |
| Shopify Plus | Hosted SaaS | High-volume D2C brands | Scaling, compliance, support | Lock-in, limits | Fully hosted |
| Adobe Commerce | Self hosted | Enterprise | Customization, ownership | Learning curve, burden | Self hosted |
| WooCommerce | Plugin-based | Small retailers on sites | Cost, integration, ecosystem | Performance | Self hosted |
| BigCommerce | Hosted SaaS | Mid-market | SEO, API, B2B | Flexibility | Fully hosted |
Shopify Plus: Hosted eCommerce for Scaling Brands
Shopify Plus serves high-volume D2C ecommerce websites and online stores for scaling. Platform handles traffic, supports currencies and methods, includes compliance. Mid-market retailers launch web store in weeks using themes and apps. Drag and drop builder simplifies setup while remaining intuitive for those without advanced technical backgrounds. SaaS platform features include all essentials.
International expansion requires currency conversion, multi-region fulfillment, localized checkout. Brand retailers appreciate managed infrastructure. Shopify includes payment gateways, themes, and commerce integrations.
Strengths: Rapid deployment, uptime, large ecosystem, support.
Limitations: Vendor lock-in, steep custom costs, limited core logic change, monthly fees scale poorly.
Pricing: Starting $2,300/month plus 1.6-2.0% transaction fees, up to $50K-$150K custom builds.
Magento: Self Hosted Enterprise
Magento (formerly Magento) is the standard for self hosted infrastructure and maximum customization. Platform offers depth for enterprises needing scale and optimization. Supports products and gateways.
Learning curve steep, requires knowledge and developers. Maintenance and infrastructure fall to teams. Works for enterprises with staff and budgets.
Strengths: Complete customization, platform ownership, no limits, mature ecosystem.
Limitations: Steep learning, high maintenance.
Pricing: $18K-$55K annually licensing, $5K-$25K hosting, $200K+ development.
WooCommerce: for an Existing WordPress Site
WooCommerce suits small online retailers, small business owners, and medium sized businesses on WordPress sites seeking to sell online. Free to install, integrates natively, enables basic ecommerce. Retail businesses selling 50-500 SKUs find WooCommerce fastest path to web store or ecommerce website. WordPress users appreciate builder for ease of setup.
Simplicity brings limits. WordPress lacks optimization, creating ceilings as catalogs grow. Scale eventually requires dedicated migration. Plugin ecosystem limits features. Gateways rely on extensions.
Strengths: Zero cost, WordPress integration, large ecosystem, basic online shopping support.
Limitations: Performance degradation at scale, limited advanced features, WordPress plugin lock-in.
Pricing: Free software, hosting, security, optimization cost $200-$1,000/month for small operations.
BigCommerce: SaaS with Built in SEO Tools
BigCommerce bridges simplicity and enterprise for medium businesses. Fully hosted SaaS with SEO tools, strong API support, B2B capabilities. Mid-market retailers seeking a web store, ecommerce website gain better SEO and API flexibility than Shopify without complexity. Supports gateways, inventory management, and scalable ecommerce solution.
SEO features are first-class. Complete API enables headless. International support includes multi-currency, multi-language, multi-storefront. Responsive themes and builder enable efficient setup. Advanced features include processing, shipping, products.
Strengths: Strong SEO, complete API, B2B, managed hosting, key features.
Limitations: Smaller ecosystem than Shopify, moderate lock-in, processing fees.
Pricing: $29.99/month basic, $299+/month mid-market. Transaction fees 0-1.0%.
Headless eCommerce for Growing eCommerce Businesses
Marketplaces and Digital Products
Ecommerce marketplaces and platforms selling downloadable items gain speed from headless. Multi-vendor ecommerce marketplaces and digital products catalogs benefit from flexible frontends that adapt per channel. Ecommerce businesses also run distinct experiences for mobile apps and social channels through a single backend API layer.
Custom API Architecture
Headless e commerce inverts platform models. Merchants buy commerce engine for products/orders, then build custom storefronts using modern frameworks. This unlocks creative freedom and enables omnichannel retail for open source architectures.
Headless works for brands running storefronts across web, iOS, Android unable to maintain separate instances. Downside: Cost and complexity. Hosted cannot support true headless. Open source ecommerce platform solutions separate head and engine. Most solutions blend head and commerce, limiting customization.
Strengths: Complete front-end freedom, omnichannel, no lock-in at storefront layer, digital products support.
Limitations: Requires engineering team, technical knowledge, higher upfront cost.
Pricing: Engine licensing $500-$5K/month plus $100K-$300K+ front-end development.
Headless buys you complete control of the experience and hands back every cross-border decision on this page as something you now have to design, build and maintain yourself.
The same platforms, compared on what crossing a border needs
The comparison earlier in this guide ranks these platforms on architecture and fit. This one ranks them on the five things above, which is a different ordering and the one that matters once a border is involved.
| Platform | Duty & tax at checkout | Local payment methods | Multi-store / locale | Where it strains |
|---|---|---|---|---|
Shopify Plus | Native via Markets, or an app | Broad through its own payments and gateways | Markets handles domains, currency and language | Less room to change checkout where a market needs something unusual |
BigCommerce | Through a tax provider integration | Wide gateway support, fewer native local methods | Multi-storefront on one account | Storefront count and API limits on lower tiers |
Adobe Commerce | Configurable, and configuring it is a project | Whatever you integrate | Strong native multi-store and multi-locale | Cost and the operational burden of running it |
WooCommerce | Plugin-dependent | Plugin-dependent | Multisite, with effort | Plugin interactions multiply with each market added |
Headless / custom | Whatever you build or buy | Whatever you integrate | Entirely yours to design | You own every one of these decisions permanently |
Notice that the honest answer in most rows is an integration rather than a feature. Landed-cost calculation, tax registration and local payment methods are bought from specialists and connected, on every platform here. What differs is how much of that connecting the platform has already done.
Buy the landed-cost and tax service on any of these platforms. The question is only how much connecting it will take.
Compare these rows against the markets you are actually opening. Four of the five matter differently in every destination you add.
Key Considerations for the Best eCommerce Platform Selection
Merchants comparing ecommerce platforms and other solutions often fixate on feature lists without evaluating integration depth, processing, and scalability. These drive outcomes and ability to lift revenue. many ecommerce platforms claim comprehensiveness but deliver narrow functionality.
Integration Depth is critical. Platform claiming 50 gateways may offer shallow syncing. Best solutions build integrations into architecture. Clarity and Magento excel. Integration works from start. Evaluate shipping, inventory sync, customer data integration. Add advanced features requires integration. User friendly interface demands clean API.
Payment Processing drives customer experience and cash flow. Hosted abstract processing (convenient, inflexible). Self hosted offer control but require PCI. Key: Fees, gateways, reconciliation. Can platform sync transactions automatically?
Operational Scalability measures logic platforms handle. $50K/month store handle 10K SKUs, 50 customers. At scale, SKU counts reach 100K+. Small platforms hit limits fast. Enterprise platforms feel overcomplex for small merchants. Consider brand support, products, whether features scale with growth.
Weight these against the markets you are actually opening, not against a generic scorecard.
Payment Costs and Transaction Fees
Payment processing costs remain opaque in selection. Hosted bundle into fees. Transaction fees range 1.6-2.5% per plan. Self hosted shift gateway selection. Understanding costs essential. Many charge hidden fees.
Payment Gateways and Methods
Credit card processing is baseline. Real cost driver: Payment method diversity. Wallets (Apple Pay, Google Pay), buy-now-pay-later (Klarna, Afterpay), regional methods (Alipay, WeChat) carry different fees and integration complexity. Global e commerce platform must support 30+ payment methods. Evaluate payment gateways carefully, premium options offer more integrations at higher transaction costs. Some include free SSL certification, verify cost impact.
Hidden Costs
Fixed transaction fees, monthly gateway fees, refund processing accumulate. Mid-market e commerce website processing $2M annually spends $60K-$100K on processing alone. Best solutions track payment costs transparently. Compare monthly fees across vendors for full financial impact on online sales.
Scalability and Tech Stack
Ecommerce platforms have technical ceilings. Hosted platforms auto-scale but impose constraints. Self hosted shift scaling responsibility but offer flexibility. A true scalable solution adjusts to growth without replatforming. Evaluate whether platform supports startup-to-enterprise growth. Most fail at revenue or SKU thresholds.
Tech Stack Impact
Platform tech stack determines scale viability more than merchants realize. Database, language, framework optimization matters. WordPress (PHP) hits walls at 10K products. Magento scales further with configuration. Poor tech stack becomes expensive pain.
Headless Scalability
Headless unlocks scaling because commerce engine and storefront scale independently. Benefit requires engineering teams with headless expertise. Many hosted platforms claim headless but deliver weak separation.
How to open the first market without learning everything at once
Open one market, properly, and measure it for a full quarter before opening another. Simultaneous launches multiply every unresolved question and make it impossible to tell which market is actually working.
Pick the market from evidence you already have
The best first market is usually one already sending you traffic and the occasional order despite you doing nothing to earn it. That is demand you can see rather than forecast. Check three things before committing: how many orders and how much traffic that country already produces, what search demand for your category looks like in its language rather than in English, and what shipping actually costs against your average order value. A market where delivery costs a third of the basket is a market that needs a higher-value product mix before it needs a platform decision. Proximity and shared language reduce the number of new problems you take on at once, which is why so many UK businesses start with Ireland and the Netherlands rather than with the largest opportunity on the map.
Decide the unglamorous things before the storefront
Four decisions, all of which are easier before launch than after. How duty and import tax will be handled, which for most businesses should be at checkout. Which local payment methods you will accept, checked against what that market actually uses rather than what your gateway offers by default. Where returns will physically go. And which pages get translated first, which should be the ones carrying the decision, product, checkout, shipping and returns, rather than the blog. None of these are platform features and all of them constrain the platform choice, which is why they come first.
Measure the things that fail late
Cross-border problems surface weeks after the order, so the launch dashboard has to look further than checkout. Watch refused and undelivered parcels, which is where a duty problem shows up. Watch the return rate for that market against your domestic baseline. Watch payment failure and abandonment at the payment step specifically, since that is where a missing local method appears. And watch delivery time to the customer rather than time to the carrier, because customs clearance sits between the two and is invisible in shipping reports.
Sequential beats simultaneous every time. Opening one market and measuring it properly is the only way to learn anything that transfers to the next one you open.
One market, one quarter, one honest read of the numbers. Then decide whether the second one is worth opening at all.
The launch that was refused at the door
Cross-border launches rarely fail on the storefront. They fail somewhere between the checkout price and the doorstep.
A UK skincare brand opens three EU markets
Average order around £45, mostly single items, sold direct to consumers. The site was already performing well domestically.
The platform decision took six weeks
Shortlists, demos, a comparison spreadsheet. The chosen platform was perfectly capable and the storefront launched in three languages on time.
What was not decided
Whether duty and import VAT would be collected at checkout. Nobody owned the question, so the default applied: prices showed ex-duty and the courier collected on delivery.
First market, the orders arrived
Traffic and conversion were encouraging. On paper the launch was working, and the team opened the second and third markets on that basis.
Then the parcels came back
Customers received a courier demand for VAT plus a handling fee, often £12 to £15 on a £45 order. Roughly one in five refused the parcel. Each refusal cost outbound postage, return postage and the refund, and produced an angry email.
Why the dashboard looked fine
Revenue was reported at checkout, and refusals landed weeks later as returns against no particular market. It took a quarter before anyone connected the return rate to the tax treatment rather than to the product.
The fix, and what it cost
IOSS registration, a landed-cost integration quoting duty and VAT at checkout, and prices shown inclusive. Refusals fell to near zero within weeks. The work took about three weeks and would have taken the same three weeks before launch, without the refused parcels or the reviews.
The platform was never the problem. A decision nobody made was, and it was made by default in the platform's favour.
Ask who owns the duty decision before anyone opens a platform demo. If the answer is nobody, that is the finding.
Decision Checklist (CTA)
Work through this list to eliminate unsuitable platforms:
- Support all required payment methods?
- Integration work without custom middleware?
- Pricing align with revenue trajectory?
- Engineering resources for self hosted?
- Platform handle expected catalog load?
- Support current business model?
- Checkout customizable for brand?
- Transparent reporting?
Contact Clarity Ventures for platform assessment ensuring solution fits requirements.
Pricing Reality
Platform licensing rarely represents largest ecommerce implementation cost. Integration, customization, training, and maintenance drive costs. A solution priced $2K/month may cost $50K+ first-year integration. Monthly fees for basic plans hide premium feature costs once sales scale.
Hosted SaaS frontloads convenience with fast setup and low overhead. But monthly recurring costs plus transaction and processing fees accumulate. $100K/month store on Shopify Plus might pay $5K-$8K monthly total on monthly plan with processing fees. Acceptable for small business, prohibitive at scale.
Self hosted frontloads development cost. Magento or Clarity build costs $100K-$300K upfront, then $15K-$50K annually. Economical above $2M-$5M annual revenue. Below that, SaaS cheaper. Match platform cost structure to revenue and goals.
Add tax registrations, translation and returns to any platform quote before comparing. They are the larger numbers.
Common Mistakes
Merchants often repeat platform selection mistakes when building ecommerce store or choosing other platforms. Assuming more features equals better fit leads to overspecification. Essential features often suffice. Ignoring total cost of ownership (integration, customization, processing exceed licensing 3-5x) hides true cost. Overestimating customization needs creates expensive builds unnecessary with out-of-box features. Underestimating timelines (months, not weeks) creates disruption. Vendor pitches over peer implementations miss deployment realities. Failing to test digital marketing and social commerce support. Neglecting inventory management, shipping integrations, payment gateways stress tests. Community support when technical expertise required.
The costliest mistakes here are decisions nobody made, which get made by default in the platform's favour.
Deep Dive: the Best eCommerce Platform for Each Business Size and eCommerce Websites Need
The best ecommerce platform for a merchant depends on stage, tech stack maturity, and growth plan. A small business launching an online store for the first time wants a website builder with a drag and drop builder, built-in features, a free ssl certificate, and predictable recurring costs. Medium businesses and medium sized businesses running multiple brands usually need an ecommerce platform with deeper payment processing, shipping integrations, and inventory management across channels. Large enterprises and businesses seeking maximum control evaluate self hosted solutions, self hosted platforms, or a scalable solution built on a custom tech stack.
Online Store and Web Store Fit
An online store optimized for online selling requires more than a storefront template. The website builder must support custom domain setup, responsive themes, customization options, and a user friendly interface that new store design hires can manage without technical knowledge. For retailers running a web store or complete online store, the best ecommerce platform bundles a store setup wizard, premium features for email and social commerce, and a wordpress plugin or saas platform option depending on the current website footprint.
eCommerce Store, eCommerce Site, and E Commerce Platforms Compared
Any serious ecommerce store today must compare hosted ecommerce platforms, open source ecommerce platform options, and bespoke e commerce platforms side by side. The best ecommerce platform for WordPress users is usually WooCommerce layered onto an existing wordpress site. The best ecommerce platform for large enterprises is an enterprise-grade self hosted or custom stack. Key features to weigh on any ecommerce site include payment gateways, processing fees, transaction fees, community support, and customizable themes. Each ecommerce website and web store also benefits from built in features for SEO, reviews, and analytics that drive sales without plugin sprawl. Evaluating ecommerce solution options for the modern ecommerce solution landscape means weighing every ecommerce solution against every other ecommerce solution on price, flexibility, and lock-in. A mature ecommerce solution absorbs growth without replatforming. The best ecommerce solution pairs strong e commerce platforms infrastructure with a website builder that non-technical staff can operate. E commerce platforms that bundle a website builder with a full e commerce platforms catalog often deliver the fastest key features coverage for small and mid-market teams.
Practical Selection Tips
Most ecommerce platforms publish pricing for a monthly plan with essential features, add advanced features at higher tiers, and offer premium features only on enterprise contracts. Businesses seeking the best ecommerce platform should evaluate ecommerce marketplaces integration, ecommerce websites speed on mobile, online sales tracking, online shopping UX on the ecommerce store, existing site migration paths, and ecommerce business model fit. current website owners already running an ecommerce site can often extend rather than replace, preserving SEO equity on the existing site.
Frequently asked questions
What is the best eCommerce platform for international expansion?
There is no single answer, and the honest version is that the platform matters less than the decisions around it. Shopify Plus is the fastest route if its Markets feature covers your destinations. Adobe Commerce suits businesses with genuinely complex multi-country operations and the team to run it. BigCommerce sits between them. WooCommerce works where the store is an extension of an existing WordPress site.
The question that actually narrows the list is which markets, under which tax treatment, with which payment methods. Answer those first and the shortlist tends to produce itself.
On specific platforms: Shopify Plus and BigCommerce both offer multi-currency, multi-language and multi-region out of the box. Adobe Commerce supports global retail but through custom development rather than configuration.
What is the difference between DDP and DDU, and which should I use?
Delivered duty paid means you calculate duty and import tax at checkout and the customer pays one price. Delivered duty unpaid means the courier collects it before delivery, and the customer gets an unexpected bill plus a handling fee.
Use DDP wherever you can. DDU is the most common reason a first overseas market disappoints: a meaningful share of customers refuse the parcel, and you pay outbound shipping, return shipping and the refund on an order that earned nothing. A platform that cannot quote landed cost at checkout is choosing DDU on your behalf.
What are IOSS and OSS?
Two EU VAT schemes. IOSS, the Import One-Stop Shop, lets a seller outside the EU collect VAT at checkout on consignments under €150 and remit it through a single registration rather than registering in every member state. OSS, the One-Stop Shop, does the equivalent for distance selling within the EU once you are established there.
Both exist to stop you needing twenty-seven registrations, and both are what make charging tax at checkout practical. Take proper advice for your own circumstances. This is an area where the detail matters and changes.
Do I need a separate website for each country?
Usually not. The three options are country domains, subdomains, or subfolders on one domain, and subfolders are right for most businesses because they concentrate authority on one site rather than splitting your SEO effort several ways. Country domains suit businesses with genuinely separate operations, legal entities or brands per market. Whichever you choose, hreflang annotations are what tell search engines which version belongs to which market, and they are easy to get subtly wrong.
Which payment methods do I actually need?
Whichever the buyers in your target market use, which is frequently not cards. iDEAL in the Netherlands, Pix and instalments in Brazil, UPI in India, bank transfer or invoice in Germany, Alipay and WeChat Pay in China. Offering cards alone in those markets does not cost you a little conversion. It removes most of the market.
Check what your platform's payment integrations reach in each destination before committing, and check whether you can settle in the currency you sell in or are paying an FX spread on every order.
How do returns work from another country?
Badly, unless you have decided in advance. International return postage on a modest order often costs more than the item, so asking the customer to pay it produces complaints and asking yourself to pay it erodes the margin that justified the market.
The two workable answers are a returns address in-market through a third-party logistics provider, which consolidates and ships back in bulk, or refunding low-value items without requiring the return at all. Decide which before launch, because the first request will arrive within days.
Does GDPR apply if my business is not in the EU?
Yes, if you are offering goods or services to people in the EU. It follows the customer rather than the seller, and it affects consent, how you handle personal data and sometimes where that data may be stored. It applies from your first EU order rather than at some threshold, so it belongs in the launch plan rather than in a later compliance review.
Can I just use a marketplace instead of building a store?
Often yes, and for a first overseas market it is frequently the sensible test. A marketplace brings existing demand, handles much of the tax and logistics complexity, and tells you whether the market wants your product before you invest in a storefront for it. What you give up is the customer relationship, the margin and control of the experience. Many businesses do both: a marketplace to validate, a store to build on.
How much does going international add to platform cost?
Less than the surrounding services do, which surprises people. The platform may charge for additional storefronts or a higher tier, and that is usually modest. The recurring costs that matter are the landed-cost and tax service, tax registrations and filings per jurisdiction, translation and its maintenance, and international shipping and returns. Budget those before comparing platform pricing, because they change which platform is affordable more than the licence fee does.
What is the most common mistake?
Treating it as a platform project. The storefront is the visible part and rarely the constraint. Tax treatment, payment methods and returns are, and they get decided late or by default. The second most common is opening several markets at once, which multiplies every unresolved question and makes it impossible to tell which market is working.
Should I translate the site or is English enough?
It depends on the market rather than on principle. English performs acceptably in the Nordics and the Netherlands and poorly in France, Italy, Spain, Japan and much of Latin America. The pragmatic sequence is to translate the pages that carry the decision first, product, checkout, shipping and returns, and leave the long-tail content until the market proves itself. Machine translation of a checkout is a false economy. That is the page where confusion costs you the order.
How do I know a market is worth opening?
Look for evidence before you invest. Existing international traffic and orders you are already receiving from that country, search demand for your category in its language, and what shipping actually costs against your average order value. Then open one market, properly, and measure it for a full quarter before opening another. Sequential beats simultaneous here, because it is the only way to learn anything transferable.
What is the fastest eCommerce platform to deploy?
Hosted platforms are measured in days for a basic store: Shopify and BigCommerce will both have you selling quickly. Shopify Plus typically takes four to eight weeks once the implementation is real rather than a trial. Self-hosted platforms run two to six months. If you already have a WordPress site, WooCommerce is the fastest route to adding a store to it.
Those are build times, not launch times for a new market. Tax registration and payment setup run in parallel and frequently take longer than the storefront.
What does it cost to build an eCommerce platform?
Licensing runs from free with WooCommerce to $50K or more annually for Adobe Commerce. On top of that, budget design at $20K to $100K, integration at $10K to $100K, and maintenance at $5K to $50K a year. In total, small sites land around $30K to $80K and enterprise builds at $200K to $500K and upward.
Transaction costs frequently exceed licensing, and they are the line most often left out of the comparison because they scale with success rather than appearing on the quote.
How do I know if I am overspending on a platform?
A workable rule of thumb: if total platform cost - fees, transaction costs, development and maintenance together - exceeds 3% to 5% of gross revenue annually, the platform is over-specified for the business running on it. The other signal is integration that requires continuous external consulting, which quietly consumes the budget that was meant for growth.
Read the figure against your own margin rather than as an absolute. A business running at 60% gross margin can carry a platform cost that would sink one running at 15%, and the same percentage means very different things at £500K and £50M of revenue. The number is useful as a prompt to check rather than as a threshold to obey: if you have never added the four components together, the exercise itself usually tells you more than the ratio does.
Can we migrate between platforms later?
Yes, but it is expensive and carries real risk. Data exports cleanly, custom logic rarely transfers, and every integration has to be reconfigured against the new platform. Budget two to six months and $50K to $150K for a migration of any substance.
The cost is a reason to choose deliberately rather than a reason never to move. It is also an argument for keeping your data exportable and your integrations loosely coupled from the start.
What makes it expensive is worth knowing in advance, because a replatform is a data project wearing a software project's clothes. Products, variants, customers, order history and content all have to move, and they rarely map cleanly because the two systems disagree about what a product is. Order history is the part underestimated most: it is needed for returns, warranties and accounting, it is usually large, and it often cannot be expressed in the destination's schema at all. Budget for reconciliation rather than transfer, and build the redirect map before launch rather than after.
Do we need headless architecture?
Only when you are genuinely running several storefronts - web, iOS, Android, social, marketplace - and cannot maintain separate instances of each. Most businesses find hosted solutions faster, cheaper and simpler, and most modern platforms provide enough omnichannel capability without going fully headless.
Going headless for international specifically is rarely the reason. Multi-locale and multi-currency are features the major platforms already have.
Related reading
About the author
Autumn Spriggle Content Writer, Clarity Ventures Autumn Spriggle is a Content Writer and Digital Marketing Associate at Clarity Ventures with key insight into eCommerce technology, business, and related topics. She stays up-to-date on the latest trends to help people like you realize the full potential for their business. More articles
Clarity builds stores that can quote duty at checkout and settle in the currency you sell in.
Landed-cost and tax integration, local payment methods, multi-locale storefronts and the ERP connection that keeps it all reconciled. We have been building and integrating commerce systems since 2007. Tell us which markets you are opening and how you intend to handle duty.