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.

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 determine things about the cart and products:

  • How many days the a shopping cart should be saved
  • Whether the products are reserved when added to the cart (and for how long (minutes) they are reserved for) or when proceeding to checkout. You need to set minutes to > 0 in order to enable reservation.
    Read more about product reservation in this article.
  • Set the default weight and volume units for new products
  • Allow different context dates to change the OrderTime context (read more here)
  • Combine products as family (read more about this function here)
Figure 3.1 The Settings settings

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.

Figure 4.1 Controlling the behavior of schema extenders

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 prodiders and only use custom navigation provider
  • Specify the maximum number of products in each group
  • Specify for how long (in minutes) products should be saved in the cache
Figure 5.1 The Navigation settings

By default, unlocalized product catalog content – productsproduct 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.

Figure 6.1 The Language settings

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).

Figure 7.1 The Only show products settings

Special for variants:

You can also choose to show the default variants in the product list instead of the main producby checking Show default variant in product list.

Figure 7.2 The Only show variants settings

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.

Figure 8.1 The Product - Group display cache settings

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.

Figure 9.1 The Fee calculation settings

You can read more about payment here, and more about shipping here.

Under Additional fields (Figure 10.1), you can:

  • Enable Bulk edit for (simple/extended) variants to edit multiple variants at once
  • Show Back Catalog checkboxes on products to boost performance by excluding products from different processes
    You can read more about Back Catalog fields in this article
Figure 10.1 The Additional fields settings

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.

Figure 11.1 The Taxes in backend settings

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.

Figure 12.1 The Power pack settings

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
Figure 13.1 The Edit and delete permissions settings

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)
Figure 14.1 The Integration settings

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).

Figure 15.1 The Fields settings

You can:

  • Allow differentiation of fields across all languagesread more about languages here
  • Allow differentiation of fields across all variantsread 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).

Figure 15.2 The Fields settings for your shops

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
Figure 15.3 The Settings section for Fields

In Settings > Ecommerce > Advanced configuration > Prices (Figure 16.1), you can control the VAT behaviour on your solution.

Read about the settings and VAT here.

Figure 16.1 The Prices settings

With the Images settings (Figure 17.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.

Figure 17.1 The Images settings

You can:

  • 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

You can read more about image patterns on shops here, and more about image patterns on Product Catalogs here.

Below, is the settings for the Autoscale tool (Figure 17.2).

Figure 17.2 The Autoscale settings for Images

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.

You must:

  • 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.

Image & Image pattern hierarchy

Consider using image patterns to work with product images, as they provide you with more flexibility and less manual labor. An image pattern checks a specified folder and assigns a product picture to the product based on a pattern you provide.

Image patterns can be configured in several places on a solution, with the more specific image or pattern being used:

For PIM, the backend uses the pattern defined on the PIM Warehouse – and the preview function uses the pattern on the product catalog used to preview products, or if not defined the pattern on the shop associated with the product catalog, etc.

The Shopping Cart settings (Figure 19.1) lets you control the Shopping Cart app's behaivour.

Figure 19.1 The Shopping Cart settings

You can:

  • 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.

With the Order discounts settings (Figure 21.1), you can control how/if discounts stack. To do so, you must choose the discount behaviour:

  • 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

You can also check Only use order discounts to disable all other types of discounts on the solution.

You can check Apply discount before taxes to apply order discounts based on the order total without taxes included.

Read more about order discounts in this article.

Figure 20.1 The order discounts settings

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 21.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
Figure 21.2 The Sales discounts settings

In the Loyalty points settings (Figure 22.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.

Figure 22.1 The Loyalty points settings

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 23.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.

Figure 23.1 The Gift cards settings

With the Assortments settings, you can enable assortments.

Assortments are flexible ways of showing certain shops, product groups or products to selected users or user groups only.

Read more about assorments and the settings in this article.

With the Rounding settings, you can customize the final price on products to look more intriguing (have all prices on the same form e.g. $59.99 and $139.99).

Rounding rules can combat weird prices after the addition of e.g. exchange rates, taxes, and VAT rates.

In the overview (Figure 25.1), you can create new rounding rules by clicking New rounding. Read more about setting up rounding rules and applying them to currencies here.

Figure 25.1 The Rounding settings

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 26.1)

Figure 26.1 The Auto-numbering settings

Click any of the auto-numbering schemes (e.g. "ORDER") to open the edit view (Figure 26.2)

 

Figure 26.2 Editing an auto-numbering

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.