Skip to content
Monokaidomanual
SlovenčinaEnglish

Parameter mappings

Matching names from feeds to your parameters — AI suggestions, confirmation, and what happens to the unmapped.

Available to roles Admin, EditorOpen in the app (Opens in a new tab)
On this page

The feed says Barva, column_33 or farba-produktu. Your catalogue has a parameter called Colour. This screen is where one is joined to the other — and without it the system does not know they are the same thing.

Parameter mappings: a table of source names from feeds matched to target parameters
Fig. 1 — Parameter mappings. On the left what the feed sent; on the right what it becomes in the catalogue.

Controls on this screen

  1. AI parameter mapping — Has the AI walk the unmapped names and propose matches. It confirms nothing on its own.
  2. Re-extract everything — Walks the catalogue again with the current mappings. Use it after a substantial change.
  3. Add mapping — Matching one name by hand.
  4. Vendor — A mapping always belongs to one vendor — the same name can mean different things to two of them.
  5. Search — At hundreds of mappings this is the fastest way to one row.
  6. Source parameter — The field name exactly as it appears in the feed. It must match character for character.
  7. Target parameter — Your parameter, where the value will be stored.
  8. Parameter code — The target parameter's internal code — what you will see in exports and in the API.
  9. Row vendor — Which feed this mapping applies to.
  10. State — An inactive mapping is ignored on import — handy for switching one off without deleting it.
  11. A technical name — CSV feeds often have no header and their fields are called column_13. A mapping is the only place that becomes a meaningful parameter.

How mapping is done

  1. Let the AI propose

    AI parameter mapping walks the unmapped names and matches what it can. It confirms nothing — you review and approve the proposals.

  2. Fill in what it could not

    Meaningless technical names (column_13) and abbreviations only the vendor understands have to be matched by hand through Add mapping.

  3. Run the extraction

    Re-extract everything walks the catalogue with the new mappings and fills the values in. Without this step the mapping takes effect only on the next import.

What happens to the unmapped

A value whose name is not mapped is not thrown away — it stays with the product as raw feed data. But it does not appear in the catalogue as a parameter, nothing can be filtered by it, and it does not count towards coverage.

How many there are is in System overview; the specific values are in the product's raw data.

Why is a mapping tied to a vendor?

Because the same name can mean different things to two vendors. Size might be frame size for one and package size for another.

I deleted a mapping — do I lose the values?

The values on products stay until a new extraction or import runs. After that the parameter stops being filled.

The target parameter I need is not in the list.

It has to be created first, in Parameter definitions.