# 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 1. Open *Basic configuration \\ Clients* and select the client. 2. Go to the value list **Free carriage limit** or **Freight costs**. 3. Create a row for the Client — **without** the eCom flag. 4. Create a row for the Shop — **with** the eCom flag. 5. Repeat for each currency if there are multiple currencies. 6. 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](https://wiki.dedesales.de/books/leistungsbeschreibung-ecom/page/bestellabschluss)
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.