Backend eCom

This makes the employee the user under which the shop operates. Without it, the eCom system does not recognise the employee as its own — role and rights then remain ineffective, even though everything appears maintained.

Important: Only one single employee may have this checkbox. A second eCom employee is not intended.

Which rights must be set

You can recognise the eCom-relevant rights by the blue cart symbol behind the entry. Rights without this symbol do not affect the shop.

A complete list with the respective effect in the shop is available in the specification on the page eCom rights at a glance.

Important: You define the scope of functions via the role, not the question of whether ordering is allowed. A customer with access can always order. If a customer should not be able to order, they need a lock at the customer. There is no right for this in the role, and it cannot be set in the backend either: it comes from the ERP system and is delivered with the customer data.

Note: How the lock affects the shop is currently under review. It has been observed that a locked customer can submit the order and receives a confirmation without an order being created. For the moment, do not rely on a lock to properly block the shop. See Order completion in the specification.

E-mail address of the employee

The e-mail address stored for the eCom employee has a special significance: In the test system, all shop e-mails go to this address, not to the customer. This also applies to the e-mail with the visible password during registration.

The address is maintained under Basic configuration > Employee.

1. Setup

Provision of Data

Attention, current limitation: Provisioning of data currently does not work for pictures. If you have changed pictures — container, login graphic or logo — please use the Rollout button in the Employee overview instead. The limitation has been reported; as soon as it is fixed, the procedure described below will apply again.

Summary

Amendments to the eCom configuration only take effect once the data has been provisioned.

The eCom system then automatically retrieves the provisioned data — depending on the setting every 15 or 30 Minutes.

The process is the same as with a normal client.

Procedure

Change and Save configuration in the web backend.
Provision data.
Wait until the eCom system has retrieved the data.

When the Pictures checkbox must be set

Amendment	Pictures checkbox
Settings, Texts, Rights, Order templates	not required
Container with new or changed picture	required
Login graphic or shop logo	required

Without this checkbox, the pictures will not be transferred, although the rest of the configuration arrives.

Most common error case

An uploaded picture does not appear in the shop. The cause is almost always one of the two:

After uploading, it was not Saved. An uploaded picture initially only resides in the temp folder; only Saving moves it to the correct folder.
It was provisioned without the Pictures checkbox.

2. Maintaining Marketing

Create and position containers

Summary

Containers are the advertising spaces of the shop. They are maintained under eCom \ Container.

A container becomes effective in two steps: you create it, and you define how the area in which it appears is displayed.

What a container is, which link types exist, and which image dimensions apply are described in the service description on the page Marketing-Container.

Create container

Open eCom \ Container. The list shows all existing containers with position, type, link type, and status. Use Create new container to add another one; clicking on a row opens an existing one for editing.
Select Container type: Image, Image with text, or Text with image. See below.
Depending on the type, add Image and Text. If the image was created with AI, check Image is AI generated — see Mark images as AI-generated. The text can be formatted using the toolbar of the Content field. The image dimensions depend on the display type of the area, see below.
Set Priority. 1 appears first.
If the container should only appear for certain customers, select a Customer list. Without a customer list, it appears for all.
Set Link type and the associated target.
Set Status to Released — only then does the container appear in the shop.
Save.
Provide data — with the Images checkbox, otherwise the image will be missing in the shop.

Optionally, a display period can be set via From and To, for example for a limited-time promotion. Without an entry, there is no limitation.

Select container type

Type	in float area	in slider
Image	image only	image only
Image with text	text to the right of the image	text below the image
Text with image	text to the left of the image	text above the image

The Content field includes its own toolbar for formatting.

When choosing the type, note in which Type the container appears: the same combination of image and text is displayed side by side in the float area and stacked in the slider. Text that fits next to the image in the float may appear differently above the image in the slider.

Add image

Use a square 900 × 900 pixel image for a float tile — also for types with text. A tile with text is twice as wide, but the image inside remains the same size as in a tile without text. So you do not need a larger image.

