Using Fulfillment Orders API instead of Fulfilment API

[TonyToms]

I am facing a dilemma regarding the deprecation of fulfillment API.

As per the documentation, we need to start using the 'fulfillmentOrders' API from next year as the 'Fulfillment' API is deprecated.

The new 'fulfillmentOrders' API seems to be a huge process with capabilities like sending fulfillment requests, approval of fulfillment requests by 3rd part service providers, creation of labels, etc. 

However, We didn't need any of those functionalities. We just need to update the fulfillment status as 'Fulfilled' for the items in an order with relevant fields like tracking no etc, which was easily done using our current fulfillment API

Is there a way we could achieve this easily considering the new API changes? If using the 'FulfillmentOrders' API is the only way ahead, could someone suggest me the best approach to easily update the 'fulfillment Status' ?

I am not an expert in order fulfillment process and if my understanding is wrong, please do guide me .

PS: We are using the phpclassic php-shopify librabry ATM.

[SocialAutoPost · Accepted solution]

@TonyToms 

As you mentioned, the new FulfillmentOrders API is a more complex and feature-rich API, and it may not be the best fit for your needs if you only need to update the fulfillment status of an order.

One potential solution that you could consider is to use the FulfillmentOrders API, but only implement the specific features that you need. For example, you could create a fulfillment order using the API, and then use the fulfillment field of the order to update the fulfillment status of the items in the order. This would allow you to take advantage of the new API, while only implementing the features that you need.

Another solution that you could consider is to use the REST Admin API, which provides more granular control over the fulfillment process. You can use the POST /admin/api/2022-01/orders/#{id}/fulfillments.json endpoint to update the fulfillment status of an order, and include the relevant fields like the tracking number in the request body. This would allow you to update the fulfillment status of an order without using the FulfillmentOrders API.

Overall, there are several options that you could consider to update the fulfillment status of an order in Shopify, even after the deprecation of the Fulfillment API. By using the FulfillmentOrders API and only implementing the specific features that you need, or by using the REST Admin API, you should be able to continue updating the fulfillment status of orders in your store.

[API_Chat]

Hi @TonyToms

I think I have the same question.

Do you have a new fulfillment endpoint to replace this URL POST /admin/api/2022-01/orders/#{id}/fulfillments.json as the new FulfilmentOrders API is live from April 23? 

thanks

[TonyToms]

Hi @API_Chat 

As until today, none of the API calls are broken for me. But I am using an external shopify library called phpclassic php-shopify. I got a few suggestions on their github page on how to archive what I need. I haven't implemented it yet, but the code seems to be exactly what I need.

I am inserting the link here. 

https://github.com/phpclassic/php-shopify/issues/283 

There is a comment made  by d3v1 on dec 23rd, which I think is the solution I am looking for.

There are few more threads  that talks about the fulfilment.

https://github.com/phpclassic/php-shopify/issues

I hope these links could provide you a solution.

[API_Chat]

@TonyToms @SocialAutoPost 

To be clear

This endpoint is being retired  

/orders/{order_id}/fulfillments.json

we need to configure the new POST endpoint below, but the description says "fulfilment order as incomplete", should is say "fulfilment order as complete" or is fulfilment order complete a different end point?

POST /admin/api/2023-01/fulfillment_orders/{fulfillment_order_id}/close.json
Description- Marks a fulfillment order as incomplete

[databot]

Hi,

Same question here, essentially.

The 2022 API call should not be an accepted solution as it is deprecated.

Our scenario is a little more complex.  How do we reflect that a downstream system split and fulfilled the order differently to what Shopify expected (ie, differently to the current set of FulfillmentOrders)?

For example: The FulfillmentOrder contains 2 lines, but the shipment data we have and are trying to inform Shopify about, was that 1 line was fulfilled from Location A and the other line was fulfillment from Location B.

In the deprecated POST Fulfillments API, this was easy, but the FulfillmentOrder API, it is not clear how to do this, or even if it is possible.

I think this will cause major issues if not resolved. 

Can anyone please provide some guidance?

[jpirola]

Did you ever find a solution to this?  I am in the exact same boat.  The prior procedure was very straightforward and I don't want to go through a bunch of hoops if I don't have to.  Like why would I even NEED a callback function if I am the one who will initiate the posting of tracking info???