Skip to main content

Enrich your catalog

Enrichment is where Clione earns its keep. For each entity — a product, a category or collection, a content page — Clione asks an AI model to describe what it is, who it's for and how shoppers search for it, and writes a meta title, a meta description and search keywords from that. What it produces is explained in Understanding enrichment.

Sync never enriches. Syncing only imports your catalog; the model is not called. Every enrichment is an action you start and confirm.

You can enrich:

  • Products (BigCommerce and Shopify)
  • Categories (BigCommerce) / Collections (Shopify)
  • Pages (both platforms)

One enrichment of one entity uses one credit. Your monthly allowance belongs to your organization: it's shared across all entity types and all the stores in the organization.


Monthly enrichment quota​

How many enrichments a month your plan includes, and which entity types it can enrich, is on Billing & Plan; every plan side by side is in Plans. Some plans enrich products only.

The allowance resets on the 1st of each calendar month (UTC). The Enrichments counter in the store panel shows how many you've used and when it refreshes.

When you run out:

  • A single-entity enrichment is refused with a quota message.
  • A bulk run enriches only what fits in your remaining quota and skips the rest. The confirm dialog tells you how many will run before you start, and your selection is kept so you can finish later.

To keep going before the month ends, upgrade your plan or buy Expand credits from Billing & Plan → Add-ons. Expand credits raise your enrichment allowance only, not your product limit. See Billing.


Three ways to enrich​

1. One entity​

  1. Open the product, category, collection or page.
  2. Click ✦ Enrich with AI in the header.
  3. Confirm in the dialog (Enrich this product? → Enrich now).

The result usually appears within seconds. A new version is saved automatically, and the previous one stays in the History tab.

If someone edited the entity by hand, the dialog warns you first: enriching replaces those manual edits with the new AI output.

2. Bulk, from a listing​

From the Products, Categories / Collections or Content list:

  1. Tick the entities you want. A bar appears at the bottom of the list. Select all … available extends the selection to everything that matches your filter.

  2. Click Enrich selected.

  3. The confirm dialog shows three numbers:

    LineMeaning
    SelectedHow many you ticked.
    Will be enrichedHow many will run now — the smaller of your selection and your remaining quota.
    Monthly quota remainingCredits left this month, or Unlimited.

    If your selection is larger than your remaining quota, a warning says how many will run and how many will be skipped.

  4. Click Enrich now to start, or Cancel to close the dialog without spending anything.

The run continues in the background. A progress bar at the bottom of the dashboard shows processed / total (and failures, if any) and survives navigation.

The dialog is the only way a bulk enrichment starts. Clione never enriches on sync, on an edit, on a plan change or on any other trigger.

3. Teach the AI (guided)​

Every entity's first tab has a Teach the AI questionnaire: Teach the AI about this product, …about this category, …about this content. It collects what Clione can't read from your catalog data.

For products:

  • About the product — who it's for, what it does, what it's made of.
  • Positioning & context — competitors, seasonality, price positioning.
  • Verifiable evidence — warranty, certifications, returns rate, reviews and manufacturing origin, which ground the quality scores in facts.
  • Specific to your sector — extra questions for your kind of catalog, when your store has a sector set. Answers are quoted as you write them.

For categories, collections and pages, one short section: About this category (who shops there, what they look for, what makes your assortment worth choosing) or About this content (who it's for, what it delivers, what it supports in your catalog).

Short answers are fine; skip what you don't know. Answers are saved on the entity and sent as context with its next enrichment — click ✦ Enrich with AI when you're done. Use it for the products and pages that matter most.


After enrichment​

Enrichment writes to Clione only. Nothing reaches your storefront until you publish it:

  • To put the new meta title, meta description and structured data on your storefront, see Publish.
  • To go back to an earlier version or undo a publication, see Rollback.
  • To review the output before publishing, see Review and approve.

Publishing many at once​

Publishing one entity happens from its Publish tab. To publish many, you have two places. Publishing never uses credits.

From a list. On Products, Categories / Collections or Content:

  • Publish selected in the bar at the bottom publishes the rows you ticked.
  • Publish signals… in the same bar publishes only the signals you pick (for example, only the FAQs) for the rows you ticked.
  • Publish All at the top publishes every entity in the list.

From the Publishing page. Click Publishing in the store menu. It has two tabs:

  • Push — Bulk publish (Publish All to Store) publishes every product of the store. Below it, Ready to publish lists the entities enriched since their last successful push (or never published), and Failures lists the pushes that never reached your store, each with Retry.
  • Log — every signal pushed, newest first, with its status and whether verification found it live. Filter by status or search by entity, signal or error.

Every bulk publish asks first. The dialog says how many entities it will write (or that it is the whole catalog) and asks you to type PUBLISH to confirm, because search engines will index what lands on your storefront. Each entity keeps a rollback point.

The run continues in the background, in batches, with a progress bar at the bottom of the dashboard. A bulk publish started from the Publishing page can be cancelled there; what was already published stays published.


What happens automatically (and what doesn't)​

ActionManual or automatic?
Enrichment after a syncManual. Sync never enriches.
Publishing after an enrichmentManual. Every write to your storefront comes from a publish you start.
Re-enrichment after a price or description changeManual. Sync brings in the new values; re-enriching is your call.
Version snapshotAutomatic. Every enrichment saves a version; the 3 most recent are kept.

Troubleshooting​

Enriching is refused — If you've used your monthly quota, the enrichment is refused with error 402 and a message saying the monthly enrichment quota is exhausted (check the Enrichments counter). If your plan doesn't include that entity type (some plans enrich products only), it's refused with a message saying your plan doesn't include that enrichment.

A bulk run finishes with failures — The progress bar and the toast say how many failed. Open those entities and enrich them one at a time to see the error.

The storefront still shows the old meta title — The enrichment hasn't been published. See Publish.

Keywords or copy look generic — Fill the Teach the AI questionnaire on that entity and enrich it again. The model does better with your audience and key benefits spelled out.

Citation markers and source-text warnings​

Internal AI citation markers are not product copy. Clione rejects generated content containing those markers and allows one regeneration. If the marker persists, the item needs review; the rejected candidate is not published.

Before single or bulk approval, Clione checks the saved proposal as well as the text submitted for review. Remove internal citation markers before approving. Possible numeric footnotes and chat leftovers show a warning: inspect them and explicitly acknowledge the warning if the text is correct. Model names such as “SL60W [II]” are not blocked merely for using brackets. A changed proposal needs a new review. You can still reject a flagged proposal.

On Store Overview → Content quality and review, choose products, categories, collections or pages and click Check synced text. This read-only report finds markers in the store’s original title, description and meta, even before enrichment. It never changes source text or blocks sync. It checks a bounded page at a time: use Check next page to continue. No flags on one page does not certify the whole catalogue.

Generated FAQs with possible chat leftovers or ordinary footnotes await review instead of being published automatically. The same warning confirmation applies when you approve selected FAQs or save a shared library answer. Cancelling the confirmation publishes nothing. Internal citation markers must be removed.

In a PIM feed’s activity, Check held products lists identifiers and review reasons for the current build. This check does not publish or count as a download. Correct the content and approve it before checking the next build. Previously approved storefront content is not automatically rewritten by this safeguard.