Create Fulfillment Order Merge Group
POST/api/fulfillment-orders/merge-group
Merge two or more pre-dispatch fulfillment orders from DIFFERENT sales orders into one merged shipment group. The group dispatches to the shipping provider as a single order keyed on the primary member; at ship time each member's sales order records its own fulfillment carrying the shared tracking. If one of the given fulfillment orders already belongs to a group, the others are added to that group.
orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Eligibility is enforced server-side: every member must be pre-dispatch (status=open, request_status unsubmitted/rejected), at the same warehouse, for the same shipping provider and shipping address. Amazon FBA fulfillment orders can never be merged.
Body fields:
fulfillment_order_ids(required, array of integers, min 2) — the fulfillment orders to merge.primary_fulfillment_order_id(optional, integer, nullable) — which member's reference the provider order is keyed on; defaults to the first id.
Returns 201 with the group and its member summaries. 409 when a member is no longer mutable (already dispatched); 422 for ineligible combinations.
Authentication: Requires Bearer token.
Request
Responses
- 201
- 401
- 403
- 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 — 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.
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.