Fulfillment payloads on order creation now require a location ID
API
Effective January 07, 2019
Fulfillment payloads on the order creation endpoint have been updated to require a location ID (a unique identifier of the location where the fulfillment should be processed). This means that if an app includes a fulfillment payload during order creation, then that payload must include a location_id.
Who is affected by this change?
Alls apps that include a fulfillment payload during order creation.
How do I prepare for this change?
Make sure your apps' fulfillment payloads include a value for location_id during order creation.
What happens if I do nothing?
If a fulfillment payload doesn't include a location ID, then the API returns a 422 error (similar to other sections of the Fulfillment resource). If you are not currently including a fulfillment payload during order creation, then no action is needed on your part.
Where can I learn more?
To demonstrate how this works, we’ve added an example to the POST /orders.json documentation.
Note: 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.