DeskLeap
ProductFeaturesPricingShopifyBlog
← Back to Blog

Shopify's abandoned checkout URL now needs all four protected customer data approvals

November 19, 2026·6 min read
Shopify's abandoned checkout URL now needs all four protected customer data approvals

Shopify's developer changelog entry of 19 November 2026 is flagged Breaking API Change and Action required. It concerns one field: the abandoned checkout recovery URL, AbandonedCheckout.abandonedCheckoutUrl in the GraphQL Admin API and abandoned_checkout_url in REST and webhooks. To read that URL, an app will need approval for all four protected customer data fields: name, email, phone and address. In Shopify's words, "Approval for only some of them isn't enough."

The customer data itself was already behind those approvals. What changes is that the recovery URL now requires the same access. Shopify's reason: the URL "opens the buyer's checkout with their name, email, phone, and address filled in", so an app that can't read those fields shouldn't be able to reach them through the link either.

The part worth planning for is what happens to an app that isn't approved. It doesn't just lose the URL.

Who is affected, and when

There are two dates and three kinds of app. Shopify's table:

  • Public apps: from 1 December 2026. Access must be requested, and "a data protection review is required".
  • Partner custom apps (built by a partner for a specific store) and merchant-created apps in the Dev Dashboard: from 1 January 2027. These apps enable the four fields themselves in the Dev Dashboard, with no review.
  • Apps created in the Shopify admin: not affected. Nothing to do.

The change applies on all supported Admin API versions and on unstable, so pinning an older API version doesn't avoid it. Apps that already hold approval for all four fields aren't affected.

GraphQL: one field takes the whole query down with it

This is the line from the entry that matters most. When an app without all four approvals selects the field, "abandonedCheckoutUrl returns an ACCESS_DENIED error, and the error nulls out the surrounding data."

  • List queries such as abandonedCheckouts return data: null. Shopify: "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.

So an app that asks for ten abandoned checkouts with their IDs and recovery URLs doesn't get ten checkouts with the URL missing. It gets nothing. Any screen, report or sync built on that query goes empty at once, and the cause is a single field.

Shopify's fix is just as small: take abandonedCheckoutUrl out of the query if the app doesn't need it, or request access if it does.

REST and webhooks: the field just goes missing

The REST side fails the opposite way. From the app's date, abandoned_checkout_url is left out of GET /admin/api/{version}/checkouts.json responses and out of the checkouts/create and checkouts/update webhook payloads for apps without access. Everything else in those responses is unchanged.

Shopify's warning: "There's no error, so your app won't be told it's missing." REST returns the field by default, so an app may receive it today without using it, and won't notice. An app that does use it is different. Shopify says features built on the URL, "such as recovery emails, SMS, or direct mail", lose their link, and code that assumes the key is present may fail.

Why it may not show up in testing

Shopify notes that development stores don't enforce protected customer data approval, so these errors won't appear there. An app can pass every test on a development store and still break on a live store on its date. To know where an app stands, check its protected customer data status in the Dev Dashboard.

For public apps, timing matters too. Shopify says reviews "can take a couple of weeks". The public-app date is 1 December 2026, so a request made after Shopify's 19 November announcement has little time to clear.

What app developers should do

  1. Search your code for both spellings: abandonedCheckoutUrl in GraphQL queries and bulk operations, and abandoned_checkout_url anywhere you read REST responses or checkout webhooks.
  2. If you don't use the URL, remove it. That is Shopify's own advice: "stop using the field." For REST, you can request only the fields you use with the fields parameter, and make sure your code handles the key being absent.
  3. If you need it, request all four fields before your date: in the Dev Dashboard, under your app's Settings → Access requests → Protected customer data → Manage, select name, email, phone and address with your reasons. Three of four will not work.
  4. Know which date is yours. Public apps: 1 December 2026. Partner custom and Dev Dashboard merchant-created apps: 1 January 2027. Apps created in the Shopify admin: not affected.

What support teams should watch for

If your store or your customers rely on an app that works with abandoned checkouts, the first sign of trouble may reach your support inbox rather than a developer's logs. Two patterns follow from Shopify's entry:

  • An app's abandoned checkout list or report is suddenly empty. Under the GraphQL behaviour above, that can mean one field was denied and the whole query came back null. It does not mean the checkouts are gone.
  • An app's recovery messages arrive without a working link, or stop going out. Under the REST and webhook behaviour, the URL is simply missing for apps without access, with no error.

In both cases the useful question for the app developer is the same: does the app have approval for all four protected customer data fields? The answer is in their Dev Dashboard. The entry covers apps reading the field through the Admin API. It says nothing about Shopify's own abandoned checkout features, so scope your answer to the app.

Shopify's 19 November changelog also carries other app deadlines, each with its own scope and date. They are separate changes, so check each entry on its own rather than assuming they share this one's rules.

Write the answer down once

When a platform change produces the same question from several people, write the answer once: which entry, which date, which apps, and what to check. Then every agent gives the same reply, and the next person can re-check it at the source.

If you're setting that up, DeskLeap brings tickets, live chat and a knowledge base into one place. The platform is 100% free with unlimited human agents; an optional AI Agent add-on is $29/mo each.

Source: Shopify developer changelog, "abandonedCheckoutUrl now requires level 2 protected customer data access", dated 19 November 2026, read 20 November 2026: shopify.dev.

Related posts

  • Shopify B2B Customer Account API Change: Blank Is Not Deleted
  • Shopify Network Access Declarations: What Changes on 1 December, What Changes on 1 January, and Which Apps Aren't Affected
  • Shopify's Server-Pixel Update Check Returns the Wrong Error: Why 'Missing Access Scope' May Mean 'This Staff Member Can't Use Your App'
Older post: Shopify B2B Customer Account API Change: Blank Is Not Deleted← All Posts
DeskLeap

Customer support that scales with your team — not against it.

Product
  • Inbox
  • Live chat
  • Knowledge base
  • Leap AI
  • Analytics
  • All features
  • Integrations
  • Shopify app
  • WordPress plugin
  • React SDK
  • Blog
Compare
  • vs Zendesk
  • vs Intercom
  • vs Freshdesk
  • vs Help Scout
  • vs Gorgias
  • vs Tidio
  • vs tawk.to
  • vs Crisp
  • Pricing
Resources
  • Blog
  • Developer docs
  • API reference
Company
  • Contact
  • Privacy
  • Terms
© 2026 Sidtechno.com LLC
PrivacyTerms