Why generic PDPs are quietly killing your margins

A buyer lands on your category page. Picks one. Reads the description.

Then opens three more tabs. Same product, three competitors. Reads each.

The descriptions are basically identical. Same bullet points. Same adjectives. Even the cadence of the sentences is a copy-paste from the supplier sheet.

She picks the cheapest. Why wouldn't she.

You just lost a sale you should have won, and you'll never see it on a dashboard. You'll write it off as market pressure, or a soft week, or something to do with the weather. It wasn't market pressure. It's a content problem dressed up as a pricing problem, and almost every retailer in Europe is bleeding from it.

How supplier descriptions get into your PIM (and stay there)

Most catalog data still arrives the same three ways. A supplier portal. A GS1 feed. A PDF the rep emailed last quarter, attached to a half-broken Excel file.

The description that ships with each of those was written once, by someone in marketing at the manufacturer, for every retailer in their distribution. That copy is intended to be neutral. Reusable. Safe.

So it gets reused. Everyone reuses it. Amazon. The marketplace. Your two biggest direct competitors. The new entrant that just undercut you 8%. They all publish the same paragraph because nobody on a catalog team has the bandwidth to rewrite five thousand SKUs every quarter.

Your team doesn't either. So you ship the supplier copy. Same as everyone else.

That's how thirty stores end up with the exact same paragraph on the exact same product. And how a buyer scans three of those paragraphs in 90 seconds, decides they're indistinguishable, and sorts by price.

The SEO version of the same problem

Google reads those identical paragraphs and treats most of them as duplicate content. It doesn't pick a winner randomly. It picks the strongest domain. That's almost never you. It's the manufacturer or the marketplace.

You spent budget on the listing. You paid for the photography. The merchandising team sized up the new collection. Then you didn't spend a few hundred euros' worth of original copy, and the page never ranks.

Months of compounding traffic flow somewhere else.

The retailers who do invest in differentiated PDPs collect that traffic. Every quarter the gap widens.

The conversion math

Most heads of e-commerce track conversion as a single line on a dashboard. It moves with traffic mix, season, paid spend. Which means when content is the cause, it never shows up clearly.

Segment the data and the gap is loud. Pages with original, persona-aware copy convert noticeably higher than pages with raw supplier copy. Add-to-cart moves first. Conversion moves a few weeks behind it. Bounce on the product page drops by a chunk you can feel in the next month's report.

You don't have to take this on faith. Pick a hundred SKUs from your own catalog. Sort by traffic. Compare the sample with original copy to the sample without. Most catalog teams have never run that test. The ones who do never publish a generic PDP again.

"We'll fix it next quarter" never happens

Every catalog team I've worked with knows their content is generic. They've known for years. The reason it stays generic isn't will. It's structural.

A copywriter who knows your brand and your customer can rewrite a single PDP in fifteen, maybe twenty minutes. For a 5,000-SKU catalog that's about 1,500 hours. Roughly ten months of one full-time writer doing nothing else. Ten months. Eating their entire OKR.

So instead you hire contractors for a quarter. Or an agency. Or you batch the work in the slow season. In every version, the project is too big to ever be finished.

New products arrive faster than you can rewrite. The voice drifts between writers. Half the catalog stays generic forever, because by the time you'd be done, the team has already moved on to next year's launch.

This isn't a productivity problem. It's a unit-economics problem. Manual rewriting at the size of a real assortment doesn't pencil out. Full stop.

What a non-generic PDP actually does

Try the test on your own site. Go to a category page. Click three products. Read the first paragraph of each PDP.

If you can't tell which retailer it is, neither can your customer.

A PDP that earns its place names the buyer somewhere in the first three sentences. Active parents. Home cooks who entertain. First-time buyers shopping for performance gear. It writes to that context, not to a spec sheet, and it answers — explicitly — the three questions the buyer is silently running through their head.

It also doesn't open with the manufacturer's name.

The mechanical version of this work is easy to dismiss as "good copywriting". It isn't. It's a configuration problem. Tone, persona, attribute taxonomy. Defined once. Applied consistently. The actual writing is downstream.

The way out is automation, not bigger teams

For most of the last decade the only proposed solutions to this problem were "hire more copywriters" or "outsource to an agency". Both fail at scale, for the unit-economics reason above. So the problem persisted.

What changed is that you can now define your brand voice, your buyer personas, and your attribute order — once — and apply that configuration to every product in the catalog. Programmatically. Seconds per SKU.

That's the architecture behind EANScan. Drop in an EAN. The platform fetches the source data, runs it through your configuration, and outputs an enriched PDP — title, description, bullets, attributes, structured metadata — that sounds like your store. Your team reviews. Your team approves. The brand stays consistent. The catalog catches up.

If you run e-commerce or catalog at a retailer with 5,000+ SKUs and any of this lands, book a demo. Send 50 EANs from your catalog before the call and we'll run them on the platform first. You see real output on real products. No slide deck.