WordPress vs Shopify vs headless: picking a platform without regret

Platform debates go wrong because they start with the technology. Start with a one-page requirements list instead. Answer each of these honestly before you compare anything.

• Revenue model. Physical products, digital products, subscriptions, services, leads, or a mix. Rank them by expected share of revenue over the next three years.
• Catalog shape. How many SKUs, how many variants per product, how often prices and inventory change, and whether you sell wholesale or B2B with custom pricing.
• Content load. How many pages, how often they change, who edits them, and whether editors are marketers or developers.
• Integrations. ERP, accounting, CRM, email and SMS platforms, fulfillment, point of sale, marketplaces. List what exists today and what is planned.
• Compliance. Sales tax across states, ADA accessibility expectations, data privacy obligations under state laws such as California's, and any industry-specific rules.
• Team. Who maintains the site after launch, and whether you employ or retain developers.
• Budget horizon. Build budget and the recurring monthly budget you can sustain for three years.

A platform decision made against this list is defensible. One made without it is a guess.

WordPress is a content system with a commerce plugin available. It excels at editorial flexibility, SEO control, custom page layouts and lead capture. It runs on hosting you choose, which means you own performance, security and updates. With WooCommerce it handles moderate catalogs well, and it is the natural fit for publishers, professional services, B2B lead generation and brands whose site is mostly storytelling with a small shop attached.

Shopify is a commerce system with a content layer attached. Checkout, payments, fraud screening, US sales tax calculation, shipping labels and inventory are solved problems on day one. The platform handles traffic spikes, PCI scope and uptime so you do not have to. Its weakness is editorial depth: complex content pages, custom data structures and unusual URL patterns take more effort than on WordPress, and some SEO details are constrained by the platform.

Headless separates the front end from the systems behind it. A commerce backend (often Shopify itself), a content system and a custom front end built in a modern framework. It can deliver excellent performance, true multi-channel delivery and complete design freedom. The cost is that you now own the integration between every piece, every preview workflow, every search feature and every bug. Nothing comes for free in the admin because there is no single admin.

Numbers vary by market and scope, but these ranges are realistic for a professionally built site in the US, starting from a small template-based scope at the low end and growing with custom design and integrations.

Monthly run cost includes hosting or platform fees, essential apps or plugins, maintenance and security. It does not include marketing, content or payment processing fees. Payment processing is often the hidden variable: Shopify's rates differ depending on whether you use its native payments, and WooCommerce stores pay whatever their gateway charges plus plugin costs.

Headless build figures look alarming until you compare them to what you would otherwise spend on custom work inside the other two platforms. If your WordPress or Shopify build already has a six-figure custom development line item, headless may not be more expensive. If it does not, headless almost certainly is.

Use these as tiebreakers once the requirements list is done.

1. If more than 60 percent of revenue is product sales, start with Shopify. The operational savings on tax, fraud, checkout and inventory are worth more than any editorial inconvenience.
2. If the site is mostly content and leads, start with WordPress. Add commerce later if it earns its place.
3. If you need both at equal weight, pick the one that matches your team. A marketing team without developers will be happier on Shopify with a strong theme. A team with WordPress experience and a developer on retainer can make WooCommerce work.
4. Go headless only if you can name the specific requirement it solves. A performance target no theme can reach, multiple storefronts sharing one backend, a native app sharing content, or a design that cannot live inside a theme. If the reason is "it is more modern," stop.
5. Never choose a platform because an agency only builds on one. Ask what they would recommend if they could build anything, and listen for whether they ask about your business first.

Rebuilds within two years are common and almost always avoidable.

Choosing for the launch, not the third year. The site that is perfect for ten products is painful at five hundred. Model where the catalog and traffic will be in 36 months.

Underestimating integrations. A platform that does everything except talk to your ERP will cost more in manual work than the difference between any two platforms. Confirm every integration exists and is maintained before signing.

Ignoring the editor experience. If the marketing team needs a developer to change a hero image, the site will fall out of date within a quarter. Watch the actual editing workflow in a demo.

Skipping accessibility. ADA-related demand letters against US websites are a routine business risk. Whatever platform you choose, budget for accessible templates and a WCAG review rather than retrofitting after a complaint.

Letting plugins or apps accumulate. A WordPress site with 45 plugins or a Shopify store with 30 apps is slow, fragile and expensive. Set a rule that every addition replaces or justifies itself.

No migration plan for URLs. Changing platforms without a redirect map throws away search equity earned over years. Export every indexed URL before the switch and map each one.

• Requirements list written and shared with everyone deciding.
• Three-year catalog, traffic and revenue projections attached to it.
• Every required integration confirmed as available and supported.
• Total cost of ownership calculated over 36 months, not just the build.
• Editor workflow demonstrated to the people who will actually edit.
• Accessibility and privacy obligations addressed in scope.
• URL migration and analytics continuity plan agreed.
• Clear owner for maintenance after launch.

We treat platform selection as the output of discovery, not the input. The sequence is discover, plan, build, improve. Discovery captures the requirements list above alongside brand positioning and growth goals, because a site that converts beautifully but cannot run the campaigns the growth team needs is a half solution. Planning maps those requirements to the shortest path, which is frequently a well-configured Shopify or WordPress build rather than custom engineering.

Build is where brand, web and automation meet. The design system, the storefront or site, and the integrations into CRM, email, inventory and support are scoped together so the launch is operational, not just live. Improve means the first ninety days are spent on measured changes to conversion, speed and content rather than on fixing surprises. Because our growth, brand, web and automation teams work from the same brief, the platform decision is tested against marketing reality before anyone writes code.

A representative example is our Commerce Infrastructure Upgrade engagement. A growing online retailer had outgrown an aging store with accumulated plugins, slow pages and manual order handling. Rather than default to a headless rebuild, discovery showed that the real constraints were integration and performance, not front-end flexibility. We re-platformed onto a modern commerce stack, consolidated the app layer, connected inventory and fulfillment systems, and built a measured migration with a full redirect map. The outcome was a store the team could operate without engineering help, with the integration layer designed to support future channels if the business chose to add them.