052. Ambientador Mikado Ropa Limpia - 1000ml

Name: 052. Ambientador Mikado Ropa Limpia - 1000ml
Brand: Vismar Factory SL
SKU: MK-ropalimpia-1000ml
Price: 35.63 EUR
Availability: InStock

052. Ambientador Mikado Ropa Limpia - 1000ml er en genopfyldning til duftpinde med en frisk og behagelig duft, angivet i duftfamilien som “Rengørings tøj” og egnet som duft til hjemmet.

Leveres i dunk på 1 liter i professionelt format til forhandlere og erhvervskunder; produktet er beregnet til genopfyldning af duftpinde og kan anvendes som refill til duftpinde eller duft til duftpinde i detail- og engrossalg.

Du kan finde flere oplysninger her: læs mere om duftpinde og hvordan de fungerer.

En stock

35,63 €

Beskrivelse

Below is a compact, practical guide + ready-to-use prompt templates and examples you can copy/paste to generate PrestaShop-ready product, category and CMS content with an LLM (ChatGPT or API). It follows proven prompt-engineering patterns: context → goal → constraints → data → output format (strict JSON/CSV) → examples. Use the link you provided as background reading; this guide distills and expands into actionable templates. 1) Prompt structure (recommended pattern) - System/Context (optional): brand voice, product catalog, PrestaShop version/constraints. - Goal: what you want (create product, category, CMS page). - Input data: values you already have (SKU, attributes, language, target keywords). - Constraints: character limits, HTML allowed, no commentary, avoid trademarks, units, format (JSON/CSV), fields required. - Output format: strict machine-readable format (JSON array or CSV). Provide schema example. - Example item: one example product/category/CMS in the requested format. 2) Common fields to request for PrestaShop - Products: sku, name, slug/friendly_url, short_description (HTML allowed), description (rich HTML), price (incl tax? specify), tax_rate, currency, wholesale_price, quantity, condition, manufacturer, supplier, ean13/upc, mpn, weight, dimensions, categories (IDs or slugs), features (name:value), tags, product_type (simple/pack/virtual), combinations (list of attribute groups + prices/quantities), images (filenames or URLs + alt_text), meta_title, meta_description, meta_keywords, active (1/0), visibility, available_for_order (1/0), available_date, minimal_quantity, reference. - Categories: id (optional), name, slug, parent_slug or parent_id, description (HTML), meta_title, meta_description, meta_keywords, image_url, active, position, display_mode (products/subcategories/both), include_in_menu. - CMS Pages: title, slug, content (HTML), meta_title, meta_description, meta_keywords, position, active, hook (footer/header), show_title, indexation (allow search engine indexing). 3) General constraints & tips - Ask for short_description ~140–300 chars; meta_title < 60 chars; meta_description ~ 120–155 chars. - Request SEO keywords naturally integrated in first 160–200 characters of description. - Ask for HTML for product pages (H2, bullets, spec table) or plain text depending on import. - Include image alt text and recommended image filename. - Request unique content avoiding duplicate phrases across items. - Specify language and locale for measurements and date formats. - Ask for output as strict JSON (or CSV columns). Tell the model “Only return JSON, no explanation.” 4) Example templates (copy/paste and adapt) A) Product — strict JSON output System prompt (optional): You are a product content writer for [BRAND]. Use a friendly/professional tone. Target audience: [audience]. Localize to [language/locale]. User prompt: Create 3 product entries for PrestaShop in JSON array only. Follow this schema exactly: [ { "sku": string, "name": string, "slug": string, "short_description": string, // HTML allowed, 140-220 chars "description": string, // full HTML, include H2, bullets, a spec table "price": number, // decimal, in EUR "tax_rate": number, // e.g., 20 "currency": "EUR", "wholesale_price": number, "quantity": integer, "condition": "new"|"used"|"refurbished", "categories": [ "slug-or-id" ], "features": [ {"name":string,"value":string} ], "combinations": [ {"attributes":{"Size":"M","Color":"Blue"}, "price_impact":number, "quantity":int } ], "images": [ {"url": string, "alt": string} ], "meta_title": string, // <=60 chars "meta_description": string, // 120-155 chars "tags": [string], "active": 1 } ] Constraints: - Return only JSON array, no commentary. - Use given language: [language]. - Include the primary SEO keyword: [keyword] in name, first sentence, and meta_description. - Keep meta_title <=60 chars, meta_description 120–155 chars. - Short description: 140–220 chars. - Provide unique content; do not use brand names unless provided. Now generate 3 products. Example of one product the format must match exactly: { "sku":"ABC123", "name":"Example Product", "slug":"example-product", ... } B) Category — strict JSON User prompt: Create 4 categories in JSON array with this schema: [ { "name": string, "slug": string, "parent_slug": string|null, "description": string, // HTML, 80-250 chars "meta_title": string, // <=60 "meta_description": string, // 120-155 "image_url": string, "active": 1, "display_mode": "products"|"subcategories"|"both" } ] Constraints: - Return only JSON. - Use tone: [brand voice]. - Include target keyword for each category in meta_title and first sentence of description. C) CMS Page — strict JSON User prompt: Create 3 CMS pages in JSON array with this schema: [ { "title": string, "slug": string, "content": string, // HTML, include H1, H2, bullets "meta_title": string, // <=60 "meta_description": string, //120-155 "active": 1, "position": int, "show_title": 1 } ] Constraints: - Return only JSON. - Use friendly FAQ-s tone for support pages, commercial tone for landing pages, etc. - Include internal links as relative URLs where relevant (e.g., "/category/slug" or "/product/slug"). 5) Sample concrete prompt + sample output excerpt (product) User prompt: You are a PrestaShop content generator. Produce 1 product in JSON only according to schema below. Language: en-GB. Brand voice: concise, trust-building. Primary SEO keyword: "organic cotton t-shirt". Schema: { "sku": "string", "name":"string", "slug":"string", "short_description":"string", "description":"string", "price":number, "tax_rate":number, "currency":"GBP", "quantity":int, "categories":[...], "images":[{"url":"", "alt":""}], "meta_title":"", "meta_description":"", "active":1 } Constraints: meta_title <=60 chars, meta_description 120–155 chars, short_description 140–180 chars. Do not include extra keys. Expected s of one field (example output snippet): [ { "sku":"T100-ORG", "name":"Organic Cotton T-Shirt - Natural White", "slug":"organic-cotton-t-shirt-natural-white", "short_description":"A breathable organic cotton t-shirt for everyday comfort. Ethically made, soft to the touch, and durable — perfect for daily wear.", ... } ] 6) Advanced prompts & features - Bulk generation: ask for N items and specify variety rules (e.g., 30% on sale, 40% new arrivals). - Variants/combinations: provide attribute lists and ask the model to expand combinations with price impacts and stock. - Multi-language: ask for array of translations: { "lang":"fr", "name": "...", "short_description":"..." } per product. - CSV output: request header line + CSV rows (but JSON is safer). - Strictness: if you will ingest the output automatically, use "You must output valid JSON only. Validate: no trailing commas." 7) Testing and validation checklist - Validate JSON for syntax. - Check lengths: meta_title, meta_description. - Check for duplicate slugs and names. - Ensure attributes match PrestaShop combinations limits and naming. - Check image URLs or filenames match upload process. - Do a dry import on a test store to catch field name differences with your PrestaShop import module. 8) Short example prompts you can copy-paste - Quick product generator: "Generate 5 product JSON entries for PrestaShop. Each must include sku, name, slug, short_description (140–180 chars), description (HTML with H2 and bullets), price (EUR), tax_rate, quantity, categories (slugs), images (url+alt), meta_title <=60 chars, meta_description 120–155 chars. Language: de-DE. Primary keywords: [keyword list]. Return JSON array only, no extra text." - Quick CMS generator: "Create 3 CMS pages in JSON. Fields: title, slug, content(HTML), meta_title, meta_description, active, position. Tone: support/helpful. Language: en-US. Include an FAQ section in each page. Return JSON only." 9) Final tips - Always request machine-readable output (JSON/CSV) if you’ll import automatically. - Provide at least 2 concrete examples in the prompt to “train” the model to match exact schema. - If you need HTML: request minimal, safe tags (