How to choose an ecommerce platform.

Do not begin with a platform shortlist

Popular platforms are designed around different assumptions. The right choice depends on what you sell, how customers choose, where you operate, which systems already matter, and who will run the store. Begin with a requirements document and label each item essential, important, optional, or explicitly out of scope.

Document current constraints and a credible near-term roadmap. Planning for every imagined future creates needless complexity, while choosing only for today's smallest catalogue can force an early migration. Use the preparation guide to collect the inputs an ecommerce project needs.

Map the complete buying journey

Describe product types, variants, bundles, subscriptions, personalization, stock states, pricing rules, customer groups, currencies, languages, taxes, delivery regions, returns, and account needs. Then map discovery through search, collections, filters, product comparison, product detail, cart, checkout, payment, confirmation, and post-purchase service.

Test the platform's limits where your business is unusual. A convincing homepage demo says little about complex variants, mixed fulfilment, trade pricing, product data, accessibility, or checkout rules. Use representative products and edge cases in any proof of concept.

Design for the people behind the store

List the systems that create or consume orders, customers, products, prices, stock, tax, fulfilment, returns, support, and marketing data. Decide which system is authoritative for each field and how quickly information must synchronize. An available integration still needs review for direction, failure handling, limits, and ongoing ownership.

Ask intended administrators to add a product, change a collection, prepare a promotion, process a refund, and find an order. Review roles, approvals, audit history, bulk editing, imports, exports, staging, and support. Operational friction repeats every day after launch.

Compare total operating cost and control

Include subscription tiers, transaction fees, payment processing, apps, themes, development, integrations, migration, testing, content entry, training, support, and future upgrades. Usage-based charges may change with orders, markets, storage, traffic, or staff accounts, so record the assumptions behind the estimate.

Understand what can be exported and who owns the domain, account, data, design, code, and licences. Check how extensions are maintained and what happens when the platform changes an API or feature. The ecommerce website cost guide explains the broader project budget.

Use one scorecard and one realistic scenario

• Fit: score each essential requirement with evidence, not sales claims.
• Customer experience: test critical journeys on mobile and desktop.
• Administration: let real operators complete common tasks.
• Integration: confirm data ownership, direction, timing, limits, and recovery.
• Risk: record migration, vendor, security, compliance, and skills dependencies.
• Cost: compare implementation and ongoing operation over a useful planning period.