Shopify does more than most teams assume
For a large majority of stores, standard Shopify with a well-built theme is the correct answer, and the reason is operational rather than technical: payments, tax, fraud, hosting, PCI scope and platform updates all stop being your problem.
The instinct to go custom often comes from one unusual requirement. Before rebuilding a platform around it, work out whether that requirement is worth what it costs — and whether an app or a modest extension covers it.
The three signals that justify going headless
Headless commerce earns its keep in three situations. First, when content and commerce genuinely interleave — editorial, configurators, guided selling. Second, when the buying journey is unusual enough that a theme fights you at every step. Third, when performance requirements exceed what a theme can reach on your catalogue size.
Absent those, headless mostly buys you a larger maintenance surface and a slower merchandising team.
B2B commerce changes the calculation
Customer-specific pricing, quantity breaks, quotes, purchase orders, credit terms and multi-user accounts push you toward either a B2B-capable platform tier or a custom layer over your commerce engine.
This is worth deciding at the start, because retrofitting account-based pricing is one of the more expensive commerce changes there is.
Compare three years, not one quote
Put build cost, platform fees, app subscriptions, hosting, maintenance and the cost of one platform migration into a single three-year figure for each option. Then add a line for merchandising velocity: how many days per month your team loses to changes it cannot make alone.
Once that table exists, the decision usually makes itself — and it is frequently the less fashionable option.
The question that actually settles it
Ask what your merchandising team wants to change next quarter, then ask how each option handles that change. If the answer on the platform is "a setting" and on custom is "a ticket", the platform wins regardless of what the architecture diagram looks like.
The inverse is equally decisive. If the change your business depends on is impossible in a theme without fighting it — a configurator, a quote flow, account-specific catalogues — you will pay for that fight every quarter until you stop.
Write both answers down before you speak to any agency, including us. It reframes the conversation from technology preference to operating cost, which is where the decision belongs.
Questions people ask about this
Yes, well past the point most teams assume. Tens of thousands of SKUs are routine. The constraints that actually bite are unusual buying journeys, deeply interleaved content, and B2B pricing models — not catalogue size.
When content and commerce genuinely interleave, when the journey is unusual enough that a theme fights you at every step, or when performance requirements exceed what a theme can reach. Absent one of those three, headless mostly buys a larger maintenance surface.
Expect roughly two to three times the build cost and a meaningfully higher running cost, because you now own the front end. That is a good trade when it removes a revenue constraint and a poor one when it removes a design frustration.