Below is a practical, copy-pasteable guide with ready-made prompt templates, examples and best practices to generate high‑quality product, category and CMS page content for PrestaShop using an LLM (ChatGPT or similar). Use these prompts as-is or adapt variables ({{...}}) to your catalog and workflow.
Quick checklist before prompting
- Provide the model with all factual product data you have (name, SKU, features, materials, dimensions, target audience, price, warranty, images).
- Specify target language, tone, word counts, and whether output should be plain text, HTML, CSV row, or JSON for import.
- Tell the model to avoid inventing facts — instruct it to use placeholders (e.g., [MISSING INFO]) when data is absent.
- Ask for SEO meta title, meta description, and suggested keywords.
- For bulk runs, produce machine‑readable output (CSV or JSON) with consistent field names.
Best practices
- Use a role and task statement: “You are an ecommerce copywriter/SEO specialist.”
- Give a short s guide: brand voice, audience, formatting rules (HTML allowed, use bullet lists for features).
- Limit hallucinations: “If a fact is not provided, write [MISSING] rather than guessing.”
- Request multiple variants (short/long, formal/casual) if needed.
- For bulk generation, return output as CSV/JSON with exact keys matching your import template.
- Validate outputs automatically: check for required fields, character counts for meta tags, and HTML validity.
Core fields for PrestaShop product CSV/JSON (common)
- id, name, sku/reference, price, wholesale_price, quantity, active (0/1)
- description_short (HTML), description (HTML)
- meta_title, meta_description, meta_keywords
- tags (comma separated)
- categories (IDs or names), manufacturer, supplier
- features (name:value pairs), attributes/combinations (size/color:values)
- image_urls (comma separated)
- visibility (both/catalog/search)
- condition (new/used/refurbished)
Templates and examples
1) Product: generate short + long descriptions, features, meta tags (HTML + JSON)
Prompt (fill in variables):
You can paste this directly to ChatGPT or your LLM:
You are an expert ecommerce copywriter and SEO specialist for an online store. Output a single valid JSON object only (no extra text) with the exact keys: name, sku, price, description_short_html, description_html, features (array of {"name","value"}), bullets (array of strings), meta_title, meta_description, meta_keywords (array), tags (array), suggested_alt_text (array matched to image_urls), warnings (string - allow [MISSING]).
Product data:
name: {{product_name}}
sku: {{sku}}
brand: {{brand}}
category: {{category}}
material: {{material}}
dimensions: {{dimensions}}
weight: {{weight}}
color: {{color}}
key_features: {{feature1}}; {{feature2}}; {{feature3}} (if none, write [MISSING])
target_audience: {{audience}} (e.g., "urban cyclists, 25-45, eco-conscious")
price: {{price}} (currency: {{currency}})
images: {{image_url1}}, {{image_url2}} (if none, leave empty string)
warranty: {{warranty}} (if none, write [MISSING])
country_of_origin: {{origin}} (if none, [MISSING])
SEO keywords (optional): {{keyword1}}, {{keyword2}} (if none, model may suggest)
Rules:
- Brand voice: {{tone}} (e.g., "friendly, concise, trust-building")
- description_short_html: max 150 characters; must be valid HTML; one
or short
.
- description_html: 80–200 words; include 2–4 short paragraphs and a bullet list of top features (use and
- ).
- Bullets: 3–6 short feature bullets (no HTML).
- Meta_title: max 60 characters; include product name and one primary keyword.
- Meta_description: max 155 characters; include a call-to-action.
- meta_keywords: 3–8 keywords/phrases.
- tags: up to 8 tags.
- suggested_alt_text: one alt text per image URL.
- Do NOT invent specs. If a field is not provided above, put the string "[MISSING]".
- Output only the JSON object. No explanation.
Example output (what to expect)
{
"name":"UrbanRide Commuter Backpack 20L",
"sku":"URB-20-CK",
"price":"69.99 USD",
"description_short_html":"
Durable 20L commuter backpack with water‑resistant fabric and padded laptop sleeve.
",
"description_html":"Designed for daily commuters, the UrbanRide 20L backpack blends minimalist s with function. It features a padded 15\" laptop sleeve, a ventilated back panel, and water‑resistant fabric to keep essentials dry.
Organize your day with multiple pockets and an integrated trolley sleeve.
- 20L capacity
- Padded 15\" laptop sleeve
- Water‑resistant exterior
- Ergonomic shoulder straps
",
"features":[{"name":"Capacity","value":"20L"},{"name":"Laptop sleeve","value":"15\" padded"},{"name":"Material","value":"Water-resistant polyester"}],
"bullets":["20L capacity for everyday gear","Padded 15\" laptop compartment","Water-resistant fabric for rainy commutes"],
"meta_title":"UrbanRide 20L Commuter Backpack - Padded Laptop Sleeve",
"meta_description":"Durable 20L commuter backpack with water-resistant fabric and padded 15\" laptop sleeve. Shop now.",
"meta_keywords":["commuter backpack","water-resistant backpack","15 inch laptop backpack"],
"tags":["commuter","backpack","laptop","water-resistant"],
"suggested_alt_text":["UrbanRide 20L backpack front view","Back view showing padded straps"],
"warnings":"[MISSING]"
}
2) Product: short sales blurb + technical specs (CSV row)
Prompt:
You are an ecommerce copywriter. Given this product data (fill in), output a single CSV row matching these headers: name,sku,price,quantity,description_short_html,description_html,meta_title,meta_description,tags,image_urls,features.
Data:
name: {{name}}, sku: {{sku}}, price: {{price}}, quantity: {{qty}}, images: {{img1}};{{img2}}, features: {{feat1}}|{{feat1value}};{{feat2}}|{{feat2value}}.
Rules:
- description_short_html: 100 chars max, single .
- description_html: 60–120 words, include
with features.
- meta_title <= 60 chars; meta_description <= 155 chars.
- features cell: pipe-separated name|value pairs, semicolon-separated.
- Do not add headers, output only the CSV row.
3) Category description + SEO
Prompt:
You are a senior ecommerce content strategist. Produce two variants for the category {{category_name}}: (A) short intro for the category page header (one sentence, 35–55 characters), and (B) a longer SEO description (120–180 words) that naturally includes keywords: {{keyword1}}, {{keyword2}}. Output JSON with keys: short_title, seo_description_html, recommended_meta_title, recommended_meta_description, suggested_filters (array), suggested_tags (array). If we don't provide keywords, suggest 4 keyword phrases relevant to the category. Use brand voice: {{tone}}. Do not invent brand-specific claims.
4) CMS pages: About Us, Shipping, Returns, Terms
Prompt (About Us example):
You are a professional copywriter for ecommerce CMS pages. Write an "About Us" page for the brand "{{brand_name}}", target audience "{{audience}}", brand values: "{{values}}" (e.g., “sustainable, locally made, curated design”). Output HTML only (no wrapper) with sections: heading , 3 short paragraphs (
), a 3-item bullet list (
- ), and a final call-to-action line (
). Keep total length 180–300 words. Do not include promotional claims you cannot support. If a fact is missing, insert [MISSING].
Shipping policy prompt:
You are a legal-friendly ecommerce writer. Generate a clear Shipping & Delivery policy page for "{{brand_name}}" covering: processing time, shipping options and carriers, international shipping, tracking, and contact instructions. Limit each section to 2–4 sentences. Provide a short FAQ with 3 Q&A pairs. Use neutral, customer-helpful tone.
Returns & Refunds prompt:
You are a returns-policy expert. Create a Returns & Refunds page covering: eligibility period ({{days}} days), conditions for return, how to initiate a return, refund timeline, and exceptions (e.g., personalized goods). Use short numbered steps and keep legalistic claims minimal. Insert [MISSING] where a specific policy detail is not given.
5) Tone/voice and length control examples
- Tone: “brand voice: friendly, informative, concise” or “luxury/premium, formal”.
- Length control: “Short description: 30–45 words. Long description: 120–150 words.”
- Format output: “Return the long description as HTML and the short as plain text.”
Tips to avoid hallucinations and bad imports
- Instruct the model to never invent specs; use [MISSING] placeholders.
- For numeric fields (weight, dimensions), validate with regex or script before import.
- Ask the model to output both plain text and HTML to allow automated checks.
- For product variants, include a combinations block (JSON) using option names + values.
Example prompt for combinations (size/color)
Prompt:
Generate combinations JSON for a product with options: Size: S,M,L; Color: Red,Blue. For each combination return: reference (SKU suffix), ean13 (if missing write [MISSING]), price_modifier (0 or +X), quantity. Output JSON array only.
Quality control workflow
1. Create prompt + sample seed data for a small batch (10 items).
2. Run the LLM and import into a staging PrestaShop store.
3. Spot-check for factual accuracy (sizes, materials, EANs), SEO length limits, and duplicate meta titles.
4. Use automated checks for required fields and blocked HTML tags (script/s).
5. Iterate prompt to fix formatting issues (e.g., remove extra quotes, commas in CSV fields).
Examples of “Perfect Prompt” you can reuse
Short product template (HTML output)
You are an ecommerce copywriter. Using the data below, write:
1) a short product summary (description_short_html, one
, max 140 chars),
2) a long product description (description_html, 120–180 words, 2–3 paragraphs plus
- bullets),
3) a 3-line feature list (bullets array),
4) meta_title (<=60 chars) and meta_description (<=155 chars),
5) 5 tags.
Data: name: {{name}}; brand: {{brand}}; material: {{material}}; dimensions: {{dimensions}}; color: {{color}}; features: {{comma-separated features}}; target audience: {{audience}}; images: {{urls}}.
Rules: Do not invent facts; if missing, write [MISSING]. Return only valid JSON.
Category page template
You are a category content specialist. For category "{{category}}", produce:
- category_heading (30–50 chars),
- category_intro_html (40–80 words),
- full_category_description_html (150–220 words, include keywords: {{kw1}}, {{kw2}}),
- meta_title (<=60 chars), meta_description (<=155 chars),
- suggested_filters (brand, price range, material, size arrays).
CMS page template (Returns)
You are a legal-friendly policy writer. Create a Returns & Refunds page for "{{brand}}". Include: eligibility, how to return (step-by-step), refund timeline, and exceptions. Output in HTML with headings and numbered lists. Keep the tone clear and helpful. Put [MISSING] where a company-specific policy detail is not provided.
Final checklist before running at scale
- Map LLM output keys to your PrestaShop import format (field names and encoding).
- Test with a sandbox import to catch CSV/JSON formatting issues.
- Prevent HTML injection by stripping disallowed tags server-side.
- Keep a manual review loop for all AI-generated product pages, at least initially.
If you want, I can:
- Turn one of your real products (paste the product data) into ready-to-import JSON/CSV using these templates.
- Generate a CSV header mapping for your specific PrestaShop version.
- Create a short prompt tailored to your brand voice and import format.
Which would you like me to do next? (Provide one product or category sample if you want a concrete generated example.)
