Shopify API 2026-07: taxSettings on Customer now accessible via GraphQL
With Admin GraphQL API version 2026-07, Shopify finally makes the taxSettings field on the Customer object accessible, allowing you to read the VAT number collected at checkout through standard queries using the read_customers or read_taxes scope.
The problem: the VAT number was there, but the API would not return it
Anyone who has built a tax or accounting integration on Shopify knows the frustration well: the customer enters their VAT number during checkout, Shopify collects and validates it, but when it comes time to sync that information to an ERP or external accounting system, the data is simply unreachable through the standard API.
Until now. With Admin GraphQL API version 2026-07, Shopify introduces a structural change that solves exactly this problem.
What changes in API version 2026-07
The taxSettings field on the Customer object becomes publicly accessible. Previously, retrieving tax information associated with a customer required manual workarounds, protected access paths, or custom logic that added significant complexity to integrations.
From version 2026-07 onwards, with read_customers or read_taxes permissions active in your app, you can run standard GraphQL queries and retrieve the taxId field directly. It returns:
- A string containing the VAT number or tax ID, if the customer provided it during checkout
- null, if the field was not filled in
No additional configuration, no special approval process: simply update your target API version and verify your active scopes.
Scope of the change: read-only
It is important to clarify the limits of this update upfront, to avoid incorrect assumptions when planning integrations.
The change is read-only. It is not possible to write or update taxId through this public API.
Furthermore, the taxIdValidation field, which contains the validation status of the tax number, is not included in public access. To retrieve validation status details, you must request access to protected customer data through Shopify's separate approval process. This is a distinct procedure that needs to be planned in advance if your integration requires it.
Practical use cases for developers and merchants
This change opens up relevant real-world scenarios, especially for those operating in the European market or managing business customers outside of Shopify's structured B2B setup.
Syncing to ERP and accounting systems
One of the most immediate use cases is the automatic synchronization of the VAT number to systems such as SAP, Microsoft Dynamics, QuickBooks, or any other ERP that requires a customer tax number to generate compliant invoices. Until now, this data had to be retrieved manually or through workarounds. With taxSettings accessible via API, the entire flow can be fully automated.
Tax compliance logic
For merchants selling in Europe, correct handling of intra-community VAT depends on the availability and validity of the customer's VAT number. Having programmatic access to this field allows you to:
- Build dynamic pricing and taxation rules
- Verify the presence of the data before issuing tax documents
- Integrate compliance checks directly into the order flow
Alignment with Shopify B2B
For customers using Shopify's native B2B features, the taxSettings field on the CompanyLocation object has been available since API version 2025-01. The new accessibility on the Customer object in version 2026-07 represents an important alignment, bringing the same level of access to business customers who are not structured as a Company within Shopify.
How to update your integration
If you are developing or maintaining tax or ERP integrations on Shopify Plus, here are the operational steps to follow:
- Update your target API version to 2026-07 in your app manifest or direct API calls
- Verify your active scopes: make sure
read_customersorread_taxesare included among the permissions your app requests - Handle the null case: implement logic to correctly handle customers who have no tax ID, since the field will return null when no data is present
- Plan for protected access if your integration also requires the
taxIdValidationfield: Shopify's approval process takes time and documentation
For a full overview of available costs and development options, visit our developer plans page.
Conclusion
Public access to taxSettings in Admin GraphQL API version 2026-07 is a technically scoped change, but one with significant practical impact for anyone building tax integrations on Shopify. It removes a concrete obstacle that forced development teams into manual solutions or fragile workarounds, and aligns tax data access for consumer customers with what has already been available for structured B2B customers. Planning your migration ahead of time is the right move.
Need senior Shopify, React or WordPress developers?
Find talent