Price list column mapping
Elbuz maps the columns of a new price list on its own, checking headers against a dictionary and passing unfamiliar ones to AI, and then reads every file from that supplier using this mapping. Here you will learn how to check and adjust the mapping, combine values from several columns, set up an individual column and map XML or JSON.
- How to map price list columns: where the name, price and SKU are
What price list column mapping is, how Elbuz maps a supplier file on its own, where to fix a field, address or format, and why an import stops with “Column addresses are not filled in”.
- How Elbuz maps price list columns on its own and when it calls AI
How Elbuz finds the name, price and SKU in a price list on its own: the header dictionary during upload, the “Auto-map columns” button, auto-setup of a new source, and when AI steps in.
- How to map columns in the wizard and check them before import
How to assign fields to price list columns in the column mapping wizard, check the mapping before import, catch shifted columns and fix data if a mistake has already reached the price list.
- Column address: how to join columns, take the first non-empty one or set fixed text
Reference for the price list column address: letter, number, composite address with text in curly braces, range, first non-empty column, and how price, quantity and category read the address.
- Price list fields and column settings: reference
Reference for price list fields in Elbuz: 50 target fields, the source card field grid, the “Resulting value” column, custom fields, currency, uniqueness, attribute and column regular expression.
- How to map an XML, BMEcat, DATANORM, JSON or CSV price list
Column address for Excel, CSV, XML and JSON price lists; BMEcat and DATANORM map themselves: supported versions, fields and price. Delimiter, encoding, rounding.