Warning: In the float area, the image can be cropped left and right. It fills the tile height, and if a neighbouring tile has a lot of text, the entire row becomes taller. Therefore, place the motif centrally and leave margins on the sides.

As a rule of thumb: use rather wide images for the slider, square ones for the float area.

For the slider, the required format depends on whether it switches automatically:

Display interval	Recommended image size
`0` — no autoplay	at least 630 pixels high, aspect ratio between about 1:1 and 2.3:1, for example 945 × 630
greater than `0` — autoplay	1500 × 500 pixels (3:1)

The slider does not crop. If the aspect ratio does not fit, the image is scaled smaller and gets blank stripes — for the autoplay slider on the sides if the image is too tall, and top and bottom if it is too wide. A larger image frame does not help, only the correct ratio.

Warning: If you change the Display interval later, the required image format of the containers at this position also changes. The complete size table is in the service description on the page Marketing-Container.

Warning: For the link type Order template, the selected order template must be enabled for eCom. See Enable order template for eCom.

If a container does not appear in the shop

Check in this order:

Check	Background
Is the Status set to Released?	Only this status appears in the shop. In progress, Completed, and Deleted remain invisible.
Is today within the From / To period?	Empty fields mean no limitation.
Does the Culture match the customer's language?	In the multilingual shop, the container must be maintained per language.
Were the data provided with the Images checkbox?	Without this checkbox, the image is missing.

A container that should no longer run does not have to be deleted — Completed removes it from the shop but keeps it in the list.

Define display type of the area

Open eCom \ Container, submenu Items.
For Type of display for the desired position — Homepage top or Homepage bottom — select Slider or Float.
For Slider: set in the field Display interval whether it switches automatically. See below.
Save and provide data.

Display interval

The field appears only for Slider.

The value is entered in milliseconds: 3000 is three seconds.

Value	Effect
`0`	The slider does not switch automatically. Several cards are shown side by side; the customer navigates using the arrows left and right.
greater than `0`	The slider switches automatically after this time. Only one card is visible at a time, with a dot navigation below.

Warning: The time applies per image, not for the entire cycle. With three containers and 3000, each image is shown for three seconds; one cycle takes nine seconds.

Consider when setting: a short interval appears restless, and a container with text needs longer to read than a pure image.

The switch pauses as long as the customer’s mouse is over the slider or it is focused via keyboard. If the customer clicks a dot in the dot navigation, the slider stops permanently on that image and does not start again automatically. Therefore, do not expect every customer to see all containers — important content belongs on the first container or in the float area.

Both positions can be freely assigned: a slider at the top and a float area at the bottom is the usual combination, but the reverse or the same display type twice is also possible.

Order of multiple containers

If multiple containers are in the same area, the priority determines the order. For a slider, the shop then shows arrows and dot navigation; for a float area, the containers are stacked from left to right.

2. Maintaining Marketing

Maintain texts

Summary

Under eCom \ Texte you maintain the texts that the customer sees in the shop — legal texts, the cookie notification, and the confirmations after registration.

Distinction: The texts of the e-mails are not here, but under Basic configuration \ Settings \ E-Mail contents. See Setting up e-mail subscriptions and maintaining templates.

For each block you can either store a text or a URL. If a URL is entered, the text is not displayed, but the link is opened.

The available text blocks

The selection is made via the field Type:

Text block	Where it appears in the shop
Legal notice	Footer, always visible
Privacy policy	Footer, always visible
Terms and conditions	Footer, only if content is stored
Cookies	Cookie confirmation on the login mask
Support Hotline	Footer, only if a text is stored
Newsletter	Footer, only if a text is stored
Access request hint	under the link Access request?
Access request confirmation	Message after submitting the access request
Password forgotten confirmation	Message after requesting a new password
New customers reservation confirmation	Message after submitting the form Not a customer yet?

Procedure

