Choose WordPress if your site is mostly content that non-technical people update. Choose Shopify if you sell physical products and want a hosted platform you never have to maintain. Choose Next.js if your project has genuine application logic or a hard performance requirement. Those three sentences resolve the majority of real decisions — the rest of this article is about the cases where they do not.
The three are not really competitors. WordPress is a content management system, Shopify is a hosted commerce platform, and Next.js is a framework you build applications with. They get compared because a business owner asking "what should my website be built on?" is offered all three by different people, each of whom is correct about a different project.
Quick comparison
| WordPress | Shopify | Next.js | |
|---|---|---|---|
| Best at | Content sites, blogs, brochure sites | Selling physical products | Applications, high-performance sites |
| Who edits content | Anyone, via the admin | Anyone, via the admin | Developers, unless a CMS is added |
| Hosting | Yours to arrange and maintain | Included and managed | Yours, typically Vercel |
| Ongoing platform fee | None | Subscription + per-transaction | None |
| Typical build cost | $800–$5,000 | $1,000–$5,000 | $800 upwards, apps quoted individually |
| Maintenance burden | Real — core, themes, plugins | Almost none | Low — dependency updates |
| Ceiling on customisation | High | Moderate — checkout is constrained | None |
| You own it outright | Yes | No — you rent the platform | Yes |
When should you use WordPress?
Use WordPress when people who are not developers need to publish and edit content regularly. That is the problem it was built for and still solves better than the alternatives. It powers a large share of the web precisely because a marketing coordinator can add a page on a Tuesday without filing a ticket.
It is the right answer for brochure sites, blogs, news and publishing, service businesses, portfolios, membership sites, and — through WooCommerce — stores where you want ownership and flexibility rather than a hosted platform.
The honest downsides
- Maintenance is real. Core, theme, and plugin updates are your responsibility, and an un-updated WordPress site will eventually be compromised.
- Plugin sprawl degrades performance. Every plugin loads assets, and sites accumulate them over years until nobody remembers what half of them do.
- Quality varies wildly. The same platform hosts excellent custom builds and unusable page-builder disasters, which makes "built on WordPress" almost meaningless as a quality signal.
- It is a frequent target precisely because it is popular, so security hygiene is not optional.
When should you use Shopify?
Use Shopify when you sell physical products, want to be running quickly, and would rather pay a platform fee than think about servers, security patches, or PCI compliance. For a straightforward catalogue it is the lowest-effort path to a working store, and the operational burden after launch is close to zero.
It suits direct-to-consumer brands, retailers with clear catalogues, businesses without technical staff, and anyone whose priority is selling rather than owning infrastructure.
The honest downsides
- You pay a subscription plus a per-transaction fee, and at volume that becomes a meaningful line item.
- Checkout is heavily constrained unless you are on Shopify Plus, which limits conversion-optimisation work.
- B2B and wholesale pricing is possible but noticeably more constrained than WooCommerce's role-based pricing.
- Apps are the usual cause of a slow Shopify store — each one injects scripts on every page load.
- You do not own the platform. Terms, pricing, and policies can change, and your store lives inside those changes.
When should you use Next.js?
Use Next.js when your project is an application rather than a set of pages — user accounts, dashboards, permissions, real-time data, complex interactivity — or when page speed is genuinely a competitive requirement rather than a preference. It gives complete control over rendering, routing, and interface, at the cost of needing a developer for content changes.
It suits SaaS products, customer portals, internal tools, marketing sites where performance is part of the product, and headless setups where WordPress supplies content to a statically generated front end.
The honest downsides
- Content changes usually require a developer unless you add a CMS, which is additional cost and complexity.
- There is no plugin ecosystem. Functionality that is a five-minute plugin install on WordPress may be two days of work.
- It is straightforwardly over-engineering for a brochure site, and you will feel that every time you want to change a headline.
- The talent pool is smaller and more expensive than WordPress, which matters when you need someone else to pick the project up.
A decision framework
Work through these in order. The first one that clearly applies is usually your answer.
- Do users log in and do things — dashboards, accounts, saved state, permissions? Build it in Next.js. A CMS will fight you for the life of the project.
- Are you selling physical products with a straightforward catalogue, and do you have no technical resource? Use Shopify. The transaction fee buys you not having an infrastructure problem.
- Are you selling with complex pricing, wholesale tiers, or a need to own everything outright? Use WooCommerce on WordPress.
- Will non-technical staff publish content weekly? Use WordPress. This outweighs almost every other consideration.
- Is the site mostly static, rarely updated, and is load speed a competitive advantage? Next.js, statically generated.
- Still unsure? WordPress. It is the lowest-regret default for a content-driven business site, and migrating away later is a solved problem.
Can you combine them?
Yes, and it is increasingly common. Headless WordPress puts the WordPress admin behind a Next.js front end: editors keep the interface they know, visitors get a statically generated site, and the WordPress installation is no longer publicly exposed. It genuinely gives you both editing convenience and front-end performance.
The cost is complexity. You are running two systems, deployment is more involved, and previewing unpublished content takes real work to set up. It earns its place on content-heavy sites with a hard performance requirement, and it is unnecessary overhead on a ten-page business site.
What about migrating later?
Every one of these migrations is routine, so the decision is not irreversible. WordPress to Shopify, Shopify to WooCommerce, and WordPress to a headless Next.js front end are all well-trodden paths. What matters is preserving URL structure with 301 redirects so search rankings and inbound links survive the move.
That said, migrations cost money and carry risk. Choosing correctly at the start is cheaper than choosing quickly. If you are genuinely unsure which platform fits, describing what the site needs to do will usually make the answer obvious within a conversation — and sometimes the honest answer is the platform nobody is selling you.