ERP, WMS and Omnichannel Inventory for China E-Commerce

For foreign brands selling into China, the china ecommerce erp wms inventory stack is not an IT afterthought: national data-exchange standards, PIPL data duties and customs three-document matching all shape how your order, warehouse and consumer data must flow — and getting it wrong delays launches and creates overselling risk. This guide sets out the systems, the standards behind them and the compliance checkpoints, so you can plan a stack that scales across Tmall, JD, Douyin and your own channels.

Quick Facts

What Is the Difference Between ERP and WMS in China E-Commerce?

ERP (Enterprise Resource Planning) manages money and orders — sales orders, purchasing, finance and reconciliation — while WMS (Warehouse Management System) manages goods — receiving, putaway, picking, packing and stock counts. In a china ecommerce erp wms inventory setup, the ERP is the commercial brain and the WMS is the physical execution layer.

You will typically need both once you operate more than one storefront or warehouse. Smaller merchants often start with the marketplace's built-in merchant tools, which handle basic order management at no extra cost, then graduate to a third-party ERP when order volume, SKU count or channel count grows. Mid-sized and larger operations generally pair a third-party ERP with a dedicated WMS, especially when they run their own bonded or domestic warehouse.

The division of labor matters for accountability. If a customer order is mis-priced, that is an ERP problem; if the wrong item ships from the shelf, that is a WMS problem. Contracts with software vendors and third-party logistics (3PL) providers should reflect this split so that data errors can be traced to the right system.

Which National Standards Govern Data Exchange Between Systems?

China's standards body has issued recommended national standards that function as the de facto plumbing for china ecommerce erp wms inventory integration. GB/T 40094.3-2021, "E-commerce Data Transaction — Part 3: Data Interface Specification," covers order, inventory and product data exchange between platforms and merchants (GB/T 40094.3-2021, SAMR).

For the warehouse side, GB/T 26772 governs data exchange between transport and warehousing businesses — the standard your WMS and 3PL will typically align to (GB/T 26772, SAMR). GB/T 18768 sets out the digital warehouse application system specification, covering how warehouse systems should be structured (GB/T 18768, MOFCOM). Complementary standards cover logistics public information platform data sharing (GB/T 22263) and XML-based inventory and order message formats (YD/T 2457.2.2-2016 and SB/T 10378.3-2004) (YD/T 2457.2.2-2016 / SB/T 10378.3-2004, SAMR).

Two points deserve emphasis. First, these are recommended ("GB/T") standards, not mandatory ones — non-compliance is not illegal. Second, they are nonetheless the industry's de facto interface language: if your systems or your 3PL cannot speak to them, integration becomes slow and expensive, and marketplace onboarding teams will often assume compatibility.

What Are the Data Retention and Security Rules for Consumer Information?

Under the draft MOFCOM e-commerce logistics service specification, consumer-related data must be retained for at least 1 year, and contracts and receipts involving consumers for not less than 3 months, unless other laws or agreements require longer (E-commerce Logistics Service Specification (draft), MOFCOM). The same draft requires network security measures aligned to GB/T 22239, the Multi-Level Protection Scheme (dengbao/MLPS) baseline (E-commerce Logistics Service Specification (draft), MOFCOM).

Under the Personal Information Protection Law (PIPL), your business is the personal information processor, while your ERP and WMS vendors act as entrusted processors. That means consent, minimum-necessity limits and retention duties sit with you, the brand — not with the software vendor (E-Commerce Law of the PRC, CAC). In practice, your vendor contracts should specify data-processing scope, security obligations and deletion or return of data on termination.

How Does Omnichannel Inventory Syncing Work — and What Is "One Pool of Stock"?

Omnichannel inventory in China rests on the "one pool of stock" (yi pan huo) model: a single unified stock position feeds all channels, with real-time synchronization, overselling protection, inter-warehouse transfers and data write-back to each storefront. The order and inventory message flows that make this possible are exactly what GB/T 40094.3-2021 standardizes (GB/T 40094.3-2021, SAMR).

A workable target architecture has four layers: a central inventory service as the single source of truth; channel connectors to each marketplace; a WMS that executes physical movements and reports back; and a reconciliation layer that flags discrepancies. Practitioners commonly aim for sub-minute sync latency, a 5–10% safety-stock buffer against overselling, and inventory accuracy above 99% (industry estimates, no official standard) — treat these as design targets rather than regulatory requirements.

Physical standardization supports the digital layer. Supply-chain policy promotes GS1-based linking of pallet barcodes, product barcodes, carton codes and logistics unit identifiers, on standard 1200mm × 1000mm pallets and 600mm × 400mm tote modules (Supply Chain System Construction Notice, NDRC). If your packaging and pallets follow these dimensions, warehouse scanning and data capture are materially smoother.

