Feed mapping
Matching feed fields to product fields, vendor mappings, availability, and replacing an uploaded file.
On this page
Every vendor names things its own way. This group of screens is where you say what in their feed corresponds to what in yours — and all of them open from a specific vendor, not from general settings.
Four screens, four different questions
| Screen | The question it answers | When it exists |
|---|---|---|
| Feed mapping | Which feed field is the name, the price, the stock, the EAN? | Dynamic vendors only (AutoAdd or the manual dynamic flow). |
| Parameter mapping | Which vendor parameter is which of yours — and which of their values is which of yours? | Every vendor. |
| Availability mapping | What does an availability string from the feed mean to the connected ERP? | Only with an ERP transfer that uses availability switched on. |
| Feed upload | How do I replace the file for a vendor whose feed is not an address? | File-based vendors only (CSV/XLSX). |
Feed mapping
This one is structure: the translation between the shape of a foreign file and the shape of a product.
| Part | What it does |
|---|---|
| Root path | Where the product list starts in the file. A wrong path means zero products imported, not an error. |
| Encoding | The feed's character set. Where you go when the diacritics come out as noise. |
| Field mappings (JSON) | The prescription itself: which feed field is which product field. |
| Source | The badge says whether the AI generated the mapping, someone edited it, or it was written by hand. |
| Confidence | On an AI proposal, its own estimate. A low value is an invitation to review the mapping. |
| Change history | Previous versions — who changed how many fields and when, with a snapshot. |
Vendor parameter mapping
Three tabs that follow on from one another:
| Tab | What you do in it |
|---|---|
| Unmapped parameters | What the vendor sends and the system has not placed yet. This is the work list. |
| Active mappings | Finished "vendor name → your parameter" pairings, each switchable on its own. |
| Value mappings | Unifying the values of one parameter: "čierna", "black", "BK" into one value. |
Each mapping states its source — Auto for ones found automatically, Manual for yours. An automatic one can be overwritten at any time; your decision wins.
Availability mapping
The translation from a textual availability in the feed to what should be sent to the ERP. The screen offers the values that actually occurred in the feed, so you are not mapping blind.
| Situation | What the screen says |
|---|---|
| The vendor has not synced yet | No values are available — they appear after the first successful import. |
| A rule for a value that disappeared | It is marked "no longer in the feed". The rule stays but does not apply. |
Feed upload
For vendors whose feed is a file rather than an address. A new file replaces the previous one and the saved column mapping is reused — you do not redo it on every upload.
I changed the mapping — are existing products rewritten?
Only at the next import. A mapping is a prescription for reading the feed, not an action over the catalogue.
The import ran but there are no products.
Typically the root path. The feed loaded; the product list was looked for in the wrong place.
Where can I see what the feed actually contains?
In a product's raw data — the product detail has its own tab showing what arrived from the vendor before any normalisation.