Skip to content

System overview

Parameter coverage across the catalogue: what is mapped, what is missing, and where it hurts most.

Available to roles Admin, Editor, ViewerOpen in the app (Opens in a new tab)

This is the one screen in the application that answers "what should I work on first?". It does not sort parameters alphabetically but by how many products they affect — so the first row of the list is always the best-spent hour of work.

System parameter overview: mapping coverage and a list of unmapped parameters ordered by impact
Fig. 1 System overview. Status on top, a work order below — parameters ranked by the number of products they touch.

Controls on this screen

  1. Extract parameters from feedsWalks the feeds and adds names that have appeared since.
  2. Go to Manage parametersThis screen is a view of a parameter across the whole catalogue. The values on individual products are elsewhere.
  3. Total parametersHow many distinct parameter names the system knows from all feeds.
  4. MappedHow many of them have a target parameter.
  5. UnmappedThe rest. A high figure is not a fault — it is work not yet done.
  6. Top-impact unmappedOrdered by the number of products affected, not alphabetically. This is the order worth working in.
  7. Name and impactThe raw feed name, the product count, and how many vendors send it.
  8. VendorsWhich feeds use this name. More vendors = one mapping helps several.
  9. AI suggestionThe target parameter the AI proposes, with its confidence. Still only a proposal.
  10. MapOpens the mapping for this name. The shortest road from finding to fixing.

Reading the figures

FieldWhat it doesNote
Total parametersThe number of distinct names that arrived from all feeds.It grows with every new vendor. A high number is not itself a problem.
MappedHow many have a target parameter.This is the only figure you want to see rise.
UnmappedThe rest.Their values are stored as raw data, but nothing can be filtered by them and they do not appear in the shop.
Mapping coverageThe share that is mapped.The same figure appears on the dashboard. A low percentage on a new catalogue is a normal state, not a fault.
98 % of mine are unmapped. Is something broken?

No. It means the catalogue is fresh and normalisation has not been done yet. Start with the first row of the top-impact list.

How is this different from Manage parameters?

This screen is a view of a parameter across the catalogue. Manage parameters is a view of the values on individual products.

When should I use “Extract parameters from feeds”?

When a vendor has been added, or an existing feed started sending new fields. It adds names the system had not seen before.