Open eCom \ Texte.
Select the desired block in the field Type.
Either enter a text or enter a URL.
Save and provide data.

The confirmation texts are your texts

Four blocks determine what the customer reads after an action: Access request confirmation, Password forgotten confirmation, New customers reservation confirmation and the hint under Access request.

The wordings quoted in the service description are the delivery state. You can completely replace them with your own formulations — for example, to add a telephone number for enquiries.

When a URL is more useful

Important: Privacy policy and Legal notice always appear in the shop always, even without maintained content — the customer then lands on a page with the wildcard text "No content is currently stored for this type." Both are mandatory information and should be filled before going live. The Terms and conditions behave differently: without content the entry does not appear at all.

For Legal notice, Privacy policy and Terms and conditions a URL is worthwhile: if you link the texts of your standard homepage, you only have to maintain them in one place.

For Support Hotline and Newsletter a text is more useful. Both menu items only appear in the shop if a text is stored — without text the menu item is missing.

Text block "Access request hint"

You need this block if you have not set the setting Not a customer yet?. Then only Access request? appears on the login mask, and this block fills the associated hint — extendable with URLs.

Without the block the hint remains empty.

2. Maintaining Marketing

Uploading Pictures

Summary

Under eCom \ Pictures you upload the two fixed graphics of the shop:

the graphic on the login page
your logo for the menu bar, which appears after the customer logs in

The required dimensions are listed in the service description on the Marketing Container page.

Procedure

Open eCom \ Pictures.
Select picture and perform Upload.
Save. This step is mandatory — see below.
Provide data, with tick Pictures.

Why three steps are necessary

This is the most common stumbling block:

Step	What happens
Upload	The picture is in the Temp folder. It is not visible in the shop.
Save	The picture is moved to the correct folder.
Provide with tick Pictures	The picture is transferred to the shop.

If one of the last two steps is skipped, the picture does not appear — even though the upload was successful and looks correct in the backend.

Pictures created with AI

If a picture is marked as AI-generated, the shop displays the notice AI GENERATED above it. The tick Picture is AI generated is also available here under eCom \ Pictures, not only at the container. See Mark pictures as AI-generated.

2. Maintaining Marketing

Mark pictures as AI-generated

Summary

From version 19 onwards, a picture can be marked as created with AI. The shop then automatically displays the note AI GENERATED above the picture.

The marking is done with the checkbox Picture is AI generated below the picture. The checkbox is available in two places: under eCom \ Container on the individual container and under eCom \ Pictures for the fixed graphics of the shop.

How the note looks and where it appears is described in the service description on the Marketing Container page.

Procedure for the container

Open eCom \ Container and edit the container.
Upload the picture via Add file, if not already done.
Set the checkbox Picture is AI generated below the picture.
Save.
Provide data, with checkbox Pictures.

The checkbox is located directly below the picture preview, between Picture upload and Content.

Procedure for the fixed graphics

You will find the same checkbox under eCom \ Pictures for the login graphic and the logo. Procedure as with uploading — see Uploading pictures — additionally set the checkbox.

The marking always applies per picture, not once for the entire shop.

If no note appears

Check	Background
Is the checkbox set and saved?	Without saving, the change remains in the mask.
Were the data subsequently provided with checkbox Pictures?	As with every picture in the shop.
Is the installation running on version 19 or newer?	Older versions do not know the marking. The shop then displays the pictures normally, just without the note.

What this means for picture selection

The note is positioned over the picture, in the upper right corner. Therefore, choose a motif for marked pictures that does not have anything important there.

See Marketing Container in the service description.

3. Maintaining Discounts

Creating and Evaluating Vouchers

Summary

Vouchers are maintained under eCom \ Voucher management.

A voucher is stored in the DeDeSales order as a Header discount. The usage rules and the effect in the order are described in the service description on the page Vouchers and Special discounts.

Create voucher

