stable本次发布有变化全部展示
来自 TikTok Shop 官方资料快照 ·
- 当前资料结构化阅读页
- 固定快照已留存，可追溯
- 官方原文可核对
资料正文
§1 What OMS apps do
Order management system (OMS) apps help sellers manage post-order operations after a TikTok Shop order is created. Use this page when your app imports orders, manages order status, coordinates 3PL or 4PL fulfillment, syncs shipping and tracking updates, handles split or combined packages, or needs to block fulfillment during the On Hold period. If your app mainly connects TikTok Shop with another commerce channel, start with the Connector or MCA requirements. If your app mainly provides shipping capacity or carrier services, start with the Shipping and Fulfillment requirements. If your app includes catalog, inventory, order, fulfillment, finance, and returns in one back-office system, start with the ERP requirements and use this OMS page for the order-fulfillment subset.
| App type | Primary purpose | Where this OMS page applies |
|---|---|---|
| Connector or MCA | Connect TikTok Shop with external commerce channels and keep shop, product, inventory, price, and order data synchronized. | Use the shared Connector baseline for shop connection, catalog, listing, and generic order sync. Apply OMS-specific rows only when the app also manages fulfillment, split/combine, or On Hold handling. |
| Shipping or Fulfillment | Provide logistics, carrier, or package execution capabilities. | Use fulfillment API and shipping-provider requirements as the primary source. Apply OMS-specific rows when the app also exposes an order management workflow to sellers. |
| OMS | Operate seller order workflows after order creation. | Use this page for 3PL/4PL fulfillment, shipment update sync, split/combine scenarios, On Hold compliance, sample order mapping, and gift/giveaway order mapping. |
| ERP | Run broad back-office operations across catalog, inventory, order, fulfillment, finance, and returns. | Use ERP requirements as the broad category page. Use this OMS page as the focused reference for order and fulfillment scenarios. |
§3 Critical: On Hold compliance
When TikTok Shop orders are placed, they enter a 1-hour On Hold period before sellers should fulfill them. OMS apps that process seller orders must recognize the On Hold status, display it correctly, and block any fulfillment action while the order is On Hold. Sellers installing the app should not see an On Hold support warning caused by the app integration.
| Scenario | Required action |
|---|---|
| The app processes seller orders or lets sellers fulfill orders. | Implement On Hold handling in order import, order status sync, and fulfillment actions. Block shipping, package creation, and other fulfillment actions until the order becomes fulfillable. |
| The app does not process orders for sellers. | Complete the On Hold Status Developer Declaration in Partner Center. Suggested entry path: Partner Center > App & Service > select the app or service > App review or pre-publish checklist > On Hold Status Developer Declaration. If the exact menu label differs by market or review flow, search for the declaration title in Partner Center. |
| The app is being tested in Development Shop. | Create a test order, confirm the initial status is On Hold, then validate the transition to Pending Shipment before allowing fulfillment. See the Development Shop manual order status update guide. |
Integration references: Order API overview, Get Order List, Get Order Detail, and Order status change webhook.
§4 Terms and tag conventions
| Term or tag | Meaning in this page |
|---|---|
| 3PL | Third-party logistics. In this OMS context, the external platform helps sellers fulfill and ship orders, then syncs shipping and tracking information back to TikTok Shop. |
| 4PL | Fourth-party logistics or fulfillment orchestration. In this OMS context, the app may coordinate fulfillment API flows or let sellers complete fulfillment from Seller Center before syncing package state. |
| Order Management tag | Use for order import, order status sync, On Hold handling, sample order mapping, gift or giveaway order mapping, and other order-data workflows. |
| Fulfillment tag | Use together with Order Management when the row requires fulfillment APIs, package shipping, tracking updates, split packages, or combined packages. |
| Promotion Orders tag | Reserve for promotion-domain use cases that require Promotion Information(434884), such as Gift with Purchase or virtual bundle setup. ORD-SYNC-GIFT remains an Order Management row because it uses Order Information(430276) and covers order mapping, not promotion creation. |
§5 OMS-specific quick reference
The rows below keep the original use case IDs and parent use case links, but add a direct Integration guide column so developers do not have to infer the implementation path from the OpenLearn parent page alone. Suffixes such as 3PL2 and 4PL2 are inherited scenario labels, not sequence numbers. Read the "Trigger or edge case" column to understand when each row applies.
| Capability | Start with these use cases | Main scopes | Integration guides |
|---|---|---|---|
| 3PL fulfillment and shipment update sync | ORD-3PL-FULFILL, ORD-3PL-UPDATE | Fulfillment Basic(430340) Order Information(430276) | Fulfillment API overview Mark Package As Shipped |
| 4PL fulfillment support | ORD-4PL-FULFILL | Fulfillment Basic(430340) Order Information(430276) | Fulfillment API overview |
| Split packages | ORD-SPLIT-API, ORD-SPLIT-3PL2, ORD-SPLIT-4PL2 | Fulfillment Basic(430340) Order Information(430276) Package Split And Combine, when required by the endpoint | Split Orders Mark Package As Shipped Access scope |
| Combined packages | ORD-COMBINE-3PL1, ORD-COMBINE-3PL2, ORD-COMBINE-4PL2 | Fulfillment Basic(430340) Order Information(430276) Package Split And Combine, when required by the endpoint | Fulfillment API overview Access scope |
| Order-state and special order mapping | ORD-SYNC-ONHOLD, ORD-SYNC-SAMPLE, ORD-SYNC-GIFT | Order Information(430276) | Order API overview Get Order Detail Development Shop manual order status update guide |
§6 Fulfillment model
| Use case ID | Required | Tags | Scopes | What the OMS must do | Solution guide | Integration guide | Trigger or edge case |
|---|---|---|---|---|---|---|---|
| ORD-3PL-FULFILL | Yes | Order Management Fulfillment | Fulfillment Basic(430340) Order Information(430276) | Sync orders to the OMS and let sellers fulfill and ship from the OMS or connected fulfillment platform. | 3PL fulfillment use cases | Fulfillment API overview Mark Package As Shipped | Required when the OMS is the place where sellers arrange shipment or submit shipping information. |
| ORD-3PL-UPDATE | Yes | Order Management Fulfillment | Fulfillment Basic(430340) Order Information(430276) | Sync updated shipping and tracking information back to TikTok Shop after an order has been dispatched. | 3PL fulfillment use cases | Fulfillment API overview | Required when sellers or fulfillment operators can edit carrier, tracking, or delivery information after dispatch. |
| ORD-4PL-FULFILL | No | Order Management Fulfillment | Fulfillment Basic(430340) Order Information(430276) | Optionally implement 4PL API flows or let sellers fulfill orders from Seller Center, then keep package state aligned. | 4PL fulfillment use cases | Fulfillment API overview | Optional when the app supports 4PL orchestration rather than direct seller fulfillment inside the OMS. |
§7 Split order scenarios
| Use case ID | Required | Tags | Scopes | What the OMS must do | Solution guide | Integration guide | Trigger or edge case |
|---|---|---|---|---|---|---|---|
| ORD-SPLIT-API | Yes | Order Management Fulfillment | Fulfillment Basic(430340) Order Information(430276) Package Split And Combine, when required by the endpoint | Split item-level fulfillment into separate packages and ship the packages through API flow. | Split order use cases | Split Orders Mark Package As Shipped Access scope | Required when sellers split an order from the OMS before shipping. |
| ORD-SPLIT-3PL2 | No | Order Management Fulfillment | Fulfillment Basic(430340) Order Information(430276) Package Split And Combine, when required by the endpoint | Recognize and fulfill split packages when sellers split the order in TikTok Shop Seller Center first. | Split order use cases | Split Orders Fulfillment API overview | 3PL edge case: Seller Center creates the split before the OMS fulfills the resulting packages. |
| ORD-SPLIT-4PL2 | No | Order Management Fulfillment | Fulfillment Basic(430340) Order Information(430276) Package Split And Combine, when required by the endpoint | Support package sync when sellers split an order in Seller Center before a shipping or 4PL application fulfills it. | Split order use cases | Split Orders Fulfillment API overview | 4PL edge case: Seller Center split happens before the shipping application executes fulfillment. |
§8 Combine order scenarios
| Use case ID | Required | Tags | Scopes | What the OMS must do | Solution guide | Integration guide | Trigger or edge case |
|---|---|---|---|---|---|---|---|
| ORD-COMBINE-3PL1 | No | Order Management Fulfillment | Fulfillment Basic(430340) Order Information(430276) Package Split And Combine, when required by the endpoint | Optionally let sellers combine multiple orders into a single shipment from the OMS or connected fulfillment platform. | Combine order use cases | Fulfillment API overview Access scope | 3PL scenario: the OMS is the system where sellers combine orders. |
| ORD-COMBINE-3PL2 | No | Order Management Fulfillment | Fulfillment Basic(430340) Order Information(430276) Package Split And Combine, when required by the endpoint | Recognize and fulfill combined packages when sellers combine orders in TikTok Shop Seller Center first. | Combine order use cases | Fulfillment API overview Access scope | 3PL edge case: Seller Center creates the combined shipment before the OMS fulfills it. |
| ORD-COMBINE-4PL2 | No | Order Management Fulfillment | Fulfillment Basic(430340) Order Information(430276) Package Split And Combine, when required by the endpoint | Support package sync when sellers combine orders in Seller Center before a shipping or 4PL application fulfills them. | Combine order use cases | Fulfillment API overview Access scope | 4PL edge case: Seller Center combination happens before the shipping application executes fulfillment. |
§9 Order-state and special order mapping
| Use case ID | Required | Tags | Scopes | What the OMS must do | Solution guide | Integration guide | Trigger or edge case |
|---|---|---|---|---|---|---|---|
| ORD-SYNC-ONHOLD | Yes | Order Management | Order Information(430276) | Support the On Hold status and block sellers from fulfilling orders during the 1-hour On Hold period. If the app does not process seller orders, complete the On Hold Status Developer Declaration in Partner Center instead of updating an order-processing flow that the app does not have. | Order sync use cases | Order API overview Get Order Detail Development Shop manual order status update guide | Critical compliance row. Applies to any app that imports orders, displays order status, or allows fulfillment actions. |
| ORD-SYNC-SAMPLE | Yes | Order Management | Order Information(430276) | Correctly map free sample orders from TikTok Shop and sync them to the OMS without treating them as regular paid orders when downstream logic differs. | Order sync use cases | Get Order Detail | Required when sample orders appear in the seller's OMS workflow. |
| ORD-SYNC-GIFT | Yes | Order Management | Order Information(430276) | Correctly map gift or giveaway products from TikTok Shop and sync them to the OMS. If the app also creates Gift with Purchase or other promotion rules, check the Promotion Orders requirements separately. | Order sync use cases | Get Order Detail | Tag corrected from Promotion Orders to Order Management because this row uses Order Information(430276) and covers order mapping. |