This question comes up in almost every e-commerce conversation we have. And the honest answer is that both can be right. It just depends on what you're actually building and what your constraints are right now.
Most people approach this the wrong way. They ask "which is better?" when the real question is "which is right for where I am today?"
Start here: Shopify is not a compromise
There's a tendency in tech circles to treat Shopify as the beginner option you graduate from. That's wrong. Plenty of businesses doing tens of millions of dollars in revenue run on Shopify and have no reason to leave. It handles the hard infrastructure problems: hosting, security, checkout compliance, payment processing. The app ecosystem is massive. You can launch fast.
If you're starting out, or if your product catalog is relatively straightforward, Shopify is almost always the right starting point. Get to revenue first. Validate that people actually want to buy what you're selling. Worry about platform limitations later, when you have the revenue to address them.
The 2 to 4 week timeline to launch is also real. A well-scoped Shopify build with a custom theme can go live quickly, and you can be taking orders the same week. That speed has real value when you're trying to move.
When Shopify actually becomes a problem
The platform starts to fight you in specific situations. The most common ones we see:
B2B or quote-based sales. Shopify's checkout is built for consumers buying one thing at a time at a fixed price. If your customers need to request quotes, negotiate pricing, order in bulk with tiered discounts, or go through an approval flow, you're going to spend a lot of time and money fighting against what Shopify assumes you're doing.
Unusual subscription or access models. Standard subscriptions work fine. Anything more complex like usage-based billing, multi-tier access to digital content, or subscriptions that change based on customer behavior gets messy fast.
Heavy integrations. Connecting to a proper ERP, a custom warehouse management system, or a proprietary back-office tool is doable on Shopify but fragile. Third-party app updates break integrations in ways that are hard to predict, and you end up maintaining a stack of workarounds rather than a clean system.
Transaction fees at scale. If you're not using Shopify Payments, which isn't available in every country or for every business type, you're paying 0.5 to 2% on every transaction on top of payment processor fees. At meaningful volume, that number starts to hurt.
What a custom build actually gives you
A custom store built on something like Next.js means you own the whole thing. No transaction fees, ever. The checkout works exactly the way your business works, not the way Shopify assumes all businesses work. Your data lives in your infrastructure. Page performance is typically better, which matters because load time directly affects conversion.
The tradeoffs are real though. You're looking at $8,000 to $20,000 or more to build properly depending on scope, and 8 to 14 weeks of development time. You also need an ongoing technical relationship, someone to handle updates, add features, fix things when they break. You can't just log into a dashboard and add a plugin.
How we actually think about this
When a client comes to us with this question, we ask a few things. What does the checkout flow need to do? Are there any integrations with systems that already exist in the business? What's the expected order volume in year one, and is there a B2B component?
If the answers are all simple, standard products, consumer checkout, no legacy systems, starting fresh, we'll often recommend Shopify. Not because it's cheaper, but because it's faster to market and that speed is genuinely valuable when you're validating.
If the checkout needs to do something non-standard, if there's an ERP or warehouse system that needs to stay in sync, or if the business model doesn't fit what Shopify assumes, we'll recommend building custom from the start. Migrating off Shopify later is painful and expensive. You end up rebuilding things twice.
The one thing we'd push back on is making this decision based purely on upfront cost. A $3,000 Shopify build that you outgrow in 18 months and have to rebuild costs more in the long run than a $12,000 custom build you can grow into. Think about where you'll be in two years, not just what you can afford today.
If you're working through this for a specific project and want a straight answer, we're happy to talk it through. We build both and don't have a preference either way.