You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As far as I can tell this is going to be the preferred method of fulfilling orders in the future.
I am in the middle of implementing in my company and I got stuck due to missing documentation and support in this SDK.
I couldn't find any documentation for the REST API on accessing the assignedFulfillmentOrders and how to accept / reject the requests after the notification.
I got as far as receiving the fulfilment request -- in practice just {"kind":"FULFILLMENT_REQUEST"} without any additional data.
We are closing this issue because it has been inactive for a few months.
This probably means that it is not reproducible or it has been fixed in a newer version.
If it’s an enhancement and hasn’t been taken on since it was submitted, then it seems other issues have taken priority.
If you still encounter this issue with the latest stable version, please reopen using the issue template. You can also contribute directly by submitting a pull request– see the CONTRIBUTING.md file for guidelines
Shopify seems to have added a new way to manage Orders without registering webhooks.
https://help.shopify.com/en/api/guides/managing-fulfillments-with-fulfillmentorders
As far as I can tell this is going to be the preferred method of fulfilling orders in the future.
I am in the middle of implementing in my company and I got stuck due to missing documentation and support in this SDK.
I couldn't find any documentation for the REST API on accessing the
assignedFulfillmentOrders
and how to accept / reject the requests after the notification.I got as far as receiving the fulfilment request -- in practice just
{"kind":"FULFILLMENT_REQUEST"}
without any additional data.I noticed there's some chatter in the Ruby community: Shopify/shopify-api-ruby#637 and Shopify/shopify-api-ruby#622 but not sure if it's relevant.
The text was updated successfully, but these errors were encountered: