If merchants using your app have already granted read_fulfillments or write_fulfillments, rest easy, asthey will not have to agree to new permissions. Instead, you can request granular access scopes for an individual shop installation.
Testing your app
When you migrate your app to a new API, it’s important to make sure your software still functions as described. By testing out Fulfillment Orders in a dev store, you can catch any potential guatemala telegram screenin issues before launching on production, saving yourself the hassle of needing to make multiple updates while ensuring merchants have a seamless experience.
You can test the functionality of your app on a dev store by creating test orders with the “Bogus” gateway. If your app is an order management app, you can then fulfill these test orders directly through the API using the updated Fulfillment Orders endpoints. If your app is a fulfillment service, you can use your development store to request fulfillment from your service through the Admin.
If you’re wondering what it might look like once updated, take a look at our sample application detailing how fulfillment and order management is done before and after Fulfillment Orders.
Read our complete migration guide for best practices when migrating to Fulfillment Orders
How these changes help
The Fulfillment Orders API models the end-to-end fulfillment process into detailed sub-pieces, so fulfillment data can sync more accurately between Shopify and an order management app or a 3PL. The Fulfillment Order API tracks the lifecycle of fulfillment work, including open, in-progress, closed, canceled or incomplete, so merchants have a more granular and complete view of their order data in Shopify.
Fulfillment orders also include location data, which Shopify would usually only display to merchants in the Admin. This location information is crucial and details which location should ideally fulfill an order.