Checkout Components Are GA: What Plus Merchants Should Build First
Checkout Components reached general availability for Plus merchants at the Summer 2026 Editions, and it is the most consequential checkout change since checkout.liquid was switched off. Every post-cart step, from contact details through to the order status page, can now be composed from drag-and-drop blocks in the checkout editor, with no app deployment required for the common cases.
The reaction has been exactly what you'd expect after three years of extensibility-era frustration. Merchants are adding blocks because they finally can. In the audits we've run since GA, we've already seen checkouts wearing six or seven new blocks, each one added in an afternoon, none of them measured.
This guide takes a different approach: a build-priority list ranked by conversion evidence, not novelty. What to ship first, what to defer, and what to refuse outright. The lens is subscription-first throughout, because checkout is where one-time buyers either become subscribers or don't.
8–22%
The conversion lift Shopify's early data attributes to merchants using checkout blocks. The width of that range is the most honest thing about it. We come back to why, and to how you should measure your own number, below.
From checkout.liquid to Components, briefly
Plus merchants of a certain vintage remember checkout.liquid fondly and not at all fondly, usually in the same sentence. One template that let you change anything, break everything, and turn each platform upgrade into a small act of archaeology. Shopify retired it for the core checkout steps in 2024, with the thank-you and order status pages following in 2025.
The extensibility era that replaced it was safer, faster and upgrade-proof, but every change needed a developer and an app deployment. We covered the build patterns that worked in our guide to checkout UI extensions. Plenty of merchants looked at the quote for moving a banner and quietly gave up on checkout customisation altogether.
Components close that gap. Underneath, they sit on the same extension architecture, so the upgrade-safety guarantees hold; the difference is that assembly now happens in the editor rather than in a repository. The wider Summer 2026 release is covered in our Editions breakdown for subscription brands. This post stays inside checkout.
checkout.liquid sunset
Core checkout steps lose Liquid access in 2024; the thank-you and order status pages follow in 2025. Total control ends.
Checkout extensibility
Upgrade-safe but developer-gated. Every banner, field and offer requires an extension build and a deployment.
Components GA
Drag-and-drop blocks on every post-cart step, assembled in the checkout editor, on extension-safe foundations.
Three eras of Plus checkout customisation: total control, total lockdown, and now governed flexibility.
What you can touch now, and what you still cannot
GA puts blocks on every step from contact details through to order status. Within those steps you can add, remove, reorder and conditionally target content without writing code. The walls that remain are deliberate, and knowing where they sit saves you from promising a stakeholder something the platform will never allow.
You can now
-
Add and reorder blocks on every checkout step, including payment
-
Target blocks by cart contents, customer segment or market, including subscription-only messaging
-
Run order-bump and upgrade offers beside the order summary
-
Capture custom fields with built-in validation
-
Style everything within your brand tokens: colour, type, corner radius
Still off-limits
-
Removing or reordering Shopify's core fields and the buy button
-
Modifying the payment element or injecting anything into it
-
Arbitrary JavaScript, CSS or third-party tags in checkout
-
Changing the step sequence itself
-
Rewriting selling-plan pricing at checkout; that stays in Functions
The boundary line at GA: composition is open, the payment core and step sequence are not.
If your roadmap needs anything from the right-hand column, the answer is still a custom extension, a Function, or accepting the platform's opinion and moving on.
The build-priority list
What follows is ranked by the strength of the conversion evidence we see across the subscription checkouts we audit, not by what demos well. Ship them in this order, one at a time, and measure between each.
Delivery expectation messaging
Concrete arrival dates beside the shipping methods; first-delivery date plus cadence for subscriptions.
Subscription upsell at checkout
A subscribe-and-save toggle that converts one-time buyers at the point of maximum intent.
Order bump offers
One small, low-consideration add-on near the order summary. One.
Trust and payment reassurance
Guarantee and cancel-anytime copy near the buy button. A real but quickly saturating effect.
Address validation
Conversion-neutral, operations-positive. Compounding value for recurring deliveries.
The Zerglo build order: ranked by conversion evidence across subscription checkout audits, not by demo appeal.
1. Delivery expectation messaging
Uncertainty about when an order will arrive is one of the most consistent abandonment drivers we see in session recordings, and it is the cheapest one to fix. A block beside the shipping methods showing a concrete date range outperforms vague "3–5 business days" copy in nearly every test we've observed.
For subscriptions, go a step further: show the first delivery date and the cadence in the same breath. "First box arrives Thursday, then every four weeks" turns an abstract commitment into a concrete schedule, and concrete schedules get completed.
2. The subscription upsell
This is the block that justifies the whole exercise for subscription brands. A customer mid-checkout with a one-time item has already decided they want the product; a clean subscribe-and-save toggle at that moment captures the ones who simply never engaged with the option earlier. Across the brands we work with, a well-built checkout toggle typically converts a low single-digit percentage of one-time buyers each month. That sounds small until you price the LTV gap between a one-time buyer and a subscriber.
The product page remains the primary venue for the subscription decision — our PDP conversion guide covers that work. Checkout is the second bite, and Components just made it cheap.
3. Order bump offers
One offer, low consideration, modest price relative to the cart. The evidence on order bumps is solid when those three conditions hold and ugly when they don't. A £6 sampler beside a £45 subscription box converts; a second £40 product introduces a fresh decision at the worst possible moment.
For subscription carts, bumps that attach to the first delivery perform noticeably better in our experience than generic add-ons, because they extend the thing the customer just chose rather than competing with it.
4. Trust and payment reassurance
A guarantee statement and a cancel-anytime line near the buy button measurably help, particularly for first-time subscription customers carrying commitment anxiety. But the effect saturates fast. One reassurance block works; three of them signal that you're nervous. If your theme already handles trust signalling well at the cart, this may test flat at checkout — which is fine, and exactly why you test.
5. Address validation
Last on a conversion-ranked list because its case is operational, not conversion. Done politely, suggesting rather than blocking, validation is roughly conversion-neutral. The return shows up in failed-delivery rates, and for subscriptions that value compounds: a bad address doesn't fail one parcel, it fails every renewal until someone notices. If your support inbox has a where-is-my-box problem, this block pays for itself quietly.
About that 8–22% claim
Shopify's early data attributes an 8–22% conversion lift to merchants using checkout blocks, and the width of that range tells you most of what you need to know. The lift you get depends almost entirely on how broken your checkout was before. A checkout with no delivery expectations, no trust content and no subscription option can genuinely jump double digits. A checkout that's already disciplined will see low single digits, and some blocks will test negative.
So measure your own number rather than budgeting against Shopify's. The clean approach is a holdout: if your testing setup can split checkout traffic, show each new block to a portion of sessions and compare completed-checkout rate and revenue per session against the control. Where a true split isn't available, run pre/post cohorts instead: four-week windows either side of the change, matched traffic mix, no overlapping promotions, and a written-down prediction before you look at the results.
Watch more than one number while you do it. An order bump can raise average order value while quietly depressing completion, and the net of those two movements is a loss that a single headline metric will never show you. For subscription brands, track the subscriber share of new orders alongside the completion rate: a checkout toggle that converts even a modest slice of one-time buyers is typically worth more over a year than a flashier block that wins the immediate conversion comparison.
Baseline first, too. Run our checkout optimisation checklist against the current state before adding anything, so you know which gaps each block is supposed to close. A block with no hypothesis attached is decoration.
A block you can't measure is a liability with good intentions.
The clutter tax
Now the uncomfortable counterweight to everything above. Checkout is the only page on your site whose entire job is completion. Every block you add competes with the buy button for attention, and the cost of that competition is invisible in the editor and very visible in your completion rate.
"Every block in your checkout must pay rent in measured conversion. The ones that can't are taking space from your buy button."
A supplements brand came to us in May having added five blocks during the Components beta: a countdown timer, a reviews carousel, two competing upsells and a charity round-up widget. Checkout completion was down roughly four points on the quarter. We stripped it back to delivery messaging and a single subscription toggle, and completion recovered within two weeks. None of the blocks was individually terrible. Together they made the payment step feel like a market stall.
There is an interaction effect to respect as well. Blocks that each test fine in isolation can fail in combination, because the customer experiences the page, not the component list. The supplements brand above had measured two of its five blocks individually, and both had passed; neither survived the company they ended up keeping. When a step already carries a block, re-measure the step as a whole after every addition rather than assuming earlier results still hold.
Restraint is a conversion tactic.
Our working rule: no more than three custom blocks per step, one offer per checkout, nothing animated, nothing that counts down. If a block survives a holdout test, it stays. If nobody can say what it's for, it goes.
What to do this quarter
The order of operations matters more than the speed. Baseline your completed-checkout rate and revenue per session. Ship delivery expectation messaging and measure for four weeks. Then the subscription toggle. Then, only if the first two earned their place, the bump and the trust block. Shipping all five at once feels productive and tells you nothing about what worked.
Components will keep widening through the year. Shopify has signalled more block types and more surfaces to come, and the agentic-checkout work happening in parallel will reward merchants whose checkouts are structured and measured rather than decorated. The discipline you build now — one block, one hypothesis, one result — is the asset that compounds.
Three years of deprecation pain bought Plus merchants a checkout that is finally both safe and flexible. The merchants who win with it will be the ones who treat that flexibility as a budget, and spend it where the evidence points.