Shopify powers over four million stores. For most e-commerce businesses, it is a great fit. That includes direct-to-consumer brands, retail shops, and simple product catalogs. It handles payments, taxes, and fulfillment integrations well. It runs the core buying experience better than a team could build from scratch in the time they have. So the real question about custom software ecommerce teams should ask is not when you want to move faster. It is this: when does your business model need something the platform simply cannot do?

The businesses that move to custom software are not always the ones with the most revenue. They are the ones whose edge depends on something the platform treats as a rare case. That might be pricing that shifts by customer segment, past purchases, and live inventory. It might be subscription rules more complex than a fixed schedule. It might be product options with deep, nested rules about what can go together. Or it might be inventory spread across warehouses, third-party logistics, and in-store stock. Sometimes the workarounds get harder than just building the feature. At that point, custom is the right call.

Pricing engines: when "percentage off" is not your pricing model

Off-the-shelf platforms model pricing in a simple way. You set a base price. You add discounts, either a percentage or a fixed amount. You may add tiered pricing by quantity. For much of B2C, that covers everything. For B2B, wholesale, and complex deals, it falls far short.

Custom pricing engines handle the hard cases. They support contract pricing, where one account has negotiated rates on a set of SKUs. They handle volume price breaks that stay correct across partly shipped orders. They support promotions with layered rules. For example, a price might apply only when the cart holds product A and at least two units of product B, but not if the customer used that promotion in the last 90 days. They also support dynamic pricing that shifts with inventory, demand, or competitor data. Shopify's discount and script APIs cover some of this. Still, their ceiling is lower than most B2B businesses need.

Inventory management that spans your actual supply chain

Standard inventory tools make simple assumptions. They assume stock sits in one warehouse. They assume the platform or a few 3PL partners handle fulfillment. Some supply chains are far more complex. You might run several warehouses, each with different SKUs. You might use vendor drop shipping with live inventory feeds. You might sell pre-orders tied to production dates. Or you might share stock across in-store and online channels. These cases need inventory logic that goes further.

Custom inventory management usually has a few parts. A warehouse layer tracks live stock across every location. Reservation logic stops you from overselling limited stock, which matters most during flash sales. Purchase order management tracks inbound stock and lets you pre-sell against confirmed POs. Allocation rules decide which warehouse fills each order, based on customer location, shipping cost, or stock on hand. The frontend needs to know what is available right now. The backend may update later, from warehouse scans. Connecting those two layers is where most custom systems need careful engineering.

Subscription and recurring purchase models beyond "ship every 30 days"

Subscription e-commerce has grown well past coffee and pet food. Those categories started it. Now businesses run subscriptions for professional tools, business supplies, curated experiences, and physical services tied to software. The rules behind these models often run deeper than Recharge or Bold Subscriptions handle on their own. Think pause-and-resume logic with different billing effects. Think tier pricing that unlocks products one-time buyers cannot get. Think usage-based billing, where the plan covers a base amount and overages bill per unit. Think churn workflows that offer specific retention deals based on why someone cancels.

You can build subscription logic on a custom payments stack. Stripe Billing or Recurly runs the billing, with your own app logic on top. This gives full control over the whole subscriber lifecycle. The cost is that you now own that complexity. Build versus buy here is one of the clearest calls in e-commerce. Say your model is "ship the same product on the same schedule for the same price." Then Recharge is the right answer. But if your model stacks rules on top of rules, custom is worth the investment.

Go headless or fully custom when your advantage lives in the commerce logic itself. That logic often cannot fit inside a platform built for the average store.

The headless approach: when to use it and what it costs

Headless commerce sits between off-the-shelf and fully custom. You use a platform's backend through its API, such as Shopify, Commercetools, or BigCommerce. Then you build a fully custom frontend. You keep the platform's checkout, payments, and compliance. You gain full control over the customer experience. There is a trade-off, though. A headless build costs much more than a Shopify theme. It needs a frontend team that can work with REST or GraphQL APIs. It also shifts frontend performance and reliability onto your team, not the platform.

Headless fits when the customer experience is your edge. Think highly interactive product configurators, rich product visuals, or deeply personalized storefronts. It works as long as the backend commerce logic still fits the platform's model. Fully custom fits when neither the frontend nor the backend fits the platform. See building an MVP that scales for a framework on where to spend the custom build budget. Then connect with TTGC at /growth-assessment to scope your e-commerce build.