Adobe Commerce Multiple Website Management
Last update: November 7, 2024
CREATED FOR:
- Beginner
- Admin
- User
Adobe Commerce empowers businesses to manage multiple stores, brands, or websites from a single backend interface without requiring technical skills. It allows the creation of multiple websites, each with its own domain, products, pricing, and customer base. Within a website, multiple stores can be created, each with its own catalog and pricing, and within a store, multiple store views can be set up for different languages or versions. This flexibility ensures efficient management of product offerings and pricing strategies, making it ideal for businesses looking to expand and scale their e-commerce operations.
Who is this video for
- Businesses looking to expand their e-commerce operations across multiple regions, brands, or product lines.
- Store managers, e-commerce directors, and marketing teams.
- Companies aiming for scalability and flexibility in their online presence.
Video Content
- Multi-Site Management
- Localization and Customization
- Scalability and Flexibility

Transcript
Let’s take a look at how Adobe Commerce enables store managers to create new websites and new stores without requiring any technical skills. Adobe Commerce offers robust multi-site capabilities that allow businesses to manage multiple stores, brands or websites from a single backend interface. Adobe Commerce allows you to create multiple websites from a single installation. Each website can have its own domain, set of products, pricing and customer base. Within a single website, you can create multiple stores. And each store can have its own product, catalog and pricing. Within a single store, you can create multiple store views. Store views are useful for managing different languages or different versions of a store. For example, you can create a store view for English, French and Spanish within the same store. For this demo, we are using a fictional brand Bodea that sells hardware, devices and software. And this business is currently operating in US. They are looking to expand to Canada. Let’s see how the Bodea store manager will create a new store for Canada that inherits the catalog and pricing from the US store. To create a new store, click on Stores, All Stores. Here, you can already see that there is a Bodea US store. Now we want to create a new store for Canada. To create a new store, simply click on Create Store. Now we are going to target this store to the Bodea website. I am going to call it Bodea Canada and give it a store code of Bodea underscore Canada. Since we want to inherit the catalog from the US site, I would just simply select the Bodea root category so that it inherits the catalog from the US store. Next, you need to create a new store view which will help you localize the content and pricing. To create a new store view, click on Create Store View. I am going to target the Bodea Canada store we just created and call the store view Bodea Canada Store View. Give it a code of Canada underscore store underscore view and set it as enabled and save the store view. Please note this operation may take some time depending on the size of the catalog and the content that needs to be inherited from the US store. So now that we have a new store set up for Canada, let’s take a look at what catalog segmentation and pricing options are available to the store manager. Click on Catalog and go to the Products page. Select a product, then select the scope to be the newly created Canada store. This action enables store managers to localize settings and pricing for a specific store view. Since we inherited the catalog from the US store, the default pricing and discount is also inherited from that store. The store manager has the option to set a different price for Canada and also create different discounts and promotions. Let’s see what other configuration options are available to the store manager. Click on Store Configuration, then select the right scope. These configurations offer a comprehensive suite of tools and settings that allow businesses to tailor their e-commerce platform to meet specific operational needs. Store managers can set default country, default locale for the store, and set the relevant store information. Additionally, store managers have the option to localize the currency for this store, as you can see here. Please note more than one currency can be enabled for a single store. Now that we have the Canada store created, let’s take a look at the storefront experience. As you can see on the storefront, the customer has the option to switch stores and see pricing in Canadian dollars. Please note that these stores can also have their own domains. Now let’s take a look at some examples where customers have built a multi-site, multi-brand experience using Adobe Commerce. The first example is Hanesbrand. Hanesbrand is leveraging Adobe Commerce and Adobe Experience Manager to deliver highly performant experience at scale across Maidenform, Champion, Hanes, Bali, and Bond brands. The next example is Dish. Dish is leveraging AEM Sites and Adobe Commerce to deliver rich experiences across Dish, Sling, and Boost Mobile brands. So as you can see, by leveraging the multi-site catalog and pricing inheritance feature of Adobe Commerce, business can efficiently manage their product offering and pricing strategies, ensuring flexibility and scalability in their e-commerce operations. Thank you.
Previous pageData Sharing
Next pageExperience Lead Data and Promotions
Commerce
- Commerce Tutorials
- Adobe Commerce Cloud
- Getting Started
- Global Reference Architecture
- Help and support
- Edge Delivery Services
- Webinars and events
- GraphQL and REST
- Adobe Developer App Builder
- Store Administration
- Customer Management
- Catalog Management
- Content Management
- Marketing Tools
- Orders and Fulfillment
- B2B for Adobe Commerce
- Tools and External services
- Commerce Intelligence
- Commerce Upgrades
- Back-end Development
- Native Front-end Luma Development
- Headless Architecture