This webhook is triggered when the FBT multi-channel-fulfillment order status has changed/updated.
Prerequisite: The Fulfilled by TikTok(FBT) Info API scope is enabled in Partner Center. For more information, refer to Access Scope.
Authorizations
Section titled “Authorizations”Request Bodyrequired
Section titled “Request Bodyrequired”object
The ID of the webhook type.
The ID of the notification.
The open_id of the seller. For more information, refer to Authorization overview.
The UNIX timestamp when this webhook was triggered.
object
MCF order information
object
The corresponding order ID in your OMS.
A unique ID that identifies different MCF orders
Once the order has been shipped, the consign_orders field will display the consignment details of the order.
object
consign order unique id
The tracking number of this consign order. If the order has not yet been handed over to the logistics carrier, this field may be a null value.
The status of this consign order
Possible Status Enumerations
- SHIPPED - Order has been shipped out from the warehouse
- HANDOVER - Order has been received by the logistics carrier and is in transit
- CLOSED - Order has been closed
- LOST - Order is lost
- DAMAGE - Order is damaged
- COMPLETED - Order has been completed
- ABNORMAL - There is an issue related to this order and cannot be fulfilled.
The goods id and quantity in this consign order.
object
Identifier for goods generated by Fulfilled by TikTok systemgoods id
The goods quantity in this consign order
This field indicates whether a consign order has been canceled by the FBT platform. If the value is true, it means the order has been canceled by the platform; if it is false, it means the order has been canceled by your OMS.
This field displays the reason for order stalling. When a consign order is in an abnormal status (such as ABNORMAL, LOST, etc.), specific issue reasons will be shown here.
The time when the mcf order is created
Responses
Section titled “Responses”Return HTTP 200 to acknowledge receipt.