Settings
The ecommerce settings page contains global settings used on the ecommerce site. This means that any change in the settings page will affect all content on the site, so be careful.
The ecommerce settings page contains global settings used on the ecommerce site. This means that any change in the settings page will affect all content on the site, so be careful.
Enables or disables the webshop on the site. Use if there is a need to shut down all functionality.
Product images are served from the storm cdn, checking this box rewrites the image urls to that they would appear to be coming from the hth site.
This is a .NET format string used to format prices on the site. Talk to a developer before changing this.
This is the name of the currency that is displayed on the site.
The number of items that will be loaded when the user clicks on the "load more" button on a product listing page.
The number of items per row that are displayed on the product list page.
The fallback image is used as a replacement when a product image can not be found.
The % of the image that should be used for white padding. The idea is to give the product images a more "airy" feel by adding padding on them.
The main ecom page, usually called shop.
When a product is unable to find a matching category in episerver the url to the product will point to the fallback category.
This is the product template used on the site. If no product template is found below a product listing page this is the one that will be used.
This should point to the page that will be opened in a modal when the user clicks on a "add to cart" button.
Should point to the first step in the checkout. If we would ever create a new checkout flow this property would need to be edited to point to the new startpage.
When the user as completed the payment procedure and is redirected back to the site, this is the page he or she will be redirected to.
Not used
The modal page that is displayed when a user wants to select a store.
The modal page that is displayed when a user has a cart conflict on the cart page.
The page that contain the terms and conditions for the site. Ths link to this page is displayed on the last step in the checkout flow.
More info needed.
The pages and their children are used in the routing of the product urls. This means that if a product category is found in any of thees pages (and children) the url will point to the correct category. The idea is that a product should only have one home, so if one would create a "christmas special" category the product would still be located on the main category, and no under the /christmas-special/productname. The reason for this is that google does not like duplicate content, and that bookmarks made to products below temporary cartegories would quickly become obsolete.
Contains a list of blocks that holds the settings for individual delivery methods.
Contains a list of the available badges on the site. To create a badge - create an e-commerce badge block and add the image and the badge id. Talk to a developer to find out how badge ids are set.
The support email for the ecom site.
The support phone number for the ecom site.
Should point to the page that contain information for the available variants modal that is displayed on the product page when a user triggers the modal.
This email template will be used when a user as completed an order and is sent an email.
This email template will be used when a user as completed an order and is sent an email.
Used in tracking with google analytics. Talk to a developer before changing this.
The account id for the livechat functionality
More info needed
More info needed
More info needed
More info needed
More info needed