Most brands should start on Shopify. That's not a concession — it's the fastest way to a working store with payments, tax, shipping, and a checkout that converts. The real question isn't whether Shopify is good; it's whether your specific business hits a wall that only a custom build can clear. Answer that honestly and you avoid the two expensive mistakes: premature engineering (rebuilding solved problems to feel in control) and platform lock-in you've outgrown (paying in lost margin and blocked roadmap to avoid a migration). This is a decision framework, not a verdict — because the right answer genuinely depends on your business.
What Shopify does better than you will
Shopify's checkout is battle-tested across millions of orders and continuously optimized by a team larger than most companies. Fraud tooling, PCI compliance, one-click Shop Pay, dozens of payment methods, address validation, and abandoned-cart recovery come essentially free. Rebuilding that from scratch is many months of work that adds zero differentiation — nobody buys from you because you wrote your own checkout, and a checkout bug costs you real orders.
Beyond checkout, you're renting a whole operational stack: inventory management, order routing, a mature app ecosystem, tax calculation across jurisdictions, and hosting that survives a Black Friday spike without you touching a server. That last point is easy to underrate — the day your product goes viral or a campaign lands, Shopify absorbs a 50x traffic spike automatically, while a custom store meets that same moment as an on-call incident. Platforms also ship improvements you inherit for free: new payment methods, checkout optimizations, fraud-model updates, compliance changes across regions. On a custom build, every one of those is a ticket in your backlog.
For a catalog of a few thousand SKUs and standard fulfillment, Shopify plus a few well-chosen apps will outperform anything a small team ships in a quarter. If your storefront is a fairly conventional catalog-and-cart, stay on Shopify and put your energy into product, brand, and acquisition — the things that actually grow revenue.
The signals that you've outgrown it
Custom starts to pay off when your business logic stops fitting the template. Watch for these:
- Complex pricing or configuration — quote-based B2B, per-customer catalogs, volume tiers, or products assembled from many interdependent options (a configurator). Shopify's variant model caps out, and the app workarounds get brittle.
- App sprawl — you're paying for a dozen apps that overlap, conflict, slow the store down, and still don't do quite what you need. The monthly app bill plus the maintenance burden of keeping them compatible starts to rival a custom feature.
- Margin at scale — at high GMV, platform fees plus transaction fees (especially if you're not on Shopify Payments) become a real line item. At tens of millions in GMV, reclaiming those points can fund the engineering.
- Unique fulfillment or inventory — multi-warehouse routing, marketplace/multi-vendor logic, complex subscriptions, rentals, or bundles with rules no app models cleanly.
- Deep systems integration — a custom ERP, a specialized 3PL, or an internal tool that Shopify's APIs can only awkwardly reach.
One of these alone is rarely enough to justify a rebuild — there's usually an app or a workaround. Two or three together, each costing you real money or blocking real revenue, is a genuine signal.
Score it honestly before you commit
Founders talk themselves into custom builds because building feels like progress, and out of them because migration feels scary. Neither instinct is a business case. Before you spend a dollar, run a blunt scoring exercise across the dimensions that actually decide this:
- Control — how much of the customer experience does the platform prevent you from shaping? On a conventional store, very little. On a novel one, a lot.
- Cost curve — plot your platform, app, and transaction fees against projected GMV for the next 24 months. Custom flips from wasteful to smart at a specific revenue point; find yours.
- Speed — Shopify ships you a feature today; custom ships it in a sprint. Early on, speed usually wins outright.
- Risk — a custom checkout is your uptime, your PCI scope, your incident at midnight. Price that risk in, don't wish it away.
- Team — do you have (or will you retain) the engineering capacity to own a store forever, not just ship one?
If custom only wins on "control" and loses on the other four, you have your answer. The brands that replatform successfully can point to a specific, quantified constraint the platform imposes and a specific number the rebuild unlocks.
The middle path most teams miss
It's not binary, and treating it as binary is the most common mistake we see. Headless commerce lets you keep a commerce engine — Shopify via its Storefront API, or an open engine like Medusa or commercetools — as the backend, while building a fully custom React or Next.js front end. You get complete design and performance freedom, the SEO benefits of server-side rendering, and pages that hit the Core Web Vitals targets that both convert and rank — all without rebuilding checkout, inventory, or payments.
For many growing brands this is the right answer: custom where it differentiates (the storefront experience, the content, the speed), managed where it doesn't (the money-touching core). Our headless commerce guide walks through the architecture and the trade-offs in depth. The catch is real, though — headless means you now own the front end's performance, deployment, and complexity, so it's a step up in engineering commitment, not a free lunch.
What a custom build actually costs
A custom store isn't just the initial build, and founders who budget only for the launch get an unpleasant surprise. You own security patches, dependency upgrades, payment-processor API changes, tax-rule updates, PCI scope, and uptime — forever. When a payment provider deprecates an API or a new tax rule lands, that's your engineering time, on your schedule, at your cost. Budget for a maintenance retainer, not just a launch, and staff for the incident at 2 a.m. during your biggest sale.
The math works when custom capability drives revenue or reclaims margin that comfortably exceeds that ongoing cost — and rarely before. If you can't point to a specific number the custom build unlocks, you're probably rebuilding for control, not returns.
There's also an opportunity cost that never shows up on the invoice. Every engineer-month spent rebuilding a checkout that Shopify already gives you for free is a month not spent on the thing only your team can build — the feature that differentiates you, the acquisition channel that grows you. For an early brand, that's usually the most expensive line of all, precisely because it's invisible.
Don't replatform to fix a problem a platform can solve
The most common regret we see isn't a custom build that failed technically — it's a custom build that solved a problem the brand could have solved on Shopify for a fraction of the cost. Slow store? That's usually a theme, an app-bloat, or an image problem, not a platform ceiling. Can't get the design you want? A headless front end fixes that without touching commerce. Conversion stalling? That's a merchandising and UX problem the conversion optimization playbook addresses far more cheaply than an engineering team. Exhaust the platform's real limits before you conclude you've hit them.
A simple decision rule
- Start on Shopify. Validate the business. Ship fast. Spend on brand and acquisition, not infrastructure.
- Move to headless when design and performance are genuinely holding you back but your commerce logic still fits a platform. Keep the money-plumbing managed.
- Go fully custom only when your business model itself doesn't fit any platform — and the revenue or reclaimed margin clearly justifies owning the whole stack, maintenance included.
If you do move off Shopify, migrate in stages rather than in one high-stakes cutover. Go headless first — keep the commerce engine, replace only the front end — and prove the new storefront converts before you touch the money-plumbing. Preserve your URL structure and 301-redirect anything that changes, or you'll hand back months of hard-won SEO the day you launch. Keep the old store live until the new one is measurably at least as good on conversion and page speed. A replatform that tanks organic traffic or checkout conversion can erase years of margin gains overnight, so treat the migration itself as a first-class project with its own budget and rollback plan, not an afterthought to the build.
Whichever direction you lean, don't forget the fundamentals that move the number that matters: our e-commerce conversion optimization guide will usually find more revenue than a replatform will, and it's a fraction of the cost.
At Doktouri we've shipped both Shopify storefronts and fully custom commerce platforms, so we have no incentive to push you toward the more expensive answer — we can tell you which one your business actually needs. If you're weighing the move, let's talk.
Originally published on the Doktouri Agency blog. We build web, mobile, SaaS, and AI products — let's talk.
Top comments (0)