Choosing an e-commerce platform for a brand-led store

The platform is the engine behind the store: products, inventory, cart, payments, taxes, orders. It shapes what your team can do every day and what the store can grow into. What the brand looks like is a separate decision, and it should stay yours.

Here we lay out the main architectures and the criteria that matter, so you can compare options against your needs instead of a vendor's demo. It works a lot like choosing a CMS: start from your content, your people and your constraints, then pick the technology.

People often frame it as "Shopify or headless", which mixes up two decisions: which commerce engine you use, and how the storefront is built on top of it. Most major platforms, Shopify included, can work both ways.

Hosted platform with a theme

The platform hosts both the engine and the storefront, and you design and build a custom theme within its templating system. Shopify and BigCommerce work this way; WooCommerce does something similar on top of WordPress, on hosting you manage.

• Strengths: faster to launch, lower running cost, built-in checkout, a large ecosystem of apps, and editing tools merchants already know.
• Limits: you work within the platform's structure. Highly custom experiences, rich editorial content or unusual product logic can run into its walls.

Headless

The commerce engine runs backstage, and a separate front end, often paired with a headless CMS, talks to it through APIs. Shopify offers this through its Storefront API; composable platforms such as commercetools are built for it; enterprise suites like Adobe Commerce and Salesforce Commerce Cloud support it too.

• Strengths: full freedom over design, motion and performance; content and commerce mix freely; one engine can feed several sites, apps or markets.
• Limits: more to build, host and maintain; some platform features and apps don't follow you to a custom front end; you need a team able to run it for the long haul.

The test we use: if you can name something a theme prevents you from doing, and that thing matters to the business, headless may be worth it. If nothing comes to mind, start with a theme.

Catalog and product logic

How many products, variants and options? Do you sell bundles, subscriptions, configurable products, digital licences or rentals? Simple catalogs fit almost anywhere. Unusual logic thins the field fast.

Markets, currencies and languages

Selling in several countries means currencies, taxes, duties, shipping rules and translated content. Check how each platform handles multiple markets and languages natively, and what calls for apps or separate stores. If you sell in English and French, see building bilingual websites.

Integrations

List every system the store must talk to: ERP, inventory, point of sale for a physical shop, product information management, CRM, email, reviews, analytics. In our experience, integrations are where the real complexity, and the real cost, likes to hide.

Content and editing

Who updates the store, and how often? Brand-led stores usually want rich storytelling around their products, so check whether the platform's editor is enough or whether you need a CMS alongside it.

Checkout

Hosted platforms control much of the checkout for security and reliability, and that's often a strength. Confirm what you can customize on the plan you'd actually use.

Total cost over time

Look several years past launch day: subscription, payment and transaction fees, apps, design and development, hosting for any custom front end, upgrades and support. A headless build usually costs more to run, and a theme loaded with paid apps can catch up faster than you'd expect. For overall website budgets, see how much a custom website costs.

Your team after launch

Someone has to run the store every day and keep it healthy. A hosted theme can be managed by a small marketing team with occasional developer help. A headless setup needs ongoing development capacity, in-house or with a partner, to handle platform changes, new features and monitoring. Be honest about who that will be before you fall for the more flexible option.

Ownership and exit

Ask how you would export products, customers and orders if you changed platforms, and who owns the theme or front-end code.

1. Write down your operations: catalog, markets, languages, fulfilment, the systems the store must connect to.
2. Describe the experience you want, and flag the parts a standard theme might not support.
3. Shortlist two or three platforms that fit the operations first.
4. Test the hard parts: your most complex product, a second market, a key integration, an editor publishing a product story.
5. Compare total cost over several years, including who will maintain the store.

Unless a platform is already a given, put these needs in your brief and ask agencies to recommend an approach and justify it. A good recommendation talks about your operations. If it mostly talks about the agency's habits, keep asking. For the design side of the project, read designing online boutiques that sell.

What to do next: list your products' trickiest rules and every system your store must connect to. That one page will narrow the platform choice faster than any feature comparison chart.