Skip to main content

Attribute Extraction

Attribute Extraction allows AI Workflows to automatically detect and fill structured product attributes based on existing product content.

Instead of manually completing product data, AI can analyze descriptions, specifications and other content to generate missing attribute values automatically.

This is especially useful when supplier data is incomplete or unstructured.


What Attribute Extraction does

Attribute Extraction reads existing product information and converts it into structured attribute data.

Examples:

  • extracting flavor from descriptions

  • identifying material types

  • detecting product dimensions

  • assigning lifecycle stages

  • identifying sustainability labels

  • recognizing technical specifications

The generated values are written into selected attributes inside Elovate.


Why Attribute Extraction matters

Many suppliers only provide:

  • raw descriptions

  • short titles

  • inconsistent specifications

without proper attribute structures.

This creates problems for:

  • filters

  • search

  • marketplaces

  • Google Shopping

  • catalog consistency

Attribute Extraction helps automate this process at scale.


Common use cases

Attribute Extraction is commonly used for:

  • filling missing attributes

  • improving product filters

  • enriching supplier catalogs

  • preparing products for marketplaces

  • improving Google Shopping feeds

  • standardizing catalog structures


Example use case

A supplier provides only this description:

"Premium salmon cat food for adult cats with sensitive digestion."

AI can automatically extract:

  • Flavor β†’ Salmon

  • Life stage β†’ Adult

  • Dietary type β†’ Sensitive digestion

These attributes can then be used for:

  • storefront filters

  • shopping feeds

  • enrichment workflows

  • translations


How Attribute Extraction works

An Attribute Extraction action consists of:

  1. AI configuration

  2. selected attributes

  3. extraction prompts

  4. moderation settings

  5. testing

  6. execution

The workflow processes products individually and attempts to fill the configured attributes automatically.


Creating an Attribute Extraction action

Inside a workflow:

  1. Open the workflow

  2. Click Add new action

  3. Select Attribute Extraction

You will then enter the Attribute Extraction configuration screen.


Configuring Attribute Extraction

The configuration screen allows you to customize how extraction behaves.

Common settings include:

  • action name

  • AI provider

  • AI model

  • moderation settings

  • editors

  • moderators

  • attributes to fill

  • prompts

  • scope

  • test products


AI provider and model

You can select:

  • the AI platform

  • the AI model used for extraction

Example:

  • OpenAI

  • GPT-5-mini

Different models may affect:

  • extraction quality

  • speed

  • reasoning quality

  • processing costs


Selecting attributes

You must choose which attributes the AI should fill.

Examples:

  • Flavor

  • Material

  • Lifecycle

  • Gender

  • Dimensions

  • Color

  • Weight

Only selected attributes are processed.


Prompt configuration

The prompt determines how the AI should extract information.

Prompts can range from:

  • simple instructions
    to

  • advanced extraction templates

Example:
"Extract the flavor and lifecycle stage from the product description."

Advanced prompts may:

  • use multiple fields

  • apply business logic

  • validate output structures

  • use internet assisted context

Prompt quality strongly affects extraction accuracy.


Scope settings

The scope determines which products the action can process.

This is often linked to:

  • workflow trigger rules

  • product groups

  • test selections

Well defined scopes improve:

  • performance

  • relevance

  • moderation efficiency


Testing Attribute Extraction

Before running the action on large product groups, you can test extraction on selected products.

Testing helps validate:

  • extraction accuracy

  • prompt behavior

  • attribute quality

  • AI reasoning

This is strongly recommended before full execution.


Understanding test results

Test results display:

  • generated attributes

  • extracted values

  • confidence scoring

  • AI reasoning

  • moderation controls

You can:

  • inspect results

  • approve outputs

  • decline outputs

  • synchronize accepted values


AI reasoning

Reasoning explains why the AI selected certain attribute values.

Example:
"The description references adult salmon cat food, therefore Flavor was set to Salmon and Lifecycle to Adult."

Reasoning improves transparency and moderation control.


Confidence scoring

Confidence scoring indicates how certain the AI is about the generated result.

Higher scores usually indicate:

  • clearer product information

  • stronger extraction certainty

Lower scores may require:

  • manual review

  • prompt adjustments

  • better source content


Running Attribute Extraction

After testing:

  1. return to the workflow overview

  2. open the action

  3. click Run action

Products are then processed individually through the extraction pipeline.

Results become visible inside the Results tab.


Results tab

The Results tab displays:

  • processed products

  • generated values

  • synchronization status

  • moderation state

  • completed tasks

  • failed tasks

This provides visibility into extraction progress.


Moderation and synchronization

Depending on the workflow configuration:

  • outputs may require approval

  • editors may review content

  • moderators may approve synchronization

Once approved, extracted attributes synchronize back into the product data.


Best practices for Attribute Extraction

Start with focused attributes

Begin with simple high confidence attributes such as:

  • color

  • flavor

  • lifecycle

  • material

before attempting more complex extraction logic.


Use category specific workflows

Different categories often require different extraction logic.

Example:

  • Fashion workflows

  • Electronics workflows

  • Pet food workflows

This improves extraction accuracy.


Test prompts carefully

Always test:

  • edge cases

  • incomplete descriptions

  • multilingual content

  • inconsistent supplier data

before running large workflows.


Review low confidence results

Low confidence outputs may require:

  • moderation

  • better prompts

  • cleaner source content

Confidence scoring should help prioritize manual review.


Example workflow

Example:
A webshop imports pet food products with incomplete attribute data.

Workflow:

  1. Trigger selects products in Dry Cat Food category

  2. Attribute Extraction fills:

    • Flavor

    • Lifecycle

  3. Content Enrichment generates:

    • Google Shopping descriptions

  4. Translation converts content to German

  5. Moderation reviews output

  6. Approved data synchronizes to Magento

This entire process runs automatically inside one AI Workflow.

Did this answer your question?