How to write product descriptions from spec sheets

Start from the source document, not a blank page

A supplier datasheet states what the product is, what it is made of, and how it performs under which conditions. It rarely says who the product is for or why anyone should care. Your description adds that layer — but every sentence should be anchored to something the document says.

Before writing, pull the facts into a plain list with units, and note each document’s name, version, and date so a reviewer can check any value later. Where two documents disagree — 1.2 kg on the spec sheet, 1.25 kg on the packaging — resolve it with the supplier instead of picking one.

• Identity: brand, product name, model number, GTIN, variants.
• Measurements: dimensions, weight, volume, net quantity — with units as printed.
• Materials and composition: materials, fiber percentages, ingredients.
• Performance: ratings, capacities, runtimes, and their test conditions.
• Compatibility: voltages, connectors, systems, minimum ages.
• Contents, care, safety, and compliance: box contents, instructions, warnings, markings, cited standards.

The anatomy of a product page

A product page is several pieces of text, each with its own job and, on most channels, its own limit. Write each element for its job instead of writing one block and cutting it up. The limits below come from each platform’s documentation; where a limit varies by channel or category, check the current guidelines.

Identifiers such as GTIN, MPN, and SKU belong in structured fields, not in the prose — channels read them from those fields.

Translate features into benefits without inventing anything

A feature is what the product has; a benefit is what that means for the buyer. The benefit is your inference, so keep it conservative: it should follow directly from the spec and the conditions it was measured under. If the benefit needs a fact the document does not contain, it is a new claim.

The last column below is the trap: the stronger-sounding version the spec alone does not support.

A step-by-step process for writing from spec sheets

Write the specification table and bullets first: the prose then draws on a verified fact base, and the title summarizes facts you have already checked.

1. Collect every source document — datasheet, safety data sheet, declaration of conformity, label artwork — with versions and dates.
2. Extract the facts with units as printed. Mark gaps and contradictions as questions for the supplier.
3. Decide the primary use and main buyer the page leads with.
4. Build the specification table: one attribute per row, consistent units and attribute names across the category.
5. Write three to six bullets, each pairing one benefit with the spec that supports it.
6. Write the title with your category formula, front-loading brand, product type, and the attribute buyers filter on.
7. Write the short description: what it is, who it is for, and the strongest reason to choose it.
8. Write the long description: use cases, how it works, box contents, and care — every claim pointing back to a bullet, spec row, or document.
9. Add care, safety, and compliance information verbatim, where it applies to the product.
10. Check each element against channel limits, then review the page against the source documents.

Title formulas by category

A title formula keeps titles consistent and makes gaps visible: if the formula calls for a capacity and the datasheet has none, you have found a missing fact. Google Merchant Center recommends the most important details first, including brand and key attributes, the distinguishing size or color for variants, the count for multipacks, and no promotional text, ALL CAPS, or emoticons.

Amazon’s title policy (effective 21 January 2025) caps most categories at 200 characters including spaces and allows no word more than twice, articles, prepositions, and conjunctions excepted. eBay advises using all 80 of its characters. The brands below are fictional.

Writing for search without keyword stuffing

Search rewards pages that clearly say what the product is: the words buyers use, in the places that carry the most weight, once. Supplier documents are written for engineers; shoppers search differently.

A copied manufacturer description gives your page nothing that distinguishes it from every retailer using the same text. Rewriting from the spec data, with your own structure and benefit statements, is what makes the page worth ranking.

• Put the main search phrase in the title and the first sentence of the description, naturally.
• Translate supplier jargon into search vocabulary and keep the code for precision: “matte black (RAL 9005)”, not just “RAL 9005”.
• Front-load key details: Google advises putting the most important information in the first 160–500 characters of the description.
• Leave out what Google Merchant Center excludes from descriptions: links, promotional text such as price, sale, or shipping, comparisons with other products, and ALL CAPS.
• Write the Shopify SEO title (70 characters) and meta description (320 characters) as a search snippet, not a copy of the product title.
• Map the same facts to structured attributes — Shopify category metafields, WooCommerce attributes, item specifics — for filters and feeds.

What you must not claim without evidence

Most product-copy risk comes from a few words that sound harmless and carry legal meaning. If the source documents do not support a claim for this exact model, it does not go on the page. This section is general information, not legal advice; rules depend on the product and market.

