I couldn't find a clear answer on this: What's the difference between a Magento Website and a Store View?
可以将文章内容翻译成中文,广告屏蔽插件可能会导致该功能失效(如失效，请关闭广告屏蔽插件后再试):
问题:
回答1:
There's actually three things: A Website, a Store and a Store View.
The most important part about Websites is that each websites has its unique customer and order base.
Stores can be used to define for example different (looking) stores with the same information.
Store Views are mostly used to handle different languages on your website. You will typically have one Store View per language.
回答2:
Website:
- Possible to maintain a separate customer base for the website, or can share the customer accounts with all websites
- Different base currency can be defined
- Different order base can be maintained (Need citation on this one)
- Different prices can be given for the website using a configuration setting or can share the price globally
- Different Website URLs can be used or can share the same website URL (Magento keeps unique cookies)
Store:
- Customer accounts are shared among all the stores under a specific website
- Same base currency
- Same Price
- Product can be assigned store specifically
- Can have different root category configuration
Store View:
- Common practice is to distinguish between different language views for store
- Different display prices
- Category settings can be different
- Same root category for all store views
Inventory is global across all the websites and stores. Either the product is IN STOCK or not! If need different inventories, have to use third party modules
Hope this helps....
回答3:
Global | Website | Store | Store View
One of Magento’s advanced features allows for management of multiple websites and stores within one installation, and we have an amazing system to support this: GWS - aka “Global, Website, Store.”
Global: This refers to the entire installation.
Website: Websites are ‘parents’ of stores. A website consists of one or more stores. Websites can be set up to share customer data, or not to share any data
Store (or store view group): Stores are ‘children’ of websites. Products and Categories are managed on the store level. A root category is configured for each store view group, allowing multiple stores under the same website to have totally different catalog structures.
Store View: A store needs one or more store views to be browse-able in the front-end. The catalog structure per store view will always be the same, it simply allows for multiple presentations of the data in the front. 90% of implementations will likely use store views to allow customers to switch between 2 or more languages.
Example scenario
Let’s say you want to sell appliances, consumer electronics, and DVD’s and CD’s. For the purpose of this example we’ll separate the catalog into two stores and three websites. The appliance line will be sold on its own website, and the remaining items on another website. You bought appliances.com and coolstuff.com for this purpose. You don’t want customer data and order data to be shared between the two websites, so data sharing will be turn off in the configuration between them.
Under coolstuff.com you create two stores - Electronics, and Media. Consumer electronics will be sold through the electronics store, and the media items through the Media store. Since each line of items is very extensive, it makes sense to create a separate category structure for the Media store and the Electronics store… otherwise the category tree would be large and cumbersome. When the stores are created, you simply assign a different root category to each store.
In addition, you want to feature your catalog for both websites in English and Spanish. To do this, you will create an English and Spanish store view for each of the three stores. When entering catalog data you can switch store views in the admin to create the additional product titles, descriptions etc… Configuration
The configuration of Magento uses GWS as a kind of tree when setting up the stores. When it is initially installed, all configuration settings point to “default”, meaning the global installation. A check box next to each configurable item can be un-checked in a particular website or store view, to indicate that this item will be specific to this website or store view. For example, you will offer authorize.net as a payment module on both websites, but you only want to offer google checkout on coolstuff.com. In the configuration, you’d select coolstuff.com in the store view drop-down, find the google API settings, and un-check “use default” in the google checkout tab. For this specific website you can now enable or disable google checkout.
All modules in the configuration function the same way.
Moving on to store views - after a store view has been created, you can configure the layout and visual settings of the store view however you’d like - a drop-down allows customers to switch between store views. This will reload the current page with the alternate view. This can be used for multiple languages, but can also be a way to easily do A-B testing between several design packages to see if one yields more conversions. The possibilities are endless!
The above is meant as a basic overview of this functionality - the best way to learn how to set it all up is to install Magento and get in there and start playing around.
I also founded two short videos that go into a little more detail regarding the configuration. Enjoy! Video: Creating Multiple Online Storefronts, Part 1
回答4:
Here is what I found on Magento site which helped me to clear the difference between the 3 notions.
Website is a parent of store (or a basis for a store). It can consist of one or several stores.
Store is a "child of website". You create and manage products and categories on this level. Store (or store view group): Stores are ‘children’ of websites. Products and Categories are managed on the store level. A root category is configured for each store.
To be browsable in the interface a store requires one or more store views. The catalog structure per store view will always be the same. It allows multiple store presentations in the front end (like the opportunity to switch between 2 or more languages)