Where Should Express Checkout Buttons Go? Shop Pay, Apple Pay, and Conversion
Shop Pay and Apple Pay buttons can lift conversion or quietly sink it, depending on where they sit. Here is where express checkout belongs on mobile.
Priya runs Maro Goods, a four-year-old DTC homeware brand on Shopify doing roughly $3M a year. Her mobile conversion rate had been stuck near 1.6 percent for two quarters while desktop sat at a comfortable 3.9 percent. Same traffic, same catalog, same prices.
She’d assumed it was a creative problem, or a speed problem, or just the way mobile is.
Then a merchant we hopped on a discovery call with described almost the exact same pattern and put words to it: most ad traffic is mobile, and maybe the express button is misbehaving up there and people bail before they ever understand what they’re buying.
So we pulled Priya’s funnel apart by device. Her checkout-started rate on mobile was actually high, higher than desktop. Her completion rate after that was terrible. People were launching into a payment sheet and then backing out, over and over, on phones.
That’s the whole problem in one sentence. The buttons were working too early.
The mobile bleed nobody could explain
Here’s what was happening on a phone. A first-time visitor landed on a product page from an Instagram ad, and the very first tappable, brightly colored thing near the top was a Shop Pay button. Not “Add to cart.” The accelerated button.
Tap it, and Shopify does exactly what it’s designed to do: it skips the cart, skips most of the consideration, and throws up a payment sheet pre-filled with a saved address and card. For a returning customer who knows the brand, that’s close to magic. For a stranger who tapped it to see the shipping cost, or just out of thumb-reflex, it’s a wall of commitment they never asked for.
So they close it. And the funnel records a checkout-start with no conversion, which reads like a pricing or a trust problem when it’s really a placement problem.
Priya’s mobile shoppers weren’t rejecting her products. They were getting ambushed by a checkout they hadn’t decided to start.
What these buttons are actually doing
It helps to be precise about the two things sitting on a Shopify product page, because they’re not the same control doing the same job.
“Add to cart” is a considered action. It moves an item into the cart and keeps the shopper in browse-and-decide mode, free to add more, check shipping, read a return policy, or change their mind. The accelerated buttons, Shop Pay, Apple Pay, Google Pay, PayPal, are a different animal. Shopify calls them dynamic checkout buttons, and their entire reason to exist is to collapse the distance between intent and payment for someone who already knows they want the thing.
That collapse is the feature and the risk in the same gesture.
Used on the right shopper it removes friction. Used on the wrong shopper it removes the consideration step they actually needed, and the mistake most stores make is treating both buttons as interchangeable and stacking them together at the top, where the express one wins the first tap by sheer visual weight.
Product page, cart, or checkout
The placement question really comes down to how much you trust the shopper’s intent at each point in the journey.
On the product page, intent is lowest. A big chunk of product-page traffic is still deciding, especially cold mobile traffic from paid social, and that’s exactly the audience an accelerated button can short-circuit. This is where most of the damage gets done.
In the cart, intent is higher. The shopper has chosen something deliberately, they’ve seen it sitting there, and a wallet button next to a normal checkout button is far less likely to ambush anyone. The cart and the checkout entry point are where these buttons earn their keep, because by then the consideration has already happened.
There’s a long-running discussion among Shopify merchants about wanting to move the express buttons off the cart page and onto the checkout page in the Dawn theme, and the instinct behind it is right even when the execution gets fiddly. Push the fast path later, toward people who’ve shown they mean it, and you stop spending it on tire-kickers.
For Priya, the fix started on the product page. We pulled the accelerated button off it on mobile and let “Add to cart” be the single, obvious primary action.
The Buy Now next to Add to Cart question
A lot of owners ask whether they should show a “Buy now” or wallet button right next to “Add to cart” on the product page, on the theory that more paths to purchase means more purchases.
It usually doesn’t work that way. Two competing primary buttons create a decision the shopper didn’t want to make, and on a small screen they sit so close together that mistaps are common. You end up paying for the express button’s downside without reliably capturing its upside.
If you want both available, make one clearly primary and the other visibly secondary. “Add to cart” as the bold, full-width action, the wallet option smaller and quieter underneath. The shopper who wants the fast lane can still find it. The shopper who doesn’t isn’t dragged into it by accident.
And honestly, on cold mobile traffic, we often just remove the express option from the product page entirely and let it surface in the cart. Conversion goes up more often than it goes down.
What you can and can’t change since the 2024 rules
Here’s where good intentions hit a wall. You can’t style these buttons however you like.
The wallet providers enforce their own branding. Apple Pay, Google Pay, Shop Pay, and PayPal all publish presentation requirements covering color, wording, height, and the minimum clear space around the button, and Shopify updated how the dynamic checkout buttons render to stay compliant with those rules. You can decide whether the buttons appear and broadly where they sit, but you cannot repaint an Apple Pay button to match your theme or relabel it to something cleverer.
What you can control is real, though. Whether dynamic checkout buttons show at all, on the product page and in the cart, theme by theme. Their position relative to your own buttons, within the limits of the theme layout. And on more flexible setups, conditional logic that shows them in some contexts and hides them in others.
So the lever isn’t visual customization, it’s presence and placement. Shopify’s own documentation on dynamic checkout buttons walks through where the toggles live, and that toggle is most of the power you actually have.
Testing placement without fooling yourself
The trap here is that express buttons almost always lift one metric while hiding their damage in another. Checkout-started climbs, which feels like a win, while completion quietly falls. If you only watch the first number, every placement looks great.
So measure the pair, and measure them by device. Watch checkout-started rate and checkout-completion rate together, segmented mobile versus desktop, because the two surfaces behave nothing alike and a blended number will lie to you. Mobile is where these decisions are won or lost.
Change one thing at a time. If you pull the express button off the product page and also redesign the page and also swap the ad creative in the same week, you’ve learned nothing about the button. Isolate it, then run it long enough to clear the noise, which for most mid-size stores means a couple of weeks rather than a long weekend. The checkout-usability research from groups like Baymard Institute is built on exactly this kind of device-segmented behavior, and it consistently shows mobile punishing friction that desktop quietly forgives.
Don’t trust your gut on this one. The whole reason the problem stays invisible is that it feels like the buttons are helping.
A layout that doesn’t cost you sales
Put together, the conversion-safe default looks pretty simple.
On the product page, especially for cold mobile traffic, lead with one dominant “Add to cart.” Keep accelerated buttons out of the first-tap zone, or off the product page entirely if your traffic skews cold and mobile, and let the consideration step actually happen.
Then in the cart and at the entry to checkout, bring the wallet buttons back where they belong, next to a clear standard checkout button. By that point the shopper has chosen, and the express path saves them real time instead of stealing their decision. That’s the spot where Shop Pay’s saved-details speed genuinely lifts completion rather than faking a checkout-start nobody finishes.
None of this is a universal law. A brand with mostly returning customers and warm traffic can run express buttons far more aggressively, because their shoppers already trust the leap. The point isn’t to hide the fast lane. It’s to stop pointing cold strangers at it before they know what they’re buying.
What we keep telling clients
Express checkout buttons aren’t the enemy, and ripping them out everywhere is just a different version of the same mistake. The buttons are a tool for collapsing friction, and the only real question is whether the shopper in front of them has earned that collapse yet.
Most of the conversion damage we find comes from a single assumption: that more visible payment options always help. On warm, returning, desktop traffic, sure. On cold mobile traffic from paid social, which for a lot of DTC brands is the majority of the funnel, an aggressive express button is a tripwire that converts the metric and loses the sale.
The fix is rarely dramatic. It’s usually moving one button later in the journey and then actually measuring completion by device, instead of celebrating a checkout-start that never finished. The stores that get this right aren’t the ones with the cleverest checkout. They’re the ones who matched the button to the shopper’s intent at each step.
Priya’s team pulled the accelerated button off the product page on mobile, kept “Add to cart” as the single primary action, and let Shop Pay reappear in the cart. Nothing else changed that week, on purpose. Her mobile completion rate climbed over the next two weeks and her mobile conversion settled at 2.4 percent, up from 1.6. The buttons were always fine. They were just in the wrong place for the people seeing them first.
Questions we get every week
Do express checkout buttons actually hurt conversion? Not inherently. They lift conversion for warm and returning shoppers who already intend to buy, and they hurt it when placed in front of cold first-time visitors who tap them before they’ve decided. The damage shows up as a high checkout-started rate paired with a low completion rate, usually on mobile.
Should I remove Shop Pay and Apple Pay from my product pages? Often yes for cold mobile traffic, and often no for warm or returning audiences. A safe default keeps the product page focused on a single “Add to cart” and lets the wallet buttons appear in the cart, where intent is higher. Test it against your own traffic before committing either way.
Can I change the color or label of an Apple Pay or Shop Pay button? No, not meaningfully. The wallet providers enforce their own branding for color, wording, and spacing, and Shopify renders the buttons to stay compliant. You control whether and roughly where they appear, not how they look.
How long should I run an express-button placement test? Long enough to clear day-to-day noise, which for most mid-size stores is around two weeks. Change only the button placement during that window, and compare checkout-started and completion rates split by mobile and desktop so a mobile problem doesn’t get buried in a blended average.
If your mobile checkout-started rate looks healthy but the sales aren’t following, let’s audit where your express buttons sit.