Shops are essential for an Ecommerce solution - all products and product groups are located in shops.

Different shops may serve as virtual storefronts, allowing you to differentiate your customers’ shopping experience, e.g. for different countries, or to create separate B2B and B2C shops.

Your shop(s) appear in the Ecommerce tree under the Product Catalog node (Figure 1.1).

Figure 1.1 Shops

In order to have multiple shops on the same solution, you need to have the Multiple Shops app installed on your solution. If you are interested in this app, please contact your Dynamicweb partner.

To create a new shop:

  • Go to Settings > Ecommerce > Product catalog > Shops
  • Click New shop in the toolbar (Figure 2.1)
Figure 2.1 Creating a shop

To edit a shop simply click it in the shops overview.

From the edit page you can delete a shop by clicking Delete shop in the toolbar (Figure 2.2).

When deleting a shop, all groups, subgroups and products in the shop will be deleted. This is non-reversible. Don’t do it, unless you are certain that this is what you want.

Figure 2.2 To delete a shop, click the delete shop button

Both creating or editing a shop will open the shop settings, which are described in the next section.

The basic shop settings provide you with the ability to set up a shop at the most basic level (Figure 3.1).

Figure 3.1 The basic shop settings

With the basic shop settings you can:

  • Provide a name for the shop and optionally select an icon for the Ecommerce tree
  • Mark this shop as your default shop
  • Select an order flow to use for orders from this shop.
  • Select a default stock state, which will be used for all products in the shop if none is set in product edit or category edit
  • Select a default cart for the shop. This cart will be used if no cart is set on the Shopping Cart paragraph settings.
  • Select a default print template. This is used when printing orders. Your template file must be within the \Templates\Ecom7\Order folder.

Greyed out settings fields

The Id field is greyed out because you cannot edit it. Once a shop is set up, it will be provided with an ID, which is a unique identifier used e.g. when integrating Dynamicweb eCommerce with third party solutions.

Likewise, you can see (but not edit) when a shop was created.

If you have PIM installed, you can use the PIM settings (Figure 4.1).

Figure 4.1 The PIM settings

If you check the Use as PIM Product Warehouse checkbox, you will be able to integrate the shop and its products when working with PIM.

In Dynamicweb Ecommerce, you can control which languages you want to use in your shop – when creating and editing your products, product groups, and so forth.

Figure 5.2 The shop language settings

With the shop language settings, you can:

  • Select the languages you want to have available when editing or creating products, product groups, etc. in the shop. 
  • Set a default language from the languages you have made available below. The default language will be used if no Ecommerce language has been selected in the website settings using the shop.

The language settings let you limit the number of languages your editors can localize products to. This can be very useful if you run shops in many countries, and have many Ecommerce languages on the solution. 

With the stock location settings (Figure 6.1), you can select which stock locations you want to make available when you manage stock on products.

Figure 6.1 The shop stock location settings

Stock locations are created under Settings > Ecommerce > Product Catalog > Stock locations.

With the order notification settings, you can select backend users who should receive notifications about new orders are placed in this shop.

Move the users from the right window to the left window to notify them when new orders are palced.

Figure 7.1 The shop order notification settings

To send order notifications to your customers, see order flows.

Image patterns - or alternative images - are a way for you to automatically match images in a folder with the products in a shop.

This is done by defining a pattern - for instance /{ProductNumber_Small.jpg} - and a folder, where you can then place product images named according to the pattern.

To set up an image pattern at the shop level:

  • Check the Use alt. images checkbox (Figure 8.1)
  • Select a folder to look in
  • Define one or more patterns to use by clicking "Click here to add new row"
Figure 8.1 Alternative images settings

You can specify a pattern based on the following product fields:





















VariantOptionLevel {VariantOptionLevel1}.jpg

Retrieves the name of the variant option added to the product.

If you e.g have colors as 1. level variants (Orange, Green, Blue) they are OptionLevel1.

If you also have sizes as variants (Large, Medium, Small, they are OptionLevel2.

You can combine these fields in any way you’d like, e.g. {ProductNumber}_{ProductManufacturer}.jpg{ProductNumber}_{VariantComboName}.jpg or {ProductID}_{ProductName}.jpg, and image patterns support using the wildcard characters ‘?’ and ‘*’.

If more than one image matches the pattern, the first one in alphabetical order will be used.

You can read about the image pattern hierarchy in this article.

With the order line fields settings (Figure 9.1), you can select which order line fields to use on this shop.

Read more about order line fields here.

Figure 9.1 Order line fields settings

Under the Indexing settings (Figure 10.1), you can control the build of the index for your products.

Figure 10.1 The indexing settings

Here, you can check the checkbox to auto-build your index for the shop's product, when any product are updated. Choose which index to auto-build beneath.


These are the database tables associated with shops and related features in the Dynamicweb database:


Contains setup data for shops as defined in Settings -> Ecom -> Product catalog -> Shops

Field name Data type Length
ShopId nvarchar 255
ShopName nvarchar 255
ShopCreated datetime 8
ShopDefault bit 1
ShopIcon nvarchar 255
ShopOrderFlowId int 4
ShopStockStateId nvarchar 255
ShopOrderContextId nvarchar 50
ShopAutoId int 4
ShopStockLocationID bigint 8
ShopUseAlternativeImages bit 1
ShopImageFolder nvarchar 255
ShopImagePatternSmall nvarchar 255
ShopImagePatternMedium nvarchar 255
ShopImagePatternLarge nvarchar 255
ShopAlternativeImagePatterns nvarchar Max
ShopDefaultPrintTemplate nvarchar Max
ShopProductWarehouse bit 1
ShopProductPrimaryPageId int 4
ShopAutoBuildIndex bit 1
ShopIndexRepository nvarchar 128
ShopIndexName nvarchar 128
ShopImageSearchInSubFolders bit 1
ShopImageUploadFolder nvarchar 255
ShopAutoCreateUploadFolderPerProduct bit 1
ShopType int 4


Keeps track of group (EcomShopGroupRelationGroupId) membership of shops (EcomShopGroupRelationShopId).

Field name Data type Length
ShopGroupShopId nvarchar 255
ShopGroupGroupId nvarchar 255
ShopGroupRelationsSorting int 4
ShopGroupRelationAutoId int 4


Keeps track of which languages (LanguageId) a shop (ShopId) is active for.

Field name Data type Length
ShopId nvarchar 255
LanguageId nvarchar 50
Id int 4
IsDefault bit 1


Contains setup data for shop notification emails as defined in Settings -> Ecom -> Product catalog -> Shops.

Field name Data type Length
ShopOrderNotificationShopId nvarchar 255
ShopOrderNotificationAccessUserId int 4
ShopOrderNotificationRelationAutoId int 4


Keeps track of which stock locations (ShopRelationStockLocationId) are available for a shop (ShopRelationShopId).

Field name Data type Length
ShopRelationStockLocationId int 4
ShopRelationShopId nvarchar 255
ShopStockLocationRelationAutoId int 4