Checkout is the part of your store that moves the most money per second, and that's where a good chunk of this decision plays out. Shopify hands you a checkout battle-tested across millions of transactions from day one; custom development hands you full control over that same screen, at the price of building it yourself. Between those two extremes sits the real question: is your business a standard catalog with a cart, or does it run on logic no template fully solves?
At Cambalache Studio we see both scenarios regularly: small businesses that need a store running next week, and businesses that already pushed Shopify to its limit and hit the ceiling. We covered this same logic for the no-code app world in Bubble vs. Custom Development; here we bring it to the specific terrain of selling online, which has its own rules.
What's Already Solved for You
Shopify is the industry standard for ecommerce, and for concrete reasons:
- Speed. You can have a store running in days, not weeks.
- Low upfront cost. Getting started is much cheaper than custom development.
- Huge app ecosystem. Reviews, upsells, email marketing, loyalty, shipping — almost any standard feature already exists as an installable app.
- Payments and security handled. PCI compliance, checkout, and payment processing come built in and tested at global scale.
- Managed infrastructure. Hosting, CDN, and uptime aren't your problem.
- Highly optimized checkout. It's one of the most fine-tuned pieces of the platform; matching that level from scratch takes time.
If your business is "product catalog + cart + payment + shipping" — the most common case — Shopify has already solved that problem better than you will starting from zero.
Where the Seams Start to Show
Shopify's limits don't show up on day one. They show up once the business stops being a standard catalog:
- Narrow checkout customization. Changing the logic of the payment step (custom fields, specific rules) usually requires the enterprise plan, noticeably pricier than the entry-level ones.
- Costs that pile up everywhere. Each app tends to carry its own monthly fee, and skipping the platform's own payment gateway adds an extra per-transaction charge. Plans change over time — check Shopify's current pricing directly before you budget for it.
- Deep integrations get forced. A proprietary ERP, warehouse or logistics with specific rules, local invoicing, or pricing and inventory logic that isn't "simple product" — all of that gets solved with third-party apps that add points of failure, or with development on top of the platform, which has its own API limits.
- Business models that don't fit natively. Subscriptions with custom rules, multi-vendor marketplaces with split payments, dynamic-pricing quote tools, B2B with per-customer price lists — Shopify can be forced into handling these, but it wasn't built for them.
- Lock-in. Your store lives inside a third party's infrastructure. Migrating after years of operation (catalog, customers, history, connected apps) is a project in itself.
The Other Side: What Custom Code Gives Your Business
Owning your code flips the equation: more upfront investment and time, far fewer limits down the road.
- Frictionless integrations. Your ERP, your logistics, your invoicing — connected with the exact logic your operation needs, without depending on the right app existing.
- Freedom in business models. If your product isn't "catalog with a cart" — a subscription with custom rules, a marketplace, a quoting system — you're not forcing a platform built for something else.
- Predictable costs at scale. No third-party transaction fees or apps piling up; infrastructure grows with your actual operation, not a vendor's pricing model.
- Full control over performance, checkout UX, and business logic.
- No lock-in. The code is yours, and any team can maintain it.
The cost is real: it takes more time to get started and a development team, something Shopify spares you on day one.
Shopify vs. Custom, at a Glance
| Shopify | Custom Development | |
|---|---|---|
| Time to launch | Days | Weeks |
| Upfront cost | Low | Medium-high |
| Cost at scale (apps + transactions) | Rises with usage | Predictable |
| Standard catalog + cart + payment | Excellent | More than you need |
| Integrations with proprietary ERP/logistics | Limited / forced | Native |
| Non-standard business models | Limited | Full |
| Checkout customization | Narrow unless on enterprise plan | Full |
| Third-party dependency | High (lock-in) | Low |
| Best for | Standard catalog, fast validation | Complex operations or a custom model |
The Middle Path: Shopify as the Engine, Custom Storefront
There's a third option that often gets overlooked: use Shopify as the commerce engine (catalog, inventory, checkout) but build the store's frontend custom, connected via API — known as "headless commerce." It's a way to keep what Shopify handles well (payments, inventory, a proven checkout) without being tied to its templates or its visual customization limits. It's not free of complexity, but it's a real alternative before jumping straight to building everything from scratch.
And If Your Problem Isn't Just "Selling Online" Anymore
The same logic from the Bubble piece applies here: it's not about picking one forever. Many small businesses start on Shopify to validate the online channel at minimal cost, and as the operation grows — more orders, more sales channels, the need to integrate inventory and invoicing — the platform's ceiling starts costing more than it saves. That's when selling online stops being the immediate problem and becomes part of a bigger one: digitizing the entire operation. That's the territory of small business digitalization — not a standalone store, but a system that connects sales, inventory, invoicing, and logistics.
Where Shopify Falls Short for You
There are concrete signs you've already passed the point where Shopify is enough:
- You need to integrate your ERP or in-house logistics in real time, and the available apps don't cover that logic.
- Per-app and per-transaction costs start weighing on your margin more than building the logic yourself would.
- Your business model — custom subscriptions, a multi-vendor marketplace (a challenge similar to the one we describe in how to launch a marketplace), B2B with per-customer pricing — doesn't fit the catalog-with-a-cart mold.
- You need to control checkout or the buying experience for a strategic reason, not a cosmetic one, and your current plan won't let you.
If none of these signs ring true yet, Shopify remains the right call: there's no reason to custom-build what a proven platform already solves better. But if two or three of them already sound familiar, custom development has stopped being a luxury and become the option that saves money in the medium term. And if you're not sure which stage you're in, that uncertainty is itself a sign it's worth talking through before deciding — you can see how we think about scope and investment in how much an MVP costs.