# Head and Branch Store Management
# Branch Store Management
# Tutorial on Using the Head and Branch Store Management System
[中文](/books/41f1f/page/6da90)
**I. Function Introduction**
The Headquarter-Branch Management module is a one-stop solution provided by elink for institutional headquarters for course distribution to branches and branch management.
**II. Purpose of Use**
It is suitable for the headquarters of various institutions to output courses, empower with content, manage data, etc. for branches/schools, franchise stores/schools, and channels, promoting the formation of a good cooperative relationship between the headquarters and branches.
**III. Use Scenarios**
A chain education institution A. Most of its branch campuses have opened stores on elink and have been using them. The headquarters wants to uniformly manage and distribute courses to both the branch campuses that have already opened elink stores and those that have not.
Education institution A can bind the relationship between the opened branch campus stores and the headquarters store through an agreement. The headquarters initiates the application, and the branch campuses authorize it to establish the headquarter-branch relationship. After that, the headquarters can distribute unified courses to the branches and manage the data of the branches.
For branch campuses that have not opened elink stores, different versions of stores can be opened according to the needs of the branch campuses first, and then the association operation can be carried out to establish the relationship.
**IV. Operation Path**
****
\[Merchant End\]
Headquarters: Merchant background of the headquarters store → Applications → More scenarios → Headquarter-Branch Management → Branch Management → Bind Branches → Initiate Application
Branches: Merchant background of the branch store → Store Settings → Bind Headquarters → Agree to Authorization
**V. Usage Tutorial**
Specific Steps:
1. Log in to the elink merchant management background, and select \[Applications\] - \[More scenarios\] - \[Headquarter-Branch Management\] - \[Branch Management\] - \[Bind Branches\] in sequence.
2. Enter the appid of the branch to be bound. If you don't know the appid of the branch, you can check it in the branch - Store Settings.
x
3. Click Next. The headquarters needs to select the permissions it wants to obtain, including \[Course Distribution\], \[User Data\], \[Order Data\], and \[Business Data\]. At the same time, for security reasons, the mobile phone number of the branch creator needs to be verified.
4. After the headquarters completes the process of applying for binding, the branch manager needs to go to the branch store to view and agree to the application. The branch manager logs in to the merchant background of the branch store, selects \[Homepage\] - \[Store Settings\] - \[Bind Headquarters\] in sequence, and clicks 'Receive' in the application record list.
5. The branch can see the permissions that the headquarters wants to obtain in the pop-up window. Before agreeing, the branch needs to verify by SMS and select the 'Headquarter-Branch Management Agreement'. After the above operations are completed, click 'Agree to Bind', and the headquarter-branch relationship is established.
6. After the headquarter-branch relationship is established, the headquarters can see the bound branches and the authorized permissions in the branch management. According to the authorized permissions, management and operations can be carried out in course distribution, user management, order management, and business data.
● If the headquarters wants to modify the authorized permissions of a bound branch, it can perform the operation of modifying permissions.
● If the headquarters wants to view the historical binding application records, click the application records to view.
**VI. Frequently Asked Questions**
1. Which version can use the Headquarter-Branch Management module?
Answer: The Headquarter-Branch Management module is only supported in the flagship version, that is,the store version of the headquarters must be the flagship version.If the version does not meet the requirements, please upgrade the version to the flagship version first to use it for free.
2. Are there any restrictions on the version of the branches?
Answer: There are no restrictions on the version of the branches. It can be the flagship version, the professional version, the ordinary version, or even the trial version.
3. After becoming a headquarters, can it still become a branch of other headquarters?
Answer: It is not supported. Once it becomes a headquarters, it cannot become a branch again. Please operate with caution.
4. After becoming a branch, can it still become a branch of other headquarters?
Answer: It is not supported temporarily. Currently, once it becomes a branch of a certain headquarters, it cannot become a branch of other headquarters again. Please operate with caution.
5. Can the headquarters unbind the bound branches?
Answer: The unbinding operation is not supported temporarily. The unbinding operation will be added later.
6. Do functions such as offline courses and educational administration support the headquarter-branch model?
Answer: The headquarter-branch model is not supported for functions such as offline courses and educational administration in this phase. Support will be added gradually later.
# Explanation of data permissions for head and branch stores
[中文](/books/41f1f/page/e7b24)
1. After authorizing the course distribution function, which courses will the branch stores receive?
Answer: The branch stores will receive the course content specified for distribution by the main store.
2. After authorizing user data, which user data of the branch stores can the main store view?
Answer: After the binding relationship between the main store and the branch stores is established, the main store can view the data of users who visit the branch stores.
3. After authorizing order data, which order data of the branch stores can the main store view?
Answer: After the binding relationship between the main store and the branch stores is established, the main store can view the new order data generated by the branch stores.
4. After authorizing business operation data, which business operation data of the branch stores can the main store view?
Answer: The main store can view the general overview of the business operation data of the branch stores since their establishment.
# Which version supports the Headquarter and Branch Management module?
[中文](/books/41f1f/page/91889)
The head and branch store management module is only available for the flagship version. That is, the store version at the headquarters must be the flagship version. If the version does not meet the requirements, please upgrade to the flagship version first to use it for free.
# What are the limitations of the branch store version?
[中文](/books/41f1f/page/43ec5)
There is no restriction on the branch store version. It can be the flagship version, professional version, basic version, or even the trial version.
# After becoming a main store, can it still become a branch of other main stores?
[中文](/books/41f1f/page/e836d)
No, once a store becomes the main store, it cannot become a branch of other stores. Please operate with caution!
# Can the head store unbind the affiliated stores that have already been bound?
[中文](/books/41f1f/page/0336d)
Unbinding operations are not supported at the moment.
# Do functions such as offline courses and educational administration support the headquarter-branch model?
[中文](/books/41f1f/page/7d04b)
Not supported in this period.
# After becoming a branch store of a main store, can it still become a branch store of other main stores?
[中文](/books/41f1f/page/6ecbd)
Temporarily not supported. Once a store becomes a branch of a certain head store, it cannot become a branch of other head stores. Please operate with caution!
# Course distribution
# For courses distributed by the head store, which course content can or cannot be modified by the branch stores?
[中文](/books/41f1f/page/a5e00)
If the editable mode is selected during distribution, all content can be modified.
If the non - editable mode is selected during distribution, the specific rules are as follows:
1) Branches cannot modify: basic information such as name, cover, content, and course mode;
2) Branches can modify: price, listing and delisting, students, and operation settings;
3) The information that branches cannot modify shall be consistent with that of the head store, i.e., when the head store makes modifications, the branches will be updated synchronously;
The specific information that cannot be modified is shown in the following table:
# The main store has already distributed Course B to Branch Store A. Can it continue to distribute Course B to Branch Store A?
[中文](/books/41f1f/page/abab)
Currently, only one distribution of the same course to the same branch store is supported. Even if you attempt to distribute it again later, it will not take effect.
# Can branch stores use marketing tools and learning assistance tools for the distributed courses?
[中文](/books/41f1f/page/7f39f)
The distributed courses support the use of marketing tools and learning assistance tools, just like self-built courses.
# Can branch stores associate the distributed courses with self-built columns, memberships, and camps?
[中文](/books/41f1f/page/c7e12)
Currently, it does not support associating distributed courses with self-built courses.
# What types of courses does course distribution support?
[中文](/books/41f1f/page/115f8)
Currently, only the distribution of text and images, audio, videos, and course series is supported. Course series that include live broadcasts, e-books, and AI interactive courses are not yet supported for distribution.
# Can the head store withdraw the courses after successful distribution?
[中文](/books/41f1f/page/fc490)
The main store can recall the successfully distributed courses. Click to enter the distribution record, and you can operate to recall the courses~
# User management
# What user data can be viewed in user management?
[中文](/books/41f1f/page/d09bf)
After the branch store authorizes the head office with user management permissions, the head office can view the user data of the authorized branch store in the user management module. Currently, it supports viewing data such as user details and information collection.
# Can all user data be viewed in the user management of the head office and its branches?
[中文](/books/41f1f/page/9461c)
Since the definition of the head and branch stores module is that the head store manages the branch stores, the headquarters can only view the user data of the branch stores in the Head and Branch Stores - User Management. The headquarters' own data can be viewed in the user list of its own store.
# Order Management
# What order data can be viewed in order management?
[中文](/books/41f1f/page/92c8c)
After the branch store authorizes the head store with order management permissions, the head store can view the branch store's order data in the order management module. Currently, it supports viewing the branch store's online orders (excluding affiliate marketing for courses orders) and offline order data.
# Can I view all order data in the order management of the head and branch stores?
[中文](/books/41f1f/page/75887)
Since the definition of the head - branch store module is that the head store manages the branch stores, the headquarters can only view the order data of the branch stores in the Head - Branch Store - Order Management. The data of the headquarters itself should be viewed in the order management of the headquarters' own store.
# Operating data
# Which business data of the branch stores can the head store view?
[中文](/books/41f1f/page/06138)
Currently, the business data is divided into two sections:
1. Real-time overview data panel;
2. List of business data for branch stores.
# How can the head store view the business data of its branch stores?
[中文](/books/41f1f/page/ef575)
After the head store submits an application and the branch stores grant authorization, the head store can view the business data of all authorized branch stores in the Head and Branch Stores - Business Data module. By default, the aggregated data of all branch stores is displayed, and you can select a single store for viewing.