Edits on the delivered descriptions stay inside the quoted SKU count, length, and voice. Feedback is worked in and sent back for approval.
eCommerce product descriptions
eCommerce product descriptionsCatalogue copy your client can publish in the shop.
Product descriptions for shop catalogues. A person writes and edits them. AI can speed the draft. You approve before anything goes out under your name.
What the descriptions are for
Clear product copy helps a shopper decide. The catalog calls this copy for shop catalogues. We do not promise a conversion rate or a ranking for any one SKU.
- 01
Each product says what it is
Features, fit, and use sit in plain language so a shopper can compare without guessing.
- 02
Tone matches the brand
Luxury, practical, or technical: the voice follows the brief, not a generic shop template.
- 03
Search terms can sit in the copy
When the brief names keywords or attributes, we weave them in without stuffing. Search work beyond the descriptions is a separate order.
- 04
Volume without a writing desk
Batches of SKUs move through one brief, one quote, and one approval path, so your team is not writing every line.
- 05
You keep the client
The writing stays under your brand. We do not contact your client's buyers.
The scope
The brief sets SKU count, length, and whether attributes, SEO fields, or variants are included. Quote follows that scope.
SKU batch
A set of products quoted together: same brand voice, same length band, one delivery date.
Longer PDP copy
Richer descriptions when the product needs story, care, or comparison detail beyond a short blurb.
Titles and meta
Product titles, short blurbs, and meta lines when the brief asks for them beside the body copy.
Catalogue refresh
Rewrites of existing descriptions when the range, pricing story, or brand voice has changed.
How it runs
From the brief to your approval
You stay in the project. We do not contact your client. Nothing is final until you approve it.
What a revision includes
A new product line, a new language, or a change of direction is a new quote. Thin product data produces thin copy.
What we do, and what we need from you
The brief and the product data set the pace. Late notes move the date.
| Task | Your agency |  |
|---|---|---|
| Descriptions that match the voice and length in the brief. | ||
| Human writing and editing, with AI used only to speed the draft. | ||
| Keyword or attribute use when the brief names them. | ||
| A confirmed SKU count and a delivery date. | ||
| The draft in Basecamp, or on the platform you use. | ||
| Revisions from your feedback, then a resubmit for approval. | ||
| No contact with your client. The work stays under your name. | ||
| Product facts: names, specs, materials, use cases, and any must-include claims. | ||
| A sample of approved voice, or a style note. | ||
| Active replies in Basecamp, or on your platform. | ||
| Feedback in time for the delivery date. | ||
| Approval before you publish under your name. |
Sell it with the shop build
Bundle descriptions with a shop or catalogue project so launch is not waiting on empty PDPs.
After launch, a refresh of seasonal ranges or a longer PDP for hero products is the usual next order.
Facts beat filler
We write from the data you send. We do not invent materials, certifications, or medical claims.
If a claim must appear, you confirm it in the brief. Unverified claims stay out of the copy.
What we will not claim
We do not promise more add-to-carts, a ranking for a SKU, or a sales lift from the descriptions alone.
Those depend on price, photos, shipping, and the rest of the funnel.
Agencies often add these
Frequently asked questions
Agencies that need shop catalogue copy under their own name, for a new range or a refresh.
Ready to brief a product-copy batch?
You keep the client. We write the catalogue lines, and you approve them before they go out under your name.