Determine where a value belongs
The source value is retained and given a fixed meaning within the product model.
color_name: Navycolor: Navy
Standardized product data
Give every product field one fixed meaning
Suppliers, feeds and web shops use different names for the same product information. Nifelo links these source fields to fixed SmartFields for, among other things, title, price, brand, GTIN, color and category. This way, control, improvement and export work from one consistent product model.
The source may differ. The meaning of your product data remains recognizable.
Consistent product model
Available in Nifelo
Product titleOne fixed title
title
Sales priceRecognizable price data
price
Product codeGTIN or EAN
gtin
ColorProduct feature
color
One shared basis for your product process
From source field to SmartField
Different names. One shared product language.
One supplier uses Colour, another color_name and a third CLR_CODE. By linking these fields to the SmartField color, Nifelo knows that they contain the same type of product information. The original source value remains available; the SmartField gives that value a fixed place and meaning.
Source fields
Supplier A
Colour
Navy Blue
Supplier B
color_name
Navy Blue
Supplier C
CLR_CODE
Navy Blue
Nifelo SmartField
Color
color
The same type of product information is given one recognizable place.
Used in Nifelo
Data controlCheck for fixed meaning
NormalizationOptional for supported values
EnrichmentComplete missing data in a targeted manner
Channel exportLink to target fields
SmartFields standardize the structure and meaning. Normalization of values is a separate, optional step.
The solid layer in Nifelo
A SmartField is the permanent place for one type of product information
A SmartField is a recognizable product field within Nifelo, with a fixed key and meaning. Think about title, price, brand, gtin, color or availability.
Your source continues to deliver the product value. The mapping determines which SmartField that value is linked to. As a result, validation, improvements and exports do not need to know what name each supplier originally used.
That makes SmartFields the shared product language between your sources and the rest of your product process.
SmartField definition
Active
Color
- Fixed key
color- Meaning
- The color of the product
- Well-known field names
- Color, color_name, CLR_CODE
- Sample value
- Navy Blue
- Reuse
- Control, standardization, enrichment and export
Then bring supported values together
A separate module can group variants such as Navy, Marine and Navy Blue into a consistent group.
NavyNavyNavy BlueNavy Blue
From source to reuse
1
2
3
4
Give meaning once. Then use that structure again.
SmartFields ensure that every next step can work with recognizable product fields, without having to understand all supplier names again.
Link the source field
Connect a supplier field to the correct SmartField. Known mappings are applied first; unclear fields can receive an AI-assisted proposal.
Check the mapping
View which source field is linked to which SmartField and adjust the proposal when necessary.
Check and improve
Validations use the fixed meaning. Enabled modules can then normalize or enrich supported fields.
Use the data in exports
Connect SmartFields to the requirements of your sales channels without reprocessing every supplier name.
One model, less repetition
A stable basis for your product catalogue
Make follow-up processes less dependent on the way in which one supplier supplies its product data.
Work independently of sources
Your internal product model does not have to change because a supplier uses different field names.
Consistent data control
Check title, price, GTIN, links and images for their meaning rather than varying source columns.
Targeted improvement
Use the same SmartFields for optional normalization, knowledge-driven completion, and AI enrichment.
Reusable for channels
Build channel mappings from a single product model, while each channel retains its own requirements and target fields.
Insight per product field
See what has changed and fix where necessary
Changes to SmartField values can be viewed per product field, including the change source and time. If a previous value is better, you can restore it and the product validation will be performed again.
Field history
colorCurrent valueNavy Blue
Navy BlueManually updated · just now
Active
NavyImport · supplier_feed.xml
Restore value
DarkBlueEnrichment · previous change
Restore value
After recovery, product validation is performed again.
SmartFields FAQ
Good to know
Clear answers about mapping, values, AI, obligations and exports.
What is a SmartField?
A SmartField is the permanent place for one type of product information within Nifelo. For example, different source fields can all be linked to the SmartField for color, price or brand.
What is the difference between a source field and a SmartField?
A source field is the name under which a supplier provides information. A SmartField is the fixed name and meaning that Nifelo uses internally. Colour, color_name and CLR_CODE can therefore all refer to color.
Does a SmartField automatically change my product value?
No. The mapping determines in which SmartField a source value belongs. Individual enabled functions can then check, normalize, or enrich supported values.
Does every SmartField mapping use AI?
No. Nifelo first uses known platform structures, field names, aliases, and previously confirmed mappings. AI is used in a targeted manner when the meaning of a source field is not yet clear. You can check the proposal.
What happens if a supplier changes a field name?
You link the new field name to the same SmartField. Subsequent processes can then continue to use the same fixed SmartField. The changed source mapping must be checked.
Are all SmartFields mandatory?
No. There are fixed basic fields, but additional requirements may depend on the product type, category and export channel.
How do SmartFields help with data quality?
Because Nifelo knows what a field means, checks can specifically look for, for example, missing titles, prices and descriptions, an invalid GTIN or unusable product and image links.
How are SmartFields used in exports?
An export mapping uses SmartFields as a source and links it to the target fields of the channel. This way, the same product information can be reused, while each channel retains its own requirements.
Can I view changes to a SmartField?
Yes. Recent changes can be viewed per product field including the previous value, change source and time. A previous value can be restored where necessary.
From separate fields to one product model
Make product data understandable for every next step
Connect your source fields to SmartFields and build a consistent foundation for monitoring, improving, and selling across multiple channels.
