Amazon and Marketplace Listing Builder
Turn verified product specifications into marketplace listing fields with length checks, image briefs, and explicit compliance flags.
Draft a title, five bullets, description, A+ outline, backend terms, and variation names from catalogue data. Review the included counts and policy flags before uploading; neither is a platform approval.
Ready-to-use prompt
The prompt
Copy it as-is, then swap the bracketed placeholders for your own details before running it.
Role: You are a marketplace listing specialist.
Context:
- Marketplace: {{marketplace}}
- Product: {{product_name}}
- Brand: {{brand}}
- Specifications: {{specs}}
- Pack size and variations: {{variations}}
- Target search terms: {{keywords}}
- Main competing listings: {{competitors}}
- Category character limits if known: {{limits}}
Task: Produce:
1. Title, within the stated character limit, in brand + product + key attribute + size order, with the character count shown
2. Five bullet points, each opening with a capitalised benefit phrase then one sentence of proof, each under 200 characters with counts shown
3. Product description of 150-250 words in plain paragraphs
4. A+ content outline: five modules with the purpose and the image brief for each
5. Backend search terms, deduplicated, no repeats of words already in the title
6. Variation naming scheme if variations exist
Then run a compliance check and list any line that risks a policy violation: medical or curative claims, competitor names, guarantees, promotional language, contact details, or subjective superlatives.
Rules:
- Show a character count next to every length-limited field.
- Never repeat a keyword between title and backend terms, it wastes indexing space.
- No claim without a supporting spec.
Finish with: the compliance flags list, or the words NO FLAGS.Estimated results
Editor's note
Why this prompt matters
Marketplace copy starts with evidence, not adjectives. A useful brief identifies what the product is, which variant the customer receives, and what the seller can substantiate. This prompt turns that brief into structured listing fields while separating persuasive copy from a final risk review.
For a worked example, consider a single 750 ml polypropylene food container, measuring 18 × 12 × 6 cm, with a snap lid. Those facts support capacity, dimensions, material, and closure wording. They do not establish leakproof performance, microwave suitability, or dishwasher safety. Missing evidence should remain missing, rather than becoming a plausible-sounding benefit.
Anatomy
Prompt engineering breakdown
Role
The marketplace specialist role focuses the response on catalogue accuracy and constrained listing copy rather than broad campaign messaging.
Context
Product, brand, specifications, and variations establish catalogue truth. Keywords guide vocabulary; competitors supply positioning context. Marketplace and limits determine applicable fields and boundaries.
Goal
Produce one reviewable listing package from supplied evidence, without inventing differentiators or treating missing inputs as permission to guess.
Constraints
The evidence rule limits claims. Length rules constrain presentation. Compliance categories create a review checklist, but do not cover every marketplace restriction.
Output format
Ordered fields, inline counts, module briefs, and a final flag list make review and transfer easier. Remove editorial counts before uploading copy.
Why this structure works
Role sets scope, Context supplies evidence, Task defines deliverables, and Rules constrain execution. Keep that skeleton and the {{lowercase_snake_case}} variable convention unchanged.
What you'll get
Expected output
Expect these fields in sequence:
- A counted title ordered as brand, product, key attribute, and size.
- Five bullets under 200 characters each, with capitalised benefit openings, supporting sentences, and counts.
- A 150–250-word description in plain paragraphs.
- Five A+ modules, each with a purpose and image brief.
- Deduplicated backend search terms excluding title words.
- Variation names when applicable.
- Specific flagged lines, or
NO FLAGS.
For the container, a grounded bullet could read: “CHECK YOUR FIT — The container measures 18 × 12 × 6 cm.” An A+ image brief could request a dimension diagram rather than an unsupported spill test.
Under the hood
Why this prompt works
The field-by-field task reduces omissions, while benefit-plus-proof bullets tie selling points to supplied evidence. A separate compliance pass makes risky lines easier to locate and revise. Counts expose potential upload problems but still need independent validation.
Title/backend deduplication is an explicit space-management rule here, not a universal explanation of marketplace indexing. Search behaviour and field support differ by channel; this draft cannot establish indexing, discoverability, or conversion outcomes.
Model fit
Best AI models for this prompt
ChatGPT
A practical primary option for assembling the requested fields and iterating against supplied limits. Ask it to recheck revisions, but verify counts with a spreadsheet or script; generated counts can be wrong.
Claude
Useful for reviewing whether benefits overstate the supporting specifications and for tightening repetitive bullets. It still needs current policy text and cannot certify compliance.
Gemini
Useful when working through pasted competitor excerpts and structured catalogue information. Keep competitor observations separate from product evidence. Access to browsing or files depends on the interface; do not assume any model has inspected live listings or current policies.
When to use
- Launching a SKU with verified specifications and category requirements.
- Converting DTC copy into constrained marketplace fields.
- Standardising variant names across an existing catalogue.
- Reworking unclear listings after separately diagnosing traffic, availability, pricing, and offer issues.
When not to use
- As final approval for medical, safety, environmental, or certification claims requiring specialist review.
- When variant data conflicts; resolve the catalogue first.
- As an Amazon-shaped upload template for a channel without equivalent fields.
- To diagnose ranking problems or replace channel-specific keyword research.
Get more from it
Pro tips
- 1
Put the marketplace locale, category, and current field limits in {{marketplace}} and {{limits}}. Identify unknown limits explicitly instead of accepting the model's remembered defaults.
- 2
Keep {{specs}} factual. If audience context matters, add a clearly labelled intended-use note there; the prompt has no separate audience variable, and audience assumptions must not become product claims.
- 3
Validate title and bullet counts including spaces and punctuation. Where backend limits use bytes, check encoding separately: a character count is not a byte count.
- 4
Confirm A+ eligibility and available module types before commissioning images. Treat the five-module output as a creative outline, not a guaranteed publishable layout.
Don't ship this
Common mistakes
✗ Treating competitor copy as supporting evidence.
Fix — Use {{competitors}} to examine positioning and vocabulary, never to inherit claims, certifications, or branded terms.
✗ Assuming NO FLAGS means approved.
Fix — It only reports this model's review. Check current category policies, restricted terms, imagery, and required disclosures separately.
✗ Adding filler to reach five benefits.
Fix — If specifications are thin, request missing facts. Do not turn a snap lid into a leakproof claim.
✗ Letting pack size drift between fields.
Fix — Cross-check title, bullets, description, images, and variation labels against {{variations}} before upload.
People also ask
Frequently asked questions
Q.Does this work for marketplaces other than Amazon?
Yes. Name the marketplace and its category character limits in the context block and the structure adapts. The compliance pass covers claim types most marketplaces restrict.
Q.Why must backend keywords never repeat the title?
Because marketplace indexing already counts the title terms. Repeating them in backend fields spends limited character space on words you are already indexed for instead of new ones.
Q.Can I trust the compliance check?
Treat it as a first-pass filter, not legal advice. It reliably catches curative claims, implied guarantees and competitor mentions, but regulated categories still need human or legal review.