Skip to content

Insights / The practical edit

Choosing an e-commerce platform: test the work behind the store

Compare e-commerce platforms through real selling tasks, integrations, operating costs and ownership. A practical shortlist process beyond feature checklists.

Back to all insights
Choosing an e-commerce platform: test the work behind the store

A store can look excellent in a demo and be awkward to run every morning. The platform decision should account for the person changing stock, processing a return and answering a customer, as well as the person designing the homepage.

Write the requirements before comparing brands

List your product types, variants, payment methods, shipping rules, markets and integrations. Include any subscriptions, trade pricing or personalised products. Separate requirements for launch from features that might be useful later.

Then describe three ordinary transactions and one awkward one. For example: a standard order, a discounted order, a return and an order containing a product that has just sold out. These become the scenarios you use to assess a shortlist.

Understand the operating model

Hosted platforms such as Shopify combine the storefront software with hosting. WooCommerce offers an open-source approach built on WordPress, with more responsibility for the chosen hosting and extension setup. Both can support substantial stores; the right fit depends on the requirements and the team managing them.

Check the current Shopify plan details and WooCommerce product information directly. Prices, included features and regional payment options change, so a fixed price copied into an old comparison can mislead a buyer.

Compare total operating cost

Build a cost sheet for the first year and a typical later year. Include the plan or hosting, development, paid themes, extensions, payment processing, support, backups and future changes. Ask which costs increase with sales, catalogue size or usage.

A low software price does not mean a low operating cost. Equally, paying for a larger plan does not solve a workflow the platform does not support. Ask suppliers to demonstrate the requirement rather than simply marking it “available”.

Run the same practical test on each option

  • Create a product with the variants and information you actually need.
  • Place an order using an appropriate test payment method.
  • Apply the shipping and discount rules you expect to use.
  • Change stock, cancel an order and process a test refund.
  • Check the customer emails and the mobile checkout.
  • Export products and orders so you understand what you can take with you.

Let the future store manager try these tasks. Record where they need help and where extra software is required. That evidence is more useful than a generic claim about ease of use.

Plan the handover and future changes

Agree who owns the domain, platform account, design files and integration credentials. Document the update and support responsibilities. If you are moving an existing store, plan the product data, customer communication, URL redirects and order history before choosing a launch date.

Finally, check the storefront on a phone and review the speed of product and checkout pages. Use our mobile-first design checklist alongside the operational test. The best platform for your business is the one that supports both the customer journey and the work behind it.

Share this perspective LinkedIn ↗ Facebook ↗ WhatsApp ↗

Have a project in mind?

Let’s talk it through

Ideas worth exploring

A little perspective.

All insights