Elbuz takes fifty standard fields from a price list — name and price to barcodes and weight — plus your own. Each column can get a currency, uniqueness flag, product attribute or regular expression.
When you need this:
- Supplier gives a shipping city or batch — create your own field.
- A column goes into a product attribute — add it in the card's field grid.
- File prices are in euros — set the column's currency and rate; you get the converted amount.
- You want the result before import — see the “Resulting value” column.
Where to start: source card → “Columns” section → field grid.
What this reference covers
- Fifty target fields — grouped by purpose; eleven are created together with the source.
- The card's field grid — cell-by-cell address editing, filters, attributes and custom fields.
- The “Resulting value” column — what an address produces, before import.
- Removing a field — what disappears with the row and what stays.
- Column settings — uniqueness, attribute, option, delimiter, regular expression, currency.
Which fields you can take from a supplier's file
Fields in the list are in alphabetical order, with attributes in a separate section after them. The fastest way to find a field is the search box at the top. Below, fields are grouped by purpose to show everything you can take from a supplier's file, not just name and price.
- Identifiers: “Name”, “Manufacturer SKU”, “Supplier SKU”, “Model”, “Manufacturer”, “Product ID on site”.
- Prices and money: “Price”, “Sale price”, “RRP”, “Old price”, “Discount”, “VAT” (the rate from the file; the rate for documents is set by the tax class), “Currency”, “Exchange rate”, “Delivery cost”, “Delivery period”.
- Availability: “Stock status (from price list)”, “Quantity”, “Warehouse name”.
- Categories and store: “Category from price list”, “Category link”, “Store name”, “Supplier”.
- Descriptions and texts: “Short description”, “Full description”, “Instruction”, “Meta title tag”, “Meta description tag”, “Meta keyword tag”.
- Links and media: “Product link (URL)”, “Link to product photo”, “Product video link”.
- Dimensions and properties: “Weight”, “Height”, “Width”, “Depth”, “Length”, “Dimension”, “Size”, “Unit”, “Color”.
- Codes and barcodes: “GTIN”, “EAN Barcode”, “ISBN Barcode”, “JAN Barcode”, “UPC Barcode”.
- Other: “Warranty”, “Product condition”, “Variant family name”, “Nutri-Score (Nutritional Value)”.
Custom fields you create will join the list next to these.
Eleven fields are created automatically
When a source is created, eleven fields go straight into the import list: “Manufacturer SKU”, “Manufacturer”, “Name”, “Price”, “Supplier SKU”, “RRP”, “Stock status (from price list)”, “EAN Barcode”, “Category from price list”, “Product link (URL)”, “Link to product photo”.
Their addresses are empty — they wait for auto-mapping or for you. The “Consider uniqueness” checkbox is already on for two of them: “Name” and “Manufacturer SKU”. These are what the system uses to tell products apart, and their empty addresses are what will stop the import.
Why the wizard has no attributes
There are two field lists, and they differ.
| Where you choose | What you see |
|---|---|
| The drop-down in a wizard row, “+ Create field…” | all target fields: 50 in a clean system, plus one for each custom field you add. The list is always complete, even if a field is already taken by another column |
| The “Add field” button in the card grid | all price list fields, including service fields, and all active product attributes — a working catalog can have thousands. Fields already added disappear from the list |
The practical takeaway: to put a column into a product attribute, open the card's field grid — the wizard has no such option.
How to edit the mapping in the card's field grid
The wizard is handy when you map from scratch and look at sample values. The grid in the “Columns” section is for quickly fixing one thing when you know where to click. You edit it cell by cell: a click opens the cell, leaving it saves.
Grid columns: “Name” (pinned, not editable), “Column address”, “Copy value to main price list” (child stock price list only), “Currency code”, “Exchange rate”, “+%”, “Multicurrency”, “Merged cell”, “Consider uniqueness”, “Option product ID”, “Product attribute”, “Product option”, “Split into products by delimiter”, “Regular expression”, “Resulting value” and a trash icon with the tooltip “Remove field from the import list”.
Row color means something too: blue is a product attribute, purple is a field you created yourself.
1
Add field2
Column wizard3
With address (7)4
No address (5)- Add field — adds a new system field to the layout.
- Column wizard — opens the window that maps file columns to system fields.
- With address — shows only the fields that already have a column address; the number in brackets is how many.
- No address — shows the fields that are still not linked to a file column, with their count.
Above the grid are three buttons and quick filters. “Add field” opens a picker with search, sections and a memory of recent choices. “Column wizard” opens the wizard. “Formulas” opens the formulas window. The “Show:” filters count fields right on the buttons — “All”, “With address”, “No address”; “Key fields” has no counter.
The “Key fields” filter shows exactly four fields: “Price”, “Name”, “Manufacturer SKU”, “Quantity”. Note that “Stock status (from price list)” isn't one of them, even though auto-mapping assigns it to stock columns. To find availability, use “With address”, not “Key fields”.
The trash icon removes a field from the import list and asks: “Remove field from the import list “‹name›”?” with the buttons “Remove” and “Cancel”.
Only users with the right to edit price lists can add, change and delete import list fields. The grid reports a refusal: on edit — “You do not have permission for this operation”, and the cell reverts to its previous value; on delete — “Operation failed!”, and the row stays.
Create your own field
If the supplier provides something no target field covers — a shipping city, a batch number — create a custom field. The dialog is called “Adding a field” and asks three things: “Field name” (placeholder: “Enter a field name, e.g. City”), “Column address” (“for example 1”) and “Field type” — “Text”, “Number”, “Price” or “Attribute”. The default type is text.
An empty name gives “Field name required!”, and the system won't create a field with a name that already exists. Success is confirmed with “New field added successfully”.
How to see what will go into a field
The last grid column shows exactly what the address you wrote produces. It isn't a separate check you have to run: the value is built by the same rules as during file import, so the tooltip shows both direct joins and inserts from curly braces. After you edit an address in a cell, the column recalculates on its own.
It shows one of three things:
- a value from the file — when the system recognized the header row and found data under it:
SMEG BLF 03 WHEU; - the address spelled out with column names — when there are no values to take:
MODEL NAME + " " + MODEL CODE. The symbols follow address syntax: plus is a join, a vertical bar is the first non-empty value, quoted text is an insert from curly braces; - a ⚠ sign before the part of the address that couldn't be parsed.
1
Resulting value column header2
Address 3 in the Name row3
What this address will bring in- The Resulting value column shows what each field will receive from the file.
- The address in the Name row points to column 3 of the file.
- Here you see the content of that column as it will go into the field.
The text in the cell is shown on one line in a muted color; you can see it in full in the tooltip on hover.
Values aren't always shown, and that's not a bug. You won't see them if the file itself isn't stored next to the source — in the cloud, the price list file is removed from the temporary folder after import.
You also won't see them when the header row isn't recognized: a row counts as the header only if at least two column names match its contents. If the saved mapping no longer matches the file, run auto-mapping again in the column mapping wizard.
If the price list was exported from Google Sheets, the header row may contain formula text instead of the column name — IFERROR(__xludf.DUMMYFUNCTION(….
The system extracts the real name from it: in such a formula, the last argument holds what was visible in the cell. If there's nothing to extract, the address shows “column” with a number — more honest than a wall of formula. Names already saved in the mapping are cleaned too, so you don't need to rerun auto-mapping for this.
Also, the cell shows a sample from one row, not a value for the whole price list. It's the first data row where the address produces anything, so if the first product's cell is empty, the sample comes from the second. For an XML feed the column is always empty: the address is a tag name, nothing to decode.
What happens when you remove a field with the trash icon
The trash icon in a grid row asks “Remove field from the import list “…”?”, and after “Remove” the row is deleted with the column address and all its settings: currency, rate, “+%”, multicurrency, the “Consider uniqueness” checkbox, the regular expression. There's no undo. The eleven fields created with the source get no special protection.
- Values already loaded into price list products stay until the next import. Import rebuilds the price list rows from the file, and the removed field won't be in them — it becomes empty.
- Removing a field doesn't write anything to your catalog by itself. But if the field is linked in the “Updating base catalog” settings and “Update if value is not empty in price lists” isn't set for it, the next update writes the empty value from this price list into products. Price, old price, RRP, cost price, quantity, stock status, manufacturer and category update differently, and this rule doesn't apply to them.
- The field's formulas aren't deleted. They're tied to the price list and the field, not to the import list row, so they keep running on every import.
- A field you add back comes in clean. Its address is empty and all toggles are off, including “Consider uniqueness”. “Name” and “Manufacturer SKU” had this checkbox on since the source was created, so after adding them back you need to turn it on manually.
What you can set for a single column
The slider icon in a wizard row opens a panel right below the row — it's called “Configure column”, and its header shows the address and the field. Only a column that already has a field assigned gets the panel: there's no point processing a value that goes nowhere. At the bottom are two buttons — “Cancel” and “Apply”.
1
Column address2
Currency group3
Consider uniqueness4
Product attribute5
Apply- Column address — which file column the value is read from.
- Currency — currency code, exchange rate and the +% markup for this column.
- Consider uniqueness — uses the value when matching rows.
- Product attribute — loads the value as a product attribute.
- Apply — saves the column settings (not pressed in this run; the panel was closed with Cancel).
The settings are split into four groups: “Address and loading” (the address itself), “Currency” (price fields only), “Value processing” and “Parsing”. Here's what each one does.
| Setting | What it does |
|---|---|
| “Consider uniqueness” | The values of all columns with this checkbox are joined into a price list row fingerprint — that's how the system tells one product from another. On by default for “Name” and “Manufacturer SKU” |
| “Merged cell” | An empty cell inherits the last non-empty value above it. This is how files are read where a group name is written once per ten rows |
| “Option product ID” | Marks the column used to group products into a main product with its options |
| “Product attribute” | After import, the value is also written to the price list product's attributes — under the field's own name |
| “Product option” | The same, but the attribute is marked as an option |
| “Copy value to main price list” | Child stock price list only: the value is carried over to the parent price list. The wizard panel doesn't have this toggle — it lives in the card's field grid |
| “Split into products by delimiter” | One file row expands into several products by the delimiter you specify |
| “Regular expression” | Applied to the cell value: the first capture group is taken, or the whole match if there are no parentheses |
| “Currency code”, “Exchange rate”, “+%” | Price fields only: the currency of the price in the file, and the rate and markup to convert it with |
In day-to-day work, the ones you'll need most are the uniqueness flag and “Product attribute”. “Product option”, “Regular expression” and “Split into products by delimiter” are tools for specific cases — don't start with them.
In the card grid, next to the currency columns, there's also a “Multicurrency” button — “Price” and “RRP” have it, and it opens a separate window. Rate, markup and multicurrency belong to pricing rules; here they're only named.
A “Consider uniqueness” checkbox with no address is the most common reason an import stops. The system checks this second, after making sure at least one column is mapped: if no field with this checkbox has an address, the import is cancelled, even if every other column is mapped perfectly. Map “Name” or “Manufacturer SKU”, and the check passes.
What to do when a field won't add
| What you see | Why | What to do |
|---|---|---|
| “Error: This field already exists!” | The field you're adding is already in this price list's import list | Find it in the grid with the “All” filter — it's already there, just without an address (field grid) |
| “Field name required!” | The name in the create field dialog is empty | Enter a name — that's what you'll see in the field list later (create your own field) |
| “You do not have permission for this operation” — a red message after editing a cell in the field grid | No right to edit price lists: the server refused, and the grid reverted the cell to its previous value | Ask for the right to edit price lists. The edit wasn't saved — entering it again won't help (rights to change fields) |
FAQ
What does the “Consider uniqueness” checkbox do?
The values of columns with this checkbox form a row fingerprint — that's how the system tells products apart. By default it's on for “Name” and “Manufacturer SKU”. If neither has an address, the import stops.
I added a removed field back — why does the import stop now?
A field you add back comes in clean, without the “Consider uniqueness” checkbox. Turn it on manually for “Name” or “Manufacturer SKU”. More: removing a field.
Why isn't “Stock status” shown in the “Key fields” filter?
“Key fields” shows exactly four fields: “Price”, “Name”, “Manufacturer SKU”, “Quantity”. To find availability, use the “With address” filter.
Why does the “Resulting value” column show column names instead of values?
The file isn't stored next to the source — in the cloud it's removed after import — or the header row wasn't recognized. More: the “Resulting value” column.
What does the row color in the field grid mean?
A blue row is a product attribute, purple is a field you created yourself. The rest are standard target fields.
Where to find it and who has access
- Menu
- Directories → Processing price lists → List of price lists
- From the source card
- “Columns” section — the field grid and the “Add field” button
- From the column mapping wizard
- the slider icon in a row → the “Configure column” panel
- Access right
- the “List of price lists” window; changing fields requires the right to edit price lists
Related topics
- For the big picture of column mapping — Price list column mapping.
- To build a field value from several columns — Column address: how to join columns.
- To set the rate and markup for the whole price list — Markup and discount in a supplier price list.
- To cut out part of a column value — Regular expressions for price lists.
