PDP Process & Roles
How a Product Detail Page moves from a blank draft to live on ecosa.com.au - who owns each step, who needs to review it, and where it happens in this console.
Ownership model
This console is owned and driven end-to-end by Ecommerce - creating PDPs, drafting content, sourcing assets, and handing off to dev. Kristy and Izy aren't gatekeepers of the whole page; they review specific sections that are their domain, then Ecommerce carries the PDP the rest of the way.
Who's who
| Name | Role | What they do here |
|---|---|---|
| Naomi (acting) | Ecommerce Manager vacant | Owns the console end-to-end while the role is vacant - drives every PDP through the process below |
| Lenie | Ecommerce Coordinator | Day-to-day PDP creation and editing, internal QA, and following up on CRO Analyzer findings |
| Kristy | Copywriter | Reviews and refines copy blocks: KSP/Short Description, Features, Materials summary, Care Instructions, FAQ |
| Izy | Digital Designer | Reviews assets pulled from Box and any custom design assets (award badges, diagrams, overlays) |
| Jam | Development Lead - Front End | Builds/maintains the Storyblok component and page template from the Ready-for-Dev export |
| Alvin | Development Lead - Back End | Wires product/warehouse data, SKUs, and any custom logic (e.g. conditional gallery rules) |
The process
Ecommerce drives every stage below - the role chips show who else is involved.
Set Up & Draft Content
Create the PDP, pull real product data, and get a first content draft in place.
Visual & Data Enrichment
Pull gallery images from Box, add badges/diagrams, and fill in variants, measurements, shipping and warranty.
Internal QA
Run the data-accuracy check, preview across Desktop/Tablet/Mobile, and confirm against the PDP Template rules.
Ready for Dev Handoff
Mark the PDP "Ready for Dev" and export the Storyblok-shaped content package.
Build & Storyblok Entry
Take the export (and Figma designs for anything new) into Storyblok and wire any custom logic.
Preview & Sign-off
Check the real render on staging before it goes live.
Publish
Goes live on ecosa.com.au.
Monitor & Iterate
Track performance and content gaps in the CRO Analyzer, then loop back to improve.
Who reviews what
| Console section | Drafted by | Needs review from |
|---|---|---|
| Basics, SEO, Variants, Trust Badges, Measurements, Shipping, Warranty, Awards | Ecommerce | — |
| Short Description/KSP, Features, Materials summary, Care Instructions, FAQ | Ecommerce | Kristy (copy & brand voice) |
| Gallery & Assets, award badge visuals, measurement diagrams | Ecommerce (sourced from Box) | Izy (correct/final assets, matches Figma) |
| Ready-for-Dev export, Storyblok entry, custom page logic | Ecommerce | Jam & Alvin |
Where this happens in the console
| Stage | Console page / action |
|---|---|
| Set Up & Draft Content | + Create New PDP, then the Basics and content steps in the Editor |
| Visual & Data Enrichment | Editor → Gallery & Assets, Variants, Measurements, Shipping & Warranty steps |
| Internal QA | Editor's data-check action, plus Preview (Desktop/Tablet/Mobile) and the PDP Template reference |
| Ready for Dev Handoff | Editor → mark status + Export |
| Monitor & Iterate | CRO Analyzer - performance opportunities, content gaps, and ad-vs-content alignment |