Now that Shopify can natively validate VAT IDs, when will the VAT ID be exposed via the Customer object in the Admin API? As of now the Customer object only exposes the tax-exempt status both in queries as well as mutations.
1 Like
Hey @ThomasBorowski 
- thanks for flagging this. I did some digging into this and spoke with my colleague Kyle who looked into a similar question here the other day:
Right now, we don’t have plans to expose the VAT/Tax IDs on the customer object in the Admin API, but I will set up an internal feature request report on your behalf - it does look like this is a really desired feature (for good reason for sure), so more than happy to do that so we have that noted on our end.
It would be really useful to have the VAT/Tax IDs exposed to the API. Serveral of our merchants run b2b shops, where we now store the VAT-ID in a metafield, but the introduction of the Shopify native fields has caused confusion, and sparked questions from merchants why they need to enter the information twice.
1 Like
A native, API-exposed field would make integration with various 3rd-party invoicing solutions a lot easier. Now you can either use Shopify Tax with the native field, which can’t be set by apps (that include VAT ID validation as part of their feature set), or you can use 3rd-party apps, but only with proprietary metafield solutions.
+1 here! Our app has long been allowing customers to collect VAT as a metafield, but being able to integrate with the standard field would be cool.
+1 here as well, having that info exposed in the API would not only be great, it’s an absolute necessity in so many cases!
Any app relatade to invoicing for example, is legaly required to display the Tax ID.
We’ve been getting it through a custom metafield until now, but now that Shopify added the feature, people really don’t understand why it is asked twice.
We even had a case where another app needed it and used its own metafield as well, resulting in THREE different fields asking for the Tax ID, that we mitigated by adapting and using the other app’s metafield so we could remove ours, but still, it’s a really ugly solution to a problem that wouldn’t exist anymore if Shopify added the field into the GraphQL API.
I really hope this task gets in the priority list on the TODO of the dev team 
not having this available via API on day one ist so shopify-coded LMAO
It’s the unit pricing ordeal all over again 
1 Like