Skip to main content
Enrichment in Cernel happens in two steps. First, a job runs your AI agents across the products you selected and proposes new attribute values. Then, on the Review surface, you approve, edit, or reject those proposed values before they’re saved to your products and synced to your integrations. The Jobs page tracks the runs; Review is where you make the decisions.

​
How it works

When you select products and click Enrich Products, Cernel creates a job that processes each product with the AI agents linked to your selected attributes. Jobs run in the background, so you can keep working while content generates. What happens to the generated values depends on the Review toggle in the enrichment modal:
  • Review on: proposed values are held as pending and collected on the Review surface, where you approve, edit, or reject them before they go live.
  • Review off: proposed values are applied to your products automatically as soon as they’re generated, with no approval step.
The Jobs page (sidebar → Jobs) tracks every run with progress indicators, plus a search box and filters to find a past run. The Dashboard also surfaces a compact Recent jobs widget. The Review surface, reached from the Review tab on the Products area, or by opening a job from the Jobs page, is where proposed values wait for your decision.

​
Why you would use this

Stay in control of what goes live

Nothing is saved to your products until you approve it. Review proposed values one product at a time, or approve in bulk when you trust the output.

Understand every proposed value

For each value, see the prompt that produced it, the agent’s reasoning, the inputs it used, and where any translation came from, so you can decide with confidence.

Never lose track of enrichment progress

See at a glance how many jobs are running, how far along they are, and who started them.

Catch and fix issues quickly

Failed and skipped values are surfaced for you to dismiss, so your review queue reflects only what still needs a decision.

​
Running enrichment

1

Select a category and products

In the sidebar under Catalog, click on a category to view its products. Use the checkboxes to choose which products to enrich, or use the header checkbox to select all visible products.
2

Choose attributes and start

Click Enrich Products. The Configure Enrichment modal opens:
  1. Optionally give the run a Title so it’s easy to find later on the Jobs page. Leave it blank and Cernel names the job for you from the attributes and category you picked (for example, Color from Electronics)
  2. Set the Product Scope. It opens on Include child products, so a master product and its variants are enriched together, which is what variant-heavy catalogs usually want. Switch it to enrich the selected products only, or to Only child products, if you’d rather narrow the run
  3. Toggle Review on to hold generated values for approval on the Review surface before they’re saved, or off to apply them automatically. Its starting position follows your organization’s approve-before-push setting, and you can override it per run
  4. Toggle Only enrich missing fields on if you only want to fill in attributes that are currently empty (existing values won’t be overwritten). Leave it off to re-enrich all selected attributes
  5. Check the Attributes you want to generate (only attributes with a linked agent appear here, so use the search box to find specific ones)
  6. Under Language Configuration, choose what happens for each enabled language: Generate the content from scratch, Translate it from another language, or Skip it. Use Apply to all to set every language at once
  7. Click Preview to see a summary of the run, then Start Enrichment to dispatch it
The Configure Enrichment modal showing the optional Title field, the Product Scope selector, the Review and Only enrich missing fields toggles, the Attributes picker, and the Language Configuration section with Generate, Translate, and Skip options for each language
The attribute count shown (e.g., “Available Attributes (5)”) only includes attributes that have an AI agent linked. If you’re missing an expected attribute, check the category’s attribute configuration.
To pick several attributes at once, click the first one, then hold Shift and click another: every attribute between the two is selected together. The range follows the list as shown, so if you’ve typed in the search box it covers just the matching attributes.
Use Only enrich missing fields when you’ve added a new attribute to a large catalog and want to backfill values for products that lack one, without touching anything you’ve already reviewed or hand-edited.
Each enrichment run processes up to 5,000 products. If you select more than that, only the first 5,000 are enriched in that run, and the rest are left untouched, with no error. To enrich a larger catalog, split it into batches of 5,000 or fewer (see below).

​
Filtering the product list

A category can hold thousands of products, so the toolbar above the product table lets you narrow the list to exactly the set you want before you enrich. Filtering is how you build a batch, focus on products that are still missing a value, or find everything a particular integration populated. Open Filter in the toolbar above the table, then click Add filter to build a condition. Each condition reads like a sentence, for example Where Color has no data. You can filter on:
  • Product attributes and Category attributes: filter by an attribute’s value, using the operators below.
  • Product properties: built-in fields such as the created date, an identifier (SKU or GTIN), whether the product Has images, and which integration or CSV import populated its values.