Open eCom \ Voucher management and add a voucher.
Select usage rule — one-time, multiple times, only on first order or once per customer.
Set discount value and specify whether it is charged percentage or as a fixed value.
Specify whether the voucher is combinable with a Special discount. See below.
Limit a period if necessary.
Save and provide data.

What you specify when creating

Besides code and discount, four fields determine for whom and when the voucher applies:

Field	Effect
From / until	Validity period. Outside this, the shop reports “The voucher has expired!”
Minimum order value	The voucher only applies from this cart value. `0` means no limit.
Type of customer selection	restricts the group of customers, e.g. all customers
Usability	how often the code may be redeemed — one-time, multiple times, multiple times only on first order or multiple times only once per customer

The discount is granted only as a percentage — the field is called Discount %.

Combinable with a Special discount

Value	Behaviour in the shop
Yes	Both discounts are added; the total goes as Header discount into the order.
No	The voucher is refused if the Special discount is higher than the voucher discount.

With No, a comparison is made, not a blanket prohibition: If the voucher is better than the current Special discount, it is accepted. Only if the Special discount would be higher does the shop reject the voucher — the customer then keeps the cheaper Special discount.

So that the customer can redeem the voucher

Additionally, the setting Voucher input under eCom \ Settings must be enabled. This activates the input field in the Cart.

Attention: Both places act independently. Without the Voucher input setting, there is no input field — the created voucher is then not redeemable, although it is valid.

So that the discount arrives in the ERP system

Attention: The Header discount only applies in your ERP system if your interface or your connector considers it. Also check how the interface is defined: fixed amounts are passed differently than percentage values.

Evaluate who has used a voucher

Open eCom \ Voucher management.
Select the desired voucher.
Switch to the tab generated vouchers on the left.
On the right, all vouchers that have been used appear.

3. Maintaining Discounts

Create Special discounts

Summary

Special discounts are maintained under eCom \ Special discounts.

Unlike a voucher, a Special discount works automatically — the customer does not have to enter anything. It applies to all customers and all items in the specified period.

Procedure

Open eCom \ Special discounts and add a Special discount.
Set discount value and period.
Save and provide data.

What to consider

The Special discount cannot be restricted to individual customers or items. If you want that, you need a voucher with a Customer list or an Order template.
It is stored like a voucher as a Header discount in the DeDeSales ORDER and is subject to the same reservations when transferring to the ERP system.

If a voucher is redeemed in parallel

The behaviour is controlled not by the Special discount, but by the voucher. For each voucher it is determined whether it can be combined with a Special discount:

Voucher combinable	Behaviour
Yes	Both discounts are added; the total goes as Header discount into the ORDER.
No	The voucher is refused if the Special discount is higher.

When you start a Special discount, therefore check the ongoing vouchers — there it is decided whether the discounts add up.

4. Customers and Notifications

Unlocking and Managing Registrations

Summary

Under eCom \ eCom customer registration you manage your customers' access.

The type has two lists: open registrations and completed registrations.

How the access model works and which e-mails are triggered is described in the service description on the Access model page.

Open registrations

Here are the customers who could not be registered automatically because there were discrepancies in the registration compared to the master data from the ERP system.

Two options:

Promotion	Result
Unlock customer anyway	The customer receives the e-mail Registration - new password and can log in.
Delete registration	The entry disappears, the customer does not receive access.

A common cause is a missing or syntactically incorrect e-mail address in the customer master data. Cleaner than unlocking is then to correct the address in the ERP system. The customer then requests access again.

Completed registrations

Here are all registered customers. Three options:

Promotion	When useful
Change e-mail address	The customer no longer has access to their stored address.
Reset password	The customer cannot log in and Password forgotten does not help.
Delete registration	Access should be revoked.

Special features regarding customer numbers

Not yet verified: The following two points have not been checked.

If your customer numbers contain letters, the names are displayed case-insensitively during registration.
Customer numbers registered with a space appear without the space.

Either could be a possible reason why an entry seems to be missing when searching.

