Shopify

Shopify is the right answer when the business wants to sell and not to run infrastructure. The platform takes hosting, security patching and PCI scope off your hands, and charges for it.

Where the money is actually made

Rarely in the theme. In our experience the returns are in the product data, titles written for how people search, correct categorisation, complete attributes, because Shopping results are matched from product data rather than from keywords. A beautiful store with a vague feed is invisible to the searches it should win.

What you trade for not maintaining a server

Shopify removes an entire category of problem: there is no hosting to patch, no core update to schedule, and no plugin conflict that can take the checkout down. What it charges for that is control. The platform decides what the checkout can do, apps carry monthly cost rather than a one-off build, and some requirements simply cannot be met.

That is a good trade for most retailers and a bad one for a few, and the honest version of this conversation happens before the migration rather than after it.

Shopify, in practice

• The app stack audited for cost and overlap, not just for features
• Catalogue and feed quality treated as the performance lever it is
• Theme changes made in a way the client can still edit afterwards

See website development for the build, and Shopify versus WooCommerce for the comparison. Shopify’s developer documentation defines what the platform allows.

How this work usually starts

A Shopify project starts with the app stack and the catalogue, not the theme. Monthly app cost and feed quality between them decide more about what the store earns than any design decision, and both are easier to fix before a redesign than after one.

Two reviews are worth running on any Shopify store before a redesign: what the apps cost each month against what they do, and whether the product feed is good enough for the channels it feeds. Both usually pay for themselves.