What Must Cross-Border E-Commerce ERP and WMS Systems Do for Customs?

If you sell cross-border into China under the bonded model, your ERP and WMS must support "three-document matching" (san dan): the transaction document (order), the payment document and the logistics document must be transmitted through the Single Window and match before clearance (GACC Announcement No. 194 of 2018). Your systems must therefore generate and push all three document types in the required format, in near real time.

This has practical consequences for system selection. Off-the-shelf Western ERP/WMS products frequently lack a customs three-document module, so brands either adopt a China-native ERP with this capability built in, or engage an integration partner to build the interface. Your WMS must also reconcile bonded-warehouse stock with customs inventory records, since discrepancies can trigger audits.

What Does a China E-Commerce Systems Stack Cost and How Long Does It Take?

Budgets vary widely by scale and deployment model. The figures below are industry estimates for planning purposes — there is no official price standard, and vendor quotes should be verified directly.

Most foreign brands launching in China start SaaS and revisit private deployment only after order volumes justify it. The larger hidden cost is integration: connecting your global ERP to the China stack, and mapping your product data to GB/T-aligned interfaces, often takes longer than the software deployment itself.

How Do You Build the Stack Step by Step?

A disciplined sequence reduces rework. Our advisory team recommends the following framework:

1. Map your channel and fulfillment model. List every storefront (marketplace, cross-border bonded, own mini-program) and decide which warehouses serve which channels, since this determines whether you need one WMS or several.
2. Choose ERP scope first. Decide whether the China ERP handles finance locally or feeds a global ERP; this choice drives data-interface requirements under GB/T 40094.3-2021 (GB/T 40094.3-2021, SAMR).
3. Select a WMS aligned to GB/T 26772 and GB/T 18768. Confirm your 3PL or own warehouse can exchange transport and warehousing data in the standard format (GB/T 26772, SAMR).
4. Design the unified inventory pool. Define sync frequency, safety-stock rules and transfer logic across channels before go-live, not after your first overselling incident.
5. Build customs interfaces if cross-border. Implement three-document matching through the Single Window and test with your bonded warehouse operator (GACC Announcement No. 194 of 2018).
6. Contract for PIPL compliance. Ensure vendor agreements designate you as processor, the vendor as entrusted processor, and specify the 1-year consumer-data retention and GB/T 22239 security baseline (E-commerce Logistics Service Specification (draft), MOFCOM).
7. Pilot, reconcile, then scale. Run one channel for 2–4 weeks, reconcile inventory daily against physical counts, then add channels progressively.

What to Watch Out For

Recommended standards are de facto mandatory in practice. GB/T 40094.3-2021, GB/T 26772 and GB/T 18768 are technically voluntary, but marketplaces and 3PLs assume them; a system that cannot exchange data in these formats will face slow onboarding (GB/T 40094.3-2021, SAMR).

The MOFCOM logistics service specification is a draft, not a final standard. The 1-year consumer-data retention and 3-month contract retention figures come from a draft for comment, not a formally issued SB/T standard — but they signal the direction of regulation and are prudent minimums to adopt (E-commerce Logistics Service Specification (draft), MOFCOM).

PIPL accountability cannot be outsourced. Even when your ERP or WMS vendor processes consumer data on your behalf, you remain the processor under PIPL, and consent, minimization and retention duties stay with your brand (E-Commerce Law of the PRC, CAC).

Cross-border clearance fails without document matching. If your systems cannot produce matching transaction, payment and logistics documents through the Single Window, bonded shipments stall (GACC Announcement No. 194 of 2018).

Physical and digital standards interlock. Non-standard pallets or missing GS1-linked barcodes create scanning exceptions that erode inventory accuracy, whatever your software claims (Supply Chain System Construction Notice, NDRC).

Frequently Asked Questions

Q: Do I need both an ERP and a WMS to sell in China?

A: Not at the start. Small merchants can operate on marketplace-native order tools, but once you exceed roughly 100 orders per day or sell on 3 or more channels, a dedicated china ecommerce erp wms inventory stack — ERP for orders and finance, WMS for warehouse execution — becomes the practical baseline for 2026 operations.

Q: Are GB/T standards mandatory for my systems?

A: No. GB/T standards such as GB/T 40094.3-2021 and GB/T 26772 are recommended, not compulsory, so non-compliance carries no direct penalty. However, they are the de facto interface language of China e-commerce, and systems that ignore them typically face 2–4 weeks of extra integration work per channel.

Q: How long must I keep consumer data from orders?

