Shopify or Custom Ecommerce: A 2026 Decision Tree

Choose Shopify (or Shopify Plus) when the catalogue is under a few thousand SKUs, the ops team is small, the launch window is weeks, and the integrations the marketing team needs (Klaviyo, Meta, Google, the email and SMS stack) are well-covered by the Shopify App Store. The platform is the right answer for 80% of D2C brands.

Choose custom ecommerce (Laravel, Medusa, a headless build) when the catalogue is large, the ops team is non-trivial, the business logic is non-standard, or the data posture (on-premise, air-gapped) makes a hosted platform the wrong answer. The cost of a custom build is the engineering, the time, and the integrations — the cost of a wrong Shopify is the migration, the lost data, and the marketing the migration paused.

Choose headless Shopify (Storefront API + a Next.js or Hydrogen front end) when the brand experience is the product, the catalogue is moderate, and the marketing stack needs API-level access to the storefront. The headless build gets you the brand control of a custom build with the catalogue operations of Shopify.

Under 500 SKUs: Shopify is the right default. The platform handles the catalogue, the checkout, the inventory, the marketing, the apps. The total cost of ownership is the subscription plus the apps, and the time to launch is weeks.

500–5,000 SKUs: Shopify Plus or headless Shopify is the right default. The platform still handles the operations, the apps, the marketing, the checkout. The headless front end gives the brand the control the brand team needs. The total cost of ownership is the subscription plus the front end, and the time to launch is 4–8 weeks.

5,000+ SKUs: custom or headless is the right default. The catalogue is large enough that the platform's data model and the app ecosystem start to show seams, and the brand experience is complex enough that the storefront needs to be custom. The total cost of ownership is the engineering plus the platform, and the time to launch is 3–6 months.

The catalogue size decides the answer, not the brand size. A large brand with a small catalogue is a Shopify brand. A small brand with a large catalogue is a custom brand.

The ops team is the team that runs the catalogue, the inventory, the marketing, the customer service after launch. The size of the team decides the platform.

A 1–2 person ops team needs a platform that handles the operations. Shopify is the right answer. The platform handles the catalogue, the inventory, the marketing, the customer service, the apps. The team runs the operations, not the platform.

A 5+ person ops team can run a custom platform, with the engineering in-house or as a retainer. The platform is the right answer when the business logic is non-standard, the catalogue is large, or the data posture requires it.

The right answer is the platform the ops team can run, not the platform the engineering team prefers.

Under 8 weeks: Shopify is the right answer. The platform launches in days, the apps in weeks, the marketing in days. The total launch window is the time the marketing team needs to prep the campaigns.

8–16 weeks: Shopify Plus or headless Shopify is the right answer. The platform still launches fast, and the brand experience can be custom enough. The total launch window is the time the brand team needs to design the front end.

16+ weeks: custom ecommerce is the right answer. The brand experience is custom, the business logic is non-standard, the catalogue is large. The total launch window is the time the engineering team needs to build the platform.

A wrong Shopify decision costs the migration, the lost data, the marketing the migration paused, and the engineering to do the migration. A wrong custom decision costs the engineering, the time, the integrations, and the marketing the build delayed. The wrong answer in either direction is 6–12 weeks of work, not just a re-platforming.

The decision is the catalogue, the ops team, the launch window. Not the brand, not the budget, not the framework preference of the team.

When the answer changes (the catalogue grew, the ops team grew, the business logic changed), the migration path is the next decision. The path is:

• Shopify to Shopify Plus: configuration, not a migration. The apps and the data stay.
• Shopify to headless: a new front end, the platform stays. The data and the apps stay.
• Shopify to custom: a real migration. The catalogue, the customers, the orders move. The apps do not.
• Custom to Shopify Plus: a real migration. The catalogue, the customers, the orders move. The custom business logic does not.

The migration path is part of the decision. A platform that migrates cleanly is a platform that lets you change your mind.

If you want a second opinion on the platform decision, our ecommerce development team can run the review. If the brief is "we need a D2C storefront that ranks and converts", our landing page development engagement is the right one.