The beauty marketplace is preparing to launch a Product Detail Page (PDP) for a women's perfume. The goal is to maximize conversion by encouraging shoppers to add the product to their cart or initiate checkout via a "Buy Now" action. Since the reference site provided in the assignment was not accessible, Nykaa, Tira, and Myntra's beauty PDPs were examined to understand common patterns. Typical perfume PDPs feature a strong hero image, clear price and discount information, ratings & reviews, trust badges (e.g., cruelty-free, best seller), a compelling description, variant or size selection, and clear calls to action (CTA). Social sharing badges and recommendations often appear below the fold.
Figma link shared in the next section
Here’s a detailed breakdown of the new PDP features:




5.Customer reviews and highlights

Small view: Mobile site feature breakdown

Detailed Feature list in the figma shared below:
Figma:
https://www.figma.com/design/9ZSkFuy6QRqrTezvxC2OUa/SSBeauty_PDP?node-id=0-1&t=iyKFPOKe6VJQkfze-1
Tools used: Figma was used conceptually to draft the wireframes; Miro for feature breakdown explanation
Objective (O) –Ship a modern PDP that improves purchase confidence, speeds high-intent checkouts, and lifts order value.
Key Results (KR)
| Key result | Measure & target | Rationale |
|---|---|---|
| Improve PDP to Checkout conversion | ≥ X% increase in "PDP session → purchase" conversion rate compared with the current baseline | Conversion directly measures in revenue, improved AOV |
| Increase add-to-cart rate | Add-to-cart rate ( For unique visitors ): Total interaction or impression / Add to Carts. | A higher add-to-cart rate is an early signal of purchase intent; |
| Reduce PDP bounce rate | ≤ 30% bounce rate (visitors leaving without interaction) | Lower bounce rate indicates the page is engaging and informative. |
| Achieve high customer satisfaction | Average PDP product rating ≥ 4.5/5 from user surveys | Ensures the design delights users and builds brand loyalty. |
Note: Cross-Epic Dependencies*:* Analytics instrumentation in Epic 1 (page load, interaction, impression events) powers funnel analysis for features in Epic 2 (checkout optimisations) and Epic 3 (personalised nudges, trust signals). Any delay in Epic 1’s analytics backend work would directly impact the measurement of Epic 2 and Epic 3 features. Similarly, product catalogue APIs from Epic 1 are reused in Epic 2 for availability checks and in Epic 3 for dynamic recommendations.
| Epic | Sprint | High-level tasks | Reasoning | Goal |
|---|---|---|---|---|
| Epic 1: Setting up the core section | Sprint 1 | Frontend:• Implement base PDP design for web & app | ||
| • Implement hero image gallery with thumbnails | ||||
| • Set up responsive layout for large, small, and app views | ||||
| • Integrate Add to Cart & Buy Now flows | ||||
| Backend:• Define table structures for products (variants, sizes, fragrance notes, offers, reviews) | ||||
| • Build queries and APIs• Configure micro-service architecutreAWS Lambda/GraphQL for integration and communication with front-end | ||||
| Analytics:• Implement base tracking for interaction/impression events• Track initial impressions for hero image gallery | ||||
| -Metrics and dashboard for tracking the initial engagement and conversion rates QA : Create test scenarios for the MTE and co-ordinate with teams to understand the user journey and flow | This sprint sets the foundation with data structures, backend APIs, and initial UI so subsequent work doesn’t need re-engineering. | The aim is to increase set up core functionalities, focused on conversion | ||
| Sprint 2 | Frontend: | |||
| • Implement carousels for recommendations and cross-sell | ||||
| • Enhanced features for delivery serviceability integrations and good-to-have features | ||||
| Bandwidth for Spill-over | ||||
| Backend: | ||||
| • Connect carousels for delivery not-serviceable scenario | ||||
| • Configure caching for faster load | ||||
| Analytics:• Track event payload events | ||||
| •implement ad vendor impressions/pageLoad events | ||||
| Design: Share the UI/UX figma that includes the must have features along with good to have components | ||||
| QA : Create test scenarios for the MTE and co-ordinate with teams to understand the user journey and flow | Builds on the base by introducing core product interaction components and ensuring backend support. | |||
| Epic 2: Conversion & engagement features | Sprint 3 | Frontend:• Design and add trust badges (best seller, cruelty-free)• Add offers/coupons module | ||
| Backend:• Implement cart microservice integration | ||||
| • Build offer validation API | ||||
| Analytics:• Event tracking for features launched in this sprint, and dashboards to track the app and user engagement | ||||
| Design: Share the UI/UX figma that includes the must have features along with good to have components | ||||
| QA : Create test scenarios for the MTE and co-ordinate with teams to understand the user journey and flow | Directly targets conversion with purchase-related flows and trust-building elements. | Deploy features proven to boost PDP-to-cart conversion rate by at least X% and checkout initiation rate by Y%, including trust badges, offer modules, and review systems. | ||
| Sprint 4 | Frontend:• Ratings & reviews section (summary, top mentions, review list)• Review submission flow• “See All Reviews” modal | |||
| Backend:• Review storage APIs• Integrate moderation/approval workflow | ||||
| Design: Share the UI/UX figma that includes the must have features along with good to have components | ||||
| QA : Create test scenarios for the MTE and co-ordinate with teams to understand the user journey and flow | ||||
| Analytics:• Event tracking for features launched in this sprint, and dashboards to track the app and user engagement | Increases engagement through social proof and UGC, boosting trust and purchase intent. | |||
| Epic 3: Enhancements & good-to-have features | Sprint 5 | Frontend:• Express checkout option• PDP-level recommendations (related products, trending)• Sticky CTA for mobile | ||
| Backend:• Integrate personalization APIs• Optimize API calls for speed | ||||
| Analytics:• Track checkout, and recommendation engagement metrics | ||||
| Design: Share the UI/UX figma that includes the must have features along with good to have components | ||||
| QA : Create test scenarios for the MTE and co-ordinate with teams to understand the user journey and flow | Adds higher-level UX and conversion boosters; also optimizes performance for smoother experience. | Advanced personalization and mobile-first improvements to increase repeat PDP visits per user and recommendation click-through rate. | ||
| Sprint 6 | Frontend:• App download nudges for small view• Enhanced review filters and media uploads• Smart offers carousel | |||
| Backend:• Support richer media storage• Configure A/B testing for enhancements | ||||
| Analytics:• Integrate features in the sprints, and implementation for interactions/impressions | ||||
| Design: Share the UI/UX figma that includes the must have features along with good to have components | ||||
| QA : Create test scenarios for the MTE and co-ordinate with teams to understand the user journey and flow | Focuses on mobile-first engagement and continuous optimization via testing and feature tracking. |
As a shopper browsing the perfume PDP
I want to easily select the desired size/variant and instantly see price, stock status, and delivery promise
so that I can make a confident purchase decision without unnecessary navigation or page reloads.
Acceptance criteria
Analytics & events
Dependencies / notes
As a returning customer who has bought this fragrance before
I want a fast path to repurchase—Express Checkout that auto-selects my last used address and payment, and a One-click Reorder control—
so that I can complete the purchase in seconds without re-entering details.
Acceptance criteria
Analytics & events
Dependencies / notes
AI for research: Chatgpt, Gemini
Wireframe: Figma
Documentation: Miro
PPT: