Ecommerce - Advanced Configuration
In this article, you will have an overview of the settings available under Settings > Ecommerce > Advanced configuration.
You can find settings regarding fields, images, product catalog, and more.
Some settings are described elsewhere such as:
The other settings are described below.
For more information about the settings in the Settings > Ecommerce area, see this other article.
In the General settings, you will find misc. settings regarding the shopping cart, product navigation, additional fields, and more.
Under Settings (Figure 3.1) you can define cart and product behavior:
- Specify how many days the cart is saved for if not fully completed
- Specify for how many minutes the products in cart are reserved for ( > 0) - see more below
- Specify when a product is reserved
- Reserve at checkout step
- Reserve when product is added to cart
- Set the default weight and volume units
- Allow different context dates to change the OrderTime context (read more here)
- Allow combine products as family (read more about this function here)
With product reservation a product which is added to the cart becomes unavailable to other customers for a time.
To use product reservation, you need to:
- Toggle Only show products - That are in stock on this page
- Toggle A check for stock status in the shopping cart app settings - this makes it possible to show notify customers during checkout if the product is out of stock (incl. reserved).
As described above you must also specify how long and at what point the product should be reserved for.
Allow different context dates
Occasionally, you may need to change the Context.OrderTime parameter of an order - e.g. if you want to test whether price calculations, discounts, or product publication periods work as intended.
To do so, simply use the OrderTime parameter in your query string, using one of the following formats:
The Allow different context dates checkbox must be checked.
The Indexing settings (Figure 4.1) allows you to control the default behavior of schema extenders for new indexing. Currently these settings only apply to the ProductIndexSchemaExtender.
The following settings are available:
- 'Do not store default fields' - if checked, fields are not stored by default
- 'Do not analyze default fields' - if checked, fields are not analyzed by default
You can read more about stored and analyzed here.
Under Navigation (Figure 5.1), you control settings for navigating through your products. You can:
- Choose to apply eCommerce navigation ONLY if the page is showed in the path
- Show the product count next to each group name
- Specify start- and endlevel to the navigation
- Discard all existing navigation providers and only use custom navigation provider (this checkbox only appears on solutions where custom providers are present)
- Specify the maximum number of products in each group
- Specify for how long (in minutes) products should be saved in the cache
By default, unlocalized product catalog content – products, product groups and related products – is not shown in the frontend, but you can change that by force-showing unlocalized content. With the Language settings (Figure 6.1), you can:
- Uncheck the "only show translated groups" checkbox to force-show unlocalized groups, products and related products
- Check the "Activate products on all language version on create" to create a version of the newly created product on all language versions (read more about what this setting does in this article)
You can read more about localizing content here.
Only show products & Only show variants
With the Only show settings (Figure 7.1), you can control how products and variants are displayed across all your product catalog apps by setting up requirements for showing products in frontend:
- If the product is in stock
- If the product has a price
- If the product is active
Please note that if you are publishing a query, most of these settings can be replaced by expressions on the query.
Special for products:
If the product is inactive, you can also choose a custom page to show instead (Figure 7.1).
Special for variants:
You can also choose to show the default variants in the product list instead of the main product by checking Show default variant in product list.
Product - Group display cache
Under Product - Group display cache (Figure 8.1), you can choose to cache product group displays in the server memory. This will result in a faster browsing of products.
You must then specify how many minutes the products should be cached in the server memory.
With the Fee calculation settings (Figure 9.1), you can choose to calculate your shipping/payment fees based on the delivery country, and not the billing country.
Under Additional fields (Figure 10.1) you can:
- Enable Bulk edit for (simple/extended) variants to edit multiple variants at once
- Check Show Back Catalog checkboxes on products to enable three performance-related fields on all products.
The back catalog fields are:
- Exclude from index
- Exclude from customized URLs
- Exclude from "All products"
These fields are primarily of interest on solutions with more than 250.000 products, if a large part of those products form a back catalog which should not be included in the list of active products.
Taxes in backend
Under Taxes in backend (Figure 11.1), you can consolidate taxes for orders to make the order details less confusing. You can:
- Show the total tax for each product in the order
- Show the total tax for the entire order
Read more about orders and consolidating taxes in this article.
With the Power pack settings (Figure 12.1), you can set a minimum number of views a product should have to appear on a "Customer who saw this also saw this"-list.
Edit and delete permissions
With the Edit and delete permissions settings (Figure 13.1), you can:
- Allow all backend users to edit orders
- Allow edit order price to exceed original order price
For security reasons you cannot capture more than the amount the order was created and authorized with by the payment provider
- Disallow backend users from deleting orders
- Disallow non-administrators from deleting shops, groups and products
You can read more about editing orders in this article.
The Integration settings (Figure 14.1) are useful if you integrate with an ERP system e.g. NAV or AX. With the settings, you can limit the available actions from the Dynamicweb backend, to ensure that the ERP system has full control over your product catalog:
- Disable the creation of products, product groups and variants from backend
- Enable group ID editing for integrational purposes (this is not recommended though)
You can read more about integration in this article.
You can control product field behavior by going to Settings > Ecommerce > Advanced configuration > Fields and modifying the field settings (Figure 15.1).
- Allow differentiation of fields across all languages – read more about languages here
- Allow differentiation of fields across all variants – read more about variants here
- Make fields required, read only, or hidden (for non admin-users - admins and administrators will continue to have access to all fields).
- Required fields will be validated when saving a product in either details or bulk edit mode, and if no values is entered in the field, the product cannot be saved.
If you have created any product categories they will appear below the standard product fields, and can be modified in the same manner.
Below the Language and variant differentiation section, you can also modify the field settings for your shops (Figure 15.2).
By default, admins and administrators can see and edit all fields - also if the field is marked as Read only or Hidden in the field settings.
However, if you check the fields in the Settings section at the bottom (Settings > Ecommerce > Advanced configuration > Fields), you can:
- Make the Read only state apply for admins/administrators too
- Make the Hidden state apply for admins/administrators too
- Allow editing of the system ID when creating new products
With the Images settings (Figure 16.1), you can select default images for products and product groups and define image patterns to render images in frontend. You can also setup the Autoscale tool.
- Choose a small, medium, and large default image for products
- Choose a small, medium, and large default image for product groups
- Define an image pattern to render the images in frontend
Below, is the settings for the Autoscale tool (Figure 16.2).
The Autoscale tool enables automatic resizing of images in frontend. Autoscaling ensures that product images are always displayed in sizes you can configure, preventing your design from breaking due to different image sizes.
- Specify a width and height for your small, medium and large image sizes
- Activate the sizes you want to work with on your solution.
If the scaling parameters are larger than the original picture size, then the image will not be resized. An image placeholder will still be rendered displaying the excess pixels, but Dynamicweb will not upscale images, since that looks just awful.
You can read more about autoscaling in this article.
The Shopping Cart settings (Figure 17.1) lets you control the Shopping Cart app's behaivour.
- Enable recalculation of prices on login (products added to an anonymous cart do not have their prices recalculated on login by default)
- Omit the payment and shipping information steps from the order process, provided that you have only created one of each in the backend
- Omit the payment step from the order process if your order total amount is 0 or less
You must also check 'Allow negative total order prices' in Settings > Ecommerce > Advanced > Prices (read about the setting here)
- Enable the built-in order step validation procedure (read more about order step validation in this article)
- Prevent field validation from triggering when a user goes backwards in the order flow
- Group discounts and taxes so they are displayed right after their parent order line in the shopping cart
- Force a new cart on each browser, even if the same user is logged in - Not recommended
- Force reorders from the Customer Center app to be recalculated when placed - this is default behavior on all new installations
- Disable deletion of the cart (order object) if it has no orderlines - normally, a cart with 0 order lines is deleted automatically
This is primarily useful if you are manipulating quotes locally or on an external system, as quotes need to be returned with the correct ID, and this is not possible if the empty cart is deleted before being enriched externally
The Extranet option lets you toggle keep anonymous cart when user logs in - which will merge the contents of an anonymous cart with the cart saved on the user (if any).
If you are using the saved for later list for products removed from cart, the Saved for later setting allow you to specify for how long a product should be on that list.
The order discount settings (Figure 18.1) control advanced behavior related to discounts:
The following settings are available:
- Choose discount behavior controls how discount are applied:
- Aggregated allows discounts to stack (default behavior)
- Highest forces the system to apply the highest value discount
- Lowest forces the system to apply the lowest value discount
- Only use order discounts disables discounts (old) on the solution
- Apply discounts before taxes forces the system to apply discounts based on prices before taxes
- Round orderline discount per quantity forces discount calculations to use rounded numbers
- Add orderline discount per quantity forces the system to list each product discount as a separate order line
Read more about discounts in this article.
An older implementation of discounts called Sales Discounts may be present on some solutions. Don’t use it – it’s been replaced by Order Discounts. If you are already using Sales Discounts, don’t use Order Discounts, as the combined results may be unpredictable and are untested.
We recommend switching your older solutions to Order Discounts instead.
In the Sales discounts settings (Figure 19.2), you can:
- Choose to differentiate on VAT groups
- Select a discount behaivour
- Aggregated allows discounts to stack
- Highest makes the system use the discount with the highest value
- Lowest makes the system use the discount with the lowest value
- Enable inclusion of product discounts
In the Loyalty points settings (Figure 20.1), you can set an expiration period for rewarded loyalty points.
You can also check Disallow rewarding points from products purchased with lotalty points to keep loyalty point transactions from triggering new loyalty point awards.
Read more about loyalty points in this article.
Per default, the expiry date for gift cards is 24 months ahead of the time of purchase, as per Danish law, but if you do business in other countries you can change it to suit your needs.
In the Gift cards settings (Figure 21.1), you can enter a new expiration value in months.
The expiry date is defined as the purchase date + the number of months defined in this field. The expiry date is calculated once - upon creation of the gift card.
You can read more about gift cards in this article.
Dynamicweb auto-numbers every order registered in the system – ORDER1, then ORDER2, etc.
However, you can customize the way orders are assigned a number with pre/postfixes and different numbering:
Go to Settings > Ecommerce > Advanced configuration > Auto-numbering (Figure 22.1)
Click any of the auto-numbering schemes (e.g. "ORDER") to open the edit view (Figure 22.2)
From here, you can change:
- The order prefix (ORDER by default)
- The order postfix (empty by default)
- The increment by which an order value should increase when a new order number is generated
You can read more about orders here.