Understanding enrichment
Every time Clione enriches a product (on sync or when you click "Re-enrich"), it generates six categories of artifacts from a single LLM call + an embedding call.
| # | Artifact | Used by |
|---|---|---|
| 1 | Semantic text — identity, reasoning, objection handler | LLMs, internal search |
| 2 | Quality scores — durability, quality, value-for-money, price positioning | Dashboard, ranking |
| 3 | Bilingual keywords (EN + ES) | Search, tag clouds |
| 4 | Vector embedding (1536-dim) | Semantic similarity search |
| 5 | JSON-LD (schema.org/Product) | Search engines, LLM crawlers |
| 6 | SEO meta signals — description, canonical URL, keywords | SEO tools, headless storefronts |
What goes into the LLM call
Your product's title, description, price, vendor, categories — that's it. Plus any hints you added via the Enrichment Wizard (target audience, materials, competitor names, etc.) if you filled it.
The LLM doesn't have access to your reviews, returns, conversion rate, or sales data yet. That means:
- The identity and reasoning fields are sharp — the LLM is great at summarising product character from titles and descriptions.
- The quality scores are educated guesses — the LLM has common sense about markets (Hermès→luxury, Primark→budget) but it's reading your catalog text, not verified performance data.
See Understanding Quality Scores for the full breakdown and what we're building to fix this.
What happens on re-enrich
- A new version of the enrichment is snapshotted (the previous output is retained in History)
- The last 3 versions per product are kept automatically — older ones are purged
- You can restore any past version from the product's History tab
- If the product was manually edited, the re-enrich dialog asks you to type OVERWRITE to confirm losing the manual edits
Where enriched content is exposed
- Inside the dashboard — for you to review, edit, rollback
- Via API endpoints —
.llm,.jsonld,.metavariants per product - Via
/.well-known/llms.txtat your tenant domain — a catalog manifest that LLM crawlers can fetch - Via the embed script — injected FAQ widgets + JSON-LD on your storefront pages
Check the Concepts → Enrichment Pipeline for the full technical reference.