Elbuz copies supplier file columns such as color, weight and material into product attributes and puts them into the product card when the catalog is updated. Mark the columns once.
When you need this:
- Color and volume are in separate columns: the “Product attribute” checkbox turns them into attributes.
- Your directory already has the attribute under its own name: a column linked directly to it won't create a second attribute next to it.
- The column is empty for half of the products: empty values are skipped, so no extra attributes appear.
Where to start: the “Columns” section of the source card → choose how to link the column.
What copying into attributes can do
- Make an attribute from a price list field: the “Product attribute” checkbox; the name comes from the field.
- Write a column directly into a catalog attribute: you pick the name from the directory.
- Get attributes into the product card: during the base catalog update.
- Check the result: in the product card after the update.
How to mark the columns that become attributes
The “Saving values from fields to attributes” operation copies column values into product attributes. Which columns it copies is decided by the “Product attribute” checkbox in the price list column mappings. Next to it in the “Value processing” group is the “Product option” checkbox, and the operation picks up columns with that checkbox too.
1
Product attribute2
Product option3
Value processing- Product attribute — the column value becomes a product characteristic.
- Product option — the column value becomes a product option.
- Value processing — the group of settings for how the column value is handled.
Until the columns are mapped, there is nothing to set the checkbox on: first you set the column mappings and destination fields, as described in price list fields and column settings. The checkbox goes on top of a finished mapping.
From there, there are two different ways to link a column to an attribute, and in the column grid they look almost the same.
- The column goes into a price list field, and the checkbox turns it into an attributeThe attribute name comes from the price list field name. The operation copies the values
- The column is linked directly to a catalog attributeThe name comes from the catalog attribute. The value is written while the file is read, with no operation
Option one: a price list field plus the checkbox
The column is linked to a regular price list field, such as “Color”, “Weight” or “Warranty”, and has the “Product attribute” checkbox selected. The value then goes both into the field and into the attributes. The attribute is created by the operation, and it works like this:
- an empty value doesn't create an attribute: rows with an empty column are skipped;
- the unit of measure isn't filled in. “500” stays just “500”, without “g” or “ml”: the operation never writes units, so the attribute reaches the catalog without one. Units are filled in only for attributes from an XML feed;
- the attribute group stays empty: the group that attributes are listed under in the product card. The group is assigned during the catalog update, and it's the default one;
- the operation takes the attribute name from the price list field name, not from the supplier's column header.
The attribute name comes from the field label in the catalog language, as in the price list product grid. In an English catalog, the checkbox on the “Color” column creates the “Color” attribute, and on the “Manufacturer” column, “Manufacturer”. Only when there is no label in the catalog language is the Russian field name used.
If the attribute in your directory has a different name, say “Product color”, it won't be linked: the names don't match, and the catalog update creates a second attribute next to the first. Before you set the checkbox on a dozen columns, check what the attributes are called in the product card after the first run.
The operation immediately tries to link the new attribute to the attribute directory, in four passes: by name with the main synonym, by name, by name code with the synonym, and by code. It compares the attribute name in the catalog language, not in the language you're currently using the app in.
Option two: the column goes directly into a catalog attribute
Besides system fields, the “+ Add field” list you use to set a column mapping also contains your catalog attributes; in the column grid such rows are highlighted in color. Choose an attribute instead of a field, and the column value goes into the attributes under that attribute's name, already linked to the directory.
The difference is when this happens: here the value is written while the file is read, not by the operation. The “Saving values from fields to attributes” operation doesn't process such columns, and it doesn't get in their way either. Empty values are skipped the same way.
The practical difference comes down to one thing: with option two, you pick the attribute name from your own directory, so there are no name mismatches and no duplicates in the attribute directory. With option one, the name is assigned for you.
How attributes get into the product card
The operation writes attributes to the price list, not to the product. They reach the product card during the base catalog update, only if “Update attributes” is turned on in its settings. That's where missing directory attributes are created, only for products already matched in the catalog. Details: updating the base catalog from price lists.
Turning off the attribute operation also turns off three more things that live in it and have nothing to do with attributes: linking option products to the main product, copying attributes between the main product and its options, and adding the option value to the product name. See order of operations.
Where to see attributes
Price list attributes aren't shown anywhere. The price list product grid has no attribute column, and its expandable row is off. You can check the result only in the product card after the base catalog update. Keep in mind on your first try: between setting a checkbox and seeing the attribute lie a full run and a catalog update.
In the run log, the operation writes only the line “Copying field values into attributes”, with no numbers, and only if it found marked columns.
Scenarios
You need color, weight or material from file columns in the product card
What to turn on. On columns linked to price list fields, turn on the “Product attribute” toggle in the “Value processing” group. The price list operations must include “Saving values from fields to attributes”. In the base catalog update settings, turn on “Update attributes”.
What you get. The operation writes the values of marked columns as attributes of the price list product. They move into the product card during the base catalog update.
What won't happen. Units of measure won't get into the attributes, and an empty value won't create an attribute. The operation doesn't process columns linked directly to a catalog attribute: they're written while the file is read. Without “Update attributes”, the attributes stay in the price list.
The directory attribute is called “Product color”, but the column is “Color”
What to turn on. In the column mapping, open the “+ Add field” list and choose the “Product color” catalog attribute instead of a price list field.
What you get. The column value is written to the attributes under your attribute's name, already linked to the directory, while the file is read.
What won't happen. The catalog update won't create a second “Color” attribute next to “Product color”.
What to do when the product card has no attributes
| What you see | Why | What to do |
|---|---|---|
| The product has no attributes, and the run log says nothing about them | No column has the checkbox: without marked columns the operation does nothing and writes no line to the log | Select the “Product attribute” checkbox on the columns you need (attributes from file columns) |
| The attributes are in the price list but not in the product card | “Update attributes” is off in the catalog update, or the price list product has no match in the catalog, or the catalog product is locked against attribute changes | Turn on “Update attributes” and check product matching (how attributes get into the catalog) |
| The attribute in the product card has a different name from the directory attribute, and a second attribute for the same thing has appeared next to it | The operation takes the attribute name from the price list field label in the catalog language, not from the attribute directory | Rename the attribute in the attribute directory, or link the column directly to the right catalog attribute (column directly into a catalog attribute) |
FAQ
Will the unit of measure, “g” or “ml”, get into the attribute?
No, the operation doesn't write units: “500” stays “500”. Units are filled in only for attributes from an XML feed. More: a price list field plus the checkbox.
The column is linked to a catalog attribute, but the operation doesn't process it. Is that a bug?
No. Such columns are written to the attributes while the file is read; the operation isn't needed for them and doesn't get in their way. More: column directly into a catalog attribute.
What else turns off if I remove the attribute operation?
Linking option products to the main product, copying attributes between the main product and its options, and adding the option value to the product name: they all live in the same operation.
Why didn't an empty column produce an attribute?
That's by design: rows with an empty value are skipped so that half of the price list doesn't get empty attributes.
Why did the attribute end up in the wrong group of the card?
The operation doesn't fill in the group. The catalog update assigns it, using the default group.
Where to find it and who has access
- “Product attribute” checkbox
- source card → “Columns” → “Configure column” → “Value processing” group
- Operation
- source card → “Additional” → “Order of operations”
- Menu
- Directories → Base product catalog → Attributes
- Access right
- price list card
- Prepare
- mapped price list columns: the checkbox is set on top of a finished column mapping
Related topics
- For the big picture: Product manufacturer and attributes from a supplier price list.
- If the columns aren't mapped yet: Price list fields and column settings.
- If the attributes are in the price list but not in the product card: How to update the catalog from price lists.
- If the column is a product variant's size or color: Option products from a price list.
- If you need to tidy up the attributes themselves: Attribute directory.
