↑↓ selectEnter openEsc close

    1. Elbuz

    Option products from a price list: how to group variants of one product

    16 min readUpdated

    Elbuz groups product variants from a supplier price list (sizes, colors, storage) under a shared main product, turning variant rows into its options.

    When you need this:

    • Each size is a separate row with the same model — they group under one main product.
    • Sizes are in one cell: “S,M,L” — a delimiter splits the row into options.
    • Option names should show the size — two flags append the variant value.
    • Only some variants have photos — photo flags share them.
    • You need size selection in the catalog — needs “Option products mode” on.

    Where to start: source card, “Columns” section → the “Option product ID” flag.

    What option products from a price list can do

    The method depends on how the supplier sends variants:

    What the operation does

    In the source’s operations list it is called “Create main products for option products”, and the hint in the window describes it like this:

    If the supplier sends each variant as a separate row (T-shirt S, M, L — three items), the operation creates a shared “parent” product and turns the rows into its options. The customer sees one product card with a size choice instead of three identical products.

    Order of operations window with the “Create main products for option products” operation and its neighbors
    1Create main products for option products
    2Previous operation
    3Next operation
    1. Create main products for option products — present in every source from the start, no need to enable it.
    2. The operation above it in the pipeline — the place in the order is set by the pipeline, not by this article.
    3. The operation below it in the pipeline — likewise, the order decides, not the article.

    The operation works on the price list draft: a temporary copy that receives the products from the file. If a stop rule blocks the run, the created options are discarded together with the draft, and the catalog stays as it was. Why the operation sits exactly where it does in the pipeline is covered in the article on the order of operations.

    Every source has it in the list: a new source gets it from the directory together with the other operations. So “turning the feature on” means nothing here: the operation is always in the list and only works when the right column is flagged.

    The operation does nothing on its own. First it looks for what to group variants by, and if it finds neither of the two column flags, it exits without changing anything.

    This is not an error: the run finishes successfully, and the run log gets the line “Option products: the operation is enabled, but the “Option product identifier” column flag is not set - nothing was done”. Without a flagged column, the operation runs idle every time, and that is normal.

    The two flags are checked in turn and don’t exclude each other. Photos are copied only in the “Option product ID” branch. The “nothing was done” line appears only when neither of the two is set
    YesNoYesNoYesNoOperation “Create main products foroption products”Is there a column with the “Split intoproducts by delimiter” flag?Each row expands into options, upto 10 valuesthe row itself stays the main productIs there a column with the “Optionproduct ID” flag?Rows with the same non-emptyvalue become optionsa row with a unique value stays aregular productrows with an empty value are notgrouped; their count goes to aseparate log lineOne main product is created foreach groupPhotos are copied according to thetwo photo flagsLog: “main products / optionproducts: N / M”Delimiter not set either?Log: “…not set - nothing was done”
    • Action or result
    • Decision: the path depends on the answer

    Two ways to group variants

    Each variant in a separate row: the “Option product ID” flag

    You set the flag in the field grid of the source card, in the “Columns” section; how to edit a column address and where the service flags sit in the grid is covered in the article on column addresses. You need a column where all variants of one product have the same value: model, manufacturer part number, series name.

    Columns grid scrolled to the option flags, with the Model row on the left
    1Option product ID checkbox in the Model row
    2Product option column
    1. The “Option product ID” checkbox in the Model row decides whether variants are grouped; without it the operation does nothing.
    2. The “Product option” column — the third flag, required for naming the options.

    The app then groups rows by the value in this column:

    • groups with more than one row become options entirely;
    • one main product is created for each such group;
    • a row with a unique value does not become an option: it stays a regular product.

    The supplier file has no separate row for the main product, so the app takes its name from one of the rows in the group; the database decides which one. The app has no naming rules for the main product.

    The price, availability, category, manufacturer and photo links are copied from that same row along with the name. If the flag is on the “Price category” column, the main product gets the category name. The main product’s variant family name equals its name: that is what holds the group together later, in the catalog.

    Rows with an empty value in the ID column are not grouped: they stay regular products. The app writes their count to the run log: “Rows with an empty option product identifier (excluded from grouping): N”. A large number means the column is filled in for only some products, and fewer rows than you expected will become options.

    An empty value isn’t the only trap. A placeholder like “-” or “0” is still a value, and all rows with it end up in one group with one shared main product. So check the column before the run: sort the product grid by it and see what the rows without a real value contain.

    Rows with the same value go into one group. Letter case and trailing spaces are ignored: “ABC” and “abc ” are one group. But a space at the start or in the middle of a value makes a different group, and the variant stays a separate product.

    All variants in one cell: “Split into products by delimiter”

    The second method is for when the supplier lists sizes in one cell: “S,M,L”. In the field grid, a column has the “Split into products by delimiter” flag, where you enter the delimiter character. One file row expands into several options, and the row itself stays the main product.

    What to know in advance:

    • Hard limit: 10 values per row. The eleventh and later values won’t appear, and there is no warning. Twelve sizes in a cell give ten options, and the last two simply disappear.
    • The option name is built in a fixed way: row name, space, value — “Blue T-shirt S”. This naming has no setting, and the flags don’t affect it.
    • The option link gets an anchor: “#” and the variant value are added to the product URL.
    • Option weight stays empty. The app uses the weight field as temporary storage for the variant value and then clears it in all options. The main product keeps its weight.
    • This method doesn’t handle photos at all. Both photo flags work only with the ID method.

    What reaches the catalog

    Options created by the operation live in the price list draft. They reach the through a separate action, the base catalog update. And there, at the very end of the transfer, the key decision is made.

    The app checks the catalog setting “Option products mode (main product + variants)”. If the mode is off, the “main product + options” link is removed, and only the shared variant family name remains of the group: the products sit in the catalog as standalone cards with nothing in common except that name. The products are not deleted; the former options simply become regular products.

    The setting is in the “System settings” window, “Catalog update” section, “Option products” group. The mode is off by default. So the typical result is: the operation did its job in the price list, the source product grid shows main products and options, and the catalog shows a flat list with the same “Variant family name”.

    You can see a product’s variants (modifications) in the catalog even without the mode: select a product in the base catalog grid, and the side panel shows the “Variants (options)” block, with buttons for the attribute values of all products with the same “Variant family name”. The block appears when there are at least two such products.

    Buttons appear only for attributes with “Use to create variable products” turned on; without any such attribute, the block shows its heading but no buttons. Clicking a button opens that variant’s card.

    The app also states this explicitly on the catalog side. If you click “Link options” in the catalog grid while the mode is off, a yellow message appears:

    Products grouped by name. The “main product + options” link was not created: option products mode is disabled in settings

    This article covers only the price list part: the “Create main products for option products” operation and the six flags in the “Products” section of the source card. What happens to options after the transfer to the base catalog (product type, the card’s “Variants” tab, the “Link options” button, the “Option products mode” setting) has nothing to do with the price list.

    For setting the main product price from the cheapest or most expensive option, see the article on choosing the supplier price.

    What the six flags on the source card do

    The flags are in the “Products” section, in the “What data to load” subsection, right after “Load attributes” and “Load photos”. The subsection is collapsed: its summary “N of M on” counts all its switches, option flags included, and “Configure” expands it.

    There is no subheading: don’t look for an “Option products” group in the card, the six flags just follow the rest. A parser source has none of these six flags in its card: what to load is set by the parser config, and the parser has its own option field flag.

    Settings → Products → What data to load: the six option flags in a row after the first two
    1Add option value to product name
    2Add option name to product name
    3Copy option photos to the main product
    4Copy main product photos to its options
    1. Add option value to product name — works only together with the “Product option” column flag.
    2. Add option name to product name — does nothing on its own and is unavailable until the previous flag is on.
    3. Copy option photos to the main product (on) — this is how a main product missing from the file gets pictures.
    4. Copy main product photos to its options (off) — turn it on together with the previous one so all variants of the group get the photos.
    FlagWhat it doesDefault
    “Add option name to product name”Changes the format of what the next flag adds: the name gets “Size S” instead of “S”off
    “Add option value to product name”Appends the variant value to the product nameoff
    “Copy option attributes to the main product”Option attributes are copied to the main product; identical values are mergedon
    “Copy main product attributes to its options”The reverse direction: main product attributes are copied to each of its options; the option keeps its ownoff
    “Copy main product photos to its options”Main product photos are copied to its options, except those the option already has; there is something to copy only when the main product got photos from the next flagoff
    “Copy option photos to the main product”Photos of all options are copied to the main product; duplicates are droppedon

    Two flags, “Copy option attributes to the main product” and “Copy option photos to the main product”, are on in every new source: that is how the database is set up. The other four stay off until you turn them on in the card.

    Four of the six flags are read by a different operation than the one with options in its name. Inside “Create main products for option products”, only the two photo flags work, and only with the ID method.

    The other four are read by the “Saving values from fields to attributes” operation, which comes later in the pipeline. Remove it from the operations list, and the four flags stop doing anything at all, even though they still look on in the card.

    How to add the size to option names

    Option names can be set up in only one of three places.

    • The ID method doesn’t change option names at all: they stay as in the supplier file.
    • The delimiter method builds the name in a fixed way: “name + value”.
    • Only the pair of flags sets up naming: “Add option value to product name” and “Add option name to product name”.

    The “Add option value to product name” flag appends the variant value to the name. But it takes the value not from a price list column, but from product attributes marked with the “Product option” flag. That’s a third checkbox in the same field grid, and the flag’s label says nothing about it.

    If no attribute has this flag, there is nothing to append, and names stay as they were.

    The “Add option name to product name” flag does nothing on its own. It doesn’t turn on separate appending; it only changes the format of what the first flag adds: “Size S” instead of “S”. That’s why in the card it sits under the first flag and is unavailable while the first one is off.

    The most common mistake here is turning on naming without setting the “Product option” flag on a column. Without it there is nothing to append: the flag silently does nothing, and the app doesn’t tell you.

    The “Add option value to product name” flag appends values only to options. The names of the main product and of the source’s regular products stay as they were, even when “Copy option attributes to the main product” has already copied the attributes of all its variants to the main product.

    How to share photos with all variants

    “Copy option photos to the main product” is the working flag: photos of all options are copied to the main product, duplicates are dropped, and the options keep their photos. It is on by default, and that’s how a main product that wasn’t in the file gets images.

    “Copy main product photos to its options” is the reverse direction: main product photos are copied to each of its options, except those the option already has. It runs last, after the previous flag.

    The main product has no photo list of its own (the app creates it), so this flag has something to copy only when “Copy option photos to the main product” is also on. With both on, each option gets the photos of all variants in its group.

    A photo flag that is off means only “don’t copy”. Photos that options got from the supplier file stay in place whatever the position of both flags.

    How to check that it worked

    Start with the run log. After the operation it has one of two lines: “…the “Option product identifier” column flag is not set - nothing was done” or “Option products: main products / option products: N / M”. The first number is how many main products got options; the second is how many rows became options.

    The source’s regular products without options aren’t counted in the first number. Neither line is marked as an error, and the log says nothing about flags that have nothing to do.

    The app shows no warnings in the window, only log lines. The finishes successfully whatever the operation’s result, so besides the log, also look at the data. In the source product grid, turn on these columns:

    • “Product type ID” — 1 for a main product, 2 for an option;
    • “Number of option products” — how many options a main product has;
    • “Variant family name” — the shared group name;
    • “Main product ID” — which row an option points to.

    Even faster: the grid’s context menu, “Option products” submenu. It has three filters: “Set filter by option set” shows the options of the selected product, “Filter by main products” shows only main products, “Set filter by product options” shows only options. The last one is the simplest check: empty means it didn’t work.

    Context menu of the products grid with the Option products submenu open
    1Set filter by product options
    2Set filter by option set
    1. Set filter by product options — the shortest check that the operation worked: an empty grid means no options were created.
    2. Set filter by option set — shows the variants of the product under the cursor.

    Some texts call options “attribute products” (for example, the description of option products mode mentions the “Attribute product parent ID” field), while the operation, flags and menu say “option product”. They are the same thing.

    What is rebuilt on the next import

    Main products and options don’t pile up in the draft from run to run. Each import replaces all of the source’s products with new ones built from the file: rows, main products, the links between them, option counts. So a repeat run doesn’t create a second main product for the same group.

    A catalog main product recognizes its draft row by a service key, not by name. With the ID method, the key is made of the source number and the value of the ID column. The main product’s name can change from run to run without breaking the link to the same catalog product.

    But if the ID value itself changed in the file, the app treats it as a new group and a new main product. With the delimiter method, the option key is made of the row name and the value, so the app treats options of a row the supplier renamed as new products.

    A previously added product is found by this key by a manual matching rule with the “Search for previously added products from price lists in the base catalog” option; it is on in a new rule.

    If you fixed names by hand

    • In the source product grid. Cells there are editable, but an edit lasts only until the next import: it replaces all the source’s rows with rows from the file, and the main product again gets the name of one of the group’s rows. There’s no way to lock a name in the draft. If names need fixing every time, use autocorrect rules: in the default order, “Apply text autocorrect rules” and “Auto-replacement of product values based on regular expressions” come before “Create main products for option products”, so the main product takes its name after the replacement.
    • In the catalog. The operation writes nothing to the catalog. Only the base catalog update overwrites names there, and only when the name link is on in the “Field links” tab. You can lock your name in two ways: the “Update if value is empty in base catalog” option on that link (then a filled-in name in the catalog isn’t overwritten), or the “Do not update” option on the product itself: field updates skip such a product entirely. Details are in the article on catalog updates.

    If some variants disappeared from the file

    The draft is built only from what’s in the new file, so groups are rebuilt every time:

    • if two or more rows remain in a group, the group is built from them; the main product gets the name of one of these rows (not necessarily the same as last time), and the option count is recalculated;
    • if one row remains, the group no longer exists: the row becomes a regular product, and the draft has no main product for this value;
    • if all rows of a group disappeared, its main product disappears too;
    • with the delimiter method, a value no longer in the cell simply produces no option.

    A catalog main product that no longer has a row in the new draft isn’t matched to this source anymore. What the catalog update does with products that are gone from the price list depends on its settings (base catalog update).

    With “Option products mode” on, the update doesn’t rebuild a link already saved in the catalog: it sets the “main + options” link only on products it adds as new. So a variant left alone in the file is still listed in the catalog as an option of its former main product.

    If options were grouped wrong or the import stopped

    You don’t need to clean anything up in the draft. Fix the column flag (remove “Option product ID” or move it to another column) and import the price list again: the new import replaces all of the source’s products, and no wrong main products remain in the draft.

    A wrong run reaches the catalog only through a base catalog update that adds new products: the main product is added there as a new product. It has the name of one of its variants, so in the catalog list it looks like a duplicate of that variant. These catalog grid columns help find such products:

    • “Source: name” — products added from a price list show the source and supplier name there;
    • “Date added” — the day of that update;
    • “Main product ID” — with “Option products mode” on, options show their main product’s number there.

    Once filtered, delete the extra main products. Two caveats first.

    • First fix the flag and re-import the price list. Otherwise the next update that adds new products will find the same main product in the draft, now with no match in the catalog, and add it again.
    • With “Option products mode” on, deleting a main product also deletes all its options. To keep the variants, first remove their link; that is done in the catalog and is outside the scope of this article. With the mode off, the catalog has no link, and only the product itself is deleted.

    A fixed flag doesn’t change old links in the catalog by itself: with the mode on, the update sets the “main + options” link only on products it adds as new.

    If the import stopped

    Main products and options are built in a temporary draft that exists only during the import. It’s moved to the source’s product list at the end, after all operations and the stop rule check.

    • You clicked “Stop”. The app checks for a stop before each operation in the list. The log shows “Import interrupted by the user!”, and the draft is discarded together with the main products and options. If the stop came during the operations stage, the final log line is also “Import interrupted by the user!” with a number in brackets: how many products remained in the source after the stop.
    • The run stopped on its own (a server or database connection failure). The temporary draft is lost with it, and no transfer happens.
    • What stays in the source’s product list depends on stop rules. If no source rule is set to “Block” (none is by default), the source’s old products are deleted at the start, as soon as rows are read from the file, and a stop after that leaves the source with no products until the next successful import. If at least one rule is set to “Block”, old products are deleted only after the check, at the end, and a stop leaves the previous list.
    • The catalog. The operation itself writes only to the draft. Main products and options reach the base catalog only through the base catalog update.
    • Retrying is safe. A new import creates the draft again and builds main products from scratch, so a stopped run won’t leave a second main product for the same group.

    Scenarios

    First run: making sure options actually appear

    What to do. Go through the list below before the first import.

    Making sure options actually appear

    What you get. After the import, the “Set filter by product options” filter shows the options, and the log shows a line with the number of main products and options.

    The supplier sends each size as a separate row with the same model

    What to do. Source card → “Settings” tab → “Columns” section: in the model field row, set the “Option product ID” flag. You don’t need to turn on the “Create main products for option products” operation: it’s already in the list. Import the price list.

    What you get. Rows with the same model become options, and one main product appears for each model. It takes its name, price, availability, category and photo links from one of the group’s rows. “Copy option photos to the main product” is on in a new source, so the main product gets photos of all its options without repeats.

    What won’t happen. Option names stay as in the file. A row whose model isn’t repeated anywhere else and a row with an empty model stay regular products. The base catalog won’t have the “main product + options” link while “Option products mode (main product + variants)” is off: only the shared variant family name remains there (what reaches the catalog).

    The supplier lists sizes in one cell: “S,M,L”

    What to do. “Columns” section: in the size field row, enter a comma in the “Split into products by delimiter” flag. Import the price list.

    What you get. The row itself stays the main product, and options “Blue T-shirt S”, “Blue T-shirt M”, “Blue T-shirt L” appear under it: row name, space, value. “#” and the value are added to each option’s link.

    What won’t happen. One row won’t give more than ten options. Photo flags don’t work with this method, and option weight will be empty (all variants in one cell).

    Each option name should show the size

    What to do. Options are already grouped by the “Option product ID” flag. In the “Columns” section, set the “Product option” flag in the size field row. In the “Products” section, turn on “Add option value to product name”, and if the name also needs the attribute name (“Size S”), turn on “Add option name to product name”.

    Check that “Saving values from fields to attributes” is in the “Order of operations”.

    What you get. The size value is appended to each option name: “Blue T-shirt S” or, with the second flag, “Blue T-shirt Size S”.

    What won’t happen. The names of the main product and the source’s regular products won’t change. Without the “Product option” flag there is nothing to append, and names stay as in the file; the run log won’t say a word about it.

    Only some variants have photos, but all need them

    What to do. Options are grouped by the “Option product ID” flag. In the “Products” section, leave “Copy option photos to the main product” on and turn on “Copy main product photos to its options”.

    What you get. First the main product collects photos of all its options, dropping repeats. Then each option gets the main product’s photos it doesn’t have yet. As a result, each option has photos of all variants in its group.

    What won’t happen. No photo is deleted: a flag that’s off means only “don’t copy”. If options are created only by delimiter, without an ID, these flags do nothing.

    What to do when options don’t appear

    What you seeWhyWhat to do
    The run finished, but the product grid has exactly as many rows as the file, and no options Neither of the two column flags is set: the operation exited without doing anything; the run log has a line about it ending with “nothing was done” “Columns” section: set the on a column that’s the same for all variants (each variant in a separate row)
    Options were created, but their names are the same as in the file The ID method doesn’t change names; naming comes from two separate flags Turn on “Add option value to product name” and set the “Product option” flag (option naming)
    “Add option value to product name” is on, but names didn’t change No attribute has the “Product option” flag, so there is nothing to append Set the “Product option” flag on the column the variant values come from (option naming)
    “Add option name to product name” is on, and nothing changed This flag only changes the format of what the other one adds; on its own it does nothing Turn on “Add option value to product name” (option naming)
    One main product appeared with hundreds of options Many rows have the same placeholder value in the ID column: “-”, “0”, a brand name Pick a column where only variants of one model share a value, and re-import the price list; remove the extra main products from the catalog (if options were already grouped wrong)
    A variant stayed a separate product Its group had only one row: a group needs two or more Check that the value really is the same for all variants: an extra space at the start or in the middle of a value makes a different group
    Some options have no photos An option has only the photos that came in its file row; photo flags don’t delete them, and photos of other variants are shared only when both flags are on Turn on both photo flags (the two photo flags)
    Options have empty weight, even though the supplier sent it The delimiter method uses the weight field as temporary storage and then clears it Set option weight through a different field (all variants in one cell)
    The eleventh variant from the delimiter didn’t appear Splitting by delimiter produces exactly 10 values Switch to the “Option product ID” flag or split the list into two fields (all variants in one cell)
    The price list has options, but in the catalog the products are standalone, with the same “Variant family name” “Option products mode” is off in the catalog settings; the link is removed after the transfer This is outside the article’s scope: it’s solved by a catalog setting (what reaches the catalog)
    “Products grouped by name. The “main product + options” link was not created: option products mode is disabled in settings” The same thing, seen from the catalog: with the mode off, the “Link options” button only creates a group by name This is outside the article’s scope: it’s solved by a catalog setting (what reaches the catalog)

    FAQ

    Where can I see option products and product variants (modifications)?

    In the price list: the “Products” tab of the source card → context menu → “Option products”. In the catalog: the side panel of the selected product, “Variants (options)” block. More: how to check and what reaches the catalog.

    Options were created in the price list, but they’re not in the catalog. Why?

    At the end of the transfer, the app checks the catalog setting “Option products mode (main product + variants)”. It’s off by default, and the link is removed: the products become standalone, with a shared variant family name, and aren’t deleted.

    How does the app know which rows are variants of one product?

    From the value of the column with the “Option product ID” flag: rows with the same value are variants of one product. A model, manufacturer part number or series name works. A group needs two or more rows.

    Can I group variants by product name?

    No. Variant names differ by definition, so you need a separate column with the same value: model, manufacturer part number, series. If the file has no such column, this mechanism doesn’t apply.

    Can I set the main product name?

    There’s no separate rule: it takes the name of one of the group’s rows. To get the right name every time, set up autocorrect rules: they run before the operation. More: if you fixed names by hand.

    How many variants can I list in one cell with a delimiter?

    Exactly ten, with no warning about the rest. If there are more variants, ask the supplier for a separate row per variant and group them with the “Option product ID” flag.

    Where it is and who has access

    Everything is set up inside the source card. The “Order of operations” window has no menu item of its own: it opens only from the card or from the menu in the window header.

    Menu
    Directories → Processing price lists → List of price lists
    Six flags
    source card → “Settings” tab → “Products” section → “What data to load” subsection
    Column flags
    “Settings” tab → “Columns” section → field grid
    Operations list
    “Settings” tab → “Additional” section → “Order of operations”
    Same list from the window
    “List of price lists” → menu in the header → “Processing rules” → “Order of operations”
    Result
    source card → “Products” tab → context menu → “Option products”
    Access right
    the price lists window; inside, access is split into separate blocks
    Prepare
    a source whose file has been imported at least once, and a column with the same value for all variants

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free