Covers all questions related to inventory management, order fulfillment, and shipping.
We're about to start developing the fulfillment endpoint but stumbled across this post here https://www.shopify.com/partners/blog/shopify-fulfillment-orders-api and clicked all the links in there. However it doesn't explain much apart from adding/migrating new user permissions.
Do we need to move from Fulfillments API -> FulfillmentOrder/FulfillmentRequest API now?
I couldn't find any of those two endpoints that updates tracking number - would we still use Fulfillment endpoint then?
Thanks!
Solved! Go to the solution
This is an accepted solution.
I found the easiest way to learn the migration was to just do it! It is not terribly hard to do. For this, the simplest pattern I found was as follows.
1. I tricked out a shop with a sample product or two, where I could book orders and monkey with fulfillments.
2. I setup that API key in Insomnia and started implementing all the GQL that matters for the new Fulfillment API.
With that, I could start to see how it all worked. It took awhile sure, but soon enough I had built an entire functional fulfillment service with every possible bell and whistle, without changing anything on the old school RestAPI style of computing in my old Apps supporting old fulfillment.
So now, I only use the new Fulfillment API, and it does sorta make sense. It has some weird inflection points, but you may never encounter those if all you do is set tracking numbers for example.
Anyway, like I say, if you skip the documentation and go more for understanding via the code, it actually does work, and makes some sense once you start seeing the results.
Dev docs
https://shopify.dev/apps/fulfillment/fulfillment-service-apps
https://shopify.dev/apps/fulfillment/migrate
Contact paull.newton+shopifyforum@gmail.com for the solutions you need
Save time & money ,Ask Questions The Smart Way
Problem Solved? ✔Accept and Like solutions to help future merchants
Answers powered by coffee Thank Paul with a ☕ Coffee for more answers or donate to eff.org
Yes, I'm aware of those. I don't think they're fully explaining well?
This is an accepted solution.
I found the easiest way to learn the migration was to just do it! It is not terribly hard to do. For this, the simplest pattern I found was as follows.
1. I tricked out a shop with a sample product or two, where I could book orders and monkey with fulfillments.
2. I setup that API key in Insomnia and started implementing all the GQL that matters for the new Fulfillment API.
With that, I could start to see how it all worked. It took awhile sure, but soon enough I had built an entire functional fulfillment service with every possible bell and whistle, without changing anything on the old school RestAPI style of computing in my old Apps supporting old fulfillment.
So now, I only use the new Fulfillment API, and it does sorta make sense. It has some weird inflection points, but you may never encounter those if all you do is set tracking numbers for example.
Anyway, like I say, if you skip the documentation and go more for understanding via the code, it actually does work, and makes some sense once you start seeing the results.
Hi ,
I am also stuck with the Shopify documentation. Its not giving proper guidance for the migration. I used rest API functions for my current fulfillment app. Could you please guide me what are the steps that you have taken ?. If you can give some example for fulfilment request to fulfilment service, fulfillment accept by fulfillment service, and closing the fulfillment with tracking no will be helpful.
Also is this migration is mandatory since the app is working well with legacy fulfillment API.
@trisha-3
Did you got a solution? if yes Please assist me.
Thanks
Hi @laiji, as what @/HunkyBill says.
It's best to play around with the API and understand what it does and cater to your needs. Maybe have a go and play around? I'm not really sure which one you are going for since there's two types of app: https://shopify.dev/apps/fulfillment.