AI prompts for product descriptions that answer buying questions

Most product descriptions are written as praise. Premium materials, exceptional comfort, designed to last. None of it answers the question the buyer is actually stuck on, which is usually something narrow and practical: will it fit through my door, does it come with the bracket, how do I wash it.

Product descriptions convert when they resolve the specific uncertainty standing between the buyer and the checkout. These five prompts work that way — a core writer driven by real customer questions, a variant for technical products, a variant for gifting, a review prompt that catches unverifiable claims, and a batch prompt for a full catalogue.

Why do product descriptions fail to convert?

Because they are written from the seller’s knowledge rather than the buyer’s ignorance. Everyone in the business knows the sizing runs small; nobody has written it down, because it is obvious to them.

Buyers who cannot resolve an uncertainty do one of two things. They leave, or they buy and return. The second is worse: you pay for the shipping both ways, the item comes back unsellable often enough to matter, and the customer’s experience of your brand is a refund.

The second failure is structural. Descriptions tend to lead with the most flattering information, but the buyer is scanning for the disqualifying information. They want to rule the product out quickly, and burying dimensions three paragraphs down does not help them buy — it just delays the decision.

Third, most product descriptions have no idea what question they are answering, because nobody looked at the support inbox before writing them.

Where do the questions for product descriptions come from?

Four places, all of which you already have. Pre-sales messages, because every question asked before purchase is a description that failed. Return reasons, because “not as expected” is a copy problem wearing a logistics costume. Reviews, especially the three-star ones, which explain what the buyer wrongly assumed. And the on-site search log, where people type the attribute they cannot find.

Collect the top ten recurring questions per category before writing anything. That list is the actual brief. Writing product descriptions without it is guessing, and the guess will be shaped by what the business finds interesting rather than what the customer finds unclear.

The core prompt for product descriptions

You are writing a product description for an ecommerce site. Your
job is to answer the questions that stop people buying, in the
order they ask them.

Product: {{name, category}}
Specifications: {{dimensions, weight, materials, capacity,
  power, compatibility — everything measurable}}
What is in the box: {{list}}
Top customer questions: {{the recurring pre-sales questions,
  most frequent first}}
Top return reasons: {{list}}
Who it is for: {{the use case it genuinely suits}}
Who it is not for: {{the use case people wrongly buy it for}}
Care and warranty: {{detail}}
Price and delivery: {{price, delivery time, returns window}}

If the customer-questions field is empty, stop and say you need
it. Without it this is decoration, not a description.

The output format

Write in this order:

1. ONE SENTENCE — what it is and who it is for. No adjectives.
2. THE ANSWERS — each top customer question answered directly,
   as its own short paragraph or bullet. Highest-frequency
   first. Do not phrase these as questions; just answer them.
3. THE SPECIFICS — measurements and materials as a scannable
   list, with units.
4. IN THE BOX — exactly what arrives, including what does not.
5. NOT FOR — the use case it does not suit, stated plainly.
6. CARE AND WARRANTY.

Rules:
- Every claim must trace to a specification or a stated fact.
- Ban: premium, luxurious, exceptional, perfect, ultimate,
  game-changing, revolutionary, must-have, unrivalled.
- No adjective may appear without a measurement nearby that
  supports it. "Lightweight" needs the weight.
- The NOT FOR section is mandatory. It reduces returns more
  than any other part of the description.
- Do not repeat the product name more than three times.
- If a top return reason is not addressed by section 2, say so
  at the end as a note to the copywriter.

A worked example

The brief

Product: Ashcroft folding desk, home office category
Specs: 100x50cm surface, 74cm high, folds to 8cm deep, 14.2kg,
  solid beech top, powder-coated steel legs, 40kg load
What is in the box: desk, 4 felt pads, allen key. No cable tray.
Top questions: does it need assembly / will it fit a 27-inch
  monitor and a laptop / how heavy is it to fold alone / does
  it wobble when typing / can it take a monitor arm
Top return reasons: too heavy to move as expected, expected a
  cable tray
Who it is for: someone working from a room that has to become a
  living room again in the evening
Who it is not for: permanent setups with heavy multi-monitor rigs
Care: wipe with a damp cloth, re-oil the top annually
Warranty: 5 years on the frame, 2 on the top
Price: £249, delivery 3-5 days, 30-day returns

The result

A folding beech desk for a room that has to go back to being a living room in the evening.

No assembly. It arrives built. Unfold the legs, stick on the felt pads, done.

A 27-inch monitor and a laptop fit on the 100 × 50cm top with room to write beside them.

It weighs 14.2kg. One person can fold and carry it, but it is a deliberate two-handed job, not something you move one-handed while holding a coffee. If you plan to move it daily, that weight is the thing to think about.

It does not wobble when typing. The steel legs lock at full extension; the felt pads matter for this, so fit them.

A monitor arm clamps to the rear edge — the beech is 22mm and takes a standard clamp. Total load limit is 40kg.

In the box: the desk, four felt pads, one allen key. There is no cable tray and none is available for this model.

Not for a permanent multi-monitor setup. If the desk never folds away, buy a fixed one — you are paying for a hinge you will not use.

Both return reasons are addressed head-on. The weight is not softened, and the missing cable tray is stated twice, because it caused returns.

The prompt for technical products

