Skip to main content

abandonedCheckoutUrl now requires level 2 protected customer data access

Starting December 1, 2026 for public apps, and January 1, 2027 for custom apps, the abandoned checkout recovery URL requires approval for all four protected customer fields (name, email, phone, and address) on all supported Admin API versions and unstable. If your app reads AbandonedCheckout.abandonedCheckoutUrl or abandoned_checkout_url but doesn't need it, stop using the field. If your app needs it, request access before your date. This is a breaking change made for security reasons.

Which apps and when

AppDateHow to get access
Public appsDecember 1, 2026Request access; a data protection review is required
Partner custom apps (built by a partner for a specific store)January 1, 2027Enable the four fields yourself in the Dev Dashboard; no review
Merchant-created apps in the Dev Dashboard (apps a store or organization builds for its own use)January 1, 2027Enable the four fields yourself in the Dev Dashboard; no review
Apps created in the Shopify adminNot affectedNothing to do

Why

The recovery URL opens the buyer's checkout with their name, email, phone, and address filled in. Apps without access to those fields already can't read that data on the AbandonedCheckout object, so the URL now requires the same access.

What happens if you don't act by your date

The following applies to apps that aren't approved for all four protected customer fields: name, email, phone, and address (read_customer_name, read_customer_email, read_customer_phone, and read_customer_address). Approval for only some of them isn't enough. Apps approved for all four aren't affected.

GraphQL Admin API: queries that select the field fail

  • abandonedCheckoutUrl returns an ACCESS_DENIED error, and the error nulls out the surrounding data.
  • List queries such as abandonedCheckouts return data: null, so you lose all the abandoned checkout data in that query, not just the URL.
  • A node or nodes lookup returns null for that checkout.
  • Bulk operations that select the field fail with ACCESS_DENIED after retrying for a few minutes.

What to do: remove abandonedCheckoutUrl from your queries and bulk operations, or request access.

# Before
{ abandonedCheckouts(first: 10) { edges { node { id abandonedCheckoutUrl } } } }

# After
{ abandonedCheckouts(first: 10) { edges { node { id } } } }

REST Admin API and webhooks: the field is left out

Warning: If your app uses abandoned_checkout_url, it won't be there anymore. From your date, the field is removed from REST responses and webhook payloads for apps without access. There's no error, so your app won't be told it's missing.

  • abandoned_checkout_url is left out of GET /admin/api/{version}/checkouts.json responses and checkouts/create / checkouts/update webhook payloads. Everything else is unchanged.
  • REST returns this field by default, so your app may receive it today without using it. If your app never reads it, you won't notice the change.
  • If your app reads it, features that use the URL, such as recovery emails, SMS, or direct mail, lose their link, and code that assumes the key is present may fail.

What to do: if your app uses the URL, request access before your date. Otherwise, make sure your app handles the field being missing. You can also stop receiving it by requesting only the fields you use with the fields parameter.

How to get access

If your app needs the recovery URL (for example, to send abandoned checkout recovery messages), request access to protected customer data: in the Dev Dashboard, go to your app's Settings > Access requests > Protected customer data > Manage, then select the name, email, phone, and address fields with your reasons. All four are required.

  • Custom apps (partner custom apps and merchant-created apps in the Dev Dashboard) can enable these fields themselves, with no review.
  • Public apps need a data protection review before access is granted. Reviews can take a couple of weeks, so request access as soon as possible.

Development stores don't enforce protected customer data approval, so you won't see these errors there. Check your app's protected customer data status in the Dev Dashboard.

Related docs

Was this page helpful?