Completeness Markers: what they are and how to configure them
Completeness Markers are indicators automatically calculated by THRON that measure, as a percentage, how many of the attributes you defined as mandatory are already populated on a product — for a specific Family and a specific Locale.
The marker is both a visual indicator in the product sheet and an operational tool: you can use it to filter and group products according to their completion status.
To configure them, you must:
Be an Administrator or have the "Can manage product data modeling" permission
Have already configured at least one Family and an active Locale
How the calculation works
Attributes: the marker verifies that each selected attribute is populated
Families: the rule applies to all products belonging to the selected Families
Locale: for localized attributes, each Locale is evaluated independently; for non-localized attributes, it is sufficient that they are populated once
Create a Completeness Marker
Go to Platform Settings → Products → Markers
Click New completeness marker
Enter a unique Code (e.g.
ready-ecommerce,translated-de)Select the Families to which it applies (up to 10)
Select the Locales on which to measure completeness (up to 10)
Click Continue, choose attributes
Select the Attributes that must be populated to reach 100% (up to 50)
Click Create marker to confirm
Recommended Configuration
Immediately create a base-product marker that includes the fundamental attributes shared by all your Families and the primary Locale: SKU, Product Name, Description and main image (Media Gallery). This is the minimum starting point to monitor catalog quality.
View completeness in the product sheet
The marker value is visible in the left panel of the product sheet, in the Completeness section. The section appears only if the product belongs to a Family and a Locale provided by the marker.
By default only the first marker is shown; click View all markers to expand them
Expand a single marker to see the detail for each configured Locale and the overall value considering all applied Locales
Hover over the marker title to preview the attributes still missing
Use the "Show only missing attributes" filter in the product sheet to view exclusively the fields to fill out — both for the current Locale and for those configured in the marker — and remove it at any time
Edit and maintenance
Go to Platform Settings → Products → Markers and click on the edit icon next to the marker to update. The detail page is divided into two sections:
Basic parameters: Code, Families and Locale. At least 1 Locale, 1 Family and 1 Attribute must be present in order to save.
Selected attributes: list of attributes included in the calculation.
Click Save changes in the header to confirm. If the configuration contains non-existent Families or attributes, the system shows an error panel and blocks saving.
To delete a marker, scroll to the bottom of the edit page and click Delete marker. A confirmation modal will appear; after confirmation you will be redirected to the list without the deleted marker.
Note: deletion is available only from the marker detail page, not from the list.
System limits
Element |
Limit |
|---|---|
Total markers per platform |
Maximum 50 |
Families per marker |
From 1 to 10 |
Locales per marker |
From 1 to 10 |
Attributes per marker |
From 1 to 50 |
Code — length |
From 2 to 50 characters |
Code — allowed characters |
Only |
Code — uniqueness |
Must be unique among all markers |
Reserved words (not usable as code) |
|
Upon reaching the limit of 50 markers, the system shows a warning panel and the New button is disabled.
Non-applicable marker
In some cases the marker is not applicable on a product, even if Family and Locale match. Instead of the percentage, an error message is shown in the product sheet.
This happens when one or more attributes included in the marker do not belong to the product's Family. The main causes are:
The attribute is not in the Family: a warning about the attribute in question is shown on the marker configuration page. It is still possible to save the marker, but it will remain non-applicable for those products.
The attribute is at a lower hierarchical level: the marker calculation does not inherit values from lower Variation levels (e.g. Variant). If the attribute is defined only at the Variant level, the marker cannot calculate it.
⚠️ Warning: always verify that all selected attributes belong to all Families included in the marker. An attribute missing in even just one Family makes the marker not applicable for products of that Family.
Best practice
One marker per goal. Create distinct markers by purpose — ready-ecommerce, translated-en, approved-marketing — instead of a single marker with everything inside. The team immediately understands what is missing and why.
Update markers when the structure evolves. If you add new Families or new Locales, include them in existing markers so you don't lose visibility on new products.
Link Locales to localized attributes. In order for the marker to correctly measure multilingual completeness, make sure that attributes that vary by language (e.g. name, description) have the Localizable Value flag active. See Creation of Product Attributes.
Related articles: Product Families and Variations Configuration Guide · Product Localizations Configuration · Creation of Product Attributes
Need help?
For technical issues, contact support@thron.com