Identify the market and seller program first
TikTok Shop fulfillment rules depend on the market, seller program, order type and permitted shipping arrangement. Before connecting a China warehouse, establish whether the proposed origin, carrier and product category are eligible for the seller's actual account. A shipping policy for one market does not grant permission to use the same route everywhere.
Create a policy record containing the shop market, seller entity, domestic or cross-border program, approved dispatch origin, supported service and current policy reference. Give the record an owner and a review date. The warehouse's operating instructions should refer to that approved combination rather than to “TikTok orders” as one universal category.
Read deadlines as scoped platform requirements
The US Fulfillment Policy, dated September 28, 2026 and reviewed here on October 15, gives a specific example. For regular US orders, it requires In Transit status within two business days of Awaiting Shipment and Delivered status within six business days of Awaiting Shipment. It also specifies automatic cancellation if an order has not reached Awaiting Collection within five business days. Other order classes have different handling rules.
These US requirements are not a general China-to-US delivery promise or a global TikTok rule. Check the current policy, business-day calendar and any applicable exceptions for the actual account before agreeing an operating plan.
Distinguish packing from qualifying dispatch
A warehouse's packed event proves that packing was recorded. It does not automatically prove that the platform recognizes dispatch. The US policy identifies qualifying dispatch evidence, including carrier acceptance and certain eligible manifest or recognized in-app scan events. The actual integration must transmit an event the platform accepts.
Map the relevant events explicitly:
| Operational event | Evidence to retain | Question for the integration test |
|---|---|---|
| Order accepted | Shop order reference and accepted timestamp | Was the correct order imported once? |
| Stock allocated | Item and quantity reservation | Can unavailable stock block release? |
| Parcel packed | Pack record and assigned tracking reference | Does a correction reach the right order? |
| Qualifying dispatch | Accepted carrier, manifest or supported scan evidence | Does the shop display the required status? |
| Delivery or exception | Service event with time and location context | Is the update accepted and visible? |
An internal status named “shipped” is insufficient evidence on its own. GS1 EPCIS provides a useful vocabulary for discussing event data, but the platform's rules determine which events qualify for its deadlines.
Work backward from the recognized event
Once the permitted route is confirmed, plan backward from the relevant deadline through carrier handoff, packing, allocation and order import. Include the carrier's collection calendar and the shop's applicable holiday calendar. Keep the order's original platform timestamp intact; do not restart the clock when the warehouse receives a delayed import.
For an illustrative pilot, compare three otherwise identical test orders: one available immediately, one held for an address issue and one received shortly before a collection cutoff. Record where each spends time. The purpose is to discover whether the workflow can meet the approved requirement, not to manufacture a favorable average by excluding held orders.
Build a visible exception queue
Assign responsibility for missing tracking, rejected carrier codes, stock shortages, cancellations and lost integration access. Show the remaining time against the applicable deadline and identify the next required action. A retry loop should not conceal a tracking update that the shop continues to reject.
Define a cancellation race procedure. If a cancellation arrives after packing but before handoff, staff need to know whether the parcel can be stopped and how inventory is restored. After handoff, the response depends on the carrier and platform workflow; an automatic stock reversal could incorrectly make dispatched units available again.
Verify the complete order before launch
Use a small approved pilot to check status display, accepted tracking, cancellation handling and delivery exceptions inside the actual shop account. Retain screenshots or exported records with the test order IDs and timestamps. A successful warehouse import alone does not validate the customer-facing order lifecycle.
For after-sales needs, agree a separate return route that is permitted and practical for that market. FulfillNexa's overseas delivery points do not receive return or inspection goods. Keep that boundary clear when assessing whether the proposed shop program can be supported.
Sources and verification links
Operational rules can change. Check the linked primary sources and confirm shipment-specific requirements before booking.
- TikTok Shop US Fulfillment PolicyTikTok Shop US Seller Academy
- EPCIS and CBVGS1