You have a Tmall or Tmall Global store generating revenue in China. You have NetSuite as your ERP. And right now, someone on your team is manually downloading CSVs from Tmall’s seller center and keying data into NetSuite every week.
This guide walks through the practical steps to connect Tmall to NetSuite, the decisions you need to make along the way, and the pitfalls that trip up most brands.
Why Connect Tmall to NetSuite?
Tmall is the largest B2C marketplace in China. For global brands, it is often the primary sales channel, generating millions in annual revenue. But Tmall’s seller center is designed for Chinese marketplace operations, not for feeding data into Western ERP systems.
Without integration, you face:
– Delayed financial data — your NetSuite instance is always a week or more behind actual Tmall performance
– Manual errors — data entry mistakes in order volumes, revenue, or inventory levels compound over time
– No real-time inventory sync — overselling on Tmall because NetSuite does not reflect current stock, or holding excess safety stock because you cannot trust the numbers
– Slow month-end close — finance spends days reconciling Tmall data against NetSuite records
What Data Flows Between Tmall and NetSuite
Tmall to NetSuite (Inbound)
– Orders: Order ID, items, quantities, prices, customer shipping info, payment status
– Payments: Settlement amounts, platform commission deductions, payment timing
– Returns and refunds: Return requests, refund amounts, reason codes
– Inventory updates: Stock levels, reserved quantities for promotions
– Marketing data: Ad spend by campaign, traffic by source (optional but valuable)
NetSuite to Tmall (Outbound)
– Product catalog: New SKUs, price updates, product descriptions
– Inventory levels: Available stock pushed to Tmall to prevent overselling
– Fulfillment updates: Tracking numbers, shipment status
– Price adjustments: Promotional pricing, coupon configurations
Integration Approaches
Option 1: Direct API Integration
How it works: Your engineering team builds a custom connector using the Taobao Open Platform API (which covers Tmall) and NetSuite’s SuiteTalk/REST APIs.
Requirements:
– Taobao Open Platform developer account (requires Chinese business entity or authorized partner)
– NetSuite administrator access with Token-Based Authentication enabled
– Engineering team with experience in both platforms’ APIs
– Ongoing maintenance capacity
Timeline: 3-6 months for initial build, ongoing maintenance.
Best for: Large enterprises with dedicated China tech teams who need highly customized data flows.
Challenges:
– Taobao Open Platform documentation is primarily in Chinese
– API rate limits require careful request management
– Tmall API changes happen frequently, often with limited advance notice
– Handling edge cases (partial refunds, split shipments, cross-border vs domestic orders) adds complexity
Option 2: iPaaS Middleware
How it works: An integration platform (Celigo, Boomi, MuleSoft, Workato) connects Tmall and NetSuite using pre-built or custom connectors.
Requirements:
– iPaaS subscription
– Tmall and NetSuite API credentials
– Integration specialist to configure data mappings
Timeline: 1-3 months.
Best for: Brands that already use an iPaaS for other integrations and have in-house integration expertise.
Challenges:
– Most Western iPaaS platforms lack native Tmall connectors — you will likely need custom development
– Data transformation rules for Chinese marketplace nuances (RMB settlement, fapiao requirements, Golden Tax integration) are rarely pre-built
– Performance at scale can be an issue during peak events (Double 11, 618)
Option 3: Purpose-Built China Integration Platform
How it works: A platform specifically designed for Chinese marketplace data handles the Tmall connection, data normalization, and NetSuite delivery.
Requirements:
– Platform subscription
– Tmall seller center authorization
– NetSuite API access
Timeline: 2-4 weeks.
Best for: Brands that want fast deployment without building China-specific integration expertise in-house.
Advantages:
– Pre-built Tmall connector maintained by China ecommerce specialists
– Data normalization handles Tmall-specific formats, settlement timing, and currency conversion
– Scales for peak events without custom engineering
– Same platform extends to JD, Douyin, and other marketplaces when you expand
Step-by-Step: Setting Up the Integration
Regardless of which approach you choose, the setup follows the same logical steps:
Step 1: Define Your Data Requirements
Before touching any APIs, align your operations, finance, and technology teams on:
– Which data fields must flow between systems?
– What is the acceptable latency? (Real-time, hourly, daily?)
– How should Tmall data map to your NetSuite chart of accounts?
– Do you need historical data migration, or start from today?
Step 2: Configure Tmall API Access
1. Register on the Taobao Open Platform (open.taobao.com)
2. Create an application and request the required API permissions (trade, item, logistics, refund)
3. Complete the app review process (typically 1-2 weeks)
4. Authorize your application to access your Tmall store’s data via the seller center
5. Store your App Key, App Secret, and Session Key securely
Note: If you are a foreign brand, you will likely need your Tmall Partner (TP) or a local entity to register the application.
Step 3: Configure NetSuite Access
1. Enable Token-Based Authentication in your NetSuite account (Setup > Company > Enable Features)
2. Create an integration record for the Tmall connector
3. Generate a token ID and token secret for API access
4. Create a custom role with the minimum required permissions (transactions, inventory, customer records)
5. Test the connection with a simple API call
Step 4: Build the Data Mapping
This is the most critical step. Map every Tmall data field to its NetSuite equivalent:
– Tmall order status “WAIT_SELLER_SEND_GOODS” maps to NetSuite Sales Order status “Pending Fulfillment”
– Tmall payment amount (after commission) maps to NetSuite revenue line
– Tmall commission amount maps to a NetSuite expense line under your “Platform Fees” account
– Tmall product SKU maps to NetSuite Item record via your master SKU table
Document every mapping decision. This becomes your integration specification.
Step 5: Handle the Edge Cases
The standard happy path (order placed, paid, shipped, received) is straightforward. The complexity lives in:
– Partial refunds — Tmall allows partial refunds on multi-item orders; NetSuite needs these as credit memos or return authorizations
– Cross-border vs domestic — Tmall Global (cross-border) has different tax treatment than domestic Tmall
– Promotional pricing — Coupons and platform subsidies reduce the settlement amount but should not reduce the reported gross price in some accounting treatments
– Split shipments — One order shipped from multiple warehouses
– Currency timing — RMB settlement converted to USD at what rate? Settlement date or order date?
Step 6: Test Thoroughly
Run parallel reporting for at least one full month:
– Process orders through both the manual and automated paths
– Compare NetSuite records against Tmall seller center reports
– Verify financial totals match within acceptable tolerance
– Test failure scenarios (API timeout, duplicate order, cancelled order after shipment)
Step 7: Go Live and Monitor
Switch off manual data entry only after parallel testing confirms accuracy. Set up monitoring for:
– API error rates and timeout frequency
– Data sync latency (time between Tmall event and NetSuite record creation)
– Reconciliation exceptions (orders that failed to sync)
– Settlement amount discrepancies
What to Watch For Post-Launch
Tmall API changes. Taobao Open Platform updates its APIs regularly. Subscribe to their developer notices and budget engineering time for quarterly connector updates.
Peak event scaling. Double 11 can generate 10-50x normal order volume in 24 hours. Your integration must handle the spike without dropping orders. Test before every major promotion.
New Tmall features. Tmall regularly adds new transaction types (livestream sales, subscription orders, Tmall Luxury Pavilion). Each may require new data mappings.
—
Digate provides a pre-built Tmall-to-NetSuite integration that handles all of the above — data extraction, normalization, edge cases, and ongoing API maintenance. We also connect JD, Douyin, Pinduoduo, and 30+ other platforms. [Book a demo](https://calendly.com/sanja-digate/30min) to see it running with your data.