Last updated: October 15, 2026
A PDP, or product detail page, is the page dedicated to a single product in an online store. It carries that product's images, title, price, variant options, description, shipping and returns information, reviews, and the add-to-cart button. It is sometimes called a product display page or simply a product page. The three terms mean the same thing and are used interchangeably across the industry.
If a shopper is going to buy, the PDP is where they decide. On a well-run store, 60–70% of revenue is won or lost on this one page type. Every other page (homepage, collection page, search results, ads) exists to route someone here.
That matters more than the definition itself: a store can have excellent traffic, a fast site and a clean brand, and still convert badly because its PDPs are doing the wrong job.
What a PDP contains
A product detail page has a fairly stable anatomy across ecommerce. These are the elements shoppers expect, roughly in the order they look for them:
| Element | What it answers |
|---|---|
| Product images and video | "What does it actually look like?" |
| Product title | "Is this the right item?" |
| Price (and compare-at price) | "What does it cost?" |
| Variant selectors | "Is it available in my size/colour?" |
| Add-to-cart button | "How do I buy it?" |
| Shipping and delivery info | "When will it arrive?" |
| Returns policy | "What if it's wrong?" |
| Product description | "Tell me the details" |
| Specifications | "Will it fit / work with X?" |
| Reviews and ratings | "Do other people like it?" |
| Cross-sells | "What goes with it?" |
A page missing any of the first six will usually underperform regardless of how good the rest is. The ones below the fold matter, but they matter second.
PDP vs PLP: the difference
These two get confused constantly, and they do opposite jobs.
| PLP (product listing page) | PDP (product detail page) | |
|---|---|---|
| Shows | Many products | One product |
| Also called | Collection, category, catalogue page | Product page, product display page |
| Shopper's question | "What are my options?" | "Should I buy this one?" |
| Shopify URL | /collections/running-shoes |
/products/nimbus-26 |
| Shopify template | collection.liquid |
product.liquid |
| Job | Narrow the choice | Close the sale |
| Usually ranks for | Category terms ("running shoes") | Product terms ("asics nimbus 26 size 10") |
The practical consequence: a PLP should make comparison easy (filters, sorting, clear thumbnails, price visible). A PDP should remove doubt (detail, proof, logistics, and one obvious action).
Deeper comparison: PDP vs PLP: Which Page Should Rank, and For What
What a PDP looks like on Shopify
On Shopify, every product you create automatically gets a PDP at /products/<handle>. The template is product.liquid (or product.json with sections on Online Store 2.0), and the theme decides what appears and in what order.
Three things are worth knowing:
1. Every product gets one whether you want it or not. Products you never intend to sell directly (samples, bundle components, internal SKUs) still generate indexable pages. Those should be excluded from search engines, not left to dilute the site.
2. Variants share a single PDP by default. One product with five colours is one page with five variant options, not five pages. That is usually right, but for products where colour has real search demand of its own, splitting can be worth testing.
3. Online Store 2.0 allows per-template PDPs. You can give a product category its own layout (a size guide block for apparel, a spec table for electronics) without touching every other product.
Why the PDP decides revenue
The PDP is the last page before intent becomes money, and it is the only page where every objection has to be answered at once. A shopper on a product page is asking, in sequence:
- Is this the right thing?
- Can I see it properly?
- Does it come in what I need?
- What will it cost me in total, including shipping?
- When will it arrive?
- What happens if I'm wrong?
- Does anyone else think it's good?
Miss any one of those and the shopper leaves to find the answer elsewhere, usually on a marketplace that already answers it. Most PDP conversion problems are not design problems. They are unanswered-question problems.
The fixes, in order of impact: Shopify Product Page Optimization: Complete PDP Guide
Common PDP mistakes
- Price and add-to-cart below the fold on mobile. Over half of ecommerce traffic is mobile; if the buy action needs a scroll, a measurable share never sees it.
- Shipping cost revealed only at checkout. The single largest driver of cart abandonment.
- Dropdowns for colour. Swatches outperform dropdowns consistently: shoppers choose what they can see.
- Description written for the brand, not the buyer. Product copy that opens with heritage and positioning rather than what the thing is and does.
- Reviews buried. Social proof that requires scrolling past the description does less work than a star rating near the title.
- One image. The expectation is 5–8, including scale, detail and in-use shots.
Frequently Asked Questions
What does PDP stand for in ecommerce?
PDP stands for product detail page. Some teams and platforms say product display page instead; both refer to the same page: the one showing a single product with its images, price, options and add-to-cart button.
Is a PDP the same as a product page?
Yes. "Product page", "product detail page" and "PDP" are used interchangeably. PDP is simply the industry shorthand, more common inside ecommerce and merchandising teams than in customer-facing language.
What is the difference between a PDP and a PLP?
A PLP (product listing page) shows many products so a shopper can compare and narrow down, such as a collection or category page. A PDP shows one product in full so a shopper can decide to buy. On Shopify, a PLP lives at /collections/... and a PDP at /products/....
How many images should a PDP have?
Five to eight for most categories. Include at least one scale reference, one detail shot and one in-use image. Apparel and furniture generally need more; simple consumables need fewer.
Should every product have its own PDP?
Every product will get one automatically on Shopify. Whether it should be indexable is a separate question: bundle components, samples and internal SKUs usually should not be.
Vil du ha et konkret tall for din butikk?
Send oss URL-en og størrelsen på katalogen. Du får et fastpristilbud tilbake med oversikt over hvilke maler det dekker. Ingen samtale nødvendig med mindre du ønsker det.
Få pristilbud
