I have noticed that Shopify allows you to create an app specific third party shopify location that you can request fulfillment, but when querying through API or graphql, it has the legacy: true flag. Are those types of third party location deprecated? I have considered using it for my app to enable the request fulfillment workflow to prevent order update after an order has been accepted for fulfillment, but I don’t want to use that type of location if it is deprecated. I also have concerns about what happens to orders and fulfillments assigned to that third party location if it gets deleted or the app is uninstalled? Would all orders or fulfillments belonging to that location get lost?
1 Like
Hey @Andrew_Jaanuu,
Third-party locations aren’t deprecated. The current fulfillment service flow you’re considering is the recommended approach and continues to be fully supported: About fulfillment services
Regarding your concerns about app uninstallation, I tested to see what happens. When I uninstalled my app, all inventory from the third-party location was re-assigned to the primary merchant location.
The recommended approach though would be to use the fulfillmentServiceDelete - GraphQL Admin mutation so you can specify the re-allocation of inventory.
Is there any reason why the third party location can’t be the primary or default location on Shopify?
Great question, I don’t know exactly why, but I would imagine it’s due to the limited scopes of fulfillment services since app managed locations are specifically tied to fulfillment services: Build for fulfillment services
If you want to manage fulfillments through a merchant managed location that’s typically done as an order management app.
If you want the app location to be the default, one way to do that is through order routing.