Skip to main content

How do I design the configuration termination?

Your customer configures their product variant. When he is finished, he can place it in a store or send you a request by e-mail, possibly with a PDF.

You can set which options you allow.

tip

You should only place a test order in the editor of your configurator when you have veröffentlicht the configurator.

Set order actions​

You can define which actions your user can perform. You can offer more than one action, e.g. both "Request" and "Add to shopping cart".

  • Open the editor
  • Depending on your Layout, you will find the action buttons at the bottom right of the 3D area.
  • Click on the pencil symbol behind it
  • The list of actions now opens in the right-hand sidebar. Expand the action you want to change.
  • Or click on
    Loading...
    (at the bottom)

Define a main action​

The main action is displayed on the last configuration step instead of the "Next" button.

  • In the header of an action, next to the name, there is a switch that selects the action as the main action.

Design overview page​

Before a configuration is saved, an overview page with the selections and the price is displayed. This page can be designed depending on the action.

To do this, click on the "Overview page" selection in the action:

  • Features and articles: The characteristics are displayed, sorted according to the steps, and the selected or entered values. In addition, the articles that are added based on these values and that determine the price are displayed.
  • Only articles: Only the articles are displayed.
  • No overview: The overview page is not displayed.

Query customer data​

  • Check the "Contact form" box in the action.
  • You can now select certain fields for customer data, which are then requested on a page after the overview page, before saving.
  • If you click on the number wheel behind one of these fields, the option opens with which you can determine whether the field is a mandatory field.
  • A data protection notice can also be entered here.
  • If an e-mail address is entered, you have the option of initiating a Mail an den Kunden here.
warning

Please note:

When you request customer data, you are collecting personal data. This data is protected by the GDPR. You must therefore obtain the user's consent before starting the configurator (on your website or store).

Dynamically hide order actions​

You can also hide actions, e.g. to provide different inputs with different outputs or to force the user to set an optional characteristic.

For example, if you want to integrate the configurator on the web and store and have different outputs:

  • Set up a feature that specifies which order buttons should be shown. This is probably hidden. It can be a numerical feature (0=website, 1=shop), which is the simplest, or a yes/no switch or a selection where the values are "keys".
  • You then set this feature differently when entering from the website or store. To do this, give the feature itself a "key", e.g. "webOrShop" and then append it to the address of the configurator, e.g. …&webOderShop=1 or …&webOderShop=web (if "web" is a value key).
  • Finally, build a rule with this characteristic and the action "Set configurator completion". You can then define which order buttons can be hidden or grayed out for each value of the characteristic.