See all services → Shopify Plus Partner
Action Required Developer

Request Protected Data Access for Abandoned Checkout URLs

The abandoned checkout recovery URL now needs approval for all four protected customer fields. GraphQL queries fail loudly, but REST and webhooks drop the field with no error at all, which is the failure mode to plan for.

Executive summary

What changed

Access to the recovery URL is now gated on holding all four protected customer fields, across every supported Admin API version and unstable. Partial approval does not count: an app cleared for email and name but not phone and address loses the field. Public apps request access and clear a data protection review. Partner custom apps and merchant-created apps in the Dev Dashboard enable the four fields themselves, no review needed. Apps created in the Shopify admin are unaffected.

Failure behaviour differs by API, and the REST case deserves attention. In GraphQL, selecting the field returns ACCESS_DENIED and the error nulls surrounding data, so a list query such as abandonedCheckouts returns data: null and you lose every record in that query, not just the URL. Node lookups return null, and bulk operations fail after retrying. In REST and webhook payloads there is no error at all: the field is simply omitted from checkouts.json responses and from checkouts/create and checkouts/update webhooks.

Why it matters

Abandoned cart recovery is often worth a measurable share of revenue, and the silent REST failure is the part that will cost someone a quarter. An integration building recovery emails from webhook payloads keeps running, keeps sending, and keeps reporting success while the link in every message is broken. Nothing flags a field that stopped arriving unless you were already asserting on it.

The GraphQL behaviour is louder but blunter. Because the error nulls the surrounding payload, one unnecessary field can take out an entire reporting pipeline. Any team doing customer data work on Shopify should audit which fields their queries actually consume, since the cheapest fix is deleting a field nobody uses.

Role-specific impact

Use-case example

Real-world scenario

A beauty brand recovers carts through a custom app that listens to checkouts/update webhooks and pushes payloads to its ESP. Recovery email drives about 3.1 percent of monthly revenue. The app is partner built, so the team has until January 1, 2027, and enabling the four fields takes minutes. The real work was defensive: the developer added an alert for when abandoned_checkout_url is absent from a payload, plus a template guard that suppresses the email rather than sending a dead link. Without it, the first sign of trouble would have been a revenue dip noticed weeks later.

Implementation checklist

  1. Search all code, queries, and bulk operations for abandonedCheckoutUrl and abandoned_checkout_url.
  2. Remove the field anywhere it is selected but not used, which resolves the issue outright.
  3. Confirm each consumer's app type, which sets your date and whether a review applies.
  4. For partner custom and Dev Dashboard apps, enable name, email, phone, and address in the Dev Dashboard.
  5. For public apps, request access and allow time for the data protection review before December 1, 2026.
  6. Add a presence assertion and alerting on the REST and webhook field so a silent omission surfaces.
  7. Guard email templates to suppress sends when the recovery URL is missing.
  8. Test a full recovery flow end to end after the change and click through the link.

FAQ

Q: We already have approval for email and name. Is that enough?

A: No. All four fields are required together for this purpose, and holding three of the four leaves you in the same position as holding none.

Q: Our recovery app is from the App Store. Do we need to do anything?

A: Your job is verification, not implementation. The vendor must request access and clear a data protection review by December 1, 2026. Ask for written confirmation, then test the flow yourself in early December.

Resources

Shopify's guide to requesting the relevant access levels: Request access to protected customer data.

Need guidance? Talk to Makro.