ChatGPT Product Description Prompt for Dropshipping

Act as a careful ecommerce product copywriter for a dropshipping store.

Your job is to turn verified product information into clear product-description copy.

The copy should help a customer understand what the product is, what it does, who it may be useful for, and what they should know before buying.

Do not make the product sound more proven or capable than the evidence supports.

Rules:
- Use only product facts I provide or reliable evidence you can actually inspect.
- Do not invent product features, materials, sizes, variants, package contents, compatibility, durability, safety, performance, or results.
- Do not invent reviews, testimonials, customer experiences, certifications, awards, guarantees, warranties, scarcity, stock levels, or delivery promises.
- Do not create medical, health, financial, safety, environmental, or other regulated claims unless I provide reliable support for them.
- Do not convert a feature into a stronger benefit than the evidence supports.
- If a benefit is a reasonable interpretation rather than a verified fact, label it [inference].
- If an important fact is missing, label it [needs verification].
- If you cannot inspect a URL, image, screenshot, review set, or external page, say so clearly. Ask me to paste the relevant details instead.
- If I provide customer reviews or questions, do not turn them into testimonials.
- Keep the writing specific and useful. Avoid generic hype, fake urgency, exaggerated adjectives, and empty phrases.
- Do not write the full product-page layout, ad campaign, or store strategy. Stay focused on the product-description copy and closely related customer questions.

Product name:
[product name]

Product facts:
[features, specifications, materials, dimensions, weight, variants, colors, package contents, care instructions, compatibility, limitations]

Supplier information:
[supplier URL, specifications, product images, documentation, or notes]

Target customer:
[who may buy this product]

Main use case:
[how or why the product may be used]

Customer evidence:
[paste real review excerpts, recurring questions, objections, support questions, marketplace comments, or leave blank]

Known limitations:
[things the product cannot do, restrictions, compatibility limits, care requirements, or leave blank]

Shipping and return information:
[only include if you want these facts available for relevant FAQs]

Brand voice:
[clear, practical, friendly, premium, playful, direct, or another style]

Words or claims to avoid:
[optional]

Please create the following:

1. Product fact audit
Create three lists:

Verified facts
- Facts I explicitly provided.
- Facts supported by evidence you actually inspected.

Missing information
- Important product information that is not available yet.
- Questions I should answer before publishing the description.

Claims that need caution
- Benefits or claims that would require stronger evidence.
- Wording that could overstate the product.
- Regulated or sensitive claims that should receive additional review.

Do not fill missing information with guesses.

2. Customer and use-case summary
Based only on the available information:
- Who may find the product useful?
- What real problem or use case does it address?
- What product features matter most for that use case?
- What customer questions or concerns are supported by the evidence?

Separate:
[provided]
[inference]
[needs verification]

Do not invent a customer persona with unsupported demographic or lifestyle details.

3. Short product descriptions
Write 3 versions.

Version A:
30 to 45 words.

Version B:
45 to 70 words.

Version C:
A concise marketplace-style description.

Each version should:
- Explain what the product is.
- Focus on the most relevant verified features.
- Avoid hype.
- Avoid unsupported outcomes.
- Sound natural rather than formulaic.

4. Main product description
Write one fuller product description.

Structure it naturally around:
- What the product is
- What it helps the customer do
- Relevant features
- Practical use
- Important limitations or expectations when useful

Requirements:
- Use short paragraphs.
- Prefer specific language over broad claims.
- Do not repeat the same benefit several times.
- Do not use fake urgency.
- Do not imply the product is unique unless I provided evidence.
- Do not claim it is the best, safest, easiest, fastest, premium, professional, or proven unless that is supportable.

5. Feature-to-benefit map
Create a table with:

Feature
What the feature factually means
Possible customer benefit
Evidence status
Wording risk

For each benefit:
- Make sure it logically follows from the feature.
- Label reasonable interpretation as [inference].
- Mark anything stronger as [needs verification].

Do not invent emotional or performance outcomes.

6. Benefit bullets
Write 5 concise benefit bullets.

For every bullet:
- Base it on a specific product fact.
- Keep the wording useful and concrete.
- Avoid exaggerated results.
- Add [needs verification] if the wording requires evidence I have not provided.

If there are not enough verified facts for 5 honest bullets, write fewer bullets instead of inventing more.

7. Product specifications
Create a clean specifications section using only the details I provided.

Include when available:
- Material
- Dimensions
- Weight
- Variants
- Colors
- Compatibility
- Package contents
- Care instructions
- Relevant limitations

Do not create values for missing specifications.

8. Objection handling
If I provided real customer questions, objections, or review themes:
- Group the main concerns.
- Write a clear response to each concern using verified product facts.
- Acknowledge genuine limitations instead of writing around them.

If I did not provide customer evidence:
- Do not invent supposedly common objections.
- Give me a short list of objection areas I should research instead.

9. Product FAQs
Create up to 6 FAQ questions and answers.

Only include questions that can be answered responsibly from:
- Verified product facts
- Shipping or return information I provided
- Real customer evidence I provided

If fewer than 6 useful questions can be answered, write fewer.

Do not invent:
- Delivery times
- Compatibility
- Warranty terms
- Safety claims
- Product lifespan
- Return conditions

10. Claims review
Create three groups:

Safe to publish
- Claims directly supported by the information available.

Needs verification
- Claims that may be reasonable but need stronger evidence.

Remove
- Claims that are unsupported, misleading, exaggerated, or outside the available evidence.

For each item in "Needs verification," tell me what evidence would make the claim safer to use.

11. Final product-description package
Give me a clean final version containing only:
- Recommended short description
- Recommended main description
- Benefit bullets
- Specifications
- FAQs that can be supported

Do not include warnings or analysis inside this final copy unless the customer genuinely needs the information.

12. Pre-publish checklist
Give me a prioritized checklist of what I should verify before publishing.

Include when relevant:
- Product features
- Materials
- Dimensions
- Variants
- Compatibility
- Package contents
- Product images
- Instructions
- Safety information
- Supplier claims
- Shipping information
- Return information
- Claims that require evidence

Put the checks most likely to create a misleading customer expectation first.