Stan Consulting · Marketing Atlas · Case File · Shopify Traffic Without Sales

The Product Page That Explained Everything Except Why to Buy.

Stan Tscherenkow Principal · Stan Consulting Filed 2026-05-07 Read time · 13 minutes

case_type: composite
proof_level: composite_pattern
cluster: shopify-traffic-without-sales
published: 2026-05-07

Read the Case File → Read the Position

01 Section 01 · The setup The setup.

A Shopify Plus DTC consumer wellness brand. Two-point-eight million annualized. Four-hundred-eighty thousand monthly sessions. Conversion rate zero-point-seven percent. The hero SKU's PDP had fourteen images, a 1,200-word description, an ingredient deck, a dosing chart, certification badges, and a video. It explained the product. It did not explain the buy.

That is the composite. The names change. The shape does not.

The brand was a Shopify Plus migration from BigCommerce, completed eighteen months before the audit. The catalog was small — eleven SKUs, one of them generating sixty-eight percent of revenue. The hero SKU was the page everyone touched: paid traffic landed on it, organic search ranked for it, the founder had personally rewritten the description twice. The page was the most-iterated surface on the site. It was also the lowest-converting hero PDP the firm had read in the year.

The marketing director had been in the role nine months. She had inherited an A/B testing roadmap built around image carousel order, badge placement, and pricing display. None of the six tests in the prior six months had moved conversion rate by more than the noise floor. The team was ready to declare CR a function of category-level commodity dynamics and shift focus to upper-funnel awareness.

The audit was scoped at this point. Seventy-two-hour written verdict. The brief was one sentence: tell us why this PDP does not convert.

Stage: Shopify Plus · DTC consumer wellness
Annualized revenue: $2.8M
Monthly sessions: 480K
Hero SKU revenue share: 68%
Conversion rate: 0.7% · site-level
PDP image count: 14 hero images plus a video
Description length: 1,200 words
A/B tests in prior 6 months: 6 · none significant

02 Section 02 · The visible problem The visible problem.

Three numbers and a pattern. That is what the marketing director brought to the audit.

Number one. Conversion rate zero-point-seven percent. The category benchmark for the wellness vertical at this price point sits between two and three percent. The site was running roughly one-third the converting share of comparable operators.

Number two. Time on the hero PDP averaged two minutes thirty-eight seconds. Scroll-depth telemetry showed the median visitor reached eighty-two percent of the page. Visitors were reading. They were not reading their way to a buy.

Number three. Add-to-cart rate on the hero PDP was four-point-two percent. Cart-to-checkout conversion was seventeen percent. The drop happened upstream of the cart. The PDP was producing low add-to-cart at high engagement, which is the signature pattern of a page that fails to deliver a buying decision.

The pattern was that every change the team made added content. Each test added an image, added a callout, added a badge, added a paragraph to the description. The page kept getting heavier. The conversion rate kept moving sideways. Nobody had asked whether the page was already too heavy. The team's instinct was that more information would close more buyers.

03 Section 03 · The wrong explanation The wrong explanation.

The team had given four explanations. Each one was almost-right and pointed away from the layer that actually mattered.

Wrong reason 01

"The category is commoditized; CR will sit where it sits." A reflex explanation that hands the operator a permission slip to stop diagnosing the page. The category had real commodity dynamics. It also had operators selling at this price point converting at three percent. The benchmark gap was the audit's whole reason to exist. Calling it a category problem ended the conversation before it could surface the page-level defect.

Wrong reason 02

"The page needs more trust signals." The team was preparing to add a fifth certification badge, a third press logo bar, and a customer-photo wall. Trust signals were not the layer that was failing. The page had eight badges, twelve press logos, and a seven-point ingredient-purity callout already in place. Adding a ninth badge does not fix a page where the buyer has no idea who the product is for.

Wrong reason 03

"The price is the issue; consider a discount." The price was tested four times in the prior year. None of the tests moved CR meaningfully. Discount tests moved volume of low-margin units without lifting the conversion rate of the cohort whose price objection had been theorized. The price was not the layer either. The page had not earned the buyer the right to evaluate the price because the page had not first answered whether the buyer was the audience.

Wrong reason 04

"More traffic will average it out; let the awareness work compound." The most expensive of the four. The team's plan was to scale paid traffic into the upper funnel and let conversion-rate noise wash out at higher volume. This is the failure pattern the position page on this batch is named after: traffic does not solve buyer hesitation, it amplifies the leak. Doubling traffic into a 0.7%-converting PDP doubles the leak, not the revenue.

All four explanations let the team keep adding content. The structural defect was upstream of the content. None of the explanations went there.

04 Section 04 · The structural cause The structural cause.

No buyer-state on the page. That sentence is the verdict. Everything below names the consequence.

The structural defect is small enough to write in a single line. The PDP did not state, anywhere above the fold, who the product was for, what failure mode the buyer was trying to escape, or what the post-purchase outcome looked like. The page explained the spec. It did not explain the buy. The fourteen images showed the product. The 1,200 words listed the ingredients, the dosing, the certifications, and the founder's story. None of those elements answered the four questions a buyer asks before pulling out a card.

