Cin7 Core is unable to import the Tax Credential data apart from the following countries China, Brazil, South Korea
When they try retrieve the data for all other countries, the data being returned in “null / blank”
Can someone look into this. This data is required, as its put into the shipping notes field in Cin7, which is mapped with Shipping Software that places it onto the Shipping Label, which is required for customs clearance
The issue is they are saying when the call upon any countries - other than stated above in my first post using that field above, then the returned data is null. The data is simple not being shared.
Can someone please check and confirm if this is indeed the case?
The countries where you are expected to see a value returned are listed in that ENUM.
If it’s returning Null when the data exists on the order, double check the API version. As more regions have been added over the years, currently not all older API versions will have a value.
I will forward your response onto Cin7, as I do not know what API version they are using.
All I know is we had a Mexico order, with a RFC value that is not being imported into Cin7. They say they call it, it returns null data, maybe it is due to using an older API version, I will check with them.
I see.. I believe the version they are using is only a couple of months old, so sounds likely. Will get back to you again if required/if Cin7 ask for more clarity.
Confirmed with Cin7 that they’re not using 2025-04 but the previous version, so that explains it. They will update to the new API version in due course (once their new Shopify integration is complete)
I have another question however.
Q1) Where is the changelog between the API version’s on the website? I couldn’t seem to find it?
Like… if myself (or even Cin7) look at the LocalizedFieldKey page, there is no indication as to what API version is required, for a specific fields to return a value, so I’m not sure how you knew that 2025-04 was required for Mexico? It appears to me that Cin7 were not aware of this (myself included).
All I can think of is either providing a changelog, or perhaps showing the API version besides the fields, so we all know what API version is required. Or perhaps I’m wrong and there’s a better way of tracking changes?