So that you are informed of enquiries

The e-mail subscription eCom - eCom customer registration must be set up. Without this subscription, you will not be informed that a registration is waiting or that an address in the ERP system needs to be corrected.

4. Customers and Notifications

Setting up e-mail subscriptions and maintaining templates

Summary

The shop's e-mail dispatch has two controls, and in case of problems, almost always one of these is the cause:

Control	Location	Controls
Subscription	Administration \ E-mail subscriptions	who receives an e-mail
Template	Basic configuration \ Settings \ Manage e-mail contents	what it contains

Setting up subscriptions

For eCom, two groups of subscriptions are relevant, and this is the most important distinction in this chapter.

Subscriptions that only concern eCom

These carry the prefix eCom - :

Subscription type	Subscriber receives	Mandatory
`eCom - Contact form`	Inquiries from the contact form
`eCom - Customer registration`	New customer inquiries and registrations with master data deviations
`eCom - Notification of failed ERP export`	Notification when a shop order could not be processed on the server	yes
`eCom - Create orders`	Notification about orders from the shop, with item listing in the mail text

General subscriptions that also apply to eCom

These carry no prefix because they apply to the shop and normal operations. Known are:

Subscription type	Triggered by the shop when
`Dispatch of orders incl. Excel`	every order — adds an Excel file to the order mail
`Customer master data change`	an address change via My profile

Attention: Filtering the subscription list by "eCom" shows only the first group. The general subscriptions are excluded — along with two notifications that the shop actually triggers. Therefore, go through the list once unfiltered when setting up.

To set up a subscription:

Open Administration \ E-mail subscriptions.
Select subscription type and assign the responsible recipients.
Save.

Attention: The subscription for the failed ERP export is mandatory. Without this subscription, no one notices that a customer order did not arrive in the ERP system.

Maintaining templates

Under Basic configuration \ Settings \ Manage e-mail contents, select the template to edit via the Type field.

Relevant for eCom are:

Template type
Contact form
Order
Registration - new password
Registration - Email new
Password forgotten
Reset password
Registration of new customers
Change e-mail

Which process triggers which e-mail

This table is the tool for the question "why is no e-mail coming" or "why is the wrong text inside":

Note: The subscription Customer master data change resulted from merging two earlier subscriptions.

Process in shop	Template	Sent via	To customer	To backoffice
Not a customer yet?	Registration of new customers	Subscription eCom - Customer registration		x
Not a customer yet?, master data deviating	Registration - Email new	Subscription eCom - Customer registration		x
Not a customer yet?, master data correct	Registration - new password	Subscription eCom - Customer registration	x	x
Access manually enabled	Registration - new password	Subscription eCom - Customer registration	x	x
Password forgotten	Password forgotten	without subscription	x
Click on the link in this e-mail	Reset password	without subscription	x
Order	Order	Subscription eCom - Create orders	x	x
Contact form	Contact form	Subscription eCom - Contact form		x
Order faulty	—	Subscription eCom - Notification of failed ERP export		x
Address change in shop	no template	Subscription Customer master data change		x
Change password in shop	—	no e-mail
Change e-mail address in shop	Change e-mail	without subscription	x

Excel file for order mail

The order mail can additionally include the items as an Excel file attachment. For this, two subscriptions are necessary:

Subscription	Effect
`eCom - Create orders`	The order mail is sent at all, with item listing in the text.
`Dispatch of orders incl. Excel`	The Excel file is generated and attached.

Without the second subscription, the mail comes without Excel.

The structure of the Excel file is fixed and cannot be configured.

Dispatch of orders incl. Excel belongs to the general subscriptions without prefix — see above.

For many backoffices, the Excel is the file actually worked with. If someone reports the order mail is unusable, the missing second subscription is the first place to check.

Behaviour in the test system

In the test system, e-mails do not go to the customer, but to the eCom employee's e-mail address from Basic configuration \ Employees. This also applies to the e-mail with the visible password.

