Enrich your catalog
Plans: Starter (limited credits) · Growth · Pro · Agency
Enrichment is where Clione earns its keep. For each entity (a product, a category or collection, a content page) Clione asks an LLM to generate a rich semantic representation: a natural-language identity, structured reasoning, bilingual keywords, quality scores, and SEO meta fields.
You can enrich:
- Products (BigCommerce and Shopify)
- Categories (BigCommerce) / Collections (Shopify)
- Pages (both platforms)
You always pay for enrichment by entity: 1 enrichment job = 1 entity processed. Your monthly quota is shared across all entity types. See Plans for the per-tier quota.
Three ways to enrich
1. Single entity (one-click)
Open any entity (a product, category, page) and click Enrich in the header.
- The enrichment runs synchronously for that one entity. You'll see the new fields in a few seconds.
- A new version is snapshotted automatically — the previous output is kept in the History tab.
- After enrichment, Clione automatically propagates the new signals to your storefront (meta title, meta description, JSON-LD where applicable). You don't need a separate "push" step.
This is the right flow when you're tweaking one product or experimenting with the enrichment wizard.
2. Bulk async (the daily workhorse)
From any listing page (Products, Categories/Collections, Pages):
- Tick the checkboxes for the entities you want to enrich. The bulk selection bar appears at the bottom of the list.
- Click Enrich selected in that bar.
- A confirm dialog appears showing how many entities will be enriched and the approximate quota cost. You must confirm explicitly — Clione never auto-enriches without your click. Type or click through to start.
- The job returns a job ID immediately. A chip appears in the top bar tracking progress (
enriched N / total), and survives navigation. - As entities complete, they auto-propagate to the storefront in the background.
Use this when you've just synced a new batch of products and want them all enriched in one pass.
You can have one bulk-enrich job per entity type running at a time. Submitting another while one is in flight queues it.
3. Enrichment wizard (guided)
For products specifically, the Enrichment Wizard is a short questionnaire that gathers context Clione can't infer from the raw product data — target audience, materials, key benefits, competitor names, sustainability claims.
Open a product → click Wizard in the header. Fill what you know; skip what you don't. Click Run wizard enrichment.
The wizard's answers are passed as additional context to the LLM. This is the highest-quality option but takes ~30 seconds per product, so use it for hero SKUs, not entire catalogs.
Wizard answers are saved on the product, so you can re-run an enrichment later with the same hints without re-filling the form.
What gets generated
For every entity type, the LLM returns:
| Artifact | What it is | Where it goes |
|---|---|---|
core_identity | A natural-language summary of what the entity is and who it's for. | Dashboard. Powers semantic search. Fed into JSON-LD description. |
reasoning | Structured: recommended_for, decision_logic, objection_handler, target_audience, plus entity-specific fields (purchase_intent for products, content_purpose for pages, seasonal_relevance for categories). | Dashboard tab. Used to generate FAQs. |
synthetic_properties | quality_perception, value_for_money, typical_competitors, meta_title, meta_description, related_entities. Plus entity-specific (price_range for products, content_freshness for pages). | Dashboard. Some fields propagate to the storefront (meta title, meta description). |
search_keywords | Bilingual (EN + ES) list of search terms shoppers actually type. | Fed into JSON-LD keywords, into meta description (top 5 appended), and into BC search_keywords (BC internal search). |
embedding | 1536-dimensional vector for semantic similarity search. | Used by Clione's internal search and the recommendation API. |
Entity parity: products, categories, collections and pages all get the same depth of reasoning and synthetic_properties. There is no "minimal" enrichment for non-products since the 2026-04-24 release.
Per-platform notes
BigCommerce
- Products propagate: meta_title (
page_title), meta_description,search_keywords,meta_keywords, canonical URL, and JSON-LD via the Schema Injector. - Categories propagate: meta_title, meta_description,
meta_keywords(as array),search_keywords. No JSON-LD yet. - Pages propagate: meta_title, meta_description,
meta_keywords(as comma-separated string — different from categories),search_keywords. No JSON-LD yet.
Shopify
- Products propagate:
title_tag(meta title),description_tag(meta description), canonical URL, and JSON-LD via the theme app block (must be enabled in your theme). - Collections propagate: meta_title, meta_description, canonical URL. No JSON-LD yet.
- Pages propagate: meta_title, meta_description, canonical URL. No JSON-LD yet.
Note: Shopify does not have meta_keywords or search_keywords fields. The bilingual keywords Clione generates are still stored and used in JSON-LD + the embed widget; they just don't write to a meta tag (Google has ignored meta_keywords since 2009 anyway).
See the full Platform capabilities matrix for a per-field reference.
Versioning and rollback
Every enrichment creates a new version. The last 3 versions per entity are retained automatically; older ones are pruned.
To rollback:
- Open the entity → History tab.
- Pick the version you want.
- Click Restore this version.
Restoring a past version re-propagates that version's fields to the storefront, so the live store flips back too.
If a product was manually edited between enrichments, the re-enrich confirm dialog asks you to type OVERWRITE to confirm — this prevents accidental loss of manual edits.
Re-enrichment cost
Every enrichment counts against your monthly quota, including re-enrichments and rollbacks-to-a-past-version-followed-by-re-enrich. The quota resets on the first of each calendar month (UTC).
If you go over quota:
- Single-entity enrichments are blocked with a clear error.
- Bulk-enrich jobs queue but do not start until your quota refreshes.
- The Account → Billing page shows quota usage live.
You can buy enrichment add-ons mid-month from Billing → Add-ons if you don't want to wait — see Billing.
What happens automatically (and what doesn't)
| Action | Manual or automatic? |
|---|---|
| First enrichment after sync | Manual. Clione does NOT auto-enrich anything on sync. You always pick what to enrich and confirm. |
| Propagation after a manual enrichment | Automatic. As soon as the enrichment completes, signals are pushed to the storefront. |
| Re-enrichment on price/description change | Manual. Sync brings in the new upstream values, but a re-enrichment is your call. |
| Version snapshot | Automatic. Every enrichment creates a snapshot, no action needed. |
| Cache invalidation | Automatic. The dashboard refreshes within seconds of enrichment finishing. |
Troubleshooting
"Enrich" button is greyed out — Either you've hit your monthly quota (check Billing), or the entity type isn't included in your plan's enrichmentEntityTypes limit. Starter, for example, may exclude pages. Upgrade or wait for the quota to refresh.
Bulk enrich completes but some entities show "not enriched" — Those specific entities errored in the background job. Open the entity directly to see the error message (usually a too-long description or a missing required field). Fix the source data and re-enrich that one.
Enriched product shows old meta title on storefront — Either auto-propagation failed (check Verification for the entity), or your storefront is heavily cached. Open the entity → Propagation tab → click Re-push to storefront to force a manual push. For storefront cache, allow up to 5 minutes for Shopify and up to your CDN TTL for BigCommerce.
JSON-LD missing on Shopify even after enrichment — The theme app block is not enabled. Without it, the metafield exists but the theme never renders it. Enable the block in your theme editor.
Bilingual keywords look generic / wrong — Use the Enrichment Wizard on that product. The LLM has more to work with when you give it target audience and key benefits explicitly.
Entity-detail pages
Every enriched entity gets a dedicated detail page in the dashboard:
- Product detail (
/store/<slug>/products/:id) — tabs: Overview, Enrichment, Edit, FAQs, Versions, Verification, Propagation, LLM Preview, Corpus, Raw JSON. - Category detail (BC) / Collection detail (Shopify) (
/store/<slug>/categories/:id) — same tab set, minus Variants. - Page detail (
/store/<slug>/pages/:id) — Overview, Enrichment, Edit, Versions, Verification, Propagation, Raw JSON.
Some tabs are plan-gated and hidden if your plan doesn't include the underlying feature (e.g. FAQs is hidden on the entity detail page if your plan doesn't include FAQ writes).
LLM Preview tab
The LLM Preview tab shows what the entity looks like to an LLM crawler — meta + JSON-LD + reasoning blob assembled the way ChatGPT or Perplexity would consume it. Use it when you want to sanity-check enrichment before propagation.
Corpus tab
The Corpus tab is the raw text the LLM was given (after HTML-stripping) plus the wizard answers. If an enrichment came out weird, this is the first place to look — usually a polluted description or a wrong category mapping is the cause.
Versions tab
See "Versioning and rollback" above. The last 3 versions are listed with diffs against the current.
Propagation tab
Shows each push of each signal to the platform — meta_title, meta_description, JSON-LD metafield. Each row has timestamp, platform status code, and the raw response body. If a propagation silently failed, this is where you find out.
The Enrichment Wizard — full reference
The Wizard has three sections:
1. Context (always shown)
- Target audience — open text. The LLM uses this to frame the identity and the recommended_for fields.
- Materials / construction — for physical products, used in quality scoring and durability assessment.
- Key benefits — bullet list. Drives the decision_logic field.
- Brand voice — formal, casual, technical, playful. Controls tone of the generated copy.
2. Competitors
- Typical competitors — list of brand + model entries. When you fill at least one, Clione locks the LLM out of regenerating the competitor list (your input wins). See Understanding scores.
3. Evidence (recommended for scoring uplift)
- Warranty — None / 6m / 1y / 2y / 3y / 5y / 10y / Lifetime.
- Certifications — comma-separated list (ISO 9001, CE, GOTS, OEKO-TEX, etc.).
- Returns rate — bracket from
<2%to>20%. - Customer reviews — aggregate rating + count.
- Manufacturing origin — country + manufacturer.
Filling 3+ of these flips the product's score badge from amber to green.
Wizard answers — per-platform persistence
Wizard answers are persisted in Clione's own database, not in the platform. They survive re-syncs and re-enrichments. If you delete the entity in BC / Shopify and re-create it (different ID), the wizard answers are lost.
If your tenant has multiple connected stores with the same product (e.g. BC + Shopify on the same SKU), wizard answers do not currently share — fill once per store. Cross-store wizard sharing is on the roadmap.