For international brands opening physical stores in China, retail systems must support local operations and global headquarters requirements. PEKON provides local retail products and implementation services covering store transactions, products and inventory, promotions and loyalty coordination, with connections to payments, e-invoicing and existing business systems. Selection starts with deciding who owns each process, then assessing how far the headquarters platform can extend.
Leaving this decision too late affects more than POS configuration. Payment onboarding, invoice integration, product and price data, loyalty rules, headquarters interfaces, store networks and staff testing can all converge just before opening. System planning should therefore be part of the store-opening programme from the outset.
Scope: This guide is for brands establishing permanent stores, customer relationships and ongoing operations in China. Short-term pop-ups and limited market tests may have simpler requirements and should be assessed separately.
The short answer: define responsibilities before choosing deployment
Headquarters can retain ERP, finance, product master data and group reporting, while a local retail platform handles POS, local payments, e-invoicing, member identification, WeChat touchpoints and store operations. If the headquarters platform already has proven support for these processes in China, extending it is also an option. Compare adaptation costs, response times and long-term maintenance responsibilities.
A more comprehensive China platform may be appropriate where local operations are more independent, channels are more complex, or loyalty rules require greater flexibility. The right choice depends on the business plan and the interfaces available at headquarters.
1. What must China retail systems support locally?
Payments, refunds, reconciliation and e-invoicing
Products, prices and promotions must translate into actual store sales, with payment and invoice results linked to the same transaction. WeChat Pay, Alipay, UnionPay or payment aggregators involve payment confirmations, refunds, daily closing, discrepancy handling and financial reconciliation. E-invoicing must also connect with order status, invoice details and returns. Adding a payment method to a global POS does not by itself validate the entire transaction process.
Member identification and service across local touchpoints
Customers may register or identify themselves through a mobile number, WeChat Mini Program or store, and use points, tiers or vouchers across touchpoints. Headquarters CRM can retain the group membership framework. The China team must establish how local identification, benefits and store service connect to that framework, including account mapping, rule ownership and responsibility for service records.
Product and inventory rules specific to the category
Beauty retailers may need batch, expiry-date and shade handling; luxury retailers may need unique item identifiers, storage locations and detailed stocktaking; sportswear retailers often manage colour and size variants, numerous SKUs and transfers between stores. Evaluate actual sales, returns, promotions, stocktaking and transfer scenarios instead of relying on generic feature names.
Headquarters data flows and accountability
Stores need usable product and price information; headquarters needs operating data with consistent definitions. Establish the source of product and pricing data, the scope and frequency of store data transfers, and responsibility for exceptions. PEKON works with the brand's existing architecture to define these connections so local operating data can feed agreed headquarters processes.
Personal information and cross-border data use require assessment against applicable requirements, internal policies and appropriate professional advice. Technical connectivity is not a reason to transfer all member data by default. For permissions, data scope and headquarters use, see China retail data security and headquarters governance.
2. Three architecture options for ongoing operations
| Architecture | Division of responsibilities | When to consider it | What to validate |
|---|---|---|---|
| Extend headquarters systems into China | Global POS and CRM serve China stores, with local payment, invoicing and other adaptations as required. | The platform has proven China payment, invoicing, Chinese-language workflows and local support; operating models are similar. | Adaptation costs, support during China trading hours, third-party dependencies and maintenance ownership. |
| Local retail front end connected to headquarters core systems | Local systems handle transactions, payments, invoicing, customer touchpoints and operations. Headquarters retains ERP, finance, master data and group reporting. | The first store or initial rollout needs local capabilities while retaining the global core architecture. | Master data sources, interface fields, synchronisation frequency, exception handling and responsibilities. |
| A more comprehensive China retail platform | China deploys POS, CRM, WeChat touchpoints, inventory and order capabilities, sharing necessary data under group requirements. | China operations have greater independence, more complex channels or more flexible local loyalty and operating rules. | Data definitions, access controls, financial integration and long-term support across China and headquarters. |
A lightweight POS may be sufficient for a temporary sales event. It addresses a limited trading requirement and is not an equivalent long-term architecture. Plans to develop loyalty, add stores or expand channels require a fresh assessment of scalability and data integration.
3. Translate system boundaries into fields, processes and owners
| Business object | Typical responsible system | Questions to resolve before launch |
|---|---|---|
| Product master data | Headquarters ERP or product system | Who maintains products, SKUs, prices, tax fields and bilingual descriptions? How are updates distributed and errors corrected? |
| Store transactions | Local POS or retail system | How are sales, promotions, returns, exchanges, shift handover, closing and offline scenarios handled? |
| Payments and refunds | Local retail system and payment provider | How are confirmations, refund status, discrepancies and reconciliation responsibilities connected? |
| E-invoicing | Local retail system and invoicing provider | How are issuance, credit adjustments or cancellations linked to orders and refunds? |
| Member identity and benefits | Local CRM or loyalty system | Who owns registration identifiers, tiers, points, vouchers and redemption rules across touchpoints? |
| WeChat touchpoints | Mini Program and relevant WeCom applications | Which platform interfaces and permissions support registration, vouchers, orders and associate service? |
| Inventory status | ERP or local retail system, depending on the architecture | What definitions apply to available stock, goods in transit, transfers, counts and adjustments? |
| Group reporting | Headquarters data or BI platform | How are currencies, time zones, organisational structures and business measures aligned? |
| Member data shared with headquarters | The brand's designated responsible system, subject to assessment | What are the purpose, fields, authorisation basis, access controls and audit requirements? |
This table provides a common discussion framework for headquarters IT, China operations, finance and suppliers. “Connect ERP” or “integrate loyalty” is not a sufficient implementation specification: field ownership, triggers, retries and issue ownership must also be explicit.
4. Eight questions to align before selecting a system
- Which touchpoints are included in phase one: permanent stores, pop-ups, e-commerce, Mini Programs or others?
- Which rules remain global, and which can the China team configure locally?
- Which system is authoritative for products, pricing, promotions, inventory, orders and members?
- Which systems and providers jointly handle payments, refunds, invoices and reconciliation?
- How are members registered and identified in China, and where can they use benefits?
- What information does headquarters need, for what purpose, at what detail and frequency, and with which access rights?
- Who owns headquarters interfaces, local configuration, third-party platforms and store hardware?
- If an interface, network or device fails before opening, who decides, who responds, and how does the store continue trading?
5. Plan backwards from the opening date
Begin the system assessment when the China business plan and first-store plan are confirmed. Put software, hardware, third-party onboarding and store readiness into one schedule.
| Store-opening milestone | System work | Required output |
|---|---|---|
| China business and first-store plans confirmed | Define local and headquarters boundaries; identify store, loyalty, payment, invoice and data needs. | Scope list, initial architecture and accountable owners. |
| Store layout and equipment plans being finalised | Confirm POS terminals, printing, scanning, networks, mobile devices and installation requirements. | Hardware and network lists; store installation points. |
| Before configuration and interface development | Agree master data, fields, status definitions, timing, exceptions and third-party applications. | Interface inventory, field mapping and responsibility matrix. |
| Before trial operations | Complete end-to-end acceptance, staff training and exception tests. | Acceptance records, issue log, training and support arrangements. |
| Before official opening | Recheck permissions, products, prices, payments, refunds, invoicing, stock and contingency procedures. | Opening checklist, escalation route and fallback procedures. |
Headquarters approvals, third-party onboarding and payment or invoice testing can determine the critical path. Duration depends on scope, interfaces, approvals, data readiness and third-party cooperation. A fixed timeline without those conditions is not a reliable commitment.
Carry first-store preparation into subsequent openings
Product data, operating procedures and interface arrangements established for the initial stores can support later openings. During implementation, PEKON documents reusable configurations and operating requirements, adapting them to each new store's equipment, network and business conditions. Brands should retain test records and issue logs so later stores can reuse validated arrangements and identify what still needs testing.
6. Validate suppliers with one connected business scenario
Separate demonstrations of registration, checkout or invoicing reveal less than a continuous scenario:
A customer registers through the loyalty Mini Program, buys a product included in a China promotion, uses member benefits and WeChat Pay at checkout, requests an electronic invoice, then returns part of the order.
Ask the supplier to explain:
- Which system creates and recognises the member, and how duplicate accounts are handled.
- Which system determines prices, promotions and member benefits.
- How payment, order, invoice and partial-return statuses relate.
- Which steps depend on third-party platforms, headquarters interfaces or project configuration.
- Where failures are recorded and who handles timeouts, unsuccessful refunds or invoice exceptions.
- Which transaction and member data remains in China and what is shared with headquarters under the agreed scope.
This scenario tests product coverage, interface boundaries, implementation experience and exception handling. It also gives headquarters IT, local operations, finance and store teams a common basis for comparison.
7. Evaluate delivery conditions as well as features
- Local operating knowledge: Can the supplier explain payments, invoices, loyalty, stock and store processes in terms of actual statuses and responsibilities?
- Headquarters coordination: Can it provide interface lists, field mapping, issue ownership and bilingual communication materials?
- Third-party dependencies: Does it distinguish its own capabilities from platform conditions, partner services and actions required from the brand?
- Testing and launch preparation: Does the plan cover normal transactions, exceptions, returns, network outages, reconciliation, permissions and opening support?
- Expansion: Which changes to stores, channels or loyalty rules are configurable, and which require interface changes or development?
- Issue ownership: How many providers cover payments, invoices, hardware and integration, and who leads diagnosis when a problem crosses systems?
8. Where PEKON can participate in a China rollout
Against these criteria, PEKON can participate in project assessment and delivery preparation in the following areas:
- Local workflows: Map POS, payments, invoices, loyalty benefits, products, inventory and WeChat touchpoints, including normal and exception states.
- Headquarters coordination: Define interfaces, field mapping and responsibilities around existing ERP, finance or data systems. Confirm the scope of bilingual interfaces and materials in the project plan.
- Third-party dependencies: Distinguish PEKON products, payment and invoice providers, platform interfaces and brand responsibilities.
- Testing and opening: Agree connected demonstrations, end-to-end acceptance, training and opening checklists, with support scope specified in the delivery plan.
- Expansion: Combine smart retail, CRM and WeChat Mini Program capabilities according to store, loyalty and channel plans. Assess new requirements against interface and configuration conditions.
- Accountability: Map software, hardware, payments, invoicing and headquarters interfaces, specifying what PEKON provides directly, coordinates, or works on with brand-appointed suppliers.
The published premium chocolate brand case (in Chinese) describes Chinese-language iPad POS for stores and an English web back office for headquarters ordering, shipping and report exports, alongside batch and expiry-date handling and ongoing configuration support. It illustrates bilingual responsibilities across stores and headquarters; each new project still needs assessment against its own architecture.
PEKON's American performance lifestyle brand case illustrates local POS, payments, electronic invoicing and business-system integration, including store-to-WMS receiving and returns and bilingual reporting. The rollout also provides an example of reusing first-store setup for subsequent openings. Use these examples to examine the selection criteria above, rather than assuming identical arrangements for every brand.
For the broader delivery scope, see PEKON's China retail systems solution for international brands, then validate the relevant capabilities through a connected demonstration.
FAQ
Can an international brand use its headquarters POS directly in China?
Yes, subject to evaluation. Check local payments, refunds, e-invoicing, Chinese store workflows, member touchpoints and local support, together with clear headquarters responsibilities. If extensive adaptation is required, compare a local retail front end as well.
How should a local POS and headquarters ERP divide responsibilities?
Headquarters ERP can retain product master data, supply chain, finance and group reporting, while the local POS handles transactions, payments, invoices, member identification and store workflows. Define master data ownership, interface fields, timing and exception responsibility explicitly.
Should all China member data be sent to overseas headquarters?
No. First define the business purpose, necessary fields, level of detail, access and audit requirements, and assess applicable rules and internal policies with appropriate professional input. Some needs can be met through aggregation or statistical outputs instead of complete records.
Does a single first store need a scalable architecture?
If it is the start of ongoing operations and expansion, confirm how additional stores, member migration, headquarters interfaces and local rules will be supported. Short-term pop-ups can be assessed against a more limited scope.
How long does a first-store system project take?
Timing depends on requirements, headquarters interfaces, third-party applications, data, hardware, networks and testing. Begin when the store plan is confirmed and include payments, invoicing and end-to-end acceptance in the opening schedule, rather than relying on a fixed duration without project conditions.
What is the most useful supplier demonstration?
Use one scenario covering member registration, store purchase, benefit redemption, local payment, e-invoicing and a partial return. Ask for system ownership, dependencies, headquarters interfaces, exception records and data boundaries at every step.
Conclusion
Selecting retail systems for China means putting headquarters governance and local operations into one clear responsibility framework. Establish who owns each business object, how processes connect and who handles exceptions before comparing deployment options and suppliers. That makes the decision relevant to both the first opening and subsequent operations.