Notes / Conversion Works
Should you add express checkout to a high-ticket product page before Black Friday?
Review express-checkout tests for high-ticket products, spot where customers get stuck, and plan a product-page experiment before Black Friday traffic arrives.
By Edu Rigonato. Published Sep 15, 2026. 12 min read.
Adding an express-checkout button below Add to Cart looks like a fairly small change. The customer has chosen the product. We give them another way to pay, and they can move forward without opening the cart.
Before Black Friday, that can sound like an easy improvement. But there are reported tests where adding that route helped, and another where it reduced completed purchases.
I would treat the position of express checkout as something to test on a specific product page. Keep the normal purchase route clear, check what the shortcut carries through, and measure whether more of the customers who see the page actually buy. The price of the product alone does not tell us which route they need.
Here is how I would work through that decision before changing the page.
Why did express checkout help one store and hurt another?
In Blend Commerce's Vegepod test , the variation kept Add to Cart and added an optional express-checkout route directly below it. The agency reported a 35.8% increase in conversion rate and a 40.13% increase in revenue per visitor. Shop Pay was already the merchant's most popular payment method, according to the report.
That is useful context. The team was giving customers an earlier opportunity to use a payment method they already used at that store.
But Blend's BBQ Land test reported the opposite direction. On product pages described as selling high-ticket grills, the express-checkout variation reduced conversion rate by 31.21% and revenue per visitor by 25.55%. Average order value rose by 8.21%, which did not make up for the weaker purchase performance.
Frequently asked questions
Can we remove the product-page button while keeping the payment method at checkout?
Yes. Product-page button display and checkout payment availability are separate settings. <a class="inl" href="https://help.shopify.com/en/manual/online-store/dynamic-checkout/add-buttons">Shopify documents how to show or hide the product-page button</a>; changing that display does not require disabling the payment provider. Verify both routes in your theme and record exactly which setting the experiment changes.
What if customers need several items or a delivery service?
Trace the full order before including it in a product-page shortcut test. <a class="inl" href="https://help.shopify.com/en/manual/online-store/dynamic-checkout/compatibility">Shopify's compatibility guidance</a> says the button purchases a single product variant, although customers can buy multiple units of that variant. It also does not support cart attributes. A basket with different products or a service collected through a cart field needs a route that preserves those requirements.
What if we cannot get a useful A/B result before Black Friday?
Use the time to check compatibility, fix reproducible errors and observe customers completing the purchase. Those findings can support a specific repair, but they do not establish an A/B lift. Keep an inconclusive experiment labelled inconclusive. I would not turn a short run into a winning case study because the calendar is running out.
Here is the test brief I would want before changing our grill page.
- Question: Does giving eligible customers an optional express route on this product page help more of them complete an order?
- Current route: Add to Cart, basket review, then checkout. The customer's payment options remain available there.
- Variation: Keep Add to Cart and add the optional accelerated route after a valid product selection. Keep the offer and other page content consistent.
- Required checks: The selected configuration carries through, required information is collected, the order can be reviewed, and the ordinary route is still easy to find.
- Decision: Compare completed orders per eligible visitor as the primary measure, with revenue, contribution and order-quality checks. Agree on the sample, worthwhile effect and stopping rule before launch.
That is where I would bring the Vegepod and BBQ Land examples back to our own store. They give us reasons to test the route carefully. Our customer's behavior, our order requirements and our result determine whether we keep it.
Pick one product page and trace both routes. Write down where the customer loses a choice, hits an error or has to repeat effort. That gives us a concrete starting point for the next CRO review.
Explore Conversion Works