Every component has its own settings for layout, price display, images, design and reporting. You find them in the editor on the left in the Settings tab. On top of that there is the header bar above the editor with the content language, Save, Reset and Publish, plus the Versions tab. This article explains every field.
Settings that apply to your whole account – languages, tax rate, domains, email sending – live under Settings in the main navigation instead: Global Settings.
The editor at a glance
| Area | Content |
|---|---|
| Left | The tabs Characteristics, Rules, Settings and Versions |
| Middle | The Edit / Preview switch |
| Right | The settings of the selected characteristic, group or rule |
| Top | The header bar (see below) |
How to create characteristics and values is explained in Add Characteristics & Values; rules are covered in Build a Rule Set.
The header bar
| Element | Effect |
|---|---|
| Content language: | Appears when your account has several languages active. You choose the language you are editing texts in. The default language is marked (default). In any other language the editor shows the notice Translation mode – only translatable fields visible and hides everything that is not translated. |
| Undo | Reverts the last change. You can click it repeatedly as long as there are changes. |
| Reset | Discards all changes since the last publish and reloads the published version. The admin asks first: Reset to published version? This cannot be undone. For a component that has never been published, the button does not exist. |
| Not live yet | Shown as long as your saved or unsaved state differs from the published version. Until you publish, the shops keep showing the old version. |
| Publish | Checks the component, saves open changes and releases the state to the shops. The button only appears when there is something to publish. |
| Save | Appears above the right-hand area as soon as there are unsaved changes. Saving creates a draft – your shops do not see it yet. |
Publishing in detail
- Click Publish. Unsaved changes are saved first.
- The admin checks the component. Errors block publishing: Publish blocked — errors must be fixed:. Warnings are shown, but publishing is still possible: Warnings (publish still allowed):.
- If someone else has saved the component since you opened it, Concurrent edit detected! appears. If you publish anyway, you overwrite their changes.
- Confirm with Yes, publish.
“Settings” tab → General

