The global settings apply to all components of your service order: languages, currency and tax, the domains the configurator may run on, the look of PDFs and emails, email sending, the shop integrations, API keys and the AI assistant. You find them in the admin under Settings in the main navigation.
Settings of a single component – layout, price display, images, design – are in the component's editor instead: Component Settings.
The tabs at a glance
| Tab | Content |
|---|---|
| Localization | Default language, default currency, tax rate, prices include taxes, active languages |
| Domains | Domains on which your configurator may load |
| Branding | Logo, colour, font, header and footer, imprint for PDFs and emails |
| Email sending | Your SMTP server for emails of the action button |
| Integrations | HTML snippets and shop plugins |
| API | API keys |
| AI | AI assistant on/off, AI model, what the assistant has remembered |
| Data processing | Data processing agreement |
Locked tabs: If a new version of the data processing agreement has been published and you have not accepted it yet, all tabs except Data processing are locked. During a trial period the lock does not apply. See Data processing.
Localization
| Field | Effect |
|---|---|
| Default language | The main language of your content. New components use it when Use global settings is selected on the component. |
| Default currency | The currency in which prices are displayed. |
| Tax rate | The tax rate in percent that your prices are calculated with, e.g. 19. |
| Prices include taxes | Ticked: the prices you enter in components are gross prices. Not ticked: net prices. |
| Active languages | The languages you maintain content in. Add language… adds a language, × removes it. In the editor the active languages appear as Content language:. |
Save with Save settings. How tax rate and shop tax work together is explained in Set Up Pricing.
Domains
Your configurator only loads on domains entered here. This also applies to the actions of the action button (PDF, email). That way nobody can embed your configurator on a foreign site.
Add domain:
- Under Domain, enter the name without
https://, e.g.www.myshop.com. - Choose the Mode: Production, Staging or Development.
- Click Add.
An entered domain also applies to its subdomains. Changes take effect after a few minutes.
Quota: At the top right you see how many domains your plan allows and how many are in use – separately for Production and Staging / Development.
Do not use staging or development domains for live systems. The admin explicitly warns about this: otherwise the whole account will be suspended.
Reported by connected shops
Connected shop plugins report the domains they run on. These appear in a separate list with Reported by, Last seen and Type. The report alone does not allow anything:
- Add to licence enters the domain into your domains – only then does the configurator load there.
- Removing an entry from this list leaves your entered domains untouched.
Branding
Branding determines the look of the PDFs and emails generated by the action button. You style the configurator itself in the component in the Design tab.
| Field | Effect |
|---|---|
| Logo | PNG, JPG or WebP, max. 2 MB. Upload with Choose file, delete with Remove logo. |
| Primary color | Colour for headings, links and the line below the header in PDFs and emails. Also the default colour of all configurators (V3) unless an Active color or your own CSS replaces it – see Customising the design. |
| Font | Inter, Arial, Helvetica, Times New Roman, Georgia or Verdana |
| Header | Header area – separately for each active language |
| Footer | Footer area – separately for each active language |
| Imprint | Your legal notice – one text for all languages |
Changes to the branding apply immediately to all future PDFs and emails.
Email sending
configento.app sends emails of the action button through your own SMTP server. Without complete settings here, no emails can be sent.
Quick setup: Choose your provider and host, port and encryption are filled in: Gmail, Microsoft 365, GMX, web.de, iCloud, SendGrid, Postmark, Mailgun, AWS SES or Mailtrap (for testing only – the mails land in the Mailtrap inbox, not with the recipient). For each provider the admin shows a hint, e.g. that Gmail needs an app password.
| Field | Effect |
|---|---|
| Host, Port | Address and port of the SMTP server |
| Encryption | STARTTLS (usually port 587), SSL/TLS (usually port 465) or No encryption |
| Username, Password | Credentials. A saved password is not displayed; use Change to enter a new one. |
| Sender address, Sender name | Who the emails come from |
Test connection checks the settings. If you enter an address under Send test email to, a test email is sent as well. When the last successful test happened is shown under Last tested.
Integrations
Here you get the HTML snippets and the shop plugins. Which cards you see depends on your account.
Accounts without the classic cloud
At the top it says: “Shop plugins connect through the service portal — no security token is needed here.”
| Card | Content |
|---|---|
| Magento 2 | The two Composer commands to copy. You then connect the extension in Magento with your Service Portal login – see Install Magento Plugin. |
| Shopware 6.7 | Download plugin for the plugin ZIP – see Install Shopware Plugin. |
| Shopify | Code for linking (see below) |
| HTML5 (V3) | Token and snippet for any website (see below) |
Accounts with the classic cloud
At the top it says: “Enable integrations and manage security tokens for each platform.” For HTML5, Magento 1.x, Magento 2.x, Shopware 5.x and Shopware 6 there is one card each with
- a switch that enables the integration,
- the Security token with Copy and New token (the old token becomes invalid – enter the new one in the plugin as well),
- Download plugin (for Magento 2.x the link leads to the download page of the Composer repository).
When switched on, the HTML5 card shows a JavaScript snippet and an iFrame snippet. Replace YOUR_TEMPLATE_ID in them with the ID of the component. For these accounts, the Preview in the admin also needs the HTML5 card to be switched on.
On top of that come the cards Shopify and HTML5 (V3).
Shopify
Install the Configento app in your Shopify shop. Click Generate connection code here and enter the six-digit Onboarding code in the Shopify admin. The code is only valid for a short time (Valid until); Generate a new code gets you a new one. Below it you see which service order the shop will be linked to. More on this: Installing the Shopify Plugin.
HTML5 (V3)
For any website without a shop plugin, with the frontend engine V3:
- Click Generate – you get a token and the V3 JavaScript snippet.
- Copy the snippet into your page and replace
YOUR_TEMPLATE_IDwith the ID of the component.
Rotate creates a new token and invalidates all previous ones – afterwards you have to replace the snippet on your pages. All attributes of the snippet are explained in HTML Snippet Integration.
API
Here you create API keys for access to the configento.app API.
Creating a key:
- Enter a Key name, e.g. the name of the integration (“PIM”, “ERP sync”).
- Choose the Permission – Read only or Read & write.
- With Read & write, optionally tick Publish and/or AI.
- Optionally choose a date under Valid until (optional) – without a date the key never expires.
- Click Create. The key is shown only once – copy it immediately and keep it safe.
| Permission | Allows |
|---|---|
| Read only | Fetching data; no changes, publishing or deleting |
| Read & write | Creating, changing and deleting drafts |
| + Publish | Taking changes live and deleting components – both take effect in the shop immediately |
| + AI | Using the AI assistant via the API – this consumes AI tokens |
Good to know:
- A key only applies to the service order in which you created it.
- In the Active keys list you see Created, Last used and the validity of each key. You change permissions and date there via Change.
- A key with an expiry date works until the end of that day. After that it is listed as Expired on; via Change it becomes valid again.
- Revoke blocks a key immediately.
- No API key can manage keys, buy AI tokens or read integration credentials.
More on the API: API — Getting Started.
AI
| Setting | Effect |
|---|---|
| AI assistant | Switch for the whole assistant. When switched off, the AI panel disappears from the admin and no data is transferred to the AI provider. Can be switched back on at any time. |
| AI model | Economical, Standard or Maximum. More capable models answer better and use more of your monthly AI quota – currently Economical 0.5×, Standard 1:1, Maximum 2×. The admin shows the current factor at each level. |
What the assistant remembers
The section What we know about you lists information about your company that the assistant automatically uses in every new chat – such as technical terms or naming conventions.
- When the assistant remembers something new, it asks you first. Points not yet confirmed are listed under Awaiting confirmation – Confirm accepts them.
- Adjust changes a remembered point, Forget deletes it.
More on the assistant: AI Agent: Build Configurator via Chat and AI Tokens.
Data processing
This is where the data processing agreement between you and justSelling is shown.
- Download PDF downloads the agreement as a PDF.
- To accept it, enter your Name under Signature client (the Date is set automatically) and click I hereby accept the present agreement. Name, date and version are saved and appear on the printed document.
- When a new version is published, you have to accept it again. Until then the other settings tabs are locked – except during a trial period.
Troubleshooting
- All tabs except “Data processing” are grey – accept the new version of the agreement.
- The configurator does not load on my page – the domain is missing under Domains, or it was only reported but not added with Add to licence.
- Emails from the action button do not arrive – email sending is not fully set up. Check with Test connection and send a test email.
- A shop plugin no longer connects – you clicked New token on the card or Rotate for HTML5 (V3). Enter the new token or snippet.
- The preview in the editor asks you to enable HTML5 – switch on the HTML5 card under Integrations.
- A language is missing in the editor – add it under Localization at Active languages and save.