Which address customer mails go to

The recipient is always the e-mail address of the eCom user, i.e. the shop access — not the address from the customer master data. If the customer changes it in the shop via Change e-mail address, from the confirmation on all further mails go to the new address. The master data remain unaffected.

This is confirmed for Password forgotten and the Order confirmation.

In the test system, all mails go to the eCom employee's address. The text then states "The e-mail recipients were rewritten in the test system! The original e-mail recipients were: …" — this allows reading the actual recipient without needing a second mailbox.

What the order confirmation contains for the customer

In the delivery state, the mail to the customer contains only a short thank you — no items, no totals, no discount.

This can be changed on two levels:

What	Where	Who
Wording of the e-mail	Basic configuration \ Settings \ E-mail contents	Yourself
Item listing in the customer mail	Own template	Your project manager at DeDeNet

The items can thus be sent along — for this a template is stored, and this is handled by the project manager. Please contact your Contact at DeDeNet for this.

The internal notification to the backoffice, however, lists the items by default.

Subject lines differ from template names

This is shown when resetting the password:

Template	Subject of the e-mail
Password forgotten	Request - Reset password
Reset password	Confirmation - Password reset

Anyone wanting to assign an e-mail to a template based on its subject looks under a different name. For the other templates, the subject is not recorded.

5. Further Configuration

Extend menu and maintain contact reasons

Summary

Two small configurations that concern the footer and the contact form of the shop.

Create custom menu items

Via eCom \ Menu extension you create additional menu items for the shop. They appear in the second column of the footer — separately for each language.

Open eCom \ Menu extension.
Select language.
Create and fill menu item.
Save and provide data.

Typical examples from a running system are menu items like eCom user manual or Newsletter.

Maintain contact reasons

The selection list in the shop's contact form comes from a code table.

Open Basic configuration \ Code table.
Select type eCom contact reason.
Maintain the desired contact reasons.
Save and provide data.

Without maintained contact reasons, the customer has no selection in the contact form.

To ensure that enquiries reach you, the e-mail subscription eCom - contact form must also be set up.

5. Further Configuration

Activate Order template for eCom

Summary

Order templates only appear in the shop if you activate them there. This is done under Order support \ Order template in the eCom section of the respective template.

The fields of this section and their meaning are described in the service description.

Procedure

Open Order support \ Order template and select the template.
In the eCom section, set the Display:

Value	Effect
None	does not appear in the shop (default)
Start menu	appears in the product groups menu
Highlight menu	appears in the Start menu and in the Highlight menu

If necessary, set Valid from and Valid until. This controls the shop period independently of the client.
If necessary, set Prefix and Name for the display in the shop.
Save and provide data.

Why separate appointments for the shop make sense

The field force usually sees promotions a few days before the start to prepare and plan appointments. For the shop, you usually do not want this — the promotion should only appear on the start day.

This is exactly what Valid from and Valid until in the eCom section are for: they override the period of the client.

Why a separate name makes sense

If the order template has a name intended for the field force — for example with internal notes or condition information — you can override it customer-optimised for the shop via the Name field.

Only for the shop, not for the field force

The checkbox Not for field force makes the template available exclusively in the eCom system.

Limit assortment to an item list

The checkbox For the selected customers of this customer list, display only the items of the item list in the eCom system acts like a closed listing: the customers of this template may only access, search for, and order the items of the item list.

Warning: If a customer appears in multiple order templates with this checkbox, the eCom system makes a random selection of which one applies. A mixture of several item lists is not possible. Ensure that each customer appears in only one such template.

What does not arrive in the shop

No modules are available in the eCom system. Modules assigned to the order template are not displayed in the shop — regardless of which they are.

5. Further Configuration

Maintaining Client Values for eCom

Summary

Some values that control the order completion in the shop are not located in eCom, but under Basic configuration \ Clients.

The basic rule: Client values apply to all channels, that is, for both Client and Shop together — unless eCom deviates via a subsequent setting.

