If your Shopify app sends abandoned cart emails or texts, check how it gets the recovery link. Shopify is moving that link behind its strictest level of customer data approval, and if you use the REST API, your app won't get an error when it disappears. The link just stops arriving.
The change went up on Shopify's developer changelog on 19 November, headed abandonedCheckoutUrl now requires level 2 protected customer data access. It's marked as a breaking change and "action required", and Shopify says it's being made for security reasons.
Why the link matters
The abandoned checkout URL is the link you put in a "you left something in your basket" email. Click it and the customer lands back in their checkout with their details already filled in. That's the whole point of it, and it's also the problem. The link opens a page showing the buyer's name, email, phone number and address.
So Shopify now treats the link like the data behind it. If your app can't already read all four of those fields, it shouldn't be able to get a link that shows them.
The dates
- 1 December 2026: public apps. Getting access means going through Shopify's data protection review.
- 1 January 2027: custom apps built by a partner for a store, and apps a merchant created in the Dev Dashboard. These get access by switching the fields on in the Dev Dashboard, with no review.
The changelog says apps created in the Shopify admin aren't affected. Apps that already have approval for name, email, phone and address aren't affected either. Approval for some of the four isn't enough. It has to be all of them.
For the usual agency setup (a custom app built for one client's store), that's 1 January. Which is a fine date on paper, and a terrible one in practice, because nobody is looking at their abandoned cart emails on New Year's Day.
What breaks, and how quietly
This is the part worth reading twice, because the three ways of getting the link fail in different ways.
GraphQL Admin API. Asking for abandonedCheckoutUrl without access returns an ACCESS_DENIED error, and the error nulls out the data around it. On a list query such as abandonedCheckouts, Shopify says you get data: null. So you don't lose the link. You lose every abandoned checkout in the response. Bulk operations that select the field fail with ACCESS_DENIED after retrying for a few minutes.
REST Admin API. The abandoned_checkout_url field is simply left out of the response from the checkouts endpoint. In Shopify's words, "There's no error, so your app won't be told it's missing."
Webhooks. The same field is left out of the checkouts/create and checkouts/update payloads.
The GraphQL failure is loud, and loud is good. Something will log an error and someone will notice. The REST and webhook versions are the worrying ones. Picture an older app that listens for checkout webhooks, waits an hour, then sends an email with the recovery link in it. After the deadline it carries on happily, sending emails with an empty link, or a broken button, or nothing at all, depending on how carefully it was written. Nothing in the logs says why.
And one more catch: development stores don't enforce protected customer data approval. So you can test the app on a dev store, see the link come through perfectly, and still have it fail on the live store.
What to do
First, find out whether you use the field. Search the code for abandonedCheckoutUrl and abandoned_checkout_url, and check what any webhook handlers for checkouts/create and checkouts/update do with the payload. Don't forget bulk operation queries, which often live in a separate file from the rest.
If you don't need it, take it out. For GraphQL that means removing it from the query. For REST, Shopify suggests asking only for the fields you use with the fields parameter, which is good practice anyway.
If you do need it, request access before the deadline. In the Dev Dashboard it's your app, then Settings, Access requests, Protected customer data, Manage. Select customer data and the name, email, phone and address fields, give your reasons, and fill in the data protection details. For public apps, Shopify notes reviews "can take a couple of weeks", so 1 December is closer than it looks.
Whichever way you go, make the code cope with the field being missing. If there's no link, the app should log it and skip that message, rather than send a customer an email with a dead button in it.
Level 2 isn't just a tick box
Shopify's protected customer data docs list what level 2 expects on top of the basics. Encrypted backups, test and production data kept apart, a data loss prevention strategy, limited staff access, strong passwords, an access log for protected customer data and a security incident response policy.
Custom apps don't go through the review, but I'd still read that list as a description of how an app holding customer names and addresses ought to be run. If your app keeps copies of checkout data on your own server, those are fair questions to ask about that server too. Shopify's recent change to erasure requests points the same way.
The wider lesson is about silent failures. An integration that stops working loudly gets fixed the same day. One that quietly sends half an email can go on for weeks. It's worth having something that checks the output looks right, not just that the job ran. That's a big part of why I ended up building my own server monitor, and the same thinking applies to anything that runs on a schedule and talks to Shopify.
If you're not sure what your app does
That's common with an app built a few years ago by someone who's since moved on. We build and look after Shopify integrations and custom apps. Our code audit (£250 + VAT) will tell you which Shopify fields and webhooks your app relies on, including this one. If you'd rather someone just kept an eye on Shopify's changes for you, Look after it starts from £355 a month + VAT.
If your abandoned cart emails come from a custom app, get in touch before Christmas rather than after New Year.
Cheers, Rob