Five things were true at the same time. None of them were independent. All of them compounded.

One. No who-it-is-for sentence above the fold. The buyer arriving from a paid ad with a problem in mind had no way to verify, in the first viewport, that the product addressed her problem. The page name and the H1 read as product-name plus category descriptor. The buyer had to read four hundred words deep before the first sentence referenced a buyer-state.

Two. No buyer-failure-mode named. The product was effective against a specific failure mode — the daily-life pattern that drives the buyer to search for a solution. The PDP referenced the failure mode obliquely, in a quote in the ingredient section, on scroll-position seventy-three percent. Most buyers never saw it.

Three. The fourteen-image gallery was sequenced for the operator, not the buyer. The first three images were product packshots. The next four were ingredient close-ups. The eighth was the dosing chart. The eleventh was a usage scene. The buyer's attention budget was exhausted on packshots before the page reached the only image that would have signalled "this is for someone like me."

Four. The 1,200-word description buried the value proposition in spec language. A reader doing a comprehension test on the description would have come away with a strong understanding of the product's chemistry and almost no understanding of its outcome. The page was written by someone who already believed in the product and had no memory of being a first-time buyer.

Five. The price point and the buy button sat at the third viewport. The page's structural job was to deliver the buyer to the buy decision. The structure delayed it. By the time the buyer reached the price, two minutes thirty-eight seconds of attention had been spent on content that did not answer the four buying questions.

Five things, one shape. The page taught the product. It did not earn the buy.

05 Section 05 · The decomposition The decomposition.

The decomposition reads in three layers. The buyer-state layer that was missing. The page-architecture layer that compounded the absence. The reporting-and-test layer that hid the defect from the team. This is the order they have to be read in. Skip a layer, miss the chain.

L1 Missing buyer-state Page-content defect

The page did not declare, in writing, who the buyer was, what the buyer's existing failure mode was, or what the post-purchase outcome looked like. Three sentences, none of them present. Every other defect in the case file is downstream of those three missing sentences.

The product description was a feature inventory. Features earn buyer trust after the buyer has decided the product is for her. The page was running the feature inventory before the buyer-state assertion, which is the inverse of the order a buying decision actually moves through.

Who-it-is-for sentence · not present above the fold
Failure-mode named · mentioned at scroll-depth 73%
Post-purchase outcome described · not present anywhere on page
H1 · product-name + category descriptor only
Subhead · spec language, not buyer language

L2 Page architecture Structural defect

With the Layer-1 defect named, the architecture made it worse. The fourteen-image gallery delayed the buyer to the price point. The 1,200-word description ran spec-first, outcome-never. The price and buy button sat at the third viewport, after the buyer's attention budget had been spent on content that did not answer the buying questions.

The image sequencing optimized for the photographer's portfolio, not the buyer's decision path. Packshots first, lifestyle scenes near the bottom, the only image that signalled the buyer-state was image eleven of fourteen. Most buyers had stopped scrolling images before they saw it.

Image gallery · 14 images, packshot-led, lifestyle-buried
Description · 1,200 words, spec-first ordering
Price + buy button position · third viewport, post-spec
Trust signals · 8 badges, 12 press logos, redundant
Above-the-fold real estate · 100% spent on visual product

L3 Reporting and test design Read-layer defect

The A/B test roadmap optimized for what the team already believed. Six tests in six months: image carousel ordering, badge placement, pricing display, sticky-add-to-cart on mobile, two more visual tweaks. None of the tests asked the question "does this page name a buyer-state." The test design assumed the page was structurally correct and that incremental visual fixes would unlock CR. The assumption was wrong; the tests confirmed the assumption was wrong; the team kept testing inside the assumption anyway.

Heatmap and scroll-depth telemetry was instrumented but never read against the buying-question framework. Engagement was high. Engagement-without-conversion is the signature of a page that buyers find interesting and unconvincing. Nobody on the team had a framework that would have read engagement and conversion together against the buyer-decision path.

A/B tests · 6, all visual or copy-tweak, none structural
Heatmap · instrumented, not read against decision path
Scroll-depth · tracked, not tied to buyer-state delivery
Test winning criterion · CR lift, no buyer-comprehension proxy

06 Section 06 · The fix or better move The fix, in install order.

The audit's written verdict named the install order. Order matters. Rewriting the H1 before the buyer-state is decided is the difference between fixing the page and shipping a different shade of the same defect.

The audit drove into the Conversion Second Opinion engagement format and from there into a thirty-day install. The PDP rebuild below is what was installed.

Day one · Decide the buyer-state in writing

Three sentences are written and signed. Sentence one names the buyer. Sentence two names the failure mode the buyer is trying to escape. Sentence three names the post-purchase outcome. The decision is the artifact. Until those three sentences exist, no copy moves on the page.
Week one · Rewrite the H1, subhead, and first paragraph

