来自 TikTok Shop 官方资料快照 ·
- 当前资料结构化阅读页
- 固定快照已留存，可追溯
- 官方原文可核对
资料正文
§1 For the US Market: Introducing 4PL Express Shipping
Expected launch date: August 12, 2026 Change type: Non-breaking enhancement Affected audience: Apps that generate TikTok Shipping labels for eligible US orders Developer action: Review how your app processes multiple shipping services and remove any hardcoded shipping service IDs.
§2 Overview
TikTok Shop plans to begin a phased rollout of 4PL Express shipping for eligible US orders on August 12, 2026. During the rollout period, the service will be available only to invited sellers and ISVs. The initial service will use UPS 2nd Day Air and expand the shipping options available through the existing TikTok Shipping label workflow.
This update does not add a new API version, order status, scope, or required request field. Apps that already process the full shipping_services list and pass a returned service ID to Create Packages should remain compatible.
§3 What is changing
Eligible US sellers can enable Express shipping in their shipping template. After the service is enabled, the existing Get Eligible Shipping Service API may return an Express option in addition to Standard shipping.
| Area | Current behavior | Expected behavior after launch |
|---|---|---|
| Service availability | Eligible 4PL orders use the Standard shipping services returned by TikTok Shop. | Eligible orders may receive Standard and Express options based on seller subscription, package attributes, and destination. |
| Service identification | Apps use the returned shipping service ID and provider information. | Apps must continue to treat the returned IDs and names as dynamic values. Express introduces additional service values, not a new response structure. |
| Package creation | Apps can pass shipping_service_id to select an eligible service or omit it to use the default service. | The same behavior continues. To select Express, pass the Express service ID returned for that order. |
| Order shipping type | Orders that require a TikTok Shipping label use shipping_type = TIKTOK. | Express orders continue to use shipping_type = TIKTOK. No new shipping_type value is introduced. |
§4 Affected APIs
Affected APIs
| API | Role in the workflow | Expected impact |
|---|---|---|
POST /fulfillment/202309/orders/{order_id}/shipping_services/query | Returns eligible shipping services. | shipping_services may include an Express option. The response shape is unchanged. |
POST /fulfillment/202309/packages | Creates a package and generates the selected shipping service. | Use the existing shipping_service_id field to select the returned Express service. |
GET /fulfillment/202309/packages/{package_id}/shipping_documents | Returns the label document and tracking number. | No contract change. Continue to process doc_url and tracking_number. |
§5 Who needs to act
| Integration type | Impact | Required action |
|---|---|---|
| Direct ERP, OMS, or shipping apps that call TikTok Shop fulfillment APIs | Your app may receive more than one eligible shipping service. | Review service parsing, selection, storage, and package creation logic. |
| ERP, OMS, or shipping apps in the Shopify ecosystem that generate TikTok Shipping labels | Your existing TikTok label workflow may need to expose or select the Express option. | Confirm that the app retrieves the TikTok Shop order ID and dynamically uses the returned shipping service ID. |
| Connector apps that only sync orders and fulfillment statuses | No direct API change unless the app uses service IDs or names for routing or tags. | Review only if your app branches on shipping service values. |
| Apps that do not support US 4PL fulfillment | No impact. | No action is required. |
§6 How to integrate
#§7 1. Identify the TikTok Shipping workflow
1. Identify the TikTok Shipping workflow
Start label generation after the order reaches AWAITING_SHIPMENT. Use the latest order details to confirm that shipping_type = TIKTOK.
§8 2. Query all eligible services
2. Query all eligible services
Call POST /fulfillment/202309/orders/{order_id}/shipping_services/query with the package dimensions, weight, and applicable order line item IDs.
Process every item in shipping_services. Do not assume that the response contains one service or that a previously stored ID remains eligible.
| Response field | Purpose | Integration guidance |
|---|---|---|
shipping_services[].id | Identifies the eligible service for this request. | Use the returned value in shipping_service_id. Do not hardcode it. |
shipping_services[].name | Displays the shipping service name. | Use it for display. Do not use an exact display string as the only routing condition. |
shipping_services[].is_default | Identifies the default service. | Honor the default if your app does not provide a service selection experience. |
shipping_services[].earliest_delivery_days and latest_delivery_days | Provide the estimated delivery range. | Display or use these values instead of maintaining a fixed Express SLA in your app. |
shipping_services[].price and currency | Provide the estimated shipping price. | Present both values together when the user selects a service. |
§9 3. Create the package with the selected service
3. Create the package with the selected service
Call POST /fulfillment/202309/packages and pass the selected service ID in shipping_service_id. If you omit this field, TikTok Shop uses the default eligible service.
§10 4. Retrieve and print the label
4. Retrieve and print the label
Use the returned package_id to call GET /fulfillment/202309/packages/{package_id}/shipping_documents. Continue to send the returned doc_url and tracking_number to your warehouse or label-printing workflow.
Do not reproduce TikTok Shop eligibility rules in your app. Query eligible services for each order and package. Express availability can vary by seller subscription, package profile, and destination.
§11 5. Handle Express restrictions
5. Handle Express restrictions
- Express shipping does not support dangerous goods.
- Express shipping does not support P.O. box destinations.
- Collection by TikTok does not provide Express pickup. Express options for CBT-configured warehouses apply only to 4PL orders and follow the regular carrier handoff workflow.
- No new signature request parameter is introduced in the current API contract. Use the returned shipping service and generated shipping document.
§12 6. Test the updated workflow
6. Test the updated workflow
| Test scenario | Expected result | What to verify |
|---|---|---|
| Standard-only 4PL seller | The eligible service response continues to support the existing Standard workflow. | No regression in package creation or label retrieval. |
| Express-enabled seller with an eligible order | The response includes an Express service. | Your app displays or selects the service and passes the returned ID. |
| Response with multiple eligible services | Your app processes every response item. | No first-item, single-service, or hardcoded-ID assumption. |
| Dangerous goods or P.O. box destination | Express is not available. | Your app continues with another eligible service or handles no-service error 21011037. |
| Express package and shipping document | Package creation succeeds and a label document is returned. | The warehouse can retrieve and print the label using the existing workflow. |
§13 Timeline and rollout
| Date | What happens |
|---|---|
| Before August 12, 2026 | Affected apps review compatibility, remove hardcoded shipping service IDs, and complete Express test scenarios. |
| Expected August 12, 2026 | 4PL Express shipping becomes available to eligible US sellers and orders. |
This release does not remove Standard shipping, deprecate an API version, or require a Partner Center declaration. There is no mandatory migration deadline for apps that do not support Express.
§14 Impact if your app does not update
Impact if your app does not update
- Apps that process only one service may not display or select Express.
- Apps that hardcode a Standard service ID may fail to create a package when that ID is not eligible for the order.
- Apps that route by an exact service name may classify Express orders incorrectly.
§15 FAQ
#§16 Is this a breaking change?
Is this a breaking change?
No. The update adds a shipping option to the existing response and package creation workflow. It does not remove or rename fields or change required parameters.
§17 Do I need to upgrade to a new API version?
Do I need to upgrade to a new API version?
No. Continue to use the existing v202309 fulfillment APIs listed in this document.
§18 Does Express introduce a new shipping type?
Does Express introduce a new shipping type?
No. Orders that require TikTok Shipping labels continue to use shipping_type = TIKTOK.
§19 Can I store one Express shipping service ID?
Can I store one Express shipping service ID?
No. Query eligible services for each order and use the returned ID. Do not assume that an ID remains eligible for another order or package.
§20 Does my app need a new parameter for signature service?
Does my app need a new parameter for signature service?
No new signature parameter appears in the current API contract. Use the selected shipping service and the generated label document returned by the existing APIs.
§21 Does this affect non-US or Seller Shipping integrations?
Does this affect non-US or Seller Shipping integrations?
No. This rollout applies to eligible US 4PL shipping workflows. Apps that do not generate TikTok Shipping labels are not directly affected.
§22 API documentation
https://partner.tiktokshop.com/docv2/page/get-eligible-shipping-service-202309 https://partner.tiktokshop.com/docv2/page/create-packages-202309 https://partner.tiktokshop.com/docv2/page/get-package-shipping-document-202309 https://partner.tiktokshop.com/docv2/page/get-order-detail-202507