How to Create a Complete Fashion PDP Asset Pack (Copy, Images, Video, Feed)

How to Create a Complete Fashion PDP Asset Pack (Copy, Images, Video, Feed)

A product page is not a product photo with a paragraph under it. It is a system: positioning, copy, fit guidance, image plan, on-model crops, PDP video, alt text, SEO, structured data, feed attributes, returns and fit-finder configuration. Each piece is a conversion lever; missing any one of them leaves margin on the table or returns on the books.

This guide walks through the operational workflow to ship a complete PDP for one fashion SKU. It is written for ecommerce managers, content producers, copywriters, and merchandisers who already work on Shopify, SFCC, commercetools, or BigCommerce with a PIM (Akeneo, Bluestone PIM, Plytix) and a DAM. It walks through the Kampana Create a Complete Fashion PDP Asset Pack workflow end to end.

Table of contents

• How the workflow works
• The PDP conversion model
• 6 things to decide before you start
• 12 steps to a complete PDP
• Copy structure that converts
• Image plan and crops that reduce returns
• PDP video that earns autoplay
• Alt text, SEO, and structured data
• Feed attributes and channel sync
• Fit finder, size guide, and returns logic
• Common mistakes to avoid
• FAQ
• Checklist before you ship

How the workflow works

A PDP fails at one of three points: the customer does not understand the product, the customer cannot find the size, or the customer does not trust the visual to match the bulk. The Kampana approach addresses each:

• Copy is structured around the four questions a fashion customer actually asks.
• Image plan covers the angles and crops the return-data shows reduces returns.
• Video earns autoplay by being short, vertical-friendly, and product-accurate.
• Feed and structured data are generated as part of the pack - not a downstream task.

The full workflow is documented at /workflows/ecommerce-pdp-asset-pack. The version below is the practitioner's view.

The PDP conversion model

A fashion shopper asks four questions on the PDP:

1. What is it? (category, silhouette, fabric, fit)
2. Will it fit me? (size guide, fit finder, model wears, reviews)
3. Will it look like the photo? (color accuracy, fabric reality, construction)
4. What is the risk? (returns, shipping, sustainability claims)

Every PDP element exists to answer one of those four. If an element does not, it is decoration.

6 things to decide before you start

1. Which SKU and which colorway is the PDP for?

A SKU with multiple colorways shares a parent PDP with variant images. A capsule with distinct merchandising may justify a separate handle.

2. What is the PDP template architecture?

Above-the-fold (hero gallery + buy box), middle (copy + key features), below-the-fold (fit, materials, care, sustainability, FAQ, reviews, related). Confirm the template and metafield map before generating copy.

3. What is the SEO target?

Primary keyword, secondary keywords, search intent, internal link plan. Keyword research happens before copy, not after.

4. What are the channel destinations?

Site PDP, Google Shopping feed, Meta Catalog, marketplace CSV, social shop. Each has its own attribute requirements.

5. What return drivers do we already see in the category?

From category return-reason data: size, fit, color, fabric expectation. PDP copy and imagery should pre-empt the top driver.

6. Who is the named approver for claims?

Material claims, performance claims, sustainability claims - legal-reviewed and signed before publish.

12 steps to a complete PDP

Step 1: Define the positioning

One sentence: who this is for, what problem it solves, what makes it the brand's version. The positioning anchors every other piece.

Step 2: Run keyword research and lock the SEO target

Primary keyword, supporting keywords, intent (informational, transactional, branded). Map keywords to copy zones.

Step 3: Write the H1 and the buy-box copy

H1 includes the primary keyword and the product type. Buy-box: name, color, price, size selector, add-to-cart, save-for-later, share. No marketing copy in the buy box - buy box is functional.

Step 4: Write the product story (above-the-fold copy)

Two to four short paragraphs answering "what is it" and "why this one". Lead with the customer benefit, support with the construction or fabric fact, close with the styling moment.

Step 5: Write the key features list

Six to ten bullets, each tied to a feature the customer can verify in the imagery or the size guide. No hype, no superlatives without substantiation.

Step 6: Write the fit and sizing guidance

Model height and size worn, fit on body (close, easy, oversize), recommended sizing (true to size, size up, size down) with a one-line rationale tied to review data. Link to the size chart and the fit finder.

Step 7: Write materials, care, and sustainability

Fabric composition with percentages. Care instructions matched to the care label. Sustainability claims with certification references; no unsupported claims.

Step 8: Build the image plan

Hero on-model, front, back, 3/4, fabric detail, hardware detail, construction detail, scale/proportion shot, flat lay. Eight to twelve images. Each image has a defined role.

Step 9: Produce the PDP video

15–30 seconds, vertical-friendly, sound-off legible, showing fabric movement, fit, and a single styling moment. Autoplay-ready (no scene that needs sound to make sense).

Step 10: Write alt text and structured data

Alt text for every image describing the product, color, view, and any contextual styling - for accessibility and image SEO. Structured data: Product, Offer, AggregateRating, Brand, GTIN, MPN, sizes, colors as JSON-LD.

Step 11: Generate the feed payload

Google Merchant: title, description, item_group_id, color, size, gender, age_group, product_type, google_product_category, GTIN, image_link, additional_image_link, availability, price, shipping. Meta Catalog: matching mappings. Marketplace CSV: per-marketplace template.

