In April 1985, Coca-Cola changed the formula of the world's most famous drink. It wasn't a hunch. The new recipe had been preferred in taste tests of nearly 200,000 consumers, which is about as much evidence as a product decision ever gets.
By June the consumer hotline was taking 1,500 calls a day against 400 before the change, and 79 days after launch Coca-Cola brought the old formula back as Coca-Cola Classic.
Coca-Cola's own history puts it in one line: "What these tests didn't show, of course, was the bond consumers felt with their Coca-Cola." My read: they were testing what people thought of a sip, and nobody measured what they felt about losing the thing.
Product pages do a smaller version of this. Say your return rate is 4 percent and you're proud of it. Mobile add-to-cart is 3.2 percent and hasn't moved in two quarters, on a page that's mostly spec rows, ingredient callouts and a comparison chart, every line of it accurate.
That return rate tells you the page describes the product honestly. It tells you nothing about the roughly 97 in every 100 mobile visitors who never added it to the cart. Like the taste test, it only hears from people who already said yes.
So the usual fix is more reasons: another spec row, a sharper comparison table, a percentage. It's the taste test again.
Why Doesn't A Page Full Of Good Reasons Convert?
Melissa Van Rickley puts it plainly in her CRO in 2026 piece. People "decide emotionally, then justify logically", and brands that "optimize as if users are spreadsheets" keep leaking revenue. The job she gives psychology-led CRO is "Removing perceived risk before adding persuasion".
In 2006 Gitte Lindgaard and colleagues at Carleton University flashed homepages at people for half a second, and later for 50 milliseconds, and asked how visually appealing each one was, and the 50 millisecond ratings lined up closely with the half-second ones.
That study measured how appealing a homepage looked, not trust and not buying. What I take from it is the order of events. She has a feeling about your page before she's read a word of it, and my read is that everything after gets read through that feeling. If the first screen says wrong place, your spec table is being read by someone looking for a reason to leave.
Where The Spreadsheet Shows Up On A Product Page
The Spreadsheet PDP is a product page that answers "does this make sense?" before it answers "is this for me?" Accurate information, wrong position:
The first mobile screen is a packshot with an ingredient list under the title, so she's asked to evaluate before she's seen herself in it.
The star rating sits under three accordions at the bottom, so "did people like me buy this?" gets answered last.
A competitor comparison chart lands in the first two scrolls, handing her other tabs to open mid-decision.
A clinical-style percentage with no who, how many or how long reads as a claim to audit, not a reason to relax.
All logic, delivered before the reassurance that gives logic somewhere to land.
What Does She Need To Feel Before The Specs Make Sense?
The question most teams bring to a stuck product page is what else they can tell her, usually more detail and more proof. It feels rigorous. It's the spreadsheet talking.
The better question is what she needs to feel before any of that is worth reading. On a product page it comes down to four questions, and the order matters more than the answers:
Is this for someone like me?
Did people like me buy it and feel fine?
What if it's wrong?
Does it make sense?
I call that order The Reassurance Sequence. The first three are feelings. The fourth is the spreadsheet, and it still matters, because it's what she uses to justify a decision she's already leaning towards. It just goes fourth. Questions one and three echo Van Rickley's own list.
Proof lands on a shopper who already feels safe. On one who doesn't, it's just more to check.
One boundary. Reassurance isn't hype. A lifestyle photo promising a feeling the product can't deliver will lift add-to-cart and then come back to you as returns. So the return rate from the top stops being a vanity number and becomes your guardrail.
This is the order we build to. It isn't a tested template, and there's no lift figure attached to it.
Run This Check On Your Top Three Product Pages
Screenshot the first screen and the first two scrolls of your three product pages with the most mobile traffic, on your phone.
Label every block R or P. R is reassurance: someone like your buyer using it, a review, a customer's own sentence, a fit or returns line. P is proof: specs, ingredients, percentages, comparison tables. If the first P shows up before the first R, you've got a Spreadsheet PDP.
Then watch 20 Microsoft Clarity recordings of first-time mobile visitors who left without adding to cart. Watch for the fast thumb-flick past the spec block, the pinch-zoom on the one photo with a person in it, the size guide tapped and closed.
If they reach the reviews and still leave, the reassurance is there but it's the wrong kind. Check whether the review photos look like the buyer you're paying to bring in.
Reorder in the theme editor, which on an Online Store 2.0 theme works on any Shopify plan, and then watch add-to-cart and return rate for 60 days, because returns lag the order. If add-to-cart goes up and returns follow it, you sold a feeling the product didn't deliver.
Nothing on a Spreadsheet PDP needs deleting. It needs moving. Put the feeling first and let the specs do the job they're good at, which is helping her explain a yes she's already leaning towards.
📥This Week's Free Resource
This week's resource is a free infographic, The Product Page Reassurance Sequence, mapping what a mobile product page should answer first, second, third and fourth, and where the specs belong. Tape it next to your screen while you do the reorder.
Thanks for reading!
Conal Brady
Ecom Luxx
P.S. Learn more about Ecom Luxx and our GrowthOps™ Partnership below:
