or tags allowed.
- description: full HTML block with 2–5 sections (intro, 3 feature bullets, specs table).
- Use the main_keyword and related_keywords provided.
- Do not write any text outside the JSON output. Return only JSON.
Product data:
{"name":"Evergreen Stainless Travel Mug 500ml","reference":"EVR-TM-500","price":"19.95","quantity":"120","main_keyword":"stainless travel mug","related_keywords":["insulated travel mug","spill-proof mug"],"brand":"Evergreen","features":[{"name":"Capacity","value":"500ml"},{"name":"Material","value":"18/8 stainless steel"},{"name":"Insulation","value":"Double-wall vacuum"}],"images":["evr_tm_500_1.jpg","evr_tm_500_2.jpg"],"categories":["Drinkware","Travel Mugs"],"condition":"new","minimal_quantity":"1"}
End.
(Example result the AI should produce: a JSON object with the keys given.)
2) Bulk product generation from CSV → CSV (CSV headers)
System:
You are an e-commerce copywriter generating product rows for PrestaShop import.
User prompt:
I will paste a CSV of product source data with columns: name, reference, price, quantity, brand, features (semi-colon separated: key:value), images (comma separated), categories (pipe-separated).
For each row, produce a CSV row with these headers in this order:
name,reference,price,quantity,description_short,description,meta_title,meta_description,meta_keywords,link_rewrite,visibility,available_for_order,show_price,condition,minimal_quantity,categories,images,features
Rules:
- meta_title 40–60 chars, meta_description 120–160 chars.
- link_rewrite must be ascii, lowercase, hyphenated.
- description must be HTML with at least one Keep drinks hot or cold for hours in this 500ml spill-proof stainless travel mug. Whether commuting or hiking, this travel mug keeps beverages at the right temperature... , Vismar Essence - productos de perfumeria y cosmetica and at least one
list of features.
- features column must be JSON array string of {"name":"...","value":"..."}.
- Output only the CSV rows (header included), nothing else.
Then paste CSV input below.
3) Category page prompt
System:
You are a category page writer and SEO specialist.
User prompt:
Create content for the category "Insulated Travel Mugs". Output JSON with keys:
category_name, meta_title, meta_description, link_rewrite, description (HTML), short_description (one sentence), suggested_filters (array of filters like capacity/material/color), featured_products_text (short promo sentence).
Rules:
- meta_title 50–60 chars, meta_description 140–160 characters.
- description HTML should include an intro paragraph, 3 benefit bullet points (
), and a short buying guide section (
Buying Guide
with 3 bullets).
- link_rewrite: seo-friendly slug.
- Include target keywords: insulated travel mug, spill proof, vacuum flask.
- Only return valid JSON.
4) CMS page (FAQ / Returns / Shipping)
System:
You are a brand content writer. Write clear, concise CMS pages optimized for conversions and customer clarity.
User prompt:
Create a "Shipping & Returns" CMS page for [Brand]. Output JSON:
{ "page_title", "meta_title", "meta_description", "content_html" }
Rules:
- content_html should have sections: intro, shipping options (table or bullets), returns policy (steps and conditions), FAQ (3 Q&A), contact CTA.
- Use friendly but professional tone. Keep meta_description ~150 chars.
- Return JSON only.
5) SEO-only prompt for meta fields (fast)
User prompt:
For the following product name and three bullets, provide:
- meta_title (max 60 chars)
- meta_description (max 160 chars)
- link_rewrite (slug)
Return as single-line JSON: {"meta_title":"...","meta_description":"...","link_rewrite":"..."}
Input example:
Name: "Evergreen Stainless Travel Mug 500ml"
Bullets: "Double-wall vacuum insulation; Leakproof lid; Fits most cup holders"
End.
Output format tips (to ensure parsable output)
- Delimiters: wrap user input in triple delimiters like ===DATA=== so the model doesn’t mix it with its instruction.
- Force machine-readable format: “Return only JSON” or “Return CSV with the exact headers”.
- Ask the model to validate: “Ensure link_rewrite contains only a-z0-9 and hyphens; if non-ascii letters exist, transliterate them.”
Example generated product (what you can expect)
{
"name": "Evergreen Stainless Travel Mug 500ml",
"reference": "EVR-TM-500",
"price": "19.95",
"quantity": "120",
"description_short": "Evergreen Stainless Travel Mug (500ml)
Specifications
",
"meta_title": "Evergreen 500ml Stainless Travel Mug | Insulated & Leakproof",
"meta_description": "500ml insulated stainless travel mug with leakproof lid. Keeps drinks hot or cold for hours—perfect for commuters. Free shipping over $50.",
"meta_keywords": "stainless travel mug, insulated travel mug, leakproof mug",
"link_rewrite": "evergreen-stainless-travel-mug-500ml",
"visibility": "both",
"available_for_order": "1",
"show_price": "1",
"condition": "new",
"minimal_quantity": "1",
"categories": ["Drinkware", "Travel Mugs"],
"images": ["evr_tm_500_1.jpg","evr_tm_500_2.jpg"],
"features": [{"name":"Capacity","value":"500ml"},{"name":"Material","value":"18/8 stainless steel"},{"name":"Insulation","value":"Double-wall vacuum"}]
}
Advanced tips
- For multilingual stores: ask for outputs per language. Example: “Return an array with keys en, fr, de each containing name, description, meta_title, meta_description, link_rewrite. Ensure link_rewrite is transliterated appropriately.”
- For A/B copies: “Provide 3 title variants and 3 meta descriptions, label them variant_A/B/C.”
- For exact HTML: provide allowed tags and forbidden tags (e.g., allow Capacity 500ml Material 18/8 stainless steel ,
,
,
, , ).
- For bulk scale: chunk CSV into batches of 50 products per prompt to avoid token limits.
- For validation: add a final clause “Output must be machine-parseable; if an error occurs, return {"error":"description"}.”
Common pitfalls and how to avoid them
- Problem: Model outputs explanations before JSON. Fix: “Return ONLY JSON — no commentary.”
- Problem: Invalid characters in link_rewrite. Fix: include explicit transliteration rule and allowed characters.
- Problem: Meta descriptions too long. Fix: require char limit and ask model to count roughly: “Keep meta_description ≤ 160 chars.”
- Problem: Duplicate meta titles. Fix: ask for unique titles and to append product SKU or brand when necessary.
Quick copy-paste prompt (single product, minimal)
You are an e‑commerce copywriter for [Brand]. Generate PrestaShop fields in JSON only for this product: name, reference, price, quantity, description_short (<=160 chars HTML), description (HTML), meta_title (<=60 chars), meta_description (<=160 chars), meta_keywords, link_rewrite (ascii lowercase hyphens), categories (array), images (array). Use brand voice: [tone]. Target keywords: [keyword1, keyword2]. Product data: === {"name":"...","reference":"...","price":"...","quantity":"...", "features":[...], "images":[...], "categories":[...], "brand":"..."} === End. Return only JSON.
Final checklist before running prompts
- Have you provided product data and key selling points?
- Have you set the brand voice and target audience?
- Did you specify exact output format (JSON/CSV) and field names?
- Did you include SEO constraints (lengths, keywords)?
- Are you batching large imports to respect token limits?
If you want, paste one or a few actual product rows (or CSV) and I’ll craft the exact prompt and produce a sample output JSON/CSV ready for import into PrestaShop.
Produktoplysninger
I tilfælde af kontakt med øjnene skylles med rigeligt vand i flere minutter.
I tilfælde af uheld kontaktes den medicinske toksikologiske informationstjeneste.
Må ikke anvendes på øjne, mund og andre følsomme dele af kroppen.
Må ikke indtages.
Opbevares utilgængeligt for børnRelated products
About VismarEssence
Reviews (0)
8 andre varer i den samme kategori:
Mikado Vanilla Sex Duftspreder – Langvarig Duft til Hjemmet
Mikado Vanilla Sex Duftspreder – Langvarig Duft til Hjemmet er en stokduft, der minder om parfumen fra Tom Ford; topnoter af bitter mandel, hjertenoter af vanilje og blomsteragtige noter samt bundnoter af vaniljeekstrakt, Ultravanil™, tonkabønne og sandeltræ. Til brug som genopfyldning til duftpinde.
Produktet leveres i dunk i større format til professionelle kunder, distributører og detailhandlere. Denne flydende genopfyldning er beregnet til refill til duftpinde og kan anvendes som duft til hjemmet i salg til engros og forhandlere.
Du kan finde flere oplysninger her: læs mere om duftpinde og hvordan de fungerer.
Beskrivelse
Below is a practical, ready-to-use guide for writing “perfect” AI prompts to generate PrestaShop product entries, category pages and CMS pages. It includes best practices, field-specific guidance, exact prompt templates (single and bulk), output-format tricks (JSON/CSV), SEO constraints, and example prompts you can copy/paste and adapt.
Quick principles first
- Be explicit about role, audience and constraints (tone, brand voice, word counts, language).
- Provide the exact output format you need (JSON, CSV, or HTML) and tell the model to produce only that format.
- Give example input data (one row or a small table) so outputs are consistent.
- Include SEO requirements: target keywords, meta title length (≈50–60 chars), meta description length (≈120–160 chars), link_rewrite rules (lowercase, hyphens, ascii).
- Ask for variants (A/B), short/long descriptions, and translations if needed.
- Validate outputs (e.g., link_rewrite contains only allowed chars; numbers formatted properly).
- For bulk operations, provide a CSV/JSON schema and ask the AI to return rows matching it.
PrestaShop fields commonly needed (map these to your export/import)
- name
- reference (SKU)
- price (tax excl/incl depending on your import)
- wholesale_price
- quantity
- description_short (short HTML or plain text)
- description (long HTML)
- meta_title
- meta_description
- meta_keywords (optional)
- link_rewrite (SEO-friendly URL slug)
- visibility (both, catalog, search)
- available_for_order (1/0)
- show_price (1/0)
- condition (new, used, refurbished)
- minimal_quantity
- features/attributes (or separate CSV)
- image filenames (if uploading images separately)
- categories (IDs or path)
- additional: pack, tags, manufacturer, supplier
Best-practice checklist before prompting
- Decide content s (formal, playful, technical).
- Provide target audience (age, experience level).
- Provide key selling points & features, and any prohibited words.
- Provide main keyword(s) for SEO and synonyms.
- State output language and character limits for meta fields.
- State the exact file format (JSON, CSV) and field order.
- Ask for uniqueness and no duplicate meta titles/descriptions across products.
Prompt building blocks (components to include)
- System/role: “You are an e-commerce copywriter for [brand].”
- Context: product data table or CSV sample, brand voice, audience.
- Task: generate fields for PrestaShop with exact names, lengths, rules.
- Output format: “Return valid JSON/CSV only — no explanation.”
- Validation: rules (link_rewrite format, meta length).
- Examples: show 1 example mapping input → expected output.
Ready-to-use prompt templates
1) Single product (JSON output, full fields)
System/role:
You are an e-commerce copywriter and SEO specialist for [Brand]. Write persuasive, SEO-optimized product content consistent with the brand voice: [brand voice: e.g., friendly, expert, concise]. Target audience: [e.g., outdoor commuters, tech-savvy millennials].
User prompt:
I will give product data. Generate a JSON object with these keys exactly:
name, reference, price, quantity, description_short (HTML), description (HTML), meta_title, meta_description, meta_keywords (comma-separated), link_rewrite, visibility, available_for_order, show_price, condition, minimal_quantity, categories (array of category names), images (array of filenames), features (array of {"name": "...", "value": "..."})
Rules:
- meta_title: 40–60 characters; meta_description: 120–160 characters.
- link_rewrite: lowercase, only letters, numbers and hyphens; no spaces or accents.
- description_short: max 160 characters, plain HTML
MK-500ml
No reviews