Send cold traffic straight to the product page when the product explains itself in one photograph and the price is low enough that being wrong doesn't sting. Build a landing page when either of those conditions fails. That's the whole rule. The ecommerce landing page vs product page question only gets complicated because most people ask it as a design question when it's a pricing and awareness question.
A product page assumes the visitor already wants the thing and is checking details: size, colour, delivery date, return window. A cold-traffic landing page assumes the visitor has never heard of you, doesn't know this product category exists, and is one thumb-flick from Instagram. Those are different jobs. Give a stranger the page built for a returning customer and you pay for the mismatch in CPA.
Ecommerce landing page vs product page: what actually differs
Not the aesthetics. The order of information.
A Shopify PDP puts price and add-to-cart within the first 600 pixels on mobile, because someone who arrived from a Google search for your brand plus "buy" needs the fastest possible path to checkout. Everything below is reference material they may never scroll to.
A cold landing page inverts that. Price appears after the reason to care. There's one call to action, repeated four or five times down the page, and no navigation bar tempting people into the About Us section. No collection links. No related products carousel offering seven alternatives to a person who hasn't yet decided they want one. The page has a single exit and it's the buy button.
So the real question isn't which template is better. It's whether your visitor needs the reason-to-care section at all.
Price point decides this more often than creative does
Rough bands we use when planning a campaign for an Indian D2C brand. Adjust for your margin, but the shape holds.
- Under ₹800. Send them to the PDP. The decision is cheap enough that a good photo, a clear price and free shipping over some threshold does the work. A landing page here usually adds friction and a page-builder script.
- ₹800 to ₹3,000. PDP, but an enriched one. This is where most brands leave money on the table. Same template, extra sections that only appear on ad-driven traffic: ingredient or material breakdown, a two-line founder note, three review screenshots with faces, a shipping and returns block written in plain language. Landing page only if you're selling something the buyer has never seen before.
- ₹3,000 to ₹15,000. Landing page, most of the time. At this price a stranger wants to know why yours costs what it costs. The PDP has no room for that argument and the argument is the sale.
- Above ₹15,000. Landing page, and stop pretending the transaction completes in one session. The page's job is a WhatsApp conversation, a callback, a size consultation or a showroom visit. We've seen ₹40,000 furniture campaigns judged on same-session ROAS and killed while the phone was ringing.
Jewellery is the sharpest version of this. A ₹90,000 gold chain sold to cold traffic is not an add-to-cart. It's a request for a rate breakdown and a conversation, and the page that converts is the one that shows how the price was built rather than just asserting it.
Awareness stage is the other half of the call
Eugene Schwartz's five levels of awareness is still the most useful frame here, and it maps cleanly onto Shopify destinations.
If the buyer is most aware (they know your brand, they know the product, they're waiting for a reason) send them to the PDP with the offer in the ad. Retargeting, abandoned cart, branded search. Landing page is wasted work.
If they're product aware (they've seen three competitors and want to know why you) the PDP can work if it carries comparison content. Most don't.
If they're solution aware (they know they want a cold-pressed oil, no idea whose) you need a page that positions. Could be a landing page, could be a collection page with a strong header.
If they're problem awareor unaware, a PDP will bounce them at eighty percent and you'll blame the creative. These people need to be told there's a category before they're told there's a price. That's a landing page, and it's usually 1,200 words with a video.
The trap: brands running one ad set against a broad Meta audience are hitting all five levels at once, then sending everyone to the same URL. Split the campaign by awareness before you split the page.
The COD wrinkle nobody accounts for
An Indian cold-traffic funnel has a second conversion event that a US funnel doesn't: does the parcel get accepted.
A landing page gives you room to influence payment method in a way a PDP doesn't. Put a prepaid incentive on the page itself, ₹50 or ₹75 off, framed as a discount rather than a COD penalty. State the COD handling fee before checkout, not at it. Add a one-line delivery promise with a real number of days for metros and a different one for the rest.
The arithmetic is worth doing. If cold traffic on a PDP converts at 1.4% with 70% COD and a 28% RTO rate on those COD orders, your effective conversion is 1.4% × (0.30 + 0.70 × 0.72) = 1.13%. Nudge the mix to 50% prepaid on a landing page and hold the same 1.4%, and you get 1.4% × (0.50 + 0.50 × 0.72) = 1.20%. That's a 6% lift before you've improved a single word of copy, and it comes with less reverse logistics and less working capital stuck in transit.
When the product page wins outright
Say it plainly, because agencies rarely do: a good enriched PDP beats a mediocre landing page, and most landing pages built in a hurry are mediocre.
The PDP has structural advantages. It's indexed, so it earns organic traffic between campaigns. It has real reviews attached with schema markup. It carries variant logic, inventory truth and Shop Pay. It's the page your team already maintains, so the price is right and the stock status isn't lying. A page-builder landing page tends to rot: the offer expires, the sizes change, nobody updates it, and six months later you're paying to send traffic to a ₹1,799 price that's now ₹2,099.
If you sell one hero SKU at ₹1,500, run ₹2 lakh a month in ads and have two people on marketing, spend the effort on the PDP. Add the sections. Fix the images. Move the reviews up.
Do the maths before you commission the build
A campaign landing page done properly costs real money, whether that's agency time or your own. So check whether the lift can pay for it.
Take a ₹2,499 product, ₹50,000 of monthly Meta spend, a ₹18 CPC. That's about 2,778 clicks. At a 1.1% PDP conversion rate you get roughly 30 orders, or ₹75,000 in revenue. Push conversion to 1.9% on a landing page and you get 53 orders, ₹132,000. The extra 23 orders at a 40% contribution margin of ₹1,000 each is ₹23,000 of additional gross profit per month at that spend level.
If the page costs ₹60,000 to build, it pays back in under three months and everything after is upside. If you're spending ₹15,000 a month on ads, the same page takes nearly a year to pay for itself and you should not build it. Scale decides.
Build a campaign template, not a graveyard of one-off pages
The version that survives contact with a real marketing calendar: an alternate Shopify product template. Duplicate your PDP template, strip the navigation and the related-products section, add three or four content blocks driven by metafields, and you have a page that's structurally a landing page but inherits price, stock, variants and reviews from the product itself. Point the ad at /products/handle?view=lp and you're done.
Festive season is when this pays. In the run-up to Diwali you're not building one page, you're building eleven, and eleven page-builder pages each loading their own CSS is how a store that scored 62 on mobile in August scores 34 in October. We've had to undo exactly that more than once, usually on the Tuesday before a sale goes live.
Speed matters more on cold traffic than anywhere else, because there's no brand loyalty to hold a stranger through a four-second load. Getting LCP under 2 seconds on a landing page with a hero video is a real piece of work: preload the poster frame, defer the video, ditch the custom font or subset it. Our notes on Shopify speed optimization cover the mechanics.
The third option: a collection page
Overlooked, and often the right answer. When the ad promises variety rather than one product, sending traffic to a single PDP is a bait-and-switch and sending it to a landing page is a wasted step. Cold traffic that wants to browse should land on a merchandised collection: a short header that carries the ad's promise, the best sellers first, filters that actually match how people shop.
The failure mode is a 400-SKU collection with Shopify's default sort and a filter menu offering "Availability" and nothing else. Someone who clicked an ad for oversized cotton shirts should be able to get to their size in one tap. If your catalogue is big enough that this is a problem, FilterPro handles the filtering and search side without a theme rebuild.
Test it honestly or don't bother
At a 1.2% conversion rate, 300 sessions per variant gives you three or four orders on each side. Three versus five orders is noise, and a decision made on it is a coin toss with extra steps. You need thousands of sessions per arm to separate a 1.2% from a 1.8%, which at ₹18 a click means real budget and two to three weeks.
So: run the two destinations as separate campaigns with matched creative and matched budget, judge on cost per delivered order rather than ROAS, and let it run past the first weekend. Then check the awkward cases. A landing page that wins on a broad prospecting audience will often lose on retargeting, because a warm visitor doesn't want to read the pitch again. Different pages for different temperatures is not over-engineering. It's the point.
If you're not sure which of your top campaigns is landing on the wrong page type, send us the three URLs you're currently spending the most on. Our free audit will tell you which ones need a landing page and which ones just need six sections added to the PDP you already have.