PrestaShop Multistore is suitable when several storefronts need to be managed in one structured environment. The main task is deciding which settings, products, customers, prices, taxes, checkout rules, and reports should be shared and which should remain separate.
Set up the structure before adding products or connecting domains. A clear separation between shared and independent data helps prevent products, prices, and orders from appearing in the wrong storefront.
Table of Contents
Plan the store structure first
List every storefront and record its purpose, target market, language, currency, domain, product range, and responsible users. Use this list to decide whether each store belongs to the same shop group or needs independent settings.
A shared setup is useful when stores use the same product base, administration process, and operational rules. An independent setup is safer when stores require different product structures, separate permissions, or rules that must not affect other storefronts.
| Area | Shared approach | Independent approach |
|---|---|---|
| Catalog | Use the same product base where products and stock information are managed together. | Maintain separate product selections when each storefront needs its own range. |
| Prices | Use common pricing rules when the stores sell under the same commercial model. | Keep pricing separate when markets use different price structures. |
| Customers | Share customer access only when customers should be recognised across the stores. | Keep customer data separate when each store has its own audience or administration. |
| Permissions | Use common administration only for users who need access to all stores. | Limit access when a user should manage only one storefront. |
Create shop groups and storefronts
- Create the shop groups. Group storefronts according to the settings and data they should share.
- Add each storefront. Give every store a clear name that identifies its market, brand, or purpose.
- Choose the sharing model. Decide which catalog, customer, price, and configuration data belongs to the group and which belongs to an individual store.
- Set access permissions. Assign each administrator only the stores and functions needed for their work.
- Save the structure before importing or creating products. This reduces the risk of attaching products or settings to the wrong storefront.
PrestaShop stores can be adapted for different countries through languages, currencies, localization settings, and geolocation rules. These settings affect how international customers see and use the store, so review them for each storefront before launch. Read more about languages, currencies, and localization in PrestaShop.
Map domains to the correct storefront
Prepare a domain record for every storefront before launch. The record should identify the domain, the intended store, the language, the currency, and the shop group. This makes it easier to detect a domain that opens the wrong storefront.
- Enter the domain for the intended storefront. Keep the domain assignment aligned with the store name and market.
- Check the domain connection. Open the domain and confirm that it displays the expected storefront.
- Test each additional domain separately. Do not assume that a working domain proves that every store is mapped correctly.
- Check the customer journey. Confirm that links, language selection, currency display, cart contents, and checkout remain within the intended store.
Manage products in the correct catalog
Before adding products, confirm whether the catalog is shared or store-specific. Product assignment should follow the structure created for the shop groups. A product that is intended for one storefront should not be made available in every store by default.
To add a product in PrestaShop, open the left-hand menu, select Sales, then Catalog, followed by Products. See the product creation path in PrestaShop.
After creating or importing products, review each store separately. Check the product name, description, images, price, availability, category, and visibility. Repeat the check for products that are shared across stores, because shared data can affect more than one storefront.
Review modules and configuration changes
PrestaShop uses modules to extend store functionality. Modules may come from different developers, so changes to modules should be tested within the relevant storefronts and shop groups. Conflicts can affect store behaviour, which makes a post-change check important. Learn about managing modules and resolving conflicts in PrestaShop.
Record which modules are active for each store and whether their settings are shared or independent. Test payment, delivery, product display, customer accounts, and checkout after changing a module.
Validate every storefront before launch
- Products: Confirm that each store shows the intended catalog, categories, prices, and availability.
- Customers: Test registration, sign-in, account details, and the intended level of customer sharing.
- Taxes: Check that the tax result matches the store’s country and localization settings.
- Checkout: Add a product to the cart, complete the checkout flow, and verify that the order belongs to the correct storefront.
- Domains: Open every domain and confirm that it loads the correct store, language, currency, catalog, and branding.
- Analytics: Verify that visits, carts, and orders can be identified by the correct storefront.
- Permissions: Sign in with each user role and confirm that access matches the assigned stores.
When separate installations are safer
Choose separate installations when the storefronts need fully independent administration, catalogs, customers, configuration, or module changes. This approach creates a stronger boundary between stores, but it also means that updates and administration must be handled separately.
Use Multistore when the stores benefit from a common structure and controlled sharing. Use separate installations when isolation is more important than central management.