Configurator Products

2,888 views · 5 min, 8 sec read · Tutorials

If your web store has never used Configurator products, some CSS (styling) may be required. Any front end developer can assist with this work using our Custom CSS module. If further assistance is required, please contact us! Read more about our scope of services.

Configurator products allow a web store user to add different ERP products to a cart using only one product in the store. Configurator products are different from variants in the sense that there are multiple products added, not just one product, as is the case with a variant product.

In this article, we’ll show you how you can set up a configurator product and configure it using the array of settings available.


Quickstart: Creating a Configurator Product and Modifying the Settings

See below for video instructions

To start exploring your options quickly, take the following steps:

  1. Login to your web store
  2. Go to Catalog > Product Configurator > Configurator Products and click New Configurator (or append /admin/mproducts_configurator/details to your web store domain)
  3. Input the Description and the Item Code TESTING124
  4. Download this Excel file. In column A in the highlighted cells (yellow), add ERP item codes. For testing purposes, these can be any ERP item codes that are active in your catalog.
  5. Go to Catalog > Product Configurator > Configurator Products > Settings, and import your modified Excel file under the Export/Import section (or append /admin/mproducts_configurator/settings to your web store domain)
  6. Assign TESTING124 to a category
  7. Navigate to the product and observe the basic configuration:

How to Create a Configurator Product

[videopress dxh7bhO2]

In the video above, we cover steps 1, 2 and 3 from the Quickstart instructions.

How to Modify the Configurator Product Settings

[videopress lRyb36wv]

In the video above, we cover steps 4, 5, 6 and 7 from the Quickstart instructions. From Step #4, we cover this information from the spreadsheet:

  • item_code – This field corresponds to the ERP item code, which is used to match up the price and the user selection with item codes in the ERP. This cannot be longer than 24 characters.
  • desc – The description is how the selection should be presented in the configurator options in the product detail.
  • swatch_name – The swatch name corresponds to the swatch codes created in Catalog > Product Configurator > Configurator Options (or append /admin/mproducts_configurator/options to your web store domain)
  • is_product – Generally speaking, all values listed here would be considered a product.
  • configurator_code – This is the Configurator product code to which each row corresponds.
  • configurator_set – This is the set/section which houses all of the options.
  • default product – This is the price itemno. Only one product should be considered the default price. This item is used to inform the initial price of the item before any option is selected.
  • section_grouping – These are the different sections within the configurator options.
  • section_desc – This is an additional description/header, which appears after the desc value.
  • section_type – This is the type of element used. Options include dropdown, textline, textarea, radio, and checkbox.
  • section_default – In our case (using dropdowns), we use this section to select a default option.
  • is_orderable – In our case (using dropdowns), we use this section to prevent our NONE products from being orderable. These entries allow us to set the section_default.
  • quantity_multiplier – This is the quantity of each item that should be in the cart if 1 unit of the configurator product is ordered. Despite what our guidance in the admin panel says, this value must be numeric. It cannot be “no”.
  • discount_percent – This is the percentage at which the price for the customer should be discounted. This allows you to offer a discount on an item as a part of a configurator product, whereas you may charge full price for the item purchased independently. It also allows you to set a single price (using the default product price only). In our example, we set all products except the default product to give a 100% discount.
  • hide_price – This setting allows you to hide the price on the front-end.
The list above is not exhaustive. However, the columns above are the most frequently used across our platform. If you have questions about other fields, please reach out to us. Please ensure that you explain what you’re trying to achieve as well so that we may best assist you. Thank you!

How to Add a Variant Product to a Configurator Product

[videopress 0eZLpL05]

How to Add A Line Item Comment to the Configurator Product

[videopress ZVxCzE3v]

How to Allow or Disallow Certain Options in Dropdown Menus using the Decision Tree

[videopress FSmWzlQm]

In the video above, we cover the decision_tree and allow/disallow columns. The decision tree allows you to pre-specify which secondary options can be chosen based on a previous selection. This is useful if you wish to establish some level of control over which items can be paired with others in a configurator product.

The video shows how you can only allow one specific item to be purchased based on a previous selection.

However, you can also do the inverse, which would be to disallow the listed product from being ordered if a previous product is selected.

Additionally, you can set multiple values in the decision_tree column, separated by commas. So, rather than restricting a certain selection of items to one based on a previous selection, you can allow or disallow a number of items based on the previous selection.

This functionality is complex. It may not be fully supported for all option types, i.e. any other type except for dropdown menus. If you’re experiencing issues, please reach out to us so we may investigate further.

If you’d like to download our final testing configurator sheet, please click here.

Was this article helpful?

Thanks for the feedback.

Need further assistance?

Email support@commercebuild.com or open a ticket and we'll get back to you.

Submit a ticket