A: Under the draft MOFCOM e-commerce logistics service specification, consumer-related data should be retained for at least 1 year, and contracts and receipts involving consumers for not less than 3 months. Where other laws or your own warranty terms require longer, those longer periods apply.

Q: What is "three-document matching" in cross-border e-commerce?

A: It is the customs requirement that the transaction document (order), payment document and logistics document be transmitted through the Single Window and match before bonded goods clear. Under GACC Announcement No. 194 of 2018, your ERP and WMS must generate and push all three document types, and mismatches stall clearance.

Q: Who is responsible for PIPL compliance — me or my software vendor?

A: You are. Under PIPL, your business is the personal information processor and your ERP/WMS vendors are entrusted processors. Consent, minimum-necessity limits and the 1-year retention duty sit with your brand, so vendor contracts must specify processing scope, security measures aligned to GB/T 22239 and data return or deletion on exit.

Q: What is "one pool of stock" and why does it matter?

A: It is the unified inventory model where a single stock position feeds all sales channels with real-time synchronization and overselling protection. Practitioners commonly target sub-minute sync latency, a 5–10% safety-stock buffer and above 99% inventory accuracy (industry estimates, 2026) — without it, each channel overstates availability and overselling follows.

Q: How much should I budget for a China e-commerce systems stack?

A: As planning estimates for 2026: SaaS ERP runs roughly RMB 3,000–30,000 per year and SaaS WMS RMB 5,000–50,000 per year, while private deployments range from RMB 100,000–1,000,000 (ERP) and RMB 200,000–2,000,000 (WMS). Add RMB 50,000–500,000 for warehouse hardware if you run your own facility.

Q: How long does implementation take?

A: SaaS deployments typically go live in 2–8 weeks, including channel connector setup and testing. Private, customized deployments run 2–6 months because of data migration and interface development. Cross-border sellers should add 2–4 weeks for customs three-document testing with their bonded warehouse before launch.

Q: Do pallet and barcode standards really affect my software?

A: Yes, materially. China's supply-chain policy promotes GS1-linked pallet, carton and logistics-unit barcodes on 1200mm × 1000mm pallets and 600mm × 400mm totes. Non-standard packaging creates scanning exceptions in the WMS, which degrades inventory accuracy and slows receiving — the digital and physical layers must align.

Q: Can CnBusinessHub help me choose and configure these systems?

A: Yes. Our advisory team can help you evaluate ERP and WMS options against your channel mix, cross-border model and PIPL obligations, and coordinate with qualified local implementation partners. We typically scope a china ecommerce erp wms inventory roadmap across 2–3 weeks before vendor selection begins.

Conclusion

Three takeaways for foreign brands planning a 2026 China launch:

1. Treat GB/T data-exchange standards as your integration baseline. GB/T 40094.3-2021 for orders and inventory, GB/T 26772 and GB/T 18768 for warehousing — voluntary on paper, de facto required in practice (GB/T 40094.3-2021, SAMR).
2. Design for "one pool of stock" from day one. A unified inventory pool with sub-minute sync and a 5–10% safety buffer prevents the overselling that damages marketplace performance scores.
3. Build compliance into the stack, not after it. PIPL processor duties, the 1-year consumer-data retention norm and customs three-document matching all shape system requirements before go-live (GACC Announcement No. 194 of 2018).

For personalized guidance on your China e-commerce licensing pathway, contact the CnBusinessHub advisory team at consult@CnBusinessHub.com to book a consultation.

Written by the CnBusinessHub Advisory Team, China market-entry advisors since 2019 — 1,500+ foreign enterprises guided across 16+ cities.

Last updated: 2026-10-11 | Next review: April 2027

Sources

1. GB/T 40094.3-2021 E-commerce Data Transaction Part 3: Data Interface Specification (SAMR)
2. GB/T 26772 Transport and Warehousing Business Data Exchange Application Specification (SAMR)
3. GB/T 18768 Digital Warehouse Application System Specification (MOFCOM)
4. E-commerce Logistics Service Specification (Draft for Comment) (MOFCOM)
5. YD/T 2457.2.2-2016 and SB/T 10378.3-2004 Data Exchange Format Standards (SAMR)
6. National Standardization System Development Plan 2016-2020, State Council Document No. 33 of 2016 (MOFCOM)
7. Supply Chain System Construction Notice (NDRC)
8. GACC Announcement No. 194 of 2018 on Cross-Border E-Commerce Three-Document Matching (General Administration of Customs)
9. E-Commerce Law of the PRC (Cyberspace Administration of China)

Related Reading

• E-commerce Integration for China Sourcing: Amazon, Shopify & Multi-Channel Guide
• Fulfillment Model Comparison 2026: Full-Managed vs Semi-Managed vs Self-Ship