Shopify checkout: why we never replace it
Checkout is where money changes hands. Why we leave it to Shopify even on headless builds, and what we customise around it instead.
Our position, stated plainly
What the checkout carries
| Responsibility | What it involves | Who handles it on Shopify |
|---|---|---|
| Payment methods | Cards, wallets, local methods per country, new ones every year | Shopify and its payment partners |
| Fraud prevention | Risk scoring, verification, chargeback handling | Shopify |
| Compliance | Card data handling standards, consumer law per market, tax display | Shopify |
| Speed and reliability | The one page that must never fail, under peak load | Shopify |
| Accessibility | Keyboard, screen readers, contrast, in the highest-stakes flow | Shopify |
| Continuous testing | Changes tested on real transactions at scale | Shopify |
A store that replaces the checkout takes over every row.
What we customise instead
- Everything before checkout. Product pages that answer the buyer’s questions, collection pages that help them choose, a cart that shows costs clearly, speed on phones.
- Trust around the button. Returns policy, delivery times, contact details and payment badges where the shopper decides.
- Checkout configuration. Branding, fields, payment and shipping options, express methods, local methods per market, all within the checkout Shopify runs.
- Rules through Functions and extensions. Conditional discounts, shipping logic, B2B terms, custom validations, added to the checkout rather than replacing it.
- Everything after. Confirmation, follow-up, account, support, in our design.
When the question is really a different one
If the way you sell genuinely does not fit any checkout, configurators with complex pricing, multi-step approvals, quotes that become orders, the store may be software rather than a shop, and the honest conversation is about building that software with Shopify handling what it does well, or without Shopify at all. That is rare, and it is not solved by a custom checkout bolted onto a standard store.
What this means for you
Leave the checkout to Shopify and spend the effort where it changes results: the pages before it, the trust around it, the configuration inside it, and the experience after it. That is where stores win and lose, and it is where a partner can do real work without taking on risks that belong to a platform.
Frequently asked questions
Can't a custom checkout convert better?
We do not have the data to say which converts better, and neither does anyone quoting a number at you. What we can say is who carries the work: the platform maintains and updates its own checkout, including the payment methods, the fraud rules and the compliance changes, while a custom checkout leaves all of that with you. The gains stores want, fewer steps, local payment methods, express options, are already in the standard checkout or its configuration.
What if we need a special checkout flow?
Most special needs, custom fields, discounts with conditions, B2B terms, shipping rules, are handled through checkout configuration, Shopify Functions or approved extensions without replacing the checkout itself. Genuinely unusual flows are a sign the store may be software rather than a shop, and that is a different conversation.
Does headless mean a custom checkout?
No. Headless means the browsing pages are built separately; cart and checkout still hand over to Shopify. The storefront builds the cart through the Storefront API and sends the shopper to Shopify's checkout to pay. That boundary is what keeps headless safe.
Sources
- Shopify Help Center: Checkout settings (accessed 2026-09-11)