With the Shopware plugin, your configurator appears directly on the product page of your Shopware shop. Your customers build the product, see the price instantly and add the finished configuration to the regular Shopware cart. The order then runs through Shopware as usual.
Requirements
- Shopware 6.7 (the current plugin is built for 6.7)
- PHP 8.2 to 8.5
- Access to the Shopware admin with permission to install extensions
- A login for the Service Portal for the service you want to connect the shop to
- At least one published component – unpublished drafts can't be selected in the shop
Using an older Shopware 6 version? Contact support before installing.
Download the plugin
You get the plugin in configento.app under Settings → Integrations.
If the tab is locked, first accept the data processing agreement under Settings → Data processing.
Which card you see there depends on your account:
| You see … | This means | Sign-in in the plugin |
|---|---|---|
| a Shopware 6.7 card with the button Download plugin | Your shop connects via your Service Portal login. You don't need a security token. | Connect to Configento (recommended) |
| a Shopware 6 card with a switch, a security token and the link Download plugin | Your account still uses legacy authentication. | Enter customer ID, secure key and security token by hand – see Legacy authentication |
Download the ZIP file and do not unpack it.
Install the plugin
In the Shopware admin
- Open Extensions → My extensions.
- Upload the ZIP file via Upload extension.
- Install and activate the configento.app Plugin.
- Clear the Shopware cache.
Via the console
If you have access to the Shopware console, copy the unpacked folder JustsellingProductConfigurator to custom/plugins/ and run in the Shopware directory:
bin/console plugin:refresh
bin/console plugin:install --activate JustsellingProductConfigurator
bin/console cache:clearThe plugin's technical name is JustsellingProductConfigurator. Older guides give a different name here that doesn't work.
Connect to Configento
You set up the connection once from the Shopware admin. You don't need to copy a token.
- Open the configuration of the configento.app Plugin in the extension management.
- In the General card, under Configento connection, there is the button Connect to Configento. Click it.
- You are redirected to the Service Portal. Sign in and confirm the connection.
- You then return to the Shopware admin. Configento connection now shows Connected as with your portal login.
Leave the switch Use legacy authentication off.
When connecting, the plugin fills in the credentials for the product page itself. You find them in the General card as Customer ID, Secure Key and Security Token. You don't need to change anything there.
Each admin user connects individually. The connection applies to the Shopware user who set it up. If a colleague works with their own Shopware login, they see the message Connect to Configento when they first open the configurator and click Connect now.
You can check the existing connection at any time with Test connection.
Edit components in the Shopware admin
Once connected, the catalogue section of the Shopware main menu has an entry configento.app. It opens configento.app directly in the Shopware admin, so you edit your components without leaving the shop.
Link a product to a component
- Open the product in the Shopware admin.
- Switch to the configento.app tab.
- Click Add component.
- Choose the component under Component name. The list shows the components of your connected service by name.
- Optional: enter a Headline. It appears above the summary of the configuration on the product page (see Plugin settings).
- Save the product.
A product has exactly one component. Once one is linked, the Add component button disappears. To link a different component, remove the old one with Remove component and then add the new one.
If a component doesn't appear in the list, it usually isn't published yet. Publish it in configento.app and reopen the product.
Which frontend engine runs
From version 5.2.0 the plugin loads the matching frontend engine for each component. V3 runs when you set it for the component, when the component contains a characteristic that needs V3, or when your account runs without the classic cloud. Otherwise it stays with Legacy. With the setting Configurator version you decide this for the whole shop, see Configurator in the shop. How the two engines differ: Frontend engine: Legacy or V3.
With V3, also:
- The price at the top of the product page includes the configuration and changes with every choice.
- If the component creates a combined product image, it replaces the product photos on the product page. In the cart, at checkout and in the order it is the line's image.
- The cart always charges the price configento.app calculates for the configuration – regardless of the price verification.
- The link on the product in the cart opens the configurator with the saved selection. The customer changes it and adds the product to the cart again.
Approve the shop domain
V3 only loads on domains that are approved for your service. From version 5.2.3 the plugin reports the domains of your sales channels to configento.app when you connect, but does not approve them itself. Take them over in the configento.app admin under Settings → Domains in the section Reported by connected shops before you switch a component to V3. If a domain is added later, enter it there yourself or connect the plugin again. More on this: Global Settings.
What happens in the shop
- The customer opens the product page. The configurator appears in the buy box and replaces the regular add-to-cart button there.
- The customer builds the product. The price is recalculated with every selection.
- Add to shopping cart puts the product and its configuration into the Shopware cart. The selected characteristics are listed below the product.
- Shopware processes the order as usual. In the order in the Shopware admin you see the configuration on the order line item.
The cart price is the price of the Shopware product plus the surcharges of the configuration. If you enter a base price in Shopware, it is added to the configuration price. If the configurator should determine the complete price, set the Shopware price to 0.
The shop always shows the last published version of the component. Changes you have only saved are visible to your customers after you publish.
Product data in formulas
With V3, characteristics of the data type Product attribute read values of the Shopware product, from version 5.2.1 of the plugin. That way a formula can work with width, weight or a property. Enter as the code in the characteristic:
| Source | Code | Example |
|---|---|---|
| Field of the product | Name of the field in Shopware | productNumber, name, ean, manufacturerNumber, manufacturer, width, height, length, weight, purchaseUnit, referenceUnit, packUnit, minPurchase, purchaseSteps |
| Custom field of the product | Technical name of the custom field | custom_banner_material |
| Property of the product | Name of the property group | Material returns e.g. Wool; several options come separated by commas |
| Variant | Name of the variant's property group | Size returns e.g. XL |
If a code exists more than once, the source higher up in the table wins. Property group names apply in the language of the sales channel. In a multilingual shop, name them the same in all languages, otherwise the characteristic stays empty in the other languages.
The price verification in the cart uses the same values. The plugin never hands out purchase prices, stock or descriptions, because the values are in the source code of the product page. More on the data type: Calculated characteristics.
Configuration in the order confirmation
The Shopware order confirmation doesn't show the selected characteristics by itself. Add this block to the Order confirmation email template, inside the loop over the order line items.
In the HTML version:
{% if nestedItem.payload.justselling_options is defined and nestedItem.payload.justselling_options|length >= 1 %}
<div>
{% for option in nestedItem.payload.justselling_options %}
{{ option.group }}: {{ option.option }}
{% if nestedItem.payload.justselling_options|last != option %}<br>{% endif %}
{% endfor %}
</div>
{% endif %}In the plain-text version:
{% if lineItem.payload.justselling_options is defined and lineItem.payload.justselling_options|length >= 1 %}, {% for option in lineItem.payload.justselling_options %}{{ option.group }}: {{ option.option }}{% if lineItem.payload.justselling_options|last != option %}{{ " | " }}{% endif %}{% endfor %}{% endif %}The variable names nestedItem and lineItem must match your template. If your loop uses a different name, replace them accordingly.
Plugin settings
All settings are in the configuration of the configento.app Plugin.
Configurator in the shop
| Configurator version | Effect |
|---|---|
| Automatic (as set for the component) (default) | The plugin asks configento.app for each component whether it runs with V3 – see Which frontend engine runs. |
| Always V3 | All components run with V3. |
| Always the previous version | All components run with Legacy. |
Settings
| Setting | Effect | Default |
|---|---|---|
| Load Chart plugin | Turn on if your components contain characteristics with charts. Legacy only. | off |
| Load Dropzone plugin | Turn on if your components contain file uploads. Without it, uploads don't work in the shop. Legacy only. | off |
| Load jQuery | Loads jQuery for the configurator. Only turn off if your theme already loads jQuery and there are conflicts. Legacy only. | on |
| Create parts list when ordering | Instead of one configured product, the individual Shopware products belonging to the selected values are ordered. For this, the Article number (SKU) of a value in configento.app must match the product number of a Shopware product. See Part Lists via Article Numbers. | off |
| CSS Path of combined Image Container | CSS selector of the area on the product page where the combined product image should appear. With V3 the image replaces the product photos there. Left empty, the image area of the product page is used. | empty |
Price verification
From plugin version 5.0.1, configento.app recalculates the surcharge of every configuration on its own server. That way a price manipulated in the browser doesn't end up in the cart.
| Mode | Effect |
|---|---|
| Off | No verification. The cart takes the price from the configurator. |
| Observe (log differences only) (default) | The cart still takes the price from the configurator. Every deviation is logged as configento.price.divergence in the Shopware log. |
| Enforce (cart uses the verified price) | The cart charges the verified price. If none is available, e.g. because configento.app can't be reached, Shopware blocks the order with a message for the customer. |
After the update, let the plugin run on Observe for a few days. If the log shows no deviations, switch to Enforce.
This setting does not apply to components with V3: the cart always charges the verified price there.
Product view
| Setting | Effect | Default |
|---|---|---|
| Show summary in tab on product page | Shows the selected configuration in the description tab of the product page | off |
| Show summary below price on product page | Shows the selected configuration below the price, with the Headline from the product link | off |
Developer-Settings
Debug mode, Development mode and the URL fields below them are meant for troubleshooting with support. Keep them off and empty in the live shop.
Subscription status in the administration
From version 5.2.1 the plugin shows a notice configento.app subscription once per session in the Shopware administration when your subscription needs attention:
| Notice | Meaning |
|---|---|
| Your trial ends on … | The trial ends within the next 7 days. |
| Your subscription is no longer active. Configurators keep working in your shop until … | The subscription has ended. The configurator keeps running until the date shown. |
| Your subscription is no longer active. Renew it to keep the configurators running in your shop. (or Your trial has ended. Take out a subscription …) | Subscription or trial have ended, but the configurator still runs. Renew before it is switched off. |
| … Configurators are no longer available in your shop. | Trial or subscription have ended. |
When configento.app no longer serves your shop, the product pages show the sentence This product cannot be configured at the moment. instead of the configurator. The plugin checks the status at most once an hour, so after a renewal it can take up to an hour until the notice disappears. You manage your subscription in the service portal.
Legacy authentication
Accounts that see the Shopware 6 card with a security token under Settings → Integrations connect the plugin with three credentials:
| Field in the plugin | Where to find the value |
|---|---|
| Customer ID | Service Portal, Services page: the value next to "Customer" for the respective service |
| Secure Key | Service Portal, Services page: the Secure key for the respective service |
| Security Token | configento.app, Settings → Integrations, Shopware 6 card. Switch the card on so that a token is generated. |
Turn on Use legacy authentication in the plugin configuration, enter the three values and save. Test connection checks the credentials. If they are correct, Legacy cloud connection OK appears. New token generates a new token in configento.app – you then have to replace it in the plugin as well.
Update the plugin
Upload the new ZIP file under Extensions → My extensions as during installation and run the update. Via the console, copy the new folder over the old one and run:
bin/console plugin:refresh
bin/console plugin:update JustsellingProductConfigurator
bin/console cache:clearConnection, settings and product links are kept during the update.
Disconnect
Disconnect is under Configento connection in the plugin configuration.
Caution: disconnecting affects the whole shop, not just your admin user. All links between products and components in the shop are deleted and the stored credentials are reset. The components themselves in configento.app are kept. After a new connection, however, you have to link them to the products again.
So only disconnect if the shop should no longer use configento.app or should work with a different service. Switching admin users doesn't require it.
In the Service Portal, under Connections, you see all connected shops: shop host, plugin, service, Connected by and Last used. You can also Revoke a connection there, e.g. if you no longer have access to the shop.
Troubleshooting
The component list in the product tab is empty
- Is your admin user connected? Open the plugin configuration and check whether it says Connected as.
- Is the component published? Drafts don't appear.
An error message appears under configento.app in the main menu
- "Stored Configento connection is corrupted — please reconnect.": click Disconnect and connect again. Keep in mind that this deletes the product links.
- "Configento service portal could not issue a token right now — please try again.": try again after a few minutes with Retry.
- "Plugin is not yet connected to Configento.": click Connect now.
The configurator doesn't appear on the product page
- Is a component selected in the product's configento.app tab and is the product saved?
- Clear the Shopware cache and reload the page in the browser.
- With legacy authentication: are customer ID, secure key and security token correct? Is the Shopware 6 card switched on under Settings → Integrations?
File upload or chart doesn't work in the shop Turn on Load Dropzone plugin or Load Chart plugin and clear the cache.
With V3 the configurator stays empty or does not load Is your shop's domain entered under Settings → Domains? See Approve the shop domain.
A product attribute characteristic stays empty The code doesn't match, or the property group has a different name in the sales channel's language. With Legacy the characteristic always stays empty in Shopware. See Product data in formulas.
The product page shows "This product cannot be configured at the moment." Your subscription or trial has ended. See Subscription status in the administration.
The price in the cart is too high The Shopware product price is added to the configuration price. Set it to 0 if the configurator delivers the whole price.
The shop shows an old version Publish the component in configento.app. The shop only shows published versions.
If none of this helps, contact support via the chat in the Service Portal. Include the Shopware version, the plugin version and the link to the affected product page.
Shopware 5
Shopware 5 is no longer developed by Shopware. The configento.app plugin for Shopware 5 doesn't get new features either. Use Shopware 6.7 for new shops.