Split Fulfillment Order
POST/api/fulfillment-orders/:fulfillmentOrder/split
Manually carve an unsubmitted (proforma) FulfillmentOrder into a NEW open/unsubmitted FO sized to the supplied per-line quantities. The original FO keeps the remainder. This is pure FulfillmentOrderLine budget redistribution — neither FO is submitted as a result (split and submit are separate concerns). To dispatch part of an order, split it then submit/hold each piece.
orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Only valid while the FO is open + unsubmitted, or open + rejected (a provider rejection leaves no carrier order behind, so removing a line to re-submit the rest is still a pre-dispatch edit). Allocations are SOL-linked, so no allocation moves on a split.
Request body
lines(required, array, min 1): the quantities to carve into the new FO.lines[].sales_order_line_id(required, integer, exists) — a SOL present on this FO.lines[].quantity(required, integer, min 1) — must not exceed the FOL'sremaining_quantity, and must not carve the FO's entire remaining budget (that would leave nothing behind — submit/fulfill the whole FO instead).
Responses
201— the NEW carved FO (open/unsubmitted).422— a quantity exceeds the FOL remaining budget, or validation failed.409— the FO is not open + unsubmitted/rejected, or the request would carve the entire FO (nothing left to split).
Required permission: fulfillment_orders.update (Fulfillment Orders → Edit) and fulfillment_orders.index (Fulfillment Orders → View). A token also needs its orders scope; the owner needs these role permissions.
Request
Responses
- 201
- 401
- 403
- 404
- 409
- 422
- 429
Created
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden
Response Headers
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Conflict
Response Headers
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.