Category Mapping allows AI Workflows to automatically assign products to categories using AI.
Instead of manually categorizing products, AI can analyze product content and determine the most relevant category structure automatically.
This is especially useful for:
supplier imports
large catalogs
marketplace onboarding
inconsistent category structures
catalog cleanup projects
What Category Mapping does
Category Mapping analyzes product information such as:
titles
descriptions
attributes
specifications
existing metadata
and matches products to the most relevant categories inside your catalog structure.
Examples:
assigning products to webshop categories
mapping supplier categories to internal categories
organizing uncategorized products
improving catalog consistency
Why Category Mapping matters
Incorrect or missing categories can negatively impact:
storefront navigation
product discoverability
filters
SEO structure
marketplace synchronization
conversion rates
Manual categorization becomes difficult at scale, especially when importing large supplier catalogs.
Category Mapping helps automate this process.
Common use cases
Category Mapping is commonly used for:
supplier catalog imports
marketplace integrations
category cleanup projects
automated product onboarding
replacing inconsistent supplier categories
improving webshop navigation
Example use case
A supplier imports products using inconsistent category names such as:
Cat Dry Food
Dry Food Cats
Adult Cat Kibble
AI can automatically map these products into:
Pets β Cats β Dry Cat Food
This creates a cleaner and more consistent catalog structure.
How Category Mapping works
A Category Mapping action consists of:
AI configuration
category selection logic
prompts
moderation settings
testing
execution
Products are processed individually through the mapping pipeline.
Creating a Category Mapping action
Inside a workflow:
Open the workflow
Click Add new action
Select Category Mapping
You will then enter the Category Mapping configuration screen.
Configuring Category Mapping
The configuration screen allows you to define how products should be categorized.
Common settings include:
action name
AI provider
AI model
moderation settings
editors
moderators
target category structure
prompts
scope
test products
AI provider and model
You can select:
the AI platform
the AI model used for category mapping
Example:
OpenAI
GPT-5-mini
Different models may affect:
categorization accuracy
reasoning quality
processing speed
classification consistency
Category selection logic
AI determines the most relevant category based on product information.
Examples of analyzed data:
product title
descriptions
extracted attributes
technical specifications
supplier categories
The AI then suggests the best matching category inside your catalog structure.
Prompt configuration
Prompts define how AI should categorize products.
Simple example:
"Assign the product to the most relevant webshop category."
Advanced prompts may include:
category hierarchy instructions
exclusion logic
business rules
supplier mapping logic
category naming standards
Example category mapping prompt
Example:
"Assign products to the most relevant ecommerce category based on the product description and attributes. Prefer the deepest matching category when possible."
Using extracted workflow data
Category Mapping often performs better after Attribute Extraction.
Example:
Attribute Extraction identifies:
product type
material
lifecycle
Category Mapping uses these attributes for more accurate classification
This creates stronger category consistency.
Scope settings
The scope determines which products the action processes.
This is often controlled through:
workflow trigger rules
supplier selections
uncategorized product filters
store scope conditions
Focused scopes improve:
mapping quality
moderation efficiency
workflow control
Testing Category Mapping
Before running large category mapping actions, you can test categorization on selected products.
Testing helps validate:
category accuracy
hierarchy selection
business logic
classification consistency
Testing is strongly recommended before large scale execution.
Understanding test results
Test results display:
suggested categories
AI reasoning
confidence scoring
moderation controls
You can:
review suggested mappings
approve category assignments
decline incorrect mappings
synchronize accepted results
AI reasoning
Reasoning explains why the AI selected a specific category.
Example:
"The product was categorized as Dry Cat Food because the description references adult cat kibble and dry nutrition."
Reasoning improves transparency and moderation control.
Confidence scoring
Confidence scores indicate how certain the AI is about the suggested category.
Higher confidence often means:
clear product descriptions
strong product identifiers
well structured category hierarchies
Lower confidence may indicate:
ambiguous products
overlapping categories
incomplete product information
Running Category Mapping
After testing:
return to the workflow overview
open the Category Mapping action
click Run action
Products are then processed individually through the mapping pipeline.
Results become visible inside the Results tab.
Results tab
The Results tab displays:
suggested categories
moderation states
synchronization status
completed tasks
failed tasks
processing progress
This provides visibility into mapping execution.
Moderation and synchronization
Depending on the workflow configuration:
category assignments may require approval
editors may review outputs
moderators may approve synchronization
Once approved, mapped categories synchronize back into the product data.
Category Mapping best practices
Use clean category structures
AI performs better with:
clear hierarchies
logical naming
consistent structures
Messy category trees reduce mapping quality.
Combine with Attribute Extraction
Extracted attributes improve categorization significantly.
Examples:
product type
material
lifecycle
intended audience
can all improve mapping accuracy.
Start with supplier specific workflows
Different suppliers often structure products differently.
Creating supplier specific workflows improves consistency and moderation quality.
Review low confidence mappings
Low confidence results may require:
manual review
hierarchy adjustments
improved prompts
cleaner product data
Confidence scoring helps prioritize moderation.
Example workflow
Example:
A webshop imports supplier products without usable categories.
Workflow:
Trigger selects uncategorized products
Attribute Extraction fills:
Product type
Material
Lifecycle
Category Mapping assigns webshop categories
Content Enrichment generates optimized descriptions
Translation localizes content
Moderation reviews output
Approved data synchronizes to Magento
This creates a fully automated product onboarding pipeline.