Why `abandonedCheckoutUrl` Now Needs Level 2 Protected Customer Data Access (and What to Do)

Starting Dec 1 2026 for public apps, Shopify requires level 2 protected customer data access to read abandonedCheckoutUrl. Learn who is affected, why the change matters, and how to update your app before the deadline.

Why `abandonedCheckoutUrl` Now Needs Level 2 Protected Customer Data Access (and What to Do)
7 sections

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

  • Review the need – Confirm that your app truly requires abandonedCheckoutUrl. If not, remove the field from your queries.
  • Update your OAuth scopes – Add the 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

  • Submit a permission request – In the Partner Dashboard, go to Apps → Your App → Permissions and click Request additional data access. Choose “Protected Customer Data – Level 2” and provide a brief justification (e.g., “Needed to send personalized abandoned cart recovery emails”).
  • Wait for approval – Shopify reviews requests manually; most are approved within 7‑10 business days.
  • Update your app version – Once approved, publish a new version that includes the updated scopes and, if necessary, the revised API calls.
  • 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

  • Today‑Oct 2026: Audit your codebase for any usage of abandonedCheckoutUrl.
  • Nov‑2026: Submit the level 2 access request if you need the field.
  • Dec 1 2026 (public apps) / Jan 1 2027 (custom apps): Deadline – apps without approval will receive a 403 error.
  • Post‑deadline: Monitor logs for permission errors and roll out fallback logic for merchants whose apps lost the URL.
  • 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.

    Tags
    Sources

    Related Articles

    Why Network Access Declarations Are Now Mandatory for Online Store Apps

    Why Network Access Declarations Are Now Mandatory for Online Store Apps

    Shopify now requires apps that run on the online store to declare their network access in shopify.app.toml. Learn what changed, who’s affected, and how to update your app before the December 2026 deadline.

    November 19, 20264 min
    Understanding the New applyResult Field in RolloutChange: What Developers Need to Know

    Understanding the New applyResult Field in RolloutChange: What Developers Need to Know

    Shopify’s GraphQL Admin API now returns an applyResult field on RolloutChange, letting apps track rollout outcomes in real time. Learn what changed, who it affects, and how to update your code to handle success, failure, and in‑progress states.

    November 19, 20264 min

    November 19, 20261 min
    Store Credit Now Powers Shopify Subscriptions with allowStoreCredit

    Store Credit Now Powers Shopify Subscriptions with allowStoreCredit

    Shopify’s 2027-01 API adds store‑credit support to subscriptions via the allowStoreCredit flag. Learn what changed, who’s impacted, and how developers can enable this new feature in minutes.

    November 19, 20265 min