How to choose · Ecommerce platforms
How to choose an ecommerce platform for your store
Last updated 25 October 2026 · 3 sources listed · Reading time about 4 minutes
Short answer
Choose by matching the platform's strengths to your catalogue shape, sales channels, payment and tax needs and the technical skill you can actually call on. Check how easily you can export products, customers and orders if you leave. A platform that fits your operations as the business grows at a manageable ownership burden beats one with the longest feature list.
Who this is for: A merchant launching or rebuilding an online shop who has to pick storefront software they will live with for years.
What to evaluate
Catalogue complexity
Shops with many variants, bundles, made-to-order options or digital goods strain simple product models. A mismatch leads to workarounds and plugins.
How to check: Model your three trickiest products in each platform's trial and see whether options, stock and pricing behave sensibly.
Payment and tax support
Local payment methods, indirect tax calculation and invoicing formats differ by country, and a shop that cannot offer familiar payment choices loses buyers.
How to check: Confirm the platform supports payment providers and tax settings in each country you sell to.
Channel integration
Selling across marketplaces, social channels and physical locations means stock and orders need to flow into one place.
How to check: List the channels you plan to use and verify there are maintained connectors rather than abandoned third-party plugins.
Customisation and ownership of code
Hosted systems limit how deeply you can change checkout and back-end logic, while self-managed systems hand you freedom and responsibility together.
How to check: Identify the two or three behaviours that make your shop distinctive and ask whether they require code-level access.
Extension ecosystem quality
Add-ons fill gaps but introduce compatibility risk, security exposure and recurring dependencies.
How to check: Review how extensions are vetted, how often they are updated and who supports them when they conflict.
Data portability
Migrating later is far easier when product, customer and order data can be exported in standard formats.
How to check: Test an export of sample data and see if it includes variants, images, redirects and order history.
Support and documentation
A small team will meet problems during sales peaks and needs responsive help and clear guides.
How to check: Read documentation for a task you expect to do often, and learn what support hours and channels exist.
Comparison
| Platform model | Good when | Watch out for |
|---|---|---|
| Hosted all-in-one service | You want to launch quickly with limited technical help and standard checkout behaviour | Limits on deep customisation and dependence on the vendor's roadmap and fee changes |
| Self-hosted open-source software | You need deep control, unusual logic or ownership of the full stack | Responsibility for hosting, updates, security patches and performance |
| Headless commerce architecture | You have developers and want a bespoke front end across several devices | Higher build and maintenance effort and more moving parts to integrate |
| Marketplace-builder or multi-vendor software | You plan to let third-party sellers list on your site | Complexity in payouts, disputes and seller compliance |
| Website builder with shop add-on | Selling is a small part of a broader site for a modest range | Thin inventory, tax and order management as the range grows |
Decision worksheet
Rate up to three options against this guide’s own criteria. It runs in your browser and saves only on this device. It is a thinking aid, not a recommendation.
1. Have you checked each criterion?
0 of 7 criteria checked.
2. Compare options (0 = fails or unknown, 3 = meets it well)
| Criterion | |||
|---|---|---|---|
| Catalogue complexity | |||
| Payment and tax support | |||
| Channel integration | |||
| Customisation and ownership of code | |||
| Extension ecosystem quality | |||
| Data portability | |||
| Support and documentation | |||
| Total (max 21) | 0 | 0 | 0 |
Questions to ask before you commit
- What is the full ongoing cost structure, including transaction charges, apps and payment provider fees, for a typical month of sales?
- How do I export all products, customers, orders and content if I leave?
- Which payment providers and local payment methods are supported in my target countries?
- How does the platform calculate and display sales tax or VAT across the regions I sell to?
- Who is responsible for security, PCI compliance and software updates?
- What happens to my site if an essential extension is discontinued?
- What performance and uptime commitments exist during high-traffic sales events?
- Are there restrictions on the types of goods I can sell?
Typical trade-offs
Pick a hosted service for speed
- Upside
- Faster launch, bundled security and fewer technical chores.
- Downside
- Less freedom to change checkout logic and exposure to the vendor's pricing and policy choices.
Choose self-hosted for control
- Upside
- Complete freedom over features, data and hosting environment.
- Downside
- You or a contractor must maintain updates, backups and performance.
Use many extensions to add features
- Upside
- Quick access to specialised functions without custom development.
- Downside
- Slower pages, conflicts between add-ons and recurring costs that accumulate.
Build a custom storefront on a commerce interface
- Upside
- A distinctive front end and consistent experience across channels.
- Downside
- Ongoing engineering commitment and slower recovery if the developer leaves.
Common mistakes
- Choosing on the demo theme alone. Test the back-office tasks you will repeat daily, such as editing stock, issuing refunds and printing labels.
- Skipping the export test. Discover limitations in data portability before launch, not when you are trying to migrate.
- Underestimating tax and invoicing needs when selling across borders. Confirm what the platform handles and what an accountant must set up.
- Installing extensions for every minor wish. Each one adds a maintenance and security surface, so keep the list short.
- Forgetting mobile shoppers. Check the checkout flow on a phone because many purchases begin and end there.
Related questions
Should a beginner choose a hosted platform or self-hosted software?
A beginner with limited technical capacity usually benefits from a hosted service because hosting, security patches and basic payments are bundled. Self-hosted software suits those with developer access or very particular requirements. The deciding question is who will fix problems at inconvenient times. If the answer is nobody on your team, choose the option that moves that duty to a vendor, while accepting the loss of some flexibility.
How much does the platform affect search visibility?
Platforms differ in how cleanly they output page titles, structured product data, URL patterns and page speed, but content quality and site structure matter more than the brand of software. Search engines publish guidance on product structured data and page experience, so check that your chosen platform can implement it. Poor performance from heavy themes or add-ons can undermine visibility on any system.
Can I switch platforms later without losing sales?
Yes, but it requires planning. You need to move products, customers where permitted, order history and, importantly, redirect old addresses to new ones so search visibility and bookmarks continue to work. Passwords usually cannot be moved in readable form, so customers may need to reset them. Schedule a migration outside peak trading periods and test the checkout thoroughly before switching traffic.
Do I need a developer to run an online shop?
Not for a standard shop on a hosted platform with an off-the-shelf design, where most tasks are configured through menus. A developer becomes useful for integrations with accounting or warehouse systems, custom checkout rules or performance problems. Even then, many merchants hire help for specific projects rather than retaining a full-time engineer.
What does PCI compliance mean for a store owner?
The Payment Card Industry Data Security Standard sets requirements for handling card data. Merchants who use hosted payment pages or tokenised checkouts, where card numbers never touch their server, face a lighter burden than those who process card data directly. Check your payment provider's guidance and the standards council's documentation to learn which self-assessment applies to your set-up.
Sources and further reading
These pages were reachable when we last checked. They informed definitions and rules referred to above; they do not endorse this guide. Where rules differ by country, check the authority for your location.
- PCI Security Standards Council — PCI Security Standards Council, retrieved 27 October 2026
- Search Central documentation — Google, retrieved 27 October 2026
- Web Content Accessibility Guidelines overview — W3C, retrieved 27 October 2026
Related guides
Comparison · Ecommerce platforms
Hosted storefront service versus self-hosted ecommerce software
Hosted services trade flexibility for convenience: updates, security and uptime are the vendor's job. Self-hosted software trades convenience for control: you can alter anything, but you carry maintenance, hosting quality and breach risk. The decision turns on available technical skill, how unusual the business logic is, and how comfortable you are depending on a vendor's pricing and rules.
Problems & fixes · Ecommerce platforms
Why shoppers abandon your online checkout and how to diagnose it
Abandonment usually comes from a handful of friction points: surprise delivery costs, forced account creation, limited payment choices, slow or confusing pages and doubts about trust. Diagnose by walking the checkout on several devices, reading session recordings or funnel step data, and asking abandoning customers directly. Fix one cause at a time so you can see what actually changed behaviour.
Requirements · Ecommerce platforms
Legal and tax requirements for opening an online store
Selling online usually involves registering the business in some form, handling indirect tax such as sales tax or VAT where thresholds apply, publishing trader information and returns terms, protecting personal data and following product safety and advertising rules. Requirements vary significantly by country and by what you sell, so verify with your national authorities and a qualified adviser. This page outlines topics to check, not advice.
Requirements · Logistics and supply chain
Data quality, integration and security requirements for supply chain systems
Supply chain systems depend on clean item and location master data, consistent identifiers, reliable interfaces with partners and appropriate security controls. Requirements include data standards for products and shipments, error handling in integrations, access control, audit logging, backup and recovery. Plan data ownership and monitoring before go-live, since most operational failures trace to bad data or broken interfaces.
How to choose · Consumer electronics
How to choose a laptop for your actual workload
Start from what you do all day, not from component names. Writing, browsing and video calls need a different machine from photo editing, software development or gaming. Then weigh portability, screen and keyboard quality, battery behaviour, repairability and software ecosystem. Memory and storage headroom usually matter more for long-term satisfaction than chasing the fastest processor tier.
Comparison · Online marketplaces
Selling on a marketplace versus running your own online store
A marketplace lends you its audience and trust in exchange for control and a share of every sale. An own store gives control of brand, data and margin but makes you responsible for generating every visitor. Most merchants begin on marketplaces to validate demand, then build an owned channel to capture repeat customers, keeping the marketplace for discovery rather than as the foundation of the business.
How to choose · Business operations
How to choose a supplier and run due diligence
Select suppliers using weighted criteria agreed before looking at quotes: capability, quality, financial stability, security and compliance, delivery reliability, and total cost of ownership. Verify claims with references, site visits or audits and check legal standing and sanctions screening. Document the decision so it can be explained and repeated. Avoid choosing on unit price alone.