Completeness Profiles
Define what “complete” means for your catalog and track attribute coverage across languages
Completeness profiles let you define what “complete” means for your catalog. Each profile specifies which attributes must be filled in — and optionally which languages they must be filled in for — before a product is considered complete.
Completeness percentages show up throughout the catalog so your team can quickly see which products need attention and prioritize enrichment work.
How completeness works
Every product, variant, and SKU in your catalog is scored against your active completeness profile. For each item, Emfas counts how many required attribute—language combinations are filled in versus how many are expected. The result is a percentage you can see in the catalog view.
A completeness profile is a curated selection of attributes. Only the attributes you have included in the profile count toward the score. If a product belongs to a family, only the profile attributes that are also part of that family count, so a product is never held back by an attribute it cannot have.
Creating a profile
Open Settings → Completeness and click Create Profile. Enter a name and an optional description, then save.
Once created, open the profile to choose which attributes and languages it tracks.
Configuring attributes
Inside a profile you will see every product, variant and SKU attribute. Toggle attributes on or off to include or exclude them from this profile's scoring. Use the search box to find specific attributes by name.
After you save your changes, Emfas rebuilds the completeness scores in the background. A progress bar shows how the update is going — large catalogs may take a few minutes to fully recalculate.
Language scope
By default, a profile tracks completeness across every language your organization has set up. If you only care about a specific set of languages — for example, because a team is responsible for a particular market — you can narrow the profile to those languages.
Open the profile and use the language picker to select which languages to include. Only languages your organization has configured will appear as options.
- All languages selected (the default) — the profile applies across every org language.
- A subset selected — only the chosen languages count toward completeness. Values in other languages are not scored by this profile.
A common use case: create a separate profile for each regional team. The English team's profile covers only English; the German team's covers only German. Each team sees completeness scored against their own language without being penalized for gaps in markets they don't manage.
Only translatable attributes are language-scoped
Language scope only affects translatable attributes. Non-translatable attributes (like SKU codes, prices, or identifiers) have a single value regardless of language, so they are counted once per item rather than once per language.
Family-specific requirements
If your organization uses families, a profile can require different attributes for different families. Jackets might need a material and a lining, while accessories only need a material.
Open the profile and click + Family above the attribute list to pick a family. You now see only that family's attributes, scored the way the profile currently treats them: every attribute in the profile that the family has is required. Toggle any attribute and the family gets its own requirement set. Save, and products in that family are scored against that set alone. Every other family keeps inheriting the profile's attribute list.
Families with their own set stay visible as chips next to All families, with the number of attributes they require. Inside a family, attributes that differ from the profile are marked with a bar; hover one to see what the profile says, and use the revert arrow to put a single attribute back. Reset to inherited drops the whole set again.
Turning every attribute off exempts the family from the profile entirely: its products show no completeness score for that profile.
Only attributes in the family count
A customized set can only require attributes that belong to the family. If an attribute is later removed from the family, it stops counting toward completeness even if the set still names it.
Default profile
One profile can be set as the default for your organization. The default is used for any user who has not chosen a personal profile.
To set a profile as the default, open it and click the ... menu in the top right, then choose Set as default. Only one profile can be the default — setting a new one automatically removes the designation from the previous default.
Personal profile selection
If your organization has multiple profiles, each team member can switch to the one that matches their role or market. Changing your personal profile selection does not affect what other team members see.
To clear your personal selection and go back to the organization default, remove your preference from the same switcher.
Editing and deleting profiles
Open a profile and click the ... menu to rename it, update its description, or delete it.
Deletion is permanent
Deleting a completeness profile removes it immediately. If the deleted profile was the organization default, no default will be active until you designate another one.