Two value lists are the exception and carry their own eCom flag.

The two value lists with eCom flag

Affected are Free carriage limit and Freight costs. Both lists have the columns Value, Currency and eCom.

If active, the value applies only to eCom. If not active, only to the DeDeSales Client.

Attention: The flag is a switch, not an addition. A row applies either to the Shop or to the Client, never to both. Anyone who wants to supply both channels needs two rows — one with the flag and one without. If the eCom row is missing, the Shop has no value.

Both lists include a currency. With multiple currencies, you therefore need one row per currency — and that again per channel.

Procedure

Open Basic configuration \ Clients and select the client.
Go to the value list Free carriage limit or Freight costs.
Create a row for the Client — without the eCom flag.
Create a row for the Shop — with the eCom flag.
Repeat for each currency if there are multiple currencies.
Save and provide data.

Interaction of Free carriage limit and Freight costs

Below the Free carriage limit, freight costs are calculated; above it, they are not.

The calculated freight costs appear in the Cart as a separate line — above the item you have stored under eCom \ Settings as the Freight costs Item. This setting therefore contains the Item number, not the amount.

Values without eCom flag

These fields of the client apply to all channels:

Field	Known effect
Minimum order value	Does not apply in the Shop — this general value is not read during order completion, but only used for export. For the Shop, the value in the eCom tab applies. See below.
Minimum delivery period in days	Controls the earliest possible date of delivery.
Maximum item value	Is calculated, but the message does not reach the customer — it is an enquiry, and the Shop skips enquiries. See below.
Warning at quantity	Similarly: is calculated, but the enquiry does not reach the customer. See below.
Holiday ID	Applies in the Shop. Determines the public holiday calendar for calculating the earliest possible date of delivery — one day is added for each public holiday encountered.
Minimum order value (warning)	Does not apply in the Shop — the value is not filled anywhere and would remain invisible as an enquiry anyway.
Minimum order quantity	Does not apply in the Shop — only in the sales client. See below.
Minimum order unit	The unit to which the minimum order quantity refers — for example pcs or crt. Not a numeric value. Also applies only in the Client.

The minimum order value appears twice

There are two minimum order values at the client: one general and one in the eCom tab. For the Shop, only the value in the eCom tab counts — the general one is not read during order completion.

Value	Effect in Shop
Minimum order value, eCom tab	applies
Minimum order value, general	none — only for export
Minimum order value of the debtor	only in a special case, see Order completion
Minimum order value (warning)	none

Attention: This is the most common confusion on this page. Anyone who maintains the value limit for the Shop in the general field wonders why nothing happens — and finds the error hard to detect because the value is correctly saved.

Why two fields are calculated but nothing appears

Maximum item value and Warning at quantity are actually evaluated server-side. However, their message is an enquiry — a message that someone in the sales client confirms to proceed.

In the Shop, there is no one who could do this. Therefore, the Shop always skips enquiries. This is a deliberate decision, not an error.

Field	Sales client	old Shop	new Shop
Maximum item value	applies	message was visible	invisible
Warning at quantity	applies	message was visible	invisible

The fields are therefore not non-functional — they just no longer have effect where the customer would see them. Anyone maintaining them for the Shop should know that they remain without consequences there.

Minimum order quantity: no effect in the Shop

The two fields belong together — a check only takes place if both are filled — and they can be combined with the debtor value. However, none of this reaches the Shop:

When loading the Cart, the undercutting is calculated and a notice text is generated ("The minimum order quantity has not been reached ...").
The interface through which the Cart retrieves its notices does not output this text. It is therefore lost before it reaches the Shop.
The order completion only checks the minimum order value in euros, not quantity. Therefore, an order is never blocked by this.

This is not a peculiarity of the new Shop — the gap already exists in the existing web interface and thus applied equally to the old Shop.

For the setup, this means: The two fields may be maintained, but they then only apply in the order entry of the sales client.

