Minimum and maximum order quantity
As a rule, you maintain both limits per product. They then apply equally to every buyer. In addition, the limits can be set per buyer and per sub-shop based on the customer number. Here, the meaning of the upper limit changes fundamentally: it then no longer refers to the individual order, but to all of the buyer’s orders together. Whether they use up their quota in one or in twenty orders does not matter. WEBSALE V8s subtracts the purchased quantity from the remaining maximum quantity with every purchase. Reference: Section OrderConditionsEnabling customer-specific order quantities
The customer-specific variant is off by default. Enable it in the shop configurationshop.config in the <Login> section.
yes activates the function. Any other value and a missing parameter leave it off.
Using the MaxUserOrderQuantitySubshop parameter, which is also located there, you specify which sub-shop the quantities refer to.
Reference: Section Login
With dependent variants
Quotas are kept per product number. With dependent variants, you must therefore do two things:- assign a separate product number to each dependent variant
- set the minimum or maximum order quantity of the buyer for each dependent variant
Assignment via an import file
The quantities per buyer and product can be passed to the WSPManager via an import file. You will receive the format from WEBSALE AG. Guide: Minimum order value and small quantity surchargeLot size
With a lot size, the shop only accepts order quantities that are an integer multiple of the specified lot size. It is maintained per product in the WSPManager. The benefit lies in the price display. The following example shows both paths for the same offer: a case of wine with twelve bottles at 98.40 EUR.
With a lot size the buyer can only order 12, 24, 36, 48 and so on, but sees the more attractive unit price.
The quantity field is pre-filled from the outset with the smallest permitted quantity, in the example therefore with 12. If the buyer nevertheless enters an unsuitable quantity, the shop displays a message.
Setting the text for the message
You set the text in theshop.config in the <NotifyMessages-Txt> section behind the parameter ProductUnitFactor.
Outputting the lot size in the template
Two tags belong together and are easily confused.Without a maintained lot size, the shop does not check anything, and every quantity is then permitted. For products with dependent variants, the check only takes effect if a quantity interpolation is set for the variant.
Customer-specific lot size
Instead of one lot size for everyone, here you assign different lot sizes to different buyer groups. Buyer and product are connected via a freely chosen ID.If a general lot size is already set on the product, it is overwritten for the buyer in question by the customer-specific one. For all other buyers, the general one continues to apply.
Step 1: Enter the ID in the customer data
Enter an ID in the customer data of the buyers in question. All buyers with the same ID will later receive the same lot size. The ID is compared without regard to upper and lower case. The field and the transfer format are given in the interfaces documentation at doku.websale.de/schnittstellen.Step 2: Enter the lot sizes in the product data
Enter the desired lot sizes for the products in question and link each one via the ID to a buyer group. Multiple lot sizes for different groups are possible per product. The setting only takes effect when both sides are maintained. If the ID is missing on the buyer or the group on the product, the general lot size applies. You will also find the format for this in the interfaces documentation at doku.websale.de/schnittstellen.Step 3: Extending the templates (optional)
On the product detail viewws_product.htm, you use this to output a hint about the individual lot size. The second block shows the stored groups as raw data and is only intended for testing.
<g><1>GroupID</1><2>Menge</2></g>, one block per group.
On the shopping cart page ws_basket.htm, the corresponding tags are available with the BASKET- prefix.
Step 4: Set the message for the ordering process
A buyer can place a product in the shopping cart and only log in afterwards. Only with the login does the shop know their lot size, and the already chosen quantity may then no longer match. The order can then not be completed. For this case, set theUserUnitFactorError parameter in the shop.config in the <NotifyMessages-Txt> section.