NexGen Parent Stores
Stores in a NexGen group which point to a common parent stores will run a common marketing of managed products across those stores. This provides a level of marketing control over many store home page shared layouts and banner groups while having local branding of the logo and theme colors.
NexGen Shared Responsibility Model
To understand what NexGen tools provide and what functionality must be carried out store by store, refer to this table which is grouped by Products, Marketing, Design, Customers, and Transactions.
Marketing
Feature | NexGen Group Feature | How To |
Banners and Sliders shared from a parent store | 👍 Yes, a NexGen feature. Create banners and sliders and push them to Child stores through inherited layouts. This includes support for rules that specifies a list of stores as an inclusion or exclusion list. | Where a child store has a layout inherited from the parent, banners can be shown as static or a slider. The banners loaded and managed in the parent store have the same URL links using products in managed catalogs or parent static pages. This includes support for rules that enable item banners for specific brands, keyword search, or categories. |
Item Merchandising shared from a parent store | 👍 Yes, a NexGen feature. Create Item Merchandising groups in a parent store and push them to Child stores through inherited layouts. This includes support for rules that specifies a list of stores as an inclusion or exclusion list. | Products in an item merchandising group must be in a managed catalog which is enabled for the child store and in a valid container. This includes support for rules that enable item banners for specific brands, keyword search, or categories |
Content Pages shared from a parent store | 👍 Yes, a NexGen feature. A content page can be created on the parent and made available in child stores. | On creating a content page on the parent store you can set rules to enable the page on all stores minus exceptions or only on specifically listed stores. |
Brand merchandising shared from a parent store | 👍 Yes, a NexGen feature. A brand can be created for use on brand merchandising widget on the parent store and made available in child stores. | Brands added to the parent store can be shown in child stores using the brand merchandising widgets. This includes support for rules that enable item banners for specific brands, keyword search, or categories |
Design
One parent store is set for each child store and some feature in a child store can inherit from the parent store.
Feature | NexGen Group Feature | How To |
Inherit a storefront theme from a parent store. | 👍 Yes, a NexGen feature. A child store can inherit a theme from it's parent store. | Then the child store can be set to use the parent store theme within the child store setting. This is done during the setup of your child store. |
Page Layouts (Layout Settings) | 👍 Yes, a NexGen feature. A child store can use the parent store layouts for all or some pages. | Then the child store can be set to use the parent store page layouts using the child store layout setting. If an exception is needed it can be configured so that a page on the child store uses a custom layout while other layouts are still inherited form the parent. |
Inherit or Override theme Colors and Fonts on a child store | 👍 Yes, a NexGen feature. | Use theme options to override and change them on the child store. |
Inherit, Add, or Override theme CSS on the child store | 👍 Yes, a NexGen feature.
| You can set a child store to override or add CSS to what is supplied by the parent store. |
Inherit, Add, or Override head and footer HTML elements on the child store | 👍 Yes, a NexGen feature. | You can set a child store to override or add content to the <head> and <footer> element supplied by the parent store. |
Products
Product strategy for NexGen group stores should be to use an existing managed catalog and set it up on each store so that you can consistently market the products across the group of stores.
Feature | NexGen Group Feature | How To |
Managed Product Catalog shared to child stores | Not a NexGen feature. There is a large range of existing suppliers with managed catalogs available to EvolutionX stores. If you need a custom managed catalog then discuss this with the EvolutionX team. | To enable an supplier's existing managed catalog, so so in each child catalog by enabling the catalog and adding it to the catalog containers. |
Own Products | Not a NexGen feature. Own products can be added by exception for each child store as required. They are not shared or managed between stores in a group and are not accessible from a parent store. If there are own products that need to be shared from a parent store to child stores then this requires a managed catalog, which you can discuss with our team. |
|
Customers
Customer accounts and users are only managed on the child store and there is no NexGen features. A common solution is to use an ERP App Store or API integration.
Feature | NexGen Group Feature | How To |
Accounts and Users | Not a NexGen feature. | Customer Accounts and users are managed in a child store only. A common implementation is to use an ERP App Store or API integration. |
Pricing | Not a NexGen feature. | Use live pricing configured for each child store to determine pricing of products for customers. |
Transactions
Transactions, such as orders and invoice payments, are only managed on the child store and there is no NexGen features. A common solution is to use an ERP App Store or API integration.