For an attribute condition, pick an operator:
Updated before / Updated after matches any change to the attribute’s value, not only ones from AI enrichment. An update pulled in from a connected integration (for example, a product edited in Shopify and synced to Cernel) counts too.
Has no data and Does not contain are the two you’ll reach for most when building enrichment batches. Has no data isolates the products that still need a value, and Does not contain lets you exclude products whose value already includes a term.
Add as many conditions as you need and join them with and or or. Switch between Simple and Advanced to keep a flat list of conditions or to group them into logic. Save a filter you use often from the Saved filters menu to reapply it in one click, and use Clear all filters to reset the table.

​
Enriching a large catalog in batches

When you have more than 5,000 products to enrich, work through them in batches and let each batch finish before starting the next:
1

Turn on Only enrich missing fields

In the enrichment modal, enable Only enrich missing fields. Each run then targets only products that still lack a value for the selected attributes, so finished products drop out of the next batch automatically.
2

Filter down to a batch

Use the product filters to narrow the selection to 5,000 products or fewer. For example, add a Has no data condition on the target attribute to show only products that still need a value.
3

Run and wait for it to finish

Start the enrichment and wait for the job to complete on the Jobs page before starting the next batch. Running back-to-back filtered batches in parallel can overlap on the same products.
4

Repeat until the column is empty

Re-apply the Has no data filter for products that still lack a value and run again. Repeat until no products remain. Track progress on the Jobs page and by filtering the attribute for products with no data.

​
Editing values in bulk

Sometimes you need to change many values by hand rather than enrich them: fixing the same wrong value across a batch of products, clearing a field before a re-run, or setting a shared value that no agent produces. Bulk select turns the product table into a grid you can select across, so you can set, clear, or enrich a whole block of values at once.

​
Selecting the values to change

Click Bulk select in the toolbar above the table to turn on selection mode. You can then pick values in a few ways:
  • A single value: click its cell.
  • A whole product: tick the product’s row to take all of its values.
  • A block: drag across cells, or click one cell and hold Shift while clicking another to extend the range. Hold the add/remove key (Cmd on Mac, Ctrl on Windows) to add or remove cells without clearing the rest.
A bar at the bottom of the table keeps a running count of what you’ve picked, for example 3 values, 1 attribute, 3 products, and lists the keyboard shortcut for each action. Press V to turn selection mode on and off, and Esc when you’re done.
The product table in Bulk select mode with three Web Research cells highlighted across three rows, and a selection bar reading '3 values, 1 attribute, 3 products' with Enrich and Bulk edit values buttons and a legend of keyboard shortcuts

​
Setting or clearing values by hand

With a selection in place, click Bulk edit values to open the editor. The attributes you selected are listed on the left; pick one to edit. For that attribute, and for each enabled language, choose what to do:
  • Set value: type the value that every selected product should get.
  • Clear: remove the existing value from the selected products. An attribute that must always have a value can’t be cleared.
  • Leave as is: skip the field, so nothing is written for it.
Click Apply to [n] values to write your changes. Because this overwrites the selected products and can’t be undone from the dialog, Cernel first asks you to confirm, showing exactly how many values and products it will change. Turn on Send for review to propose the edits on the Review surface instead, so they wait for approval before they’re saved.
The Bulk edit attribute values modal: the selected attribute and product count on the left, a language selector, and Leave as is, Set value, and Clear options with a text field and an Apply button
A single bulk edit covers up to a set number of values. If your selection is larger, Cernel updates the first batch and tells you how many values were left unchanged, so you can narrow the selection, or run the edit again, to finish the rest.

​
Enriching a selection

Instead of typing values, click Enrich on the selection bar to generate the selected values with AI, using the same agents as a full enrichment run. Enrich needs a rectangular selection, meaning the same products picked in every selected attribute, so if your selection is ragged, drag a block rather than picking single cells. Bulk select is also available on the Review surface, where you can edit or decide many proposed values together before they’re saved. See Deciding in bulk.

​
The Jobs page

Open the Jobs page from the sidebar to see a table of your jobs, newest first. Each row in the table shows:
  • Name: the job’s title (the one you set, or the one Cernel generated from the attributes and category), or its ID if untitled
  • Status: a colored badge: Pending, Running, Success, Failed, or Cancelled
  • Progress: how many elements are done out of the total (for example, 42 / 100)
  • Trigger: how it was started, by an Automation or run manually
  • Created by: the teammate who started the job
  • Created: when the job started
  • Actions: rename the job at any time, and cancel the job while it’s still running