Step 12: Configure fit finder, size guide, and returns

Size guide complete and bound to category. Fit finder (True Fit, Fit Predictor, Bold) configured with the SKU's fit data. Returns policy linked. Free-return eligibility surfaced if applicable.

Copy structure that converts

Tested copy patterns for fashion PDP:

• H1: product name + key descriptor (e.g., "Wide-Leg Cropped Linen Trouser").
• One-line subhead: the customer benefit or moment.
• Two-paragraph story: what it is, why this version.
• Six to ten bullets: substantive features, not adjectives.
• Fit block: model wears, recommended sizing, fit feel.
• Materials block: composition, hand, care, sustainability.
• FAQ: top three questions surfaced by the reviews of similar SKUs.

Image plan and crops that reduce returns

Returns data shows the highest-impact images, in order:

1. Scale/proportion shot - full-body on-model so the customer reads the silhouette correctly.
2. Detail crop on construction - hem, seam, hardware that the customer wants to verify.
3. Fabric close-up - texture and weave under neutral light.
4. Back view - half of returns are about how the garment sits from behind.
5. Color-true reference - under daylight or D65, so the customer can compare to ambient light.

Skipping the scale/proportion shot is the single most common cause of preventable size-related returns.

PDP video that earns autoplay

A PDP video that requires sound to make sense is a PDP video that does not perform. Rules:

• 15–30 seconds total.
• First two seconds show the garment in motion on body or in scale.
• No voiceover dependency; rely on visual + minimal text overlay.
• Show fabric drape, fit on body, one styling moment, a hardware or construction detail.
• Export in vertical 9:16 and square 1:1 versions for social shop reuse.

Alt text, SEO, and structured data

Alt text rules:

• Describe the product, color, view, and styling context.
• Avoid keyword stuffing; alt text is read by screen readers and Google equally.
• Use unique alt text per image; do not repeat the H1.

Structured data:

• Product, Offer, Brand, AggregateRating as JSON-LD.
• GTIN and MPN where available.
• Sizes and colors enumerated.
• Availability synced to inventory.

A correctly marked-up PDP is eligible for richer Google Shopping placements and image-pack inclusion.

Feed attributes and channel sync

Google Merchant attributes that materially affect performance:

• title: brand + product type + key descriptor + color, within 150 characters.
• description: structured, first 160 characters carry the load.
• item_group_id: required for variant grouping; do not omit.
• color: standardized color value, not a marketing name.
• size: standardized size value.
• gender, age_group, product_type, google_product_category: complete and accurate.
• image_link: PDP master; additional_image_link: up to 10 variants.
• availability, price, shipping: synced to source of truth.

Meta Catalog mirrors most attributes; marketplace CSVs follow their own templates but the source-of-truth data is the same.

Fit finder, size guide, and returns logic

• Size guide bound to the category; matched to the brand's fit block; uses the customer's measurement convention (cm/in toggle).
• Fit finder integrated and seeded with the SKU's fit data; benefits compound with usage.
• Returns policy linked from the buy box and surfaced in the FAQ.
• Free returns or paid returns stated explicitly; ambiguity drives cart abandonment.
• Return reason codes post-purchase tagged for ongoing PDP iteration.

Common mistakes to avoid

• H1 without the primary keyword or the product type.
• No scale/proportion shot. Drives size returns.
• Video that needs sound to make sense.
• Sustainability claims without certification reference.
• Feed payload missing item_group_id (variants disconnect).
• Same alt text on every image.
• Fit guidance contradicting the size guide.
• PDP shipped without legal review on claims.

FAQ

How many images is the right number?

Eight to twelve. Fewer and the customer cannot verify; more and load time becomes the conversion blocker.

Does the PDP need video?

For most fashion categories, yes - particularly for fabric-heavy categories (knits, denim, outerwear, anything with drape). Static imagery cannot show drape and movement.

Should the PDP show price in multiple currencies?

Yes, geo-resolved at the platform level. Currency switching that requires a manual toggle is a friction point.

How do we handle a SKU with 20 colorways?

Group under one PDP with variant images, additional_image_link, and a colorway selector that swaps the gallery. Forking to 20 separate PDPs splits SEO equity.

What about reviews?

Always surface reviews above-the-fold (aggregate rating) and below-the-fold (filtered detail). Review submission flow tagged by size purchased so the corpus is useful for the next refresh.

What about user-generated content?

UGC carousel below the hero is a strong conversion lift. Confirm usage rights before publishing.

Checklist before you ship

• Positioning sentence written and approved.
• SEO target locked.
• H1, story, bullets, fit, materials, sustainability all written.
• Eight to twelve images covering required roles.
• Scale/proportion shot present.
• Video 15–30s, vertical-friendly, sound-off legible.
• Alt text unique per image.
• Structured data (Product, Offer, Brand, AggregateRating) validated in Rich Results Test.
• Google Merchant payload validated (item_group_id, color, size, etc.).
• Meta Catalog and marketplace CSV regenerated.
• Fit finder, size guide, returns linked.
• Claims legal-reviewed.

Run this workflow in Kampana

Kampana automates every step in this guide while keeping a human in the loop wherever it matters. You bring the SKU, the brand voice, and the legal sign-off. Kampana ships the PDP.

Start with the Create a Complete Fashion PDP Asset Pack workflow, or book a contact session to walk through your PDP standard with the team.