Magento
AI Product Creator
AI Product Creator builds complete, SEO-grade products for you — from a product name, from a manufacturer’s spec sheet, or in bulk. It writes the copy, suggests categories, maps the specs onto your attributes (creating the ones you’re missing, with your approval), and saves the result as a draft — disabled and hidden from the storefront until a human signs it off.

Compatibility
Section titled “Compatibility”PHP
AI engine
Safety
Three ways to create
Section titled “Three ways to create”Type a product name and the AI writes a full product: SEO name, SKU, short & long description (structured HTML — intro, H2s, a list and a spec table), meta title/description, URL key, and suggested categories. Best when you don’t have a spec sheet.
Paste a manufacturer’s spec-sheet text (or upload a PDF) and name the target product. The AI reads the document, extracts the real specifications, maps them onto your existing attributes, flags any specs that need a new attribute, writes the SEO copy, and saves a draft — all grounded strictly in the document.
Run an import job over a source (e.g. CSV) to create many products at once, with a progress tracker and a per-record success/error log under Import Jobs.
The schema-aware workflow
Section titled “The schema-aware workflow”What sets this apart from “AI description” tools is that it understands your catalogue’s attributes, not just free text.

-
Snapshot your schema. The Schema Explorer exports your attribute set(s) into a schema dictionary the AI maps against. Snapshots are saved and reused.
-
Scan a document. Upload a spec sheet; the AI compares its specs against your schema and shows which map to existing attributes and which are gaps (no attribute yet).
-
Approve new attributes. You review the recommended new attributes and approve them — only then are they created (capped per run, codes sanitised). Nothing is written to your EAV schema without your say-so.
-
Create the draft. The product is saved with every matched spec mapped to the right attribute (select/multiselect option labels resolved to IDs automatically).

Import jobs
Section titled “Import jobs”Bulk runs are tracked as jobs: name, source, status, progress %, processed/total, success and error counts, and a results/error log — so a large import is observable and auditable.

Configuration
Section titled “Configuration”Stores → Configuration → AgenticEcom · AI → AI Product Creator — and the working screens live at Catalog → AI Product Creation (AI Product Creator, Schema Explorer, Configuration).

| Group | Key settings |
|---|---|
| AI Engine | Enable, Google AI API Key (encrypted), primary + fallback text models. |
| Product Defaults | Default status for AI drafts, default attribute set, max new attributes per run (caps EAV growth). |
| Prompts | Editable Quick-Generate and PIM-Extract prompt templates (with {{placeholders}}). |
Will AI products show up on my storefront automatically?
No. They’re created Disabled and Not Visible Individually, so they stay out of the catalogue and search until you review and publish them. Treat each as a draft to approve.
Does it invent specifications?
No — that’s the core guardrail. In PIM Extract it uses only what the document states; in Quick Generate it uses only what it genuinely knows about that exact product, and leaves anything uncertain blank (prices it can’t verify come back as 0).
Can it create attributes I don’t have yet?
Yes, but only with your approval. The AI flags specs that don’t match any existing attribute; you approve which to create. Creation is capped per run and the attribute codes are sanitised, so an AI run can’t flood your EAV schema.
Is the generated HTML safe?
Yes — all generated description HTML is run through a server-side sanitiser (allow-listed tags, scripts/event-handlers/unsafe-URLs stripped) before it’s saved, so it can’t carry stored-XSS to your storefront.
Is it secure?
Every screen sits behind its own ACL resource (manage, import, generate, jobs, schema, schema_create, config); the API key is encrypted and sent in a request header; new-attribute creation is admin-approved and capped; and URL keys are de-duplicated on save. Verified clean on PHP 8.4 and 8.5.