Basic settings
| Field | Effect |
|---|---|
| Title | Name of the component in the overview and in the shop plugins. Can be maintained per language. |
| Headline | Optional headline above the configurator. Can be maintained per language. |
| Default locale for this component | The language you maintain the content in. Use global settings takes over the account's default language. |
Summary
| Field | Effect |
|---|---|
| Show combined article number | Shows the article number of the configured product at the end of the summary, e.g. “Article number: CL-W-GR”. V3 only. |
The combined article number is made of the article numbers of the selected values, in the order of the characteristics and separated by “-”. If a selected value has no article number, the characteristic's own counts. For a multi-selection, the first one present counts. Characteristics a rule hides don't count. The shop plugins put the same number into the cart, and the PDF and email of the action button offer it as {{combined_sku}}. In the Preview, the Combined article number checkbox shows it even when it is switched off in the summary.
Shop cart
| Field | Effect |
|---|---|
| Quantity changeable in the cart | On (default): the customer can change the quantity of the configured product in the cart, e.g. order the same configuration three times. Off: the cart keeps the line at quantity 1, and the product page shows no quantity field. |
Turn the setting off when the customer already chooses the quantity in the configurator, e.g. "100 pieces" with a graduated price. Otherwise the shop counts the quantity a second time. The change takes effect in the shop after you Publish. The shop plugins support it from Shopware 5.3.2, Magento 5.1.5 and PrestaShop 0.6.2, and they enforce it in the shop itself: a quantity change that bypasses the page still stays at 1.
Min / Max display
| Field | Effect |
|---|---|
| Show min/max | Shows the allowed range for input fields with a minimum and maximum value. |
| Min/max pattern | Format of this display. $min and $max are replaced by the limits, e.g. ($min - $maxcm) → “(40 - 240cm)”. |
Combined product image
| Field | Effect |
|---|---|
| Combined image | No, Combined product image (the images of the selected values are layered on top of each other) or 360° combined image (rotatable view, in Legacy and V3). |
| Animation 360 | 360° only: No loading animation, Loading without percentage, Loading with percentage or Percentage only. V3 shows the same loading indicator with percentage for the last two. |
| Start sequence in 360 view | 360° only: which image the rotation starts with. |
| Show 3D icon after (CSS selector) | 360° only: after which element of the page the 3D icon appears. Legacy only. |
How to add the images for this and how the rotation works: Image Visualisation & Uploading Images.
Extra charge
| Field | Effect |
|---|---|
| Display price | Shows the surcharges of the values in the configurator. |
| Price type | Absolute: the surcharge of the value. Relative: the difference to the currently selected value. |
| Display if zero | Also shows surcharges of 0. |
| Price pattern | Format of the display. $price is replaced by the amount with sign and currency, e.g. [$price] → “[+15.00 €]”. |
More on the pricing logic: Set Up Pricing.
Group layout
| Field | Effect |
|---|---|
| Group layout | How the groups are displayed: No groups, Tabs or Accordion (Legacy only). |
| Wizard | Appears when No groups is not selected. Guides step by step through the groups. |
| Auto scroll on tab change | Wizard only: scrolls up to the configurator when the step changes. |
| Top offset for auto scroll | Wizard only: distance in pixels to the top edge, e.g. for a fixed header of the shop. Default 80. |
| Wizard navigation (V3) | Wizard only: Tabs, progress and buttons (default), Back/Next buttons only or None if the shop page controls the steps itself. Applies to V3 only. |
| Option image position | Where the image of a characteristic sits next to it: Left, Right or Do not show. |
| Values excluded by rules | Hide (default): values a rule excludes disappear. Show disabled: they stay visible but cannot be selected – for radio buttons, checkboxes, dropdowns and image lists. Characteristics a rule hides then stay visible too, greyed out and disabled. Legacy knows this setting for values only. |
Groups, tabs and wizard in detail: Groups, Layout & Wizard.
Frontend engine
| Field | Effect |
|---|---|
| Engine | Legacy (default) or V3. Determines which configurator runs in the shop. |
If the component contains a characteristic that only V3 supports (currently the captcha), the settings show the notice Requires Frontend V3 at the top. What distinguishes the engines and where each one runs: Frontend Engine: Legacy or V3.
“Settings” tab → Design
| Field | Effect |
|---|---|
| Active color | Colour for selected values, active elements and the action button – for this component only. Empty: the colour from your CSS, otherwise the Primary color under Settings → Branding. |
| Loading animation color | Colour of the loading animation. In Legacy it is only used for the combined product image. In V3 it also colours the loading indicator of the 360° view. |
| Custom CSS | Your own CSS, loaded with the configurator – for adjustments to your shop design. |
| Custom JavaScript | Your own JavaScript, loaded with the configurator. |
Custom CSS and JavaScript depend on the structure of the configurator. Legacy and V3 generate different HTML – if you switch the engine, check your adjustments in the preview. How to adapt V3 to your shop design with CSS and which classes stay the same permanently is described in Customising the design (CSS).
“Settings” tab → Reporting
Reporting sends events to Google Analytics 4 that show how your customers use the configurator: which values they choose and which configurations they complete. It only runs in the V3 engine.
The configurator does not load a Google tag of its own. It hands the events to the Google tag of your page – to gtag or, if you use Google Tag Manager, to its dataLayer. If the page has no Google tag, nothing is sent. Your visitors' consent thus stays in one place: your cookie banner and the way you embed your Google tag.
| Field | Effect |
|---|---|
| Enable reporting | Turns reporting on and shows the other fields. |
| GA4 measurement ID | Optional. With a measurement ID (G-…) the events go to that property; when empty, to the property the page's Google tag uses. Universal Analytics IDs (UA-…) no longer work and are ignored. |
| Track complete configuration | Additionally reports every chosen value when the configuration is completed. |
| Hide characteristics | Internal names of characteristics that should not be reported, separated by commas. |
These events arrive in GA4:
| Event | When | Parameters |
|---|---|---|
configento_view |
The configurator has loaded. | configento_component_id, configento_component |
configento_select |
The customer chooses a value. | plus configento_characteristic, configento_value |
configento_complete |
The configuration is completed, for example via Add to cart or an action button. | plus value (price) and currency |
configento_configured_value |
Only with Track complete configuration: one per chosen value at completion. | as configento_select |
Characteristics and values appear with their names in the component's default language, so a multilingual shop does not get separate rows per language. Only characteristics with values are reported – such as select, radio buttons, checkboxes and image lists. Free text is left out because it can contain personal data, which Google does not allow in Analytics. Nothing is sent from the preview in the editor.
To evaluate the parameters in GA4 reports, create them in GA4 as custom dimensions with the scope "Event". You can mark
configento_completeas a key event.
“Settings” tab → Custom fields
Here you create your own additional fields, which then appear on every characteristic or every value – for example an internal material number or a supplier code.
- Fields for characteristics and Fields for values: Add field creates a field, and you give it a Name. The type is always Text.
- You then enter the values on the characteristic or value in the Custom fields section.
- The values travel with the configuration into the cart and the order, so that a shop or an ERP system can evaluate them – for values, those of the selected value when the characteristic is a single selection. They are not visible to your customers. In V3 you can also read them with JavaScript using
getCharacteristics(), see JavaScript API reference.
Custom fields are not input fields for your customers. Ask for name, email or company with normal characteristics, e.g. with a small input field.
“Versions” tab
Every save creates a version, every publish a version marked Published. In the Versions tab you can
- compare a version with your current state using Compare with draft,
- Select two versions and Compare them,
- Restore a version. It replaces your current draft, but only becomes visible in the shop after you Publish.
If there is no version yet, save the component once.
Troubleshooting
- A change does not arrive in the shop – if Not live yet is shown at the top, click Publish. Saving alone is not enough.
- The “Reset” button is missing – the component has never been published. There is no version to reset to.
- I only see some of the fields – you are editing a language other than the default language. Switch Content language: to the language marked (default).
- Accordion has no effect – the component runs on V3. V3 has no accordion and shows the characteristics without groups.
- The 360° image does not rotate – check that each value has a whole image sequence in the 360° images section. Layers with only one image do not rotate.
- Reporting delivers no data – reporting only runs in V3 and needs a Google tag on the page (see above). Also check whether your visitor consented in the cookie banner.
- The combined article number is missing from the summary – none of the selected values and none of the characteristics has an article number, or the component runs on Legacy.
- The quantity in the cart cannot be changed – Quantity changeable in the cart is turned off in the component. Turn it on and publish the component.
- Excluded values disappear instead of showing greyed out – set Values excluded by rules to Show disabled and publish the component.