Above-the-fold copy is rebuilt against the three sentences. The H1 names the buyer-state, not the product category. The subhead names the failure mode. The first paragraph names the post-purchase outcome with one numeric specific. The product name moves into the page metadata and the page chrome, not the load-bearing headline position.
Week one · Resequence the image gallery

The gallery is cut from fourteen images to seven. The new sequence: image one is the buyer-state lifestyle scene. Image two is the product in use. Image three is the result. Images four through seven are the spec-side content the original gallery led with. Image eleven of the original gallery, the only one that signalled a buyer-state, becomes the new image one.
Weeks one and two · Rewrite the long description

The 1,200-word description is cut to four hundred words. The new structure: 100 words on outcome, 100 words on the use case, 100 words on the spec content the buyer needs to verify the claim, 100 words on the trust elements. The ingredient deck and dosing chart move to expandable sections below the buy zone, where the buyer can verify them post-decision.
Week two · Move the price and buy button to the first viewport

Sticky buy bar added at the page level. Price visible above the fold on first viewport on desktop and mobile. The buyer who decides quickly does not have to scroll three viewports to act on the decision. The buyer who needs more reading still gets it; the structure stops penalizing the buyer who decides fast.
Week three · Rebuild the test roadmap

The next six A/B tests now ask structural questions, not visual ones. Test one: which buyer-state H1 produces the highest add-to-cart. Test two: outcome-led versus use-case-led first paragraph. Test three: spec-deck above versus below the fold. Test four: video versus lifestyle photo as image one. Test five: sticky buy bar variants. Test six: cross-sell positioning. The roadmap optimizes for buyer-state-delivery, not for visual polish.

07 Section 07 · The lesson The lesson.

A PDP's job is to deliver a buyer to a buying decision. The buyer arrives with a problem in mind and a budget already mostly spent in his or her head. The PDP either confirms the problem and earns the buy in the first viewport, or it loses the buyer to the back button. Spec content does not earn the buy. Spec content lets a buyer who has already made the buy verify she made it correctly. The order matters. The page that runs spec-first is reading the buying decision backwards.

The eighteen-month delay between the migration and the audit is the part that compounds. Pages that explain the product are easy to write because the team writing them knows the product. Pages that explain the buy are hard to write because they require the team to remember being a first-time buyer, which is the memory the team has the least of. The longer the page runs in spec-first form, the more the team forgets what the buyer needed in the first viewport, and the more iterations they spend optimizing inside the wrong frame.

The lesson is that PDP rebuilds start with three sentences, not with a Figma file. The three sentences are who, what failure, and what outcome. Until those three are written and signed, every visual decision downstream amplifies whichever frame the team already had. The default is the failure mode. The default Shopify theme reinforces it. The default is what most teams will iterate against forever.

Five Cents · Stan's note

What I keep seeing in this pattern is that the team running the PDP loves the product. Founders especially. They love the ingredient list, they love the manufacturing process, they love the certifications, they love the story. They write the page from inside that love and they cannot see, when they read it back, that the page is for them and not for the buyer. The buyer does not love the product. The buyer has a problem and is auditioning a solution. The page is supposed to be the audition, not the love letter.

The piece I want operators to take from this case is that adding content is the trap. Every time a PDP underperforms, the instinct is to add a badge, add a section, add a callout. The right move is almost always the opposite: cut content, raise the buy decision higher on the page, name the buyer-state earlier. Subtraction is harder than addition because subtraction asks the team to defend why each element is on the page, and most elements cannot be defended against the buying-decision path.

What this case file is for: if your PDP is high-engagement, low-conversion, and your test roadmap is full of visual variants, you have this case file. The next move is the read, and the read is what the Conversion Second Opinion delivers in seventy-two hours.

Stan Tscherenkow · Marketing Atlas · 2026-05-07

09 Section 09 · Related Atlas entries Related Atlas entries.

Each link below points at a related Atlas page that handles a piece of the case file in more depth. Reference pages give the definition. Position pages give the firm's defended doctrine. The hub gives the map.

If this is the pattern in your account

Decide the buyer-state. Then call.

If the case file maps to your hero PDP — high engagement, low conversion, a test roadmap full of visual variants — the engagement that runs this diagnostic is the Conversion Second Opinion. A written verdict against the buyer-state framework, scoped at $999, delivered in seventy-two hours. If the verdict says rebuild, the Sprint engagement runs the rebuild. If the verdict says hold, you keep the read.

Get the Conversion Second Opinion · $999 Or read the methodology →

The Product Page That Explained Everything Except Why to Buy.

Day one · Decide the buyer-state in writing

Week one · Rewrite the H1, subhead, and first paragraph

Week one · Resequence the image gallery

Weeks one and two · Rewrite the long description

Week two · Move the price and buy button to the first viewport

Week three · Rebuild the test roadmap

Five Cents

Product Detail Page

Shopify Conversion Rate

Trust Signals

Traffic Does Not Solve Buyer Hesitation

Conversion Rate Is a Symptom, Not a Diagnosis

Marketing Atlas

Decide the buyer-state. Then call.