Click any row to open that job’s proposed values on the Review surface, already scoped to the job. The Jobs page itself is for tracking. All approve, edit, and reject actions happen on Review.
The Jobs page showing the search box and the Status, Trigger, Created by, Product, and date filters above a table of jobs with Name, Status, Progress, Trigger, Created by, and Created columns, and a rename (pencil) action on every row
A job-status indicator sits in the app header and stays visible while you’re signed in, so you can keep an eye on active work from anywhere in the app. It spins while jobs are running and shows a count of active jobs. Click it to open the Running jobs list, jump straight to a job, or choose View all jobs to go to the Jobs page.

​
Finding a job

A search box and a row of filters sit above the table so you can narrow a long history to the run you’re after:
  • Search jobs by name to match on the job title
  • Status: show only Pending, Running, Success, Failed, or Cancelled jobs
  • Trigger: show only jobs started by an Automation or run manually
  • Created by: show only jobs a particular teammate started
  • Product: show only jobs that ran on a specific product
  • From and To: limit to jobs created within a date range
Use Clear filters to reset them all at once.

​
Renaming a job

Every job can be renamed, whatever its status. Enrichment setup has several steps and the job title is easy to skip past, so you can give a run a clearer name after it has started, or even once it has finished. In the Actions column, click the Rename job action, type a new Job name, and click Save. The new name appears everywhere the job is shown, including the header job-status list. A blank name, or a name you haven’t changed, can’t be saved.

​
Cancelling a job

While a job is Pending or Running, a Cancel job action appears in its Actions column. Cancelling stops the run: anything already finished is kept, but the remaining items aren’t processed, and this can’t be undone. Cernel asks you to confirm (Cancel job to go ahead, or Keep running to leave it) before stopping the job. Finished jobs (Success, Failed, or already Cancelled) have nothing left to stop, so they show no cancel action.

​
Older jobs

Jobs run before the Jobs & Review update are kept available under Show older jobs at the bottom of the page. Expand it to browse your earlier history; collapse it again with Hide older jobs.

​
Recent jobs on the Dashboard

The Dashboard’s Recent jobs widget shows the most recent runs at a glance, with the same status and progress information. Use it to jump to the full Jobs page when you need the complete history.

​
Job statuses

A finished job (Success) doesn’t mean its values are live. If the run had Review turned on, the proposed values wait for your approval on the Review surface (see below).

​
Reviewing proposed values

When a run has Review turned on, the values your agents generate aren’t saved straight away. They wait on the Review surface as proposed values until you approve, edit, or reject them. This is where you decide what actually goes live on your products.

​
Where Review lives

There are two ways into Review:
  • From the Products area: at the top of the Products screen, switch between Catalog (browse your products) and Review (work through proposed values). The switch keeps whichever category you have selected, so you can jump straight from a category’s products to that category’s review queue. Pick categories from the taxonomy tree in the sidebar to narrow what you’re reviewing.
  • From a job: click any job on the Jobs page to open the review queue scoped to just that job’s products. A Back to jobs link returns you to the Jobs page.

​
The review queue

The review queue lists one row per product, with a card for each proposed value. Every card shows the attribute, the proposed value, the language, and a status badge: Use the toolbar to focus the queue:
  • Search by product name
  • Languages: show only the languages you want to review
  • Filter by job: narrow to a single job’s products
  • Attribute filter: hide or show value cards by attribute
  • Show failed & skipped: on by default; turn it off to see only values that are waiting for a decision
  • View options: let each card grow on a sideways-scrolling row, or lay values out in a column per language
The Review surface: the Catalog / Review switcher at the top, the product and review filters (languages, jobs, attributes, and a Show failed & skipped toggle), and the queue listing products with their proposed-value cards and bulk Dismiss, Reject, and Approve actions

​
Approving, rejecting, and dismissing

You have three actions, depending on a value’s state:
  • Approve: accept the proposed value; it replaces the product’s current value for that attribute.
  • Reject: discard the proposed value; the product’s current value is left unchanged.
  • Dismiss: acknowledge a Failed or Skipped value. There’s nothing to approve or reject, so dismissing simply clears it from your queue once you’ve seen it.
