Fulfillment payloads on the orders#create endpoint have been updated to accept a location id.
This means that if you are including a fulfillment payload during order creation, that payload will now require a location id.
Not including a location id as part of these fulfillments will return a 422 error, similar to other sections of the fulfillment API.
If you are not currently including a fulfillment payload during order creation, no action is needed on your part.
To showcase how to leverage this, we’ve added an example to the POST /orders.json documentation.
The fulfillments payload requires an array of fulfillments, but currently only supports a single fulfillment.
Therefore, when passing a fulfillment payload as part of order creation, all line items will need to be fulfillable from that location.