Location object in GraphQL confusing access documentation

Hi team,

We’re having trouble accessing the Location object via the Admin GraphQL API.

The documentation clearly states at the top:

Requires read_locations access scope, read_inventory access scope, or read_markets_home access scope.

Our app has the read_markets_home scope, yet the 2025-07 API returns this error:

Access denied for address field. Required access: read_locations access scope

Upon closer inspection, clicking the lock icon next to each field reveals:

Requires read_locations access scope.

This feels counterintuitive. It seems the only field accessible with read_inventory scope is id, and with read_markets_home, it’s just id and name.

It’s frustrating that this information is so hidden. We’re simply trying to determine the country of orders placed through Shopify POS.

Could you please clarify or fix this to make the Location object fully accessible with the read_markets_home scope as stated?

Thanks!

1 Like

Hey @Patrick_Jakubik, thanks for that feedback.

Over the last few versions, the locations object has been limited and requires the read_locations for full access to all of the fields.

This post here clarifies why the ID is only available with read_inventory Location ID Queryable with Inventory Scopes - Shopify developer changelog

This was a breaking change in the 2024-07 release 2024-07 release notes

I can see as you do that the docs are confusing as the note at the top of the docs does seem like either of those scopes would give full access to the object. It would help to provide clarification that read_markets_home and read_inventory are limited to only certain fields. I’ll pass that feedback on :memo: