The 2024-07 API version requires the read_locations scope to retrieve inventory levels with location information using GraphQL, whereas the REST API only needs the read_inventory scope.
This is a breaking change. Is there a way to backfill the read_locations scope for existing merchants?
Alternatively, could Shopify consider relaxing the restriction so that inventory levels with location information can be queried using just the read_inventory scope?
A temporary solution would be to migrate back to REST for 2024-07, but that doesn’t seem right.
Could anyone from Shopify please advise? Thank you!
Is the issue that, if you add this new scope to your app, merchants who are currently using your app will need to re-authenticate the app in other to accept the new scope?
For context, we run an inventory management app that operates in the background.
The issue is that many merchants currently using our app may not open it to re-authenticate. As a result, the API requests will break once we upgrade to 2024-07 or later.
While sending emails to merchants to prompt them to re-authenticate helps, some may miss or ignore those messages.
Is there any way we could backfill the read_locations scope for those merchants who already have the read_inventory scope?
I’ve connected with the team working on REST → GraphQL migration, and we’re working on a solution that will make this transition process easier, specifically around adding new scopes. No ETA to share but we’re working on this.
Our app is also affected. All stock update automations will fail after upgrading to version 2024-07. Merchants usually set up the automation and rarely open the app again, so it’s complicated to ensure reauthentication.
I think this is just for GraphQL but it’s been helpful for us so we can keep tracking inventory inventory for merchants who haven’t logged into the app for a while.