Category rules can be stricter than general advertising rules. In the EU, food supplements must not be presented as preventing, treating, or curing disease (Directive 2002/46/EC, Article 6(2)), and in the US a supplement’s structure/function claims require the FDA disclaimer set out in 21 CFR 101.93. EU cosmetics must hold proof of the claimed effect in the product information file where justified (Regulation (EC) No 1223/2009, Article 11(2)(d)). Under the EU Toy Safety Directive, warnings that drive the purchase decision, such as minimum age, must be visible before purchase, including online (Directive 2009/48/EC, Article 11(2)).

• “Safe”, “non-toxic”, “chemical-free”, “hypoallergenic”: only with documented evidence for this product, never as a blanket promise.
• “Eco-friendly”, “sustainable”, “biodegradable”, “recyclable”: use a specific, documented claim (such as a stated recycled-content percentage), not a general label.
• “Certified”, “approved”, “tested to”: only when the documentation shows it covers this model. CE marking is affixed by the manufacturer, who takes responsibility for conformity (Regulation (EC) No 765/2008, Article 30) — don’t call it a certification.
• Medical claims — “treats”, “cures”, “prevents”, “relieves pain” — have no place on ordinary consumer products, cosmetics, or supplements.
• “Clinically proven”, “dermatologically tested”, “#1”, “best”: only with evidence the brand can produce.
• Warranty, returns, and shipping promises: only where your store policy defines them.

A reusable product description template

Use it as a fixed order of sections. Fill every placeholder from the fact list; if one cannot be filled, leave it visibly open for the supplier instead of writing around it.

• Title: [Brand] [Product type] [Key attribute], [Second attribute], [Size, capacity, or count] — following your category formula.
• Short description: [Product type] for [primary use or buyer]. [Strongest benefit], thanks to [supporting spec].
• Opening paragraph: what the product does, where it is used, and the problem it solves.
• Bullets (three to six): [Benefit] — [spec that supports it, with unit].
• How to use: setup or application steps from the instructions, in the source order.
• What’s in the box: every included item and quantity, from the packing list.
• Specifications table: Attribute | Value | Unit, with consistent attribute names across the category.
• Care and maintenance: cleaning and storage guidance from the source.
• Safety and compliance information: warnings verbatim, where applicable; manufacturer name and contact address; responsible-person details where the manufacturer is not established in the EU.
• Identifiers: GTIN, MPN, and SKU entered in structured fields, not in the prose.

Localizing product descriptions

Translate the approved source-language page, not a draft. Each version should say exactly what the original says, with number formats adapted to the market and regulatory text in the wording each market requires.

• Keep the datasheet’s measured values. If you add converted units (inches for the US), round consistently and keep the original.
• Many European languages use a decimal comma (1,5 kg) where English uses a point (1.5 kg).
• Map apparel sizes with the supplier’s size chart, not by formula.
• Keep brand names, model numbers, INCI names, and hazard statement codes unchanged.
• Research search terms per market; buyers’ phrases are often not literal translations of the English keyword.
• Labelling and instruction language rules are separate legal requirements: for example, EU textile labels must be in the official language(s) of the Member State where the product reaches the consumer, unless that Member State provides otherwise (Regulation (EU) No 1007/2011, Article 16(3)).
• Have a native speaker who knows the category review each language.

Reviewing AI-drafted product descriptions

AI tools are useful for a first draft from structured data — and fluent at adding plausible details the source never stated. Treat every AI draft as unreviewed until someone has checked it against the documents. Google Merchant Center asks for AI-generated titles and descriptions in the structured_title and structured_description attributes, with digital_source_type set to trained_algorithmic_media.

Use this checklist on every draft, human or AI. The rule: each claim must be traceable to a source document or to product data someone has already reviewed.

Doc2Shelf applies this at catalog scale: it extracts fields from supplier PDFs, gives each extraction a confidence score, records extracted facts with their source page and a short quote, drafts listing copy from that product data, flags missing information as [REQUIRED: …] placeholders, and blocks publishing until a person has reviewed the listing. The check against your source documents stays with your team.

• Every number, unit, and model reference matches the source document exactly.
• Every claim can be traced to a source document or reviewed product data — nothing is “typical for the category”.
• No certifications, standards, test results, or markings appear that the documents do not show for this model.
• Warnings and regulatory statements are verbatim, complete, and present where they apply.
• Benefits follow from the stated test conditions, and variant details match the variant the page describes.
• Every element fits the channel’s limits, and gaps are flagged for the supplier rather than filled in.