Send Without Sales Channel Shipping Label
POST/api/sales-orders/:salesOrder/channel-shipping-labels/:label/skip
Send the order to its warehouse WITHOUT the channel's label ("Send without Walmart label"): the 3PL buys its own postage. For a label that is held (for example waiting for a box size) or whose purchase failed, and that was never paid for. No request body. The label becomes skipped, a note is added to the sales order, and the order is dispatched again.
orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Authentication: Requires Bearer token.
Requires the sales_orders.update permission.
Only labels whose can_skip is true in List Sales Channel Shipping Labels can be skipped. A label already paid for must be voided first. TikTok Shop labels cannot be skipped: TikTok ships those orders on its own label. An ordinary dispatch never skips the label; this is the only way to send a held order without it.
Response fields: status (the label's status after the call, skipped on success).
Errors: 422 with a message when the label does not belong to the order, is paid for, or cannot be skipped; 404 when the sales order does not exist.
Path parameters:
- salesOrder (required): Sales order ID.
- label (required): the label's
label_id.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Content
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.