Generated product copy fails in a distinctive way. It is grammatical, well organised, and utterly forgettable, because it converts every fact it is given into an adjective. A product that ships in two days becomes "fast delivery". A material that resists scratching becomes "premium quality". Everything is elevated, so nothing stands out.
The cause is that the model is asked to write persuasively about a specification list. Specifications are inputs, not copy. Turning them into something a person wants to read requires one more step, and that step is deciding what each specification means for the person buying.
Why generated copy all sounds the same
Ask for a description of a product with a list of attributes and you get back a paragraph where every attribute has been promoted one level of abstraction. Numbers become comparatives, materials become adjectives, and durations become vague assurances.
The result reads as generic even when the product is not, because abstraction strips out the only parts that were distinctive. "Charges in 38 minutes" is a fact a competitor may not be able to claim. "Fast charging" is a claim every competitor already makes.
The fix is not a better prompt style. It is supplying a different input: instead of the specification, the consequence of the specification for a specific person.
Specifics beat superlatives
Replace each adjective with the thing it was hiding. This is mechanical work and it transforms the copy faster than any amount of rewriting.
- "Durable" becomes "the seam is double-stitched; it is the first thing to fail on the cheaper version".
- "Lightweight" becomes "540 grams, which is roughly the weight of a full water bottle".
- "Easy to clean" becomes "the tray lifts out and goes in the dishwasher".
- "Premium" becomes whatever actually justifies the word — a material, a warranty, a manufacturing detail.
If a specification cannot be converted into a consequence, that is useful information. It means the specification does not matter to the buyer, and it can be left out rather than dressed up.
The objection line
Every product has one or two objections that stop people buying. The most valuable sentence in a description usually addresses one of them directly.
You almost certainly know what these are: the question your support inbox gets, the reason for returns, the thing the sales conversation keeps returning to. Writing it into the description does two things — it removes the objection for readers who had it, and it signals honesty to readers who did not.
The form is a plain statement of the limitation, followed by what it means in practice. "It does not fit a standard A4 folder. If you carry loose A4 paper, this is the wrong one. If you use a tablet or a phone, the internal pocket is sized for both." A description that rules people out is more persuasive to the people it does not rule out.
Describing for different buyers
A single description tries to serve everyone and usually serves nobody. The same product has at least three audiences with different questions: the person who needs it to work, the person who needs it to last, and the person who needs to justify the purchase to someone else.
Rather than writing three separate descriptions, order the same facts differently for each. The practical buyer wants the specification and the compatibility before anything else. The durability-focused buyer wants the materials and the warranty. The person justifying a purchase wants the outcome and the comparison with the alternative they were considering.
A useful test: read the description and ask which of these three readers would get their question answered in the first two lines. If the answer is "none of them", the opening is spending its space on atmosphere.
Structuring a description
A description that converts tends to move through five beats, and the order matters more than the length.
- What it is and who it is for. One sentence. No adjective stacking.
- The outcome. What changes for the buyer once they have it.
- The specifics. The numbers, materials, dimensions, compatibility. This is where most descriptions under-invest.
- The limitation. What it does not do, stated plainly.
- The next step. What the reader should do, and what happens when they do it.
The limitation placed before the call to action is not a mistake. It functions as a filter and as a credibility device at the moment when the reader is deciding whether to trust the rest of the page.
Writing for search and for humans
Product pages are usually found by people searching for something specific, which means the specific terms need to appear on the page in a readable form. The temptation is to add a keyword block at the bottom; the better move is to make sure the search terms appear naturally in the specifics section, where they were going to be relevant anyway.
Names matter here. If buyers call the product by a term you do not use, use theirs. Interior naming conventions are invisible to the person searching.
The section headings do a lot of the work. Headings like "Compatibility", "Dimensions", and "What is included" are not creative, and that is the point — they match what people are scanning for. Reserve the more inventive language for the opening and the outcome.
Checking the output
Run these four checks over any generated description. They catch most of what goes wrong.
- The superlative scan. Count the adjectives that assert quality without evidence. Anything above three or four in a short description is a problem.
- The substitution test. Swap in a competitor's product name. If the description still reads correctly, it does not describe this product.
- The number check. Verify every figure against the actual specification. An invented measurement is worse here than in an article, because the buyer may check it against the product they receive.
- The objection check. Does the description address the reason people would not buy? If it stays silent on the obvious drawback, it reads as advertising rather than information.
Scaling without flattening
When you have hundreds of products, the temptation is to run one template across all of them, which reproduces the original problem at scale. The alternative is not writing every description by hand; it is varying the inputs rather than the prompt.
Build the specific material once per product — the actual measurements, the compatibility list, the known limitation, the one detail that makes this item different from the nearest alternative — and let the template handle the arrangement. The template provides consistency; the per-product specifics provide everything that makes the page worth reading.
Then spot-check. Take one description in twenty and read it as a buyer, asking only whether you can tell what you are getting. That is the test the description exists to pass.