You are writing a product description for a technical product
where the buyer's main risk is incompatibility.

Product: {{name}}
Full specification: {{paste datasheet values}}
Compatibility: {{what it works with, and what it does not}}
Required to function: {{anything needed but not included}}
Standards and certifications: {{list}}
Common wrong purchase: {{what people buy this instead of, or
  by mistake}}
Installation: {{who can install it, what tools, how long}}
Top customer questions: {{list}}

Write in this order:
1. WHAT IT IS — one sentence, using the term the buyer searches.
2. WILL IT WORK WITH YOURS — the compatibility answer, first,
   as a clear yes/no structure by scenario.
3. WHAT ELSE YOU NEED — anything required and not included.
4. SPECIFICATION — full table, every value with its unit.
5. INSTALLATION — realistic time, tools, and whether it needs a
   qualified person.
6. IF YOU ACTUALLY NEED — the common wrong purchase, and what to
   buy instead.

Rules:
- Never round a specification value or drop a unit.
- Do not claim compatibility that is not in the input, even where
  it is likely. State it as untested instead.
- Section 6 loses you one sale and prevents one return and one
  bad review. Keep it.
- If a certification is claimed, include the standard number.

The prompt for gifting

You are writing a gift-context version of an existing product
description. The buyer is not the user, which changes every
question they have.

Existing description: {{paste}}
Price: {{price}}
Recipient it suits: {{who}}
What could go wrong as a gift: {{sizing, taste, duplication,
  needing setup}}
Gift logistics: {{gift wrap, receipt options, delivery cut-off,
  extended returns over holidays}}

Write 120-160 words answering the gift-buyer's questions:
- Will they already have one, and how do I tell.
- What if it is the wrong size or not their taste.
- Does it need assembly or an account before it works.
- Will the price be visible.
- When must I order by.

Rules:
- Do not restate the specification. Link to it.
- Say plainly if the item is a poor gift for someone whose
  preferences you do not know.
- No sentimental framing. The buyer is anxious about being
  wrong, not short of feeling.

The review prompt: catching unverifiable claims

Audit the product description below against the specification.

Output, quoting exact text:

1. UNSUPPORTED CLAIMS — anything not traceable to the
   specification or stated facts.
2. NAKED ADJECTIVES — every descriptive adjective with no
   nearby measurement supporting it.
3. UNANSWERED QUESTIONS — each listed customer question, and
   whether the description answers it. Say where.
4. UNADDRESSED RETURN REASONS — each return reason, and whether
   the description now prevents it.
5. REGULATED CLAIMS — anything implying a health, safety,
   environmental, efficiency or performance benefit that would
   need substantiation. Flag every one.
6. MISSING EXCLUSIONS — anything a buyer would reasonably
   assume is included that is not.

SPECIFICATION: {{paste}}
QUESTIONS: {{paste}}
RETURN REASONS: {{paste}}
DESCRIPTION: {{paste}}

Category five is the one with teeth. Environmental and performance claims in product descriptions fall under the CAP Code, and “eco-friendly” or “twice as fast” written by a model is a claim you now have to substantiate.

Writing product descriptions across a catalogue

You are writing descriptions for {{n}} products in one category.
A buyer will compare several, so they must be structured
identically and differ only where the products differ.

Category-wide facts: {{delivery, returns, warranty, care —
  anything true of every product}}
Category-wide questions: {{the questions asked about everything
  in this category}}
Voice reference: {{paste one approved description}}
Products: {{table — name, specs, box contents, product-specific
  questions, return reasons, not-for}}

For each product, write the description in the established
format.

Rules for the batch:
- Every description answers the category-wide questions, in the
  same order, in the same words where the answer is the same.
- Never carry a product-specific spec, question or exclusion
  between rows.
- If two products in the batch are hard to tell apart from their
  descriptions, output
  INDISTINCT: {{A}} / {{B}} — {{what a buyer cannot tell}}
- Any row with no customer questions: output
  ROW {{n}} NEEDS questions and write nothing.

Common mistakes with product descriptions

Skipping the customer-questions field because you think you know the product. You do — that is the problem. The knowledge that makes you fast is the knowledge that makes you blind to what is unclear.

Deleting the “not for” section because it feels like discouraging a sale. It is the highest-ROI paragraph in most product descriptions. A prevented return saves two shipping legs, a restock, and a review that costs you future sales.

Letting the model keep an adjective by adding a vague number. “Lightweight at just 14.2kg” is not honest framing; 14.2kg is not light. The rule is that the measurement supports the adjective, not that it appears nearby.

Writing once and never revisiting. Product descriptions should be updated whenever a new question recurs in the inbox. The description is a living answer to a changing set of misunderstandings.

What to check before product descriptions go live

Check every measurement against the actual product, not the spec sheet, at least once per category. Supplier data is wrong often enough that a description built on it will eventually be wrong in a way a customer discovers.

Read the description as someone who is about to spend the money and is looking for a reason not to. If the disqualifying information is not findable in ten seconds, you are optimising for clicks rather than for orders that stay.

Confirm that any performance, health or environmental claim has documentary substantiation on file before it publishes, and that nothing implies a comparison you have not tested.

Finally, track returns by reason for the eight weeks after a rewrite. It is the only measurement that tells you whether the description worked, and it is more informative than conversion rate, because a description can lift conversion and cost you money.