Mark order as "Ready for Pickup" using Rest API v2021-01

Retired Boards Appdev Fulfillment Api

Topic summary

Issue: Setting local pickup orders to “Ready for Pickup” via REST (v2021-01, orders//fulfillments.json with shipment_status=ready_for_pickup) instead marks orders as “Picked Up.” Code snippets and payload examples are central to understanding the problem.

Early response asked for x-request-id to investigate, but no resolution via REST was provided. Multiple participants reported this as a longstanding bug with no REST workaround.

Recent update: A path exists via Admin GraphQL, not REST. The mutation referenced is fulfillmentOrderLineItemsPreparedForPickup (docs link provided for API 2023-04).

Complications surfaced:

  • One user’s GraphQL attempts returned schema errors (input type not defined, field missing on Mutation, unused variable), indicating the mutation wasn’t available/recognized in their environment.
  • Another user couldn’t proceed because their order had no fulfillments or fulfillmentOrders nodes, which the mutation requires.

Current status:

  • REST: No solution/workaround reported; behavior remains incorrect for this use case.
  • GraphQL: Supported mutation exists, but some users face schema and data prerequisites issues.
  • No final resolution or confirmed fix; open/ongoing with unanswered questions on enabling the GraphQL mutation and ensuring fulfillment orders exist.
Summarized with AI on January 24. AI used: gpt-5.
1

Hi,
While trying to mark the Local Pickup order as “Ready for Pickup” through Rest API, we’re unable to do so.
The endpoint that is being used is: ‘orders//fulfillments.json’
Below attached is the Data object that is being sent in the call
var data = {
“location_id”: “”,
“tracking_numbers”: ,
“line_items”: ,
“shipment_status”: “ready_for_pickup”
}
When making a fulfillment call through API, the order is marked as Picked Up on Shopify instead of Ready for Pickup.
Can you please help us out with this as to what we’re doing wrong here?
Your earlier response will highly be appreciated.
Thanks

2 Likes
2

Hi @William_Leeson

Could you please provide an x-request-id from one of the requests that did this? It’s found in the response headers. If you can let me know, I can take a look through our logs and see if I can determine what’s going wrong here!

Thanks,

1 Like
3

From what I understand this has still not been fixed? Has anybody had further information regarding this?

1 Like
4

Hi Csam,

We are having the same issue as well. Can you tell us a solution to this problem?

Thanks,
Jaclyn

5

Apparently a known bug which has not been fixed for years. So no workaround as of yet ;(

6

Anybody know if this has been resolved yet?

5 year old bug - cant allow 3rd parties to mark an order ready for collect? crazy

7

Now you can,

Using GraphQL (no work around using REST API)
https://shopify.dev/api/admin-graphql/2023-04/mutations/fulfillmentOrderLineItemsPreparedForPickup

1 Like
8

Hello, can you explain me how to do this?

FulfillmentOrderLineItemsPreparedForPickupInput isn't a defined input type (on $input)
Field 'fulfillmentOrderLineItemsPreparedForPickup' doesn't exist on type 'Mutation'
Variable $input is declared by fulfillmentOrderLineItemsPreparedForPickup but not used

These are the errors I get when i try to use the mutation. https://shopify.dev/docs/api/admin-graphql/2023-04/mutations/fulfillmentOrderLineItemsPreparedForPickup

1 Like
9

Thanks for your help. My problem is that there’re no fullfillments created on my order. Its already paid, but there’s no node created, so I cannot call the GraphQL mutation you indicate.

I see this in my order:

“fulfillments”: ,
“fulfillmentOrders”: {
“nodes”:
}