5. Further Configuration

Maintain Settings

Summary

Under eCom \ Settings you configure the behaviour of the shop.

Which settings exist, what values they take, and what they do is described in the specification on the page Settings at a Glance. This page only describes the procedure and the places where mistakes are commonly made.

Procedure

Open eCom \ Settings.
Change setting.
Save.
Provide data.

A change takes effect at the earliest after the next shop retrieval interval, i.e. after 15 or 30 minutes.

Settings that only take effect together with another place

This is the most common source of errors: the setting is set, but the second place is missing.

Setting	Also requires
Voucher input	a created voucher under eCom \ Voucher management
Freight costs item	Freight costs and Free carriage limit as client values with eCom flag
Apply minimum order value from debtor	delivered debtor data; otherwise the client value applies
Default language	Item texts and product group texts in the selected culture
Not a customer yet?, checkbox removed	the text block Access request – General Information under eCom \ Texts

Change shop colours via CSS

The colouring is stored as free text in the field CSS. The colours are given as CSS variables in HSL notation.

For switching to your corporate colour, usually two values are sufficient:

--primary set to your corporate colour — dark shade.
--primary-soft set to the same hue angle, but very light.

The HSL notation is hsl(hue saturation lightness). To make it lighter or darker in the same colour, you only change the last value. Variables with var(--primary) automatically take the value of the main colour.

Warning: Each colour has a -foreground colour, i.e. the text colour on it. Ensure sufficient contrast, otherwise text in the shop becomes unreadable.

The page background

Previously, the shop generated a background gradient from --primary. This could only be disabled by manually setting its two endpoints --verlauf-warm and --verlauf-kalt to the same colour.

There is now a dedicated variable. Both endpoints point to --shop-hintergrund, which in turn points to --primary-soft:

--shop-hintergrund: var(--primary-soft); --verlauf-warm: var(--shop-hintergrund); --verlauf-kalt: var(--shop-hintergrund);

Because both endpoints have the same value, in the default state no gradient is visible — the background is solid. And because the value is linked to --primary-soft, it automatically adapts to the corporate colour: Whoever changes --primary-soft gets the matching background.

Set a different background. Now only one line is needed instead of two:

:root { --shop-hintergrund: hsl(0 0% 100%); }

Want a gradient. Set --verlauf-warm and --verlauf-kalt individually to two different colours and leave --shop-hintergrund untouched.

Note on colour choice: A strong main colour appears much stronger over large areas than on a button. Because the background is linked to --primary-soft — the light shade — this is less noticeable than before. Still, check the result on the finished shop before fixing the colour.

The default state and a counterexample

The shop is delivered in orange. Next to it is a blue palette as an example for a change — both are based on one hue angle:

Variable	Orange (default)	Blue (example)
`--primary`	`hsl(27 87% 49%)`	`hsl(215 100% 25%)`
`--primary-soft`	`hsl(27 87% 94%)`	`hsl(215 100% 94%)`
`--secondary`	`hsl(36 82% 50%)`	`hsl(211 100% 40%)`
`--accent`	like `--primary`	like `--primary`
`--ring`	like `--primary`	like `--primary`
`--shop-hintergrund`	`var(--primary-soft)`	freely selectable
`--verlauf-warm`, `--verlauf-kalt`	both `var(--shop-hintergrund)`	both `hsl(0 0% 100%)` — white, so no visible gradient

From --primary to --primary-soft the hue and saturation remain the same; only the lightness jumps — for orange from 49 to 94 per cent, for blue from 25 to 94. This is exactly how the notation is intended: one colour, two lightness levels.

--secondary differs slightly in both cases — a few degrees in hue and a lighter level. This is enough to set off secondary elements without introducing a second colour.

Note: --accent and --ring take the main colour. If you do not explicitly want them different, you do not have to set them. In practice, there are thus three values: --primary, --primary-soft and --secondary.

The complete list of variables is in the specification.