Both Approve and Reject let you add an optional comment to record why you made the call, useful for teammates reviewing the same catalog later. To work quickly, select multiple cards (or whole product rows) and use the bulk Approve, Reject, or Dismiss buttons. To decide the whole queue in one go, use the header select all: this reaches every in-review value that matches your current filters, including products beyond the ones loaded on screen, so you don’t have to scroll to the bottom first. When you’re reviewing a single job, select all covers that job’s entire pending set the same way. You can still deselect individual products to leave them out. When a bulk decision spans many products at once, Cernel asks you to confirm before applying it.
Keep Show failed & skipped on while you work through a new job so you can dismiss the values that didn’t generate, then your queue reflects only the decisions you still owe.

​
Reviewing one product in detail

Click a product (or open a single value) to go to its detail view, which lays everything out in three columns:
  • Current value: what’s saved on the product right now. Approving a proposed value replaces it.
  • Pending · In review: the proposed values awaiting your decision. Select one to inspect it.
  • Inspector: everything behind the selected value, so you can decide with full context.
The product review detail view with three columns (Current value, the Pending in-review proposed values, and an Inspector showing the value's status, language, translation source, and the Used attributes, Reasoning, and Prompt tabs), with Previous, Next, and Approve all controls in the header
The Inspector shows the value’s status, attribute, language, source (for example, AI enrichment), and date. If the value was translated, it notes which language it was translated from. Three tabs explain how the value was produced:
  • Used attributes: the product data the agent fed into its prompt as inputs
  • Reasoning: the agent’s own explanation of why it generated this value
  • Prompt: the exact compiled prompt, including any images, that produced the value
From here you can Approve or Reject the selected value (with an optional comment), edit it inline before approving, or use Approve all to accept every still-pending value on the product. Previous and Next move you through the products in your current queue or job without returning to the list.
When you’re reviewing a single job, decided values stay visible in place, marked with their decision, instead of disappearing. In the general queue, a product drops out once you’ve resolved its values.

​
Understanding value sources

Every attribute value carries a source so you can tell where the data came from. In the product table, hover over an attribute value to open its details popover. The source appears there alongside the value, with a label and icon:

​
Advanced configuration

Click a job on the Jobs page to open the review queue scoped to just that job’s products. In this job-focused view, values you’ve already decided stay visible in place, marked Approved or Rejected, so you can see the full picture of what the job produced. A Back to jobs link takes you back to the Jobs page when you’re done.
If your organization has multiple languages enabled, agents generate values for each configured language, and each value shows its language. Use the Languages filter in the review toolbar to focus on one or more languages, or switch on Language columns in View options to lay each product’s proposed values out in a column per language. Manage languages in Tools > Languages.
Select multiple value cards, or tick a whole product row to select all of its values, then use the bulk Approve, Reject, or Dismiss buttons. You can attach an optional comment to a bulk Approve or Reject. When a decision spans a large number of products at once, Cernel asks you to confirm before applying it.Use the header select all to decide the entire queue at once. Cernel resolves this against your current filters (languages, attributes, and, in a job review, the job in focus), so it approves or rejects every matching in-review value, including products beyond the ones currently loaded on screen. Deselect individual products first if you want to leave them out, and the confirmation dialog will note how many you excluded.
Not every value generates successfully. Failed values are ones the agent couldn’t produce; Skipped values are ones it had nothing to generate for. These can’t be approved or rejected; instead, Dismiss them to acknowledge you’ve seen them and clear them from your queue. Keep Show failed & skipped turned on to handle them; turn it off to see only values awaiting a decision.

​
Frequently asked questions

Open the job from the Jobs page to see its status, and check the review queue for any values marked Failed. Common causes:
  1. Agent configuration issue: the linked agent’s prompt may be empty or invalid
  2. Missing dependencies: a required attribute dependency isn’t enriched yet
  3. API error: a temporary issue with the AI provider
Not directly. Instead, go back to the product table, select the products that failed, and start a new enrichment. Check the agent configuration first to fix whatever caused the failure.
Enrichment no longer fails just because a single image is unusable. If an image can’t be fetched, isn’t a valid image, or is unusually large, Cernel skips that one image and generates the value from the product’s remaining inputs (its other images, text, and attributes). A run only fails when nothing usable is left to work from.When an image is skipped, the agent records a short note in its Reasoning, for example “A product image was not processed (the image exceeds the size limit)” followed by the image’s address. Open the value in the review detail view and check the Reasoning tab to see it. If a generated value seems to be missing detail you expected from a photo, this note is the first place to look.
Yes, while it’s still Pending or Running. Open the Jobs page and use the Cancel job action in that job’s Actions column, then confirm. Cancelling stops the run: anything already finished is kept, but the remaining items aren’t processed, and it can’t be undone. Once a job reaches Success, Failed, or Cancelled, there’s nothing left to stop, so no cancel action is shown. See Cancelling a job.
Yes. The Configure Enrichment modal has an optional Title field. Whatever you type there becomes the job’s Name on the Jobs page, so a run is easy to find later. Leave it blank and Cernel names the job for you from the attributes and category you selected (for example, Color from Electronics). You can also rename a job later, in any status: use the Rename job action in its Actions column on the Jobs page. See Renaming a job.
Reject is a decision about a value the agent did generate: you’re declining to save it, and the product keeps its current value. Dismiss applies to Failed or Skipped values, where there’s nothing to save in the first place; dismissing just acknowledges you’ve seen them and removes them from your queue.
They wait on the Review surface as proposed values until you act on them. Nothing is saved to your products or synced to your integrations until you approve it. Reach Review from the Review tab on the Products area, or by opening a job from the Jobs page. The starting position of the Review toggle in the enrichment modal follows your organization’s approve-before-push setting (in Settings > Platform), and you can override it for any individual run.
Changing the organization’s approve-before-push setting only affects future runs: it sets the default position of the Review toggle when you start an enrichment. It does not retroactively approve or push values that are already waiting in Review. Those still need a decision: approve them from the Review surface, or reject them if you don’t want them.
Each enrichment run processes up to 5,000 products. If you select more, only the first 5,000 are enriched in that run and the rest are silently skipped. For larger catalogs, enrich in batches of 5,000 or fewer, turning on Only enrich missing fields and waiting for each job to finish before starting the next. See Enriching a large catalog in batches.
Yes. Click Bulk select in the product table toolbar, pick the cells, rows, or columns you want (drag or Shift-click to take a block), then click Bulk edit values to Set value, Clear, or Leave as is for each attribute and language. This writes the values directly, so use Send for review in the editor if you’d rather have them approved first. See Editing values in bulk.
No. Writing values in the bulk editor overwrites the selected products and can’t be undone from the dialog, which is why Cernel asks you to confirm the count first. If you want a safety step, turn on Send for review so the edits wait as proposed values on the Review surface until you approve them.
Yes. By default the product table’s search and filters match parent products only. Turn on the Search within children toggle in the product table toolbar to widen the match to child products as well, so you can land on an individual variant. The toggle stays disabled until you enter a search term or apply a filter, since it needs something to match against.With it on, each matching variant appears under its parent product, with extra columns for the properties that set that variant apart and the matched text highlighted, so you can see exactly which children matched and why.Once you’ve found the variants you want, select the parent product and set the Product Scope in the enrichment modal: choose to include child products, or to run only on the children. See Running enrichment for the scope options.
Yes. When you enrich variants (with a Product Scope of Include child products or Only child products), their proposed values wait for a decision on the Review surface just like a parent product’s. Selecting a category in the sidebar, or applying a search or filter, keeps the variants in view: each variant lists as its own row alongside its parent, and you approve, edit, or reject its values the same way.Bulk actions cover variants too. When you use the header select all to decide a whole category or a whole job, every matching variant value is included, not only the parent products. For variant-heavy catalogs this means the queue can show many more rows than you have parent products, since each enriched variant contributes its own.
Yes. Cernel supports multi-language enrichment. The enrichment modal shows your enabled languages, and AI generates content in each configured language. You can manage languages in Tools > Languages.
Turn on Only enrich missing fields in the enrichment modal. When this toggle is on, the AI only generates values for attributes that have no value yet; existing values you’ve reviewed or hand-edited are left alone. Turn it off to re-enrich every selected attribute, overwriting current values.
Most products finish in under a minute. Text attributes are the quickest, while attributes that generate images or pull in external data can take a few minutes per product.Adding more attributes does not make enrichment slower. Cernel works on all selected attributes for a product at the same time, so the total wait is only as long as the slowest one.Small batches typically complete in seconds. Larger runs across hundreds of products may take several minutes. If you have multiple jobs running at once, they may take a little longer as Cernel shares capacity fairly across your workspace.
Jobs remain visible on the Jobs page. Recent runs appear at the top; earlier history, including jobs from before the Jobs & Review update, is available under Show older jobs. The Dashboard’s Recent jobs widget gives you a quick view of the latest runs with a link through to the full page.

​
What’s next

AI Agents

Create and refine agents to improve the quality of your enrichment output.

Automations

Set up automatic enrichment for new products so you don’t have to start jobs by hand.