Answers

Shopify or a custom build: how to actually decide

For almost every business asking the question, the answer is Shopify, and the honest version is that you have to work to find the case where it is wrong. A custom build earns its place only when a specific part of your store, the catalog, the checkout, the pricing logic, or one integration, is something Shopify cannot do without a fight.

So the real question, should I use Shopify or a custom build, is two questions wearing one coat: what does your store need to do that is genuinely unusual, and who is going to keep the code alive after launch. Answer those two honestly and the platform picks itself.

Start with Shopify and make it prove it is wrong

Shopify is a hosted platform. The hosting, the PCI compliance, the checkout, the payment routing, the uptime, and the security patches all happen without you touching them. That is not a small convenience. It is most of the real work of running a store, done by someone else, on a schedule that never stops.

A custom build moves every one of those jobs onto you. Each becomes a line item you own and pay to maintain for as long as the store is live. That cost is real and it is permanent, which is exactly why the bar for choosing custom should be high. If you cannot name the specific thing Shopify refuses to do, you do not need a custom build yet, and most stores never reach that line.

What Shopify genuinely cannot do well

There is a short list of real limits. If your store lives on this list, custom or headless starts to make sense. If it does not, you are about to pay for a problem you do not have.

• Rule based pricing that changes per customer, per quantity, or per contract, beyond what a wholesale channel or a discount app can cover.
• A catalog with a genuinely strange shape: configurable products with many interdependent options, or inventory that must mirror a separate system of record in real time.
• A checkout you need to rebuild rather than extend. Shopify guards its checkout tightly, for good reason, so deep changes there are the clearest signal to look at a custom or headless build.
• A storefront that is really an application, like a quoting tool, a configurator, or a members area with real logic, where selling products is only a small part of the job.

Notice that none of those is wanting it to look different or wanting it to be faster. Design and speed are not platform decisions. You can build a fast, distinctive storefront on Shopify, and that is usually the right way to get both.

The cost nobody puts in the comparison

The price to build is the smallest number in this decision. The number that matters is maintenance: security updates, dependency upgrades, a payment provider changing an API, a browser quietly breaking a checkout flow at a bad hour. On Shopify a platform team absorbs almost all of that. On a custom stack it is yours, and it arrives whether or not you have the time to deal with it.

This is why the decision is really about who keeps the code alive in year two. If you have, or will pay for, a team that owns that work, a custom store is viable. If the honest answer is that nobody owns it and it will just sit there, a custom store is a liability dressed as an asset, and Shopify is the responsible choice. Where that line sits in real numbers is a conversation for the /pricing/ page rather than a guess here.

Where this touches search, not just the storefront

One quiet factor tips more of these decisions than owners expect: how the site gets found. Both Shopify and a custom build can be made fast and fully crawlable. The real difference is control. On a custom stack you control every byte of the rendered page, every redirect, and every piece of structured data. On Shopify you control most of it and shape the rest through the theme and a small, deliberate set of apps.

For most stores that control gap does not decide anything, because the thing that wins in search is not platform exotica. It is a well built site with content that answers the questions real buyers are typing. If search is central to your plan, design it in from the first wireframe instead of bolting it on later. Ninetyfifth Marketing does that search work only on sites it builds, which keeps the platform choice and the search plan in one pair of hands. The method is laid out at /services/seo/.

A simple test that settles it

Run the decision as three questions, in order, and stop at the first one that answers it.

• Can Shopify do the unusual thing your store requires, using native tools or one or two trusted apps? If yes, use Shopify.
• Is the hard requirement inside the checkout, the pricing engine, or a catalog Shopify cannot model? If yes, price a custom or headless build before you commit.
• Who maintains the code in year two? If the honest answer is nobody, that alone argues for Shopify.

Most owners who ask whether to use Shopify or a custom build finish this test on Shopify, with a custom theme and a clear reason behind every app they add. That is not a compromise. It is the build with the lowest total cost and the fewest things that can break on a Friday night.