Localization extensions developer preview

[Jason_Tigas]

Currently available, the Localization Extensions developer preview allows partners and app developers to access the tax id collected during checkout and use this information to augment shipping apps (to expedite customs clearance) and invoicing apps (to issue gov. invoices).

As of the 2020-07 release candidate, orders made through checkout in countries that require a tax id for customs clearance or government invoicing will have this information available through the GraphQL API.

You can try these changes using a development store with the 'Localization Extensions' developer preview enabled.

For more information on how to apply tax IDs on checkout and view them through the GraphQL API, refer to our tutorial.

[wiretrackio]

Hi there, thanks for the improvement.

Would you have any information on how to use that through the REST API? Couldn't find it in the current documentation.

Thanks

[plentz]

Hi Wiretrackio,

Currently, we don't support REST.

[wiretrackio]

Okay, so @Jason_Tigas says:

"As of the 2020-07 release candidate, orders made through checkout in countries that require a tax id for customs clearance or government invoicing will have this information available through the REST and GraphQL API." 

So from what I understand this is a misunderstanding and there is no such field in the REST API, right? Could you please point developers to where is this field available using the GraphQL API?

Thanks.

[Jason_Tigas]

Hi @wiretrackio , you are indeed correct. Apologies for that misprint and thanks for pointing out the error. 

The post has been updated.

[KBetterReports]

Hi there,

Are there any plans to get this to REST API so that webhooks are supported?

We have quite a few merchants looking for these localization extensions and currently the only way is to get a manual Graphl QL query (  https://shopify.dev/tutorials/get-a-country-field-using-localization-extensions ) without any update webhooks.

It would be a great addition and would make the reporting and compliance much easier.

[Jason_Tigas]

Hi @KBetterReports ,

It's on our radar and we're working on getting something out.

[KBetterReports]

Really appreciate the quick response, @Jason_Tigas ! Thank you.

It is great to hear that it is on the roadmap. Any timeline or expected release?

[ChrisSaju]

Hey @Jason_Tigas,

Do you have an update on when we can get this on REST API?

[jsmith]

@Jason_Tigas 

Any update on the plan to expose data from these fields via the REST API? The February 26 deadline is looming.

This is very inconvenient for your customers with an existing Shopify REST API integration: you are introducing required fields to checkout which cannot be disabled, with no way to access the data from those fields...

[ChrisSaju12]

Hey @Jason_Tigas,

Following up on this request again.

[TFCH]

Hi all,

i'm trying to use graphql to get localization extensions values on a production store, with no luck.

Using this graphql request:

{
                  order(id: "gid://shopify/Order/XXXXXXXXXXXXX") {
                    id
                    localizationExtensions(first: 5) {
                        edges {
                            node {
                                countryCode
                                purpose
                                title
                                value
                                }
                            }
                        }
                    }
                }

The only result i can get is

"message": "Field 'order' doesn't exist on type 'QueryRoot'" 

[TheGameSteward]

Hi TFCH,

Where XXXXXXXX is equal to your order_number.  Note: not the Order Name.  Order name is the unique order id users use in the shopify admin to identify an order.  Instead, use the order_number which you'll see in the URL when you open an order in the Shopify Admin (see highlight below)

{
  order(id: "gid://shopify/Order/XXXXXXXXX") {
    id
    localizationExtensions(first: 5) {
      edges {
        node {
          countryCode
          purpose
          title
          value
        }
      }
    }
  }
}

I note the above because otherwise your script looks okay.

Hope that helps,

Dan

[alexlesa]

Hi all,

Is there any intention on surfacing these fields to the REST API? And if so, what is the timeline on this? There seems to be no update. 

Kind Regards,

[Jonathan-HA]

Just wanted  to +1 the requests to make this available on the REST API.