PrestaShop Multistore allows you to manage multiple online shops from a single admin panel, whilst maintaining separate configurations and product ranges. It is a built-in feature that is useful when you want to coordinate multiple brands, markets or sales channels with a centralised management.
The benefit is clear: you work on the same system, without having to switch back and forth between separate departments all the time. However, the setup requires careful attention, particularly when sharing customers, quantities and orders.
To work out whether this solution is right for your business, start by considering what all shops have in common.
How PrestaShop Multistore works
The multistore feature adds a management structure to your PrestaShop installation. Each shop has its own address and can have its own specific business settings.
The key point is the working environment. Before editing a product or configuration, select the relevant shop. You can also work on a group or on all shops, where the settings allow this.
These are the three levels of management.
| Background | Scope of operations |
|---|---|
| All shops | Settings applicable to the entire organisation |
| Retail group | Settings common to all shops in the group |
| Single shop | Changes specific to the selected shop |
The choice of context determines where a change is applied. An update intended for a single catalogue may affect several shops if you work in the wrong context.
The single panel therefore reduces the number of operational steps, but requires clear procedures. This function falls within the scope of The benefits of PrestaShop for e-commerce, especially when business operations become complex.
When is it best to manage several shops at the same time?
A multi-store approach makes sense when there are genuine commercial differences between the shops, alongside processes that can be centralised. Opening multiple outlets without a clear objective increases the workload and spreads resources too thinly.
Brands and markets with different needs
Multiple brands may require different visual identities, product ranges and promotions. A multi-store structure allows these choices to be kept separate whilst maintaining a single management structure.
International sales may also require dedicated online shops, with content, delivery terms and offers tailored to each market.
Simply translating the catalogue, however, does not automatically justify opening a second shop. PrestaShop already offers multilingual and multi-currency features. A multi-store setup becomes useful when business rules or the organisation of the catalogue also change.
B2B sales and private customers
A business-to-business channel may have different requirements from those of retail sales: exclusive product ranges, bespoke commercial terms and specific purchasing processes.
Dividing the shop into two sections is useful when these differences affect the entire shopping experience. If only the price changes, customer groups may be sufficient.
The management of B2B price lists and catalogues It must therefore be designed before the multi-store structure. Defining who buys, which products they see and what terms they are offered prevents the creation of unnecessary additional shops.
Enable the multi-store feature and set up the structure
Set-up is quick. The most important part is deciding how to organise the shops and what data to share.
On a live e-commerce site, create a full backup and carry out the configuration in a test environment. Structural changes must not affect ongoing sales.
Activation and access to the management system
In PrestaShop versions 8 and 9, the documented path starts from Shop settings > General. Here you can enable the multi-store feature.
Once activated, the management option appears in Advanced settings > Multistore. In this section, you can organise groups, shops and addresses.
The operational process consists of three steps:
- Create the group based on the sharing requirements.
- Add the shop and define the initial associations.
- Set up your address and business settings.
Once these steps have been completed, the context selector becomes an everyday tool. This must also be clear to those who manage products and orders.
Retail groups and initial imports
Groups set up shops that are required to share certain information. The relevant criterion is operational: which data should remain shared and which should be kept separate?
When setting up a shop, you can import data from an existing shop, depending on the available options. This speeds up the initial set-up, but Importing and sharing are different operations.
Copying a configuration does not mean that it will remain synchronised over time. Even an initially identical product range may be managed differently in individual shops.
Set these rules before adding new customers and starting sales.
Catalogues, customers and orders: what to share
Centralisation works when every instance of data sharing meets a business need. Sharing everything without distinguishing between processes can lead to business errors and management difficulties.
Products and quantities available
A product can be linked to more than one shop, whilst stock availability and configurations depend on the links and the selected context. You should not assume that every change is automatically applied to all shops.
Sharing stock levels enables shops within the same group to use the same stock levels for identical products.
This does not amount to the comprehensive management of multiple physical warehouses. Warehouses, bookings and logistics flows may require dedicated management software or integrations.
When quantities are not shared, stock management requires the context of the individual shop. The context of the group or all shops is not available for that operation.
Shared customers and orders
Customer sharing allows you to use the same login details across the group’s shops. This is useful when you want to provide seamless access between linked shops.
Order sharing has specific prerequisites: it also requires shared customers and quantities. These options must therefore be considered together.
The PrestaShop 1.7 documentation states that customer and order sharing cannot be disabled once enabled. These are design choices that require careful consideration, not merely graphical preferences.
Sharing orders also requires shared customer details and quantities: the decision involves master data and stock availability, not just the sales list.
For brands with separate customer bases, separating the data may be more appropriate.
Domains and SEO: every shop has its own address
A single panel does not make public addresses identical. Each shop must have a different URL and a structure that is easy for customers and search engines to understand.
Domains, subdomains and subfolders
You can use separate domains or organise your shops using subdomains and subfolders. The choice depends on your brand identity and business strategy.
For independent brands, separate domains maintain a clear distinction. For related projects, subdomains or subfolders can provide a more coordinated structure.
Virtual URLs require simplified URLs to be enabled, as outlined in the PrestaShop documentation.
The configuration also involves the server: linking a domain in the control panel does not replace DNS and HTTPS certificate management. All public addresses must resolve correctly to the installation.
Content and indexing of individual showcases
More shops mean more pages to organise. Titles, descriptions, categories and text must be tailored to the audience of each shop window.
Duplicating the entire catalogue across multiple domains can make it less clear which page should be displayed in search results.
For language versions, hreflang attributes help Google recognise alternatives intended for different languages or regions. Canonical tags, on the other hand, indicate the preferred URL amongst duplicate or very similar pages.
These settings serve different purposes. They must be coordinated with URLs, sitemaps and internal links, without indiscriminately redirecting all shops to a single version.
Modules, services and centralised maintenance
A single installation simplifies technical management, but it also centralises dependencies. A problem caused by an update may affect several shops.
The multi-store compatibility A module must comply with the project requirements. A correctly installed extension does not necessarily support separate configurations for each shop.
For payments, the right links between the shop, the account and the operating conditions are required. The’Nuvei’s PrestaShop integration It is a solution designed specifically for payments on the platform; multi-store functionality remains a separate requirement for implementation.
The same applies to integrations with ERP and CRM systems. Dedicated modules and APIs can transfer orders, customer details and stock availability, but each data flow must identify the shop from which it originates.
Performance also requires a holistic view. Traffic, catalogue searches, imports and automated processes all use the same infrastructure.
A poorly configured cache may display content from the wrong shop. Updates must be tested on all shopfronts, including the customer login, shopping basket, checkout and order confirmation.
I specialise in PrestaShop e-commerce development and maintenance with a focus on the project’s structure. For an SME, this means having clear procedures, recoverable backups and technical management that is consistent with business processes.
Frequently Asked Questions about PrestaShop’s multi-store feature
Is the multi-store feature included in PrestaShop?
Yes. It is a built-in feature that can be enabled via the admin panel. You do not need an additional module to enable the management of multiple shops.
Does every shop need to have a different domain name?
No. Each shop must have a unique URL, but it can use a separate domain, a subdomain or a subfolder within the same domain.
Are the quantities shared automatically?
No. Sharing stock levels is a decision taken by the group. It allows the group’s shops to use the same stock levels for identical products.
A unique framework, built around your processes
PrestaShop Multistore is useful when several shops share operational activities but need to maintain separate product ranges. The outcome depends on the design of sharing arrangements, even before the technical implementation.
Define your product ranges, customers, quantities and addresses before opening new shop windows. A well-organised structure makes day-to-day management easier and ensures business continuity.
Would you like to manage multiple shops from a single dashboard? I can help you design a PrestaShop solution tailored to your business.
