For an international brand planning its first store in China, the initial retail system decision also shapes how subsequent stores can open and operate. The immediate priority is to support trading. The longer-term requirement is to retain the data, rules and operating experience that have already been proven.
A typical growth path is to establish one successful store, replicate the operating model across more locations, and eventually coordinate multiple brands, regions and entities. If the initial data structure only works for a single store, or permissions are added through temporary arrangements, expansion creates more data cleanup, process changes and retraining. The consequences of early decisions become clearer as the network grows.
PEKON's approach to supporting brands from their first store through group-level operations follows this principle: system planning should reflect the brand's stage of development and preserve operational continuity. The three stages below describe changing business responsibilities. They do not require every brand to deploy the same products or follow the same timetable. Implementation scope should be determined by current needs.
1. Three Stages of Growth, Three Different Priorities
At the first-store stage, the priorities are opening on time and ensuring staff can use the system. With multiple stores, the focus shifts to replicating a consistent operating model and giving headquarters visibility into each location. At group level, the challenge is sharing a technical foundation across brands and regions while retaining their distinct operating rules.
| Stage | Business priority | System responsibilities | What to establish before the next stage |
|---|---|---|---|
| First-store launch | Can the store open and complete real trading workflows? | POS, payments, products, promotions, inventory, membership and basic reporting; ERP, order management system (OMS) and e-invoicing connections where required. | Working store processes, accurate foundational data and a rehearsed opening plan. |
| Multi-store expansion | Can new locations adopt the same proven operating model? | Organizational permissions, store-opening templates, multi-store inventory, member engagement and operating analysis; B2B ordering when franchise or distributor operations require it. | Templates for store setup, access rights, training, acceptance testing and release changes. |
| Group-level governance | Can multiple brands and regions coordinate without conflicting rules? | Organizational hierarchy, brand separation, master-data ownership, consistent group reporting definitions, integration governance and audit. | Clear shared and separate responsibilities, interface standards, a permissions matrix and a change-management process. |
Growth changes both functionality and management responsibilities. Product, customer and transaction rules established in the first store influence later rollout. Permissions and store-opening templates developed during expansion become part of group governance. Documenting early rules makes it easier to identify what can be retained and what must change.
2. First Store: Make the Complete Operating Process Work
A first store usually has a fixed opening date. The system needs to support sales, refunds, shift handovers, daily closing, stocktaking and exception handling in the actual store environment. Scope can be focused, but every process included in the launch must be configured, taught and tested.
Checkout extends beyond taking an order and collecting payment
Before launch, test real products and promotion rules through sales, returns and exchanges, offer redemption and split payments. Establish how missing records are recovered after a network or interface failure. Reconcile the resulting orders, payments and daily closing records.
For international brands entering China, the project also needs to address local payments, electronic invoicing, language requirements and the way China data is reported to headquarters.
Build usable product and inventory data from day one
Before importing data, define product codes, barcodes, categories, units, prices and responsibility for activating or withdrawing products from sale. Test opening balances, receiving, sales, returns and stocktaking with the initial inventory so that the store does not need to reconstruct its records in spreadsheets after opening.
The required detail depends on the category: shades and batches in beauty; style, color and size in sportswear; batches and expiry dates in food; and item-level unique identifiers in consumer electronics.
Align membership rules with the brand's existing channels
If the brand intends to build long-term member relationships, establish registration, identification, tiers, points, coupons and privacy consent before the first store opens. If customer touchpoints already exist on Tmall, Douyin or WeChat mini-programs, agree which identities and benefits can be connected, how often information is synchronized and who handles exceptions.
OneID means recognizing the same customer across a single brand's stores, mini-programs, e-commerce and sales-associate touchpoints. It does not mean automatically merging the membership programs of different brands within a group. Each brand's membership club remains separately managed.
Use the brand's own workflows for acceptance testing
A feature demonstration shows that an entry point exists. Acceptance testing establishes whether a process works. Store managers, sales associates, operations, finance and IT should walk through representative scenarios together: Is the store workflow practical? Can headquarters find the corresponding records? Can an interface interruption be located? Does daily closing reconcile?
The operating manual and issue list produced by this exercise become the basis for launching the second store.
PEKON began working with one Chinese multi-brand beauty group from its third store, and with another functional skincare brand from its first store. These examples show that system planning can start early in a brand's offline development. Before opening, discuss whether additional stores can reuse product codes, recognize members of the same brand and receive appropriate permissions within the established organizational structure.
3. Multiple Stores: Turn First-Store Experience into Repeatable Standards
As the network grows, the focus moves from making one store work to enabling headquarters oversight and repeatable openings. Manually configuring products, prices, accounts and campaigns store by store soon creates inconsistencies. Transfers, stocktaking, loyalty benefits and reporting also become more complex as regions and store formats multiply.
Template the organization, roles and permissions
Headquarters, regional teams, directly operated stores, franchisees and individual roles need different access. Permissions should cover specific actions such as viewing, creating, editing, approving, voiding and exporting, with appropriate activity records.
A new store can start from a tested organization and role template, with adjustments for its format. This reduces ad hoc access grants and the risk of users operating beyond their responsibilities.
Make the store-opening process repeatable
A new-store template should cover store records, permissions, product and opening-stock setup, payment configuration, device installation, training, scenario testing and opening support. For each step, identify the owner, prerequisites, completion evidence and exception procedure.
The result is a common preparation standard with less dependence on a small number of people who know the system well.
Bring inventory and membership into everyday network management
Teams need to view sales and inventory by store, region and product; manage ordering, receiving, transfers and stocktaking; and analyze shortages, excess stock and turnover using the brand's rules. Within the same brand, member identity and benefits should remain consistent across stores, mini-programs, e-commerce and sales-associate activity, within authorized access.
In the DR PLANT retail project described by PEKON, the brand's network had reached 4,680 stores. The project supported promotions running simultaneously across more than 4,000 locations, real-time calculation of member benefits, and connections between order, inventory, membership and marketing data and the brand's ERP and CRM.
The practical tasks were specific: stores could execute promotions during campaign peaks; checkout could calculate member benefits; and headquarters could use store data to review operating performance. Expanding brands can use these tasks to design their own load tests and reconciliation scenarios. See the DR PLANT customer story.
Add B2B ordering when the channel model requires it
PEKON's B2B Ordering Platform is not a mandatory first-store purchase. It becomes relevant when a brand develops franchisees, distributors or direct-supply store relationships and needs to manage catalogs, account rules, ordering policies, approvals, payment status and shipment status online.
ERP, warehouse management systems (WMS) and finance retain their respective responsibilities. B2B ordering connects the ordering process between headquarters and its channel customers.
4. Group Operations: Share the Foundation and Preserve Brand Autonomy
Group complexity grows as brands, legal entities, regions, channels and systems increase together. The group wants to share technology investment and management standards. Individual brands still have different products, prices, promotions, membership programs and store processes.
Start by documenting what can be shared, what must remain separate and what the group governs centrally.
The group layer is suited to organizational structure, account security, interface standards, data quality, common reporting definitions and audit. Each brand manages its own products, prices, promotions, membership club, store inventory and daily operations.
Within authorized boundaries, the group can aggregate and compare sales, inventory and membership metrics. That does not imply default sharing of customer identities, points, coupons, stored value or marketing permissions. Membership clubs are configured separately, and customer data is managed according to agreed processing responsibilities and authorizations.
Inventory ownership remains defined by brand, product, legal entity, warehouse and store. Ordering, replenishment, transfers and stocktaking operate within the relevant brand's scope. Group reporting uses common statistical definitions without changing stock ownership or operational permissions.
Master-data and integration responsibilities also need explicit ownership: Who maintains products? Which system is authoritative for inventory? How do orders reach OMS or finance? Which definitions does business intelligence (BI) use? Then agree what data is exchanged, how often and who resolves failures. As interfaces multiply, release control, monitoring and issue records become ongoing management responsibilities.
Systems must also accommodate new regions, formats and business models. PEKON began building its PEKON Jingang Low-Code PaaS platform in 2017 to address ongoing change through low-code development, visual configuration and API orchestration. Group requirements for organization, permissions, workflows and interfaces can build on established products. Whether a requirement uses configuration, development or integration depends on existing capabilities and project scope and should be validated through business scenarios.
5. Activate Capabilities as the Business Needs Them
The product mix should follow operating requirements. PEKON Smart Retail System provides the foundation for store transactions and operations. CRM supports customer relationships within a brand. B2B ordering serves franchise and distributor models. AI inventory optimization requires continuous, accurate sales and stock data.
| Business requirement | First-store priorities | How the capability develops | Relevant PEKON product |
|---|---|---|---|
| Open stores and replicate operations. | Validate transactions, products, promotions, inventory and daily closing. | Add role and store-setup templates for multiple stores; separate operating scopes by brand and provide authorized group views. | PEKON Smart Retail System |
| Build ongoing customer relationships within a brand. | Establish registration, identification, tiers, points and coupon rules. | Connect touchpoints within the brand and develop segmented engagement; configure separate membership clubs for group brands. | Omnichannel CRM & Loyalty Platform |
| Manage ordering by channel customers. | Defer for a directly operated first store unless channel operations already require it. | Manage catalogs, accounts and orders as franchise and distributor networks grow; configure regional and channel-tier rules with clear ERP, WMS and finance boundaries. | B2B Ordering Platform |
| Improve inventory decisions using operating data. | Build accurate product, sales, inventory and in-transit records. | Use multi-store data for diagnostics, replenishment and within-brand transfer recommendations; adapt strategies to store and product differences as scale grows. | AI Inventory Optimization Engine |
WeChat mini-programs can support an online store, member services and sales-associate activity according to the brand's customer-touchpoint plan. Whether they launch with the first store depends on the existing channel and membership strategy. Adding products simply to broaden the initial scope creates unnecessary complexity. See the PEKON product portfolio.
6. Category-Specific Operating Requirements Still Matter
Retail categories have material differences. Beauty needs shade, batch, expiry and sample management. Sports footwear and apparel need style-color-size structures and visibility into broken size ranges and excess stock. Collectibles and IP retail involve licensed merchandise and blind-box unpacking. In beauty-care chains, prepaid service packages support acquisition, higher-value purchases and repeat visits, so the system must manage both marketing rules and subsequent service delivery, beyond counting redemptions.
These differences determine the required depth of product, inventory, membership and transaction rules. PEKON reports experience supporting more than 200 brands and over 30,000 stores across seven retail sectors and international brands entering China. A shared technical foundation supports common business objects, while category and project requirements still need specific validation.
| Category or operating context | Key requirements to examine |
|---|---|
| Beauty | Shades, batches and expiry dates, samples and gifts, complex promotions, repeat member purchases and channel ordering. |
| Luxury | Mobile POS, VIP identification, store appointments, RFID and in-store service workflows. |
| Sports footwear and apparel | Style-color-size structures, multi-attribute SKUs, multi-store inventory, promotions and sales-associate-led member engagement. |
| Collectibles and IP retail | Licensed merchandise, inventory changes when blind-box packs are opened, fan membership and different store formats. |
| Beauty-care chains | Appointments and staff scheduling, service packages, service records, repeat member visits and franchise operations. |
| Branded food | Batches and expiry dates, gift-box combinations, seasonal inventory, near-expiry handling and repeat purchases. |
| Consumer electronics | Flagship-store transactions, item-level identifiers, inventory status and after-sales registration. |
| International Brands Entering China | Local POS, payments, e-invoicing, membership touchpoints and headquarters-system integration. |
Industry solutions help identify priorities. Each project must still confirm capability boundaries. Classify requirements as standard functionality, configuration, integration, custom development or currently unsupported, then validate them with representative products, roles and documents. Use a proof of concept (POC) during selection, followed by system integration testing (SIT) and user acceptance testing (UAT) during implementation. Retain the results from each stage.
7. Answer Five Questions Before Defining the System Scope
What will the store network look like over the next two to three years?
Directly operated stores, franchisees, distributors, pop-ups and department-store counters have different transaction, permission and settlement requirements. Base scope on the intended operating model rather than a generic feature list.
Which capabilities must go live at this stage?
First stores prioritize opening and basic operations. Multi-store networks prioritize repeatability and headquarters management. Group programs address multi-brand governance and complex integration. For deferred capabilities, record the conditions that will trigger implementation so that future work has a clear starting point.
Who maintains each type of data?
For products, prices, inventory, members, orders and organizational records, identify the accountable owner, permitted editors and intended users. If historical data must migrate, also define cleansing rules, reconciliation methods and ownership of exceptions.
How will existing systems divide responsibilities?
Before implementation, agree what retail, ERP, OMS, WMS, finance, BI and e-commerce systems will each retain. Define interface fields and authoritative records.
How will you demonstrate that the system fits?
Ask the supplier to use the brand's own business scripts. Acceptance should cover normal and exception workflows, permission separation, data reconciliation and interface failures. For every requirement, record its capability category, validation result and unresolved issues.
8. Further Reading for Your Current Stage
- Preparing a first physical store: First-Store Retail Digitalization: Where to Start (Chinese).
- Entering China: explore PEKON's solution for international brands entering China for local store and headquarters integration requirements.
- Moving from e-commerce into physical retail: An E-Commerce Brand's Guide to Its First Physical Store (Chinese).
- Evaluating suppliers: How First-Store Brands Can Assess a Retail Vendor's Industry Knowledge (Chinese).
- Expanding the store network: Retail Systems When a Brand Grows from 20 to 300 Stores (Chinese).
- Managing multiple beauty brands: Shared Group Management and Independent Brand Operations (Chinese).
9. Set the Scope for the Stage You Are In
Supporting growth becomes concrete through scope decisions and acceptance tests. Establish working processes now, then carry forward validated data, rules and templates. Record the triggers for deferred investment so that future expansion builds on an agreed plan.
Use the five questions above with operations, store, finance and IT teams to create one shared scope record: what must be completed now, when later capabilities should start, who owns each item and how it will be accepted.
Frequently Asked Questions
Which system capabilities should a brand launch with its first store?
Start with POS, payments, products, promotions, inventory, member identification and basic reporting. Connect ERP, OMS, e-invoicing and other surrounding systems according to actual requirements. Scope can be focused, but every live workflow needs configuration, training and validation with real scenarios.
Do we need every product at the first-store stage?
No. A directly operated first store should prioritize transactions and basic operations. A defined membership strategy may justify CRM and mini-program capabilities at launch. B2B ordering is relevant to franchise, distributor or direct-supply ordering models. Evaluate AI inventory optimization once sales and stock data are sufficiently stable.
What needs to change when expanding from one store to several?
Add organizational and role permissions, store-opening templates, multi-store inventory, consistent within-brand membership rules, store and regional reporting, and processes for training, acceptance and releases. Add B2B ordering and channel-account rules when franchise or distributor operations require them.
Can directly operated stores, franchisees and distributors use identical rules?
Some product structures, interfaces and technical capabilities can be shared. Permissions, pricing policies, inventory accountability, ordering processes and data visibility should reflect the business relationship. Establish the applicable compliance boundaries for franchisee retail pricing and customer personal information before implementing related rules.
When should we establish CRM and loyalty capabilities?
If long-term member relationships are part of the strategy, establish registration, identification, tiers, points and coupons at the first-store stage. Connect stores, mini-programs, e-commerce and sales-associate touchpoints within the same brand as the network grows. Configure separate membership clubs and access rights for brands within a group.
Is AI inventory optimization appropriate for a first store?
The initial priority is accurate product, sales, inventory and in-transit data. Once operating history is available, assess store count, assortment and inventory problems to determine whether AI-supported diagnostics, replenishment, transfer recommendations and rule refinement are appropriate.
Does group-level operation mean all brand data should be shared?
No. A group can reuse the technical platform, organizational framework, interface standards, security mechanisms and aggregate metrics. Products, prices, promotions, membership clubs, inventory and store processes remain managed within each brand. Specify the extent of sharing through a permissions matrix and data-responsibility record.
Must we replace our existing ERP, OMS or WMS?
Not necessarily. Clarify each system's responsibilities, then assess integration, module upgrades or replacement. Focus on master-data sources, order and inventory definitions, interface stability, historical-data migration and the ability to support additional stores and brands.
How can we assess whether a system will support long-term growth?
Look beyond the feature list to organizational permissions, data boundaries, integration methods, product development and implementation support. Demonstrate or test representative products, promotions, refunds, loyalty benefits, inventory and interface failures. Classify the results as standard functionality, configuration, integration, custom development or currently unsupported.
Your Five-Question Retail System Planning Checklist
Use the following prompts to turn the discussion into a practical preparation record. For each answer, record an owner, the evidence needed and any unresolved decision.
- Store network: List the store formats and operating relationships expected over the next two to three years.
- Current scope: Separate launch requirements from deferred capabilities and define the trigger for each later investment.
- Data ownership: Assign responsibility for products, prices, inventory, members, orders and organizational records, including migration checks where needed.
- System responsibilities: Map retained systems, authoritative records and required data exchanges.
- Acceptance evidence: Define normal and exception scenarios, permissions tests, reconciliation checks and the evidence required for sign-off.
Whether you are preparing a first store, expanding a network or planning group operations, bring this record and your existing system map to a discussion with PEKON. The goal is to agree a practical product scope and launch plan for the stage your brand has reached. Explore PEKON's China retail solution for international brands.