My app currently works with the products REST api endpoint. In the response, for each product variant there is a “grams” field with the weight of that product variant. I’m migrating my app to use the new GraphQL products API and I noticed there is no more grams field (or weight field as of 2024-07 …

Hi folks, Thanks for the valuable feedback on this. Wanted to share that the API has been updated and this should now be resolved [image] InventoryItem Queryable and Updatable with Products Scopes — Shopify... Shopify’s developer changelog documents all updates to Shopify’s platform. F…

Hi Steves, Is your app on the Shopify App Store? If you update your scopes to include read_inventory access scope with OAuth (or use your app’s toml file if you have a Shopify managed installation) Shopify will prompt the store owners to grant access for this new scope.

Hi @Liam-Shopify , thank you for the response. We are listed on the Shopify App Store. As far as I know I would need to update the scope to include read_inventory and send the users again to “/admin/oauth/authorize” with the new scope for them grant it. Only then I can request the inventoryItem. A…

+1 for a way to automatically backfill access scopes due to breaking changes like this where fields are moved to a different resource that requires a separate access scope. As we do these migrations from REST and also as the GraphQL schema changes, it’s really not ideal to keep notifying merchants …

Totally understand this is not an ideal approach and has risks in terms of ensuring merchants read emails. I’ve connected with the product team in this area to see what they’re recommendation is and how we could improve this.

We are exactly in the same boat, we had no need of read_inventory scope previously and I just found out that we need read_invntory scope, we have over 1.2k merchants for whom things will likely fail :frowning:

@Asaf_Gitai For read_locations, any plans to at least provide a form to request backfilling the scope (similar to how read_publications was handled) for those migrating from REST? The use case is for retrieving inventory levels by location. The REST API only requires read_inventory to retrieve Inv…

@Asaf_Gitai thanks for adding this, but without read_inventory and read_location, it’s not really useful for my usecase (export inventory levels by location), like @Jonathan-HA said.

No response yet, they’re probably very busy right now. I really do hope they consider a backfill option or even better is to allow either read_locations or read_inventory to access the Location resource (just like how InventoryItem can now be accessed with either read_products or read_inventory).

I received the reply, and confirmed the breaking change. Can you please also send email to support asking them to do something? To me this is unacceptable. I already replied and asking them to automatically apply this scope if inventory scope is in.

Getting a product variant weight (previously grams in REST API) requires a new scope that my app does't currently have

New GraphQL Product APIs

that January 27, 2025, 10:18am 10

Yes! I am facing this problem too. Have you received the response from shopify? my post is here: Read_locations scope is needed for inventorySetQuantities

Topic		Replies	Views
GraphQL Locations Shopify App Store dev-stores	3	122	January 27, 2025
2024-07 read_locations scope required - backfill request GraphQL Admin API Troubleshooting rest-migration , general-gql-troubles	16	462	April 2, 2025
Cannot access the field inventoryItem on ProductVariant Extensions checkout-ui-ext	11	300	May 8, 2025
Read_locations scope is needed for inventorySetQuantities GraphQL Admin API Troubleshooting rest-migration	0	105	January 27, 2025
inventoryLevels Query Not Working - access_denied GraphQL Admin API Troubleshooting general-gql-troubles	2	55	October 30, 2025

Getting a product variant weight (previously grams in REST API) requires a new scope that my app does't currently have

Related topics