Restore Voided Shipment
POST/api/sales-order-fulfillments/:salesOrderFulfillmentId/restore
Restore (un-void) a previously voided shipment. No request body.
orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
The shipment returns to its pre-void status (typically submitted), and the void audit fields (voided_at, voided_by, void_reason) are cleared.
Side effects:
- Restoring back to a shipped status re-creates the inventory movements and cost-layer consumption that the void reversed, and re-marks allocations as fulfilled.
- If the shipment's sales-channel fulfillment (e.g. Shopify) was cancelled during the void, the channel submission is reset so a fresh fulfillment is pushed to the channel on the next sync.
- Product inventory and average-cost figures are recalculated in the background.
Errors (422):
- the shipment is not voided (nothing to restore)
- the shipment is part of a multi-shipment merge group and cannot be restored individually
- insufficient allocation to restore a shipped fulfillment (the error names the SKU and quantities)
Requires the orders:write token scope.
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 Entity
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.