How to choose an ecommerce platform around your operations

Describe the catalogue in real terms

Count the kinds of product relationships, not only the number of products. Variants, bundles, subscriptions, made-to-order items and trade pricing create different requirements. A hypothetical ceramics shop selling a few finished pieces has a different model from a wholesaler selling packs with customer-specific prices. Use representative products to expose complexity before reviewing storefront templates.

Record what buyers need to compare: dimensions, materials, compatibility, delivery eligibility or availability. Identify where that information currently lives and who can keep it accurate. If product data is scattered across spreadsheets and emails, the platform decision should include a cleanup and ownership plan. Importing inconsistent data into a more capable system does not make it coherent.

Follow an order behind the scenes

Map an order from payment through fulfilment, cancellation and return. Include stock updates, shipping rules, tax handling, invoices and customer communication. Confirm requirements with the people doing the work. A checkout that looks simple may create manual steps when it meets an existing warehouse or accounting process. Those steps belong in the comparison, even if they are not visible to buyers.

For the ceramics example, fragile packaging, limited stock and replacement handling may matter more than elaborate merchandising. For a trade store, account approval and order limits may be essential. Document exceptions such as split shipments and partial refunds. Ask suppliers to demonstrate the actual exception rather than describing the platform as flexible without showing how the work would happen.

Separate standard capability from custom work

For every requirement, label the proposed solution as built in, configured, provided by an extension or custom developed. Record who maintains each part and what happens if it changes or becomes unavailable. Extensions can be appropriate, but a chain of dependencies introduces coordination work. Treat that work as a cost and responsibility, not an invisible implementation detail.

Avoid assuming that a technically possible feature is a sensible first-release feature. A custom product configurator may be unnecessary if a clear selection guide and enquiry flow solve the immediate need. Compare the smaller alternative. Conversely, do not force a complex trade workflow into a consumer checkout simply because the starting subscription appears cheaper. Fit matters more than initial convenience.

Compare the full ownership model

Estimate setup, content migration, recurring services, maintenance and internal training separately. Ask what access the owner receives to products, orders, theme code and integrations. Clarify how data can be exported and what a future move would involve. Costs that depend on usage or third-party services should be described as assumptions to confirm, not fixed promises.

Review who will make routine changes after launch. A platform that needs specialist help for every campaign can be a poor match for a small team with frequent promotions. Another business may prefer that controlled workflow. Discuss approval roles and staging arrangements so operational freedom does not mean unreviewed changes to checkout or pricing in the live store.

Test a representative journey

Use real sample data with permission, or clearly labelled test data, to evaluate discovery, selection, checkout and fulfilment. Include an unavailable variant, a delivery restriction and a return scenario. Test on a phone and with keyboard navigation. Ask both a buyer and a store operator to complete a task, because a platform can suit one group while frustrating the other.

Build a decision record that states the chosen option, alternatives, trade-offs and unresolved dependencies. Where a capability has not been demonstrated, keep it open. A paid discovery or proof-of-concept phase may be appropriate for a risky integration. It is usually easier to change a proposal before migration than to discover an essential workflow is unsupported after orders begin.

Platform selection checklist

• Model representative products, variants and pricing relationships.
• Map fulfilment, refunds, cancellations and unusual orders.
• Identify source data and its ongoing owner.
• Distinguish standard, extension and custom requirements.
• Compare setup and continuing ownership costs.
• Confirm access, export and maintenance responsibilities.
• Test buyer and operator journeys before committing.

A good platform brief explains the business model and the work required to serve it. Bring that brief to a development conversation along with the exceptions, not just a list of attractive reference stores. The final choice should make everyday operations manageable while leaving an honest path for future changes.