Shopify is tightening security around the abandoned checkout recovery URL. Effective December 1 2026 for public apps and January 1 2027 for custom apps, any app that reads the abandonedCheckoutUrl field must first be granted level 2 protected customer data access for all four protected fields—name, email, phone, and address. In this post we break down exactly what’s changing, who needs to act, and the steps you should take right now to stay compliant.
What’s Changing?
Previously, any app could request the abandonedCheckoutUrl field from the Admin API without additional approval. Starting the dates above, that field is locked behind level 2 protected customer data access. This means your app must be explicitly approved to read the URL, which contains the shopper’s personal information (name, email, phone, address). If your integration does not need the URL, Shopify recommends you stop requesting it altogether.
Who Is Affected?
Both public and custom apps are in scope, but the deadline differs. Public apps—those listed on the Shopify App Store—must have the required permission by December 1 2026. Custom apps built for a single merchant have a slightly later deadline of January 1 2027. Merchants themselves are not directly impacted unless the apps they use rely on this field; they’ll see broken recovery links if the app isn’t updated.
Why the Change Matters
The abandoned checkout URL can be used to reconstruct a shopper’s cart and contact details, making it a prime target for misuse. By requiring level 2 access, Shopify aligns this data with the same protection level as other sensitive customer fields, reducing the risk of data leakage and ensuring that only vetted apps can handle it.
How to Request Level 2 Access
abandonedCheckoutUrl. If not, remove the field from your queries.unauthenticated_read_customer_data scope with level 2. In your app’s OAuth request, include:scope=read_customers,read_checkouts,unauthenticated_read_customer_data_level_2
Code Adjustments You May Need
If you’re already using GraphQL, wrap the field in a conditional check that only runs when the app has the new permission. Example:
`query GetAbandonedCheckout($id: ID!) {
abandonedCheckout(id: $id) {
id
... on AbandonedCheckout {
abandonedCheckoutUrl @include(if: $hasLevel2)
}
}
}`
On the REST side, you can filter the field out of the response if the scope is missing:
GET /admin/api/2024-07/abandoned_checkouts.json?fields=id,created_at
This way, you avoid a 403 error when the permission isn’t granted yet.
Next Steps & Timeline
abandonedCheckoutUrl.Conclusion & Call to Action
Shopify’s move to protect the abandoned checkout URL is a clear signal that customer data security is non‑negotiable. By acting now—auditing your usage, requesting level 2 access, and updating your code—you’ll keep your app functional and your merchants happy. Need help navigating the permission request flow or refactoring your API calls? Reach out to our Shopify developer community or drop a comment below; we’re here to make the transition smooth.
