Product evidence
Record verified facts, seller statements, available visual proof, constraints, and important missing inputs.
Reusable product listing template
A product listing template built around questions, proof, and sequence
Organize a product project before final copy or design begins. The template keeps facts, missing inputs, buyer concerns, content jobs, claim risks, and approvals in one traceable structure.
Reusable across channelsFacts and unknowns kept separateProduction and preflight in one flow
The template sections
A practical handoff for strategy, copy, design, and review
The template is channel-neutral. Platform-specific fields and policies must be added from current official guidance.
Buyer decision map
List concerns, the proof each concern requires, and the risk of communicating without that proof.
Content architecture
Define the hero job, two to six proof blocks, visual hierarchy, three to eight storyboard shots, and prompt needs.
Approval checklist
Track safer claims, statements to avoid, ownership notes, rights, platform checks, and final human sign-off.
How to complete the template
Five passes from raw input to production handoff
Complete the sections in order so attractive creative does not outrun the available product evidence.
Fill the fact sheet
Add the product, audience, specifications, package contents, use context, constraints, and unknowns.
Map buyer concerns
Name the main uncertainties and identify the evidence available or still needed for each one.
Select a direction
Compare three concern-and-proof strategies and record the chosen angle plus refinement notes.
Plan every content job
Assign a purpose and evidence requirement to the hero, proof blocks, images, and storyboard.
Close the preflight
Resolve or explicitly retain needs-input and risk items before copy, media, and channel publication are approved.
Transparent demonstration
A compact template entry for one buyer concern
The sample demonstrates the fields, not a completed customer listing or performance result.
Illustrative template entry — not production content
Leak-resistant travel mug
Channel-neutral template
The seller supplies capacity, materials, external dimensions, lid parts, and care instructions.
Will the mug fit the intended cup holder, and what must be cleaned after use?
Show measured base diameter and an exploded view of the seller-confirmed lid components.
Do not claim universal cup-holder fit or dishwasher compatibility without verified evidence.
Copyable working template
Product listing brief: fields your team can fill in
Use the sections below in a document, spreadsheet, or project tool. Keep unknowns visible and add channel-specific fields from current official guidance.
Channel-neutral manual template. Completing it does not verify a fact, create final marketplace fields, or approve publication.
1. Project context
Define the exact offer and the decision this project is intended to support.
- Product and variant
- Exact model, size, color, quantity, bundle
- Channel and market
- Marketplace or storefront, country, language
- Audience and use
- Who is considering it and for what supported use
- Current problem
- The buyer question or page gap to resolve
- Owner and review date
- Responsible person and next verification date
2. Source register
Record where each fact came from instead of relying on an untraceable combined brief.
- Source
- Specification, instruction, test, image, seller statement
- Source owner
- Person or organization responsible for it
- Facts supported
- Exact statements this source can support
- Date or version
- When the source was issued or confirmed
- Open question
- What this source does not establish
3. Buyer concern map
Create one row for every uncertainty that materially affects product understanding.
- Buyer concern
- The question to answer
- Decision importance
- Why it matters and how early it should appear
- Available evidence
- Fact, image, document, or demonstration
- Missing proof
- Information still required
- Claim risk
- What could be overstated without that proof
4. Selected direction
Document the chosen strategic angle so later copy and media do not drift.
- Leading concern
- The buyer question that leads the page
- Supported value
- The value that follows from supplied facts
- Proof path
- Evidence sequence that supports the direction
- Creative hook
- A bounded, non-factual framing idea
- Refinement notes
- Approved changes and retained limitations
5. Page architecture
Repeat these fields for the hero and every proof block in the intended order.
- Block number and format
- Hero, image, description block, specification, video
- Buyer question
- The uncertainty this block addresses
- Content job
- What the block must explain or show
- Fact and evidence
- The source-backed information it can use
- Owner and status
- Ready, needs input, or risk
6. Media production brief
Use one row per image or scene and retain a real-product approval check.
- Asset job
- Question the image or scene must answer
- Source material
- Approved photo, specification, or required new capture
- Composition or action
- What should be visible and in what order
- Negative constraints
- Details the asset must not invent or change
- Approval check
- Real-product details to compare before use
7. Claim register
Keep proposed language, required evidence, and safer alternatives together.
- Proposed claim
- The statement being considered
- Evidence required
- What would make the statement supportable
- Risk level
- Low, medium, or high with a reason
- Safer alternative
- Bounded wording supported now
- Do-not-say entry
- Wording that must not reach production
8. Publication preflight
Close the project with named owners rather than treating generation as approval.
- Fact check
- Numbers, materials, compatibility, contents, limitations
- Media check
- Product fidelity, rights, captions, generated details
- Channel check
- Current fields, policies, category rules, prohibited claims
- Open issue owner
- Person and due date for each unresolved task
- Final approval
- Approver, date, and source version used
Copy the complete template
Open the plain-text version and copy it into the workspace where your team assigns owners and records sources.
Product listing brief: fields your team can fill in Channel-neutral manual template. Completing it does not verify a fact, create final marketplace fields, or approve publication. 1. Project context Define the exact offer and the decision this project is intended to support. Product and variant: Exact model, size, color, quantity, bundle Channel and market: Marketplace or storefront, country, language Audience and use: Who is considering it and for what supported use Current problem: The buyer question or page gap to resolve Owner and review date: Responsible person and next verification date 2. Source register Record where each fact came from instead of relying on an untraceable combined brief. Source: Specification, instruction, test, image, seller statement Source owner: Person or organization responsible for it Facts supported: Exact statements this source can support Date or version: When the source was issued or confirmed Open question: What this source does not establish 3. Buyer concern map Create one row for every uncertainty that materially affects product understanding. Buyer concern: The question to answer Decision importance: Why it matters and how early it should appear Available evidence: Fact, image, document, or demonstration Missing proof: Information still required Claim risk: What could be overstated without that proof 4. Selected direction Document the chosen strategic angle so later copy and media do not drift. Leading concern: The buyer question that leads the page Supported value: The value that follows from supplied facts Proof path: Evidence sequence that supports the direction Creative hook: A bounded, non-factual framing idea Refinement notes: Approved changes and retained limitations 5. Page architecture Repeat these fields for the hero and every proof block in the intended order. Block number and format: Hero, image, description block, specification, video Buyer question: The uncertainty this block addresses Content job: What the block must explain or show Fact and evidence: The source-backed information it can use Owner and status: Ready, needs input, or risk 6. Media production brief Use one row per image or scene and retain a real-product approval check. Asset job: Question the image or scene must answer Source material: Approved photo, specification, or required new capture Composition or action: What should be visible and in what order Negative constraints: Details the asset must not invent or change Approval check: Real-product details to compare before use 7. Claim register Keep proposed language, required evidence, and safer alternatives together. Proposed claim: The statement being considered Evidence required: What would make the statement supportable Risk level: Low, medium, or high with a reason Safer alternative: Bounded wording supported now Do-not-say entry: Wording that must not reach production 8. Publication preflight Close the project with named owners rather than treating generation as approval. Fact check: Numbers, materials, compatibility, contents, limitations Media check: Product fidelity, rights, captions, generated details Channel check: Current fields, policies, category rules, prohibited claims Open issue owner: Person and due date for each unresolved task Final approval: Approver, date, and source version used
Template scope
A reusable structure does not replace channel requirements
The template organizes decision-making but cannot establish factual accuracy or complete platform-specific fields.
The template is not an automatic marketplace import, listing builder, or publishing integration.
It does not include guaranteed-current field limits, category attributes, SEO keywords, or prohibited-claim rules for every channel.
It does not produce final copy, final design files, legal approval, or a performance forecast.
Media prompts and generated drafts require real-product comparison and rights verification.
Teams should add their own owners, source links, approval dates, and channel-specific checks.
Next step
Turn the template into a guided product project
Use Aisle to collect the inputs, expose gaps, compare directions, and assemble the structured pack behind the handoff.