Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- The change starts December 1, 2026 for public apps and January 1, 2027 for partner custom apps and merchant apps created in Dev Dashboard.
- Selecting the URL in GraphQL can fail the entire abandoned checkout list. REST and affected webhooks omit the URL field.
- Verify all four fields in Dev Dashboard and test failures with synthetic responses. A successful development-store query does not establish production approval.
Identify the app type, field dependency, and effective date
On November 19, 2026, Shopify announced that reading an abandoned checkout recovery URL requires permission for four protected customer fields: name, email, phone, and address. This applies to all supported Admin API versions and <code>unstable</code>. Public apps are affected from December 1, 2026 and need data protection review. Partner custom apps for a specific store and merchant apps created in Dev Dashboard are affected from January 1, 2027. They can enable the four fields in the dashboard. Apps created directly in Shopify admin are unaffected.
Inventory what the app reads in GraphQL queries, bulk operations, REST parsing, and webhook consumers. If a reporting feature only uses IDs, dates, or status, remove the URL from its GraphQL and bulk selections. For features that genuinely use the link, such as recovery email or SMS, check the applicable permissions.
GraphQL rejects the selection. REST and webhooks omit the field
When an app lacks any of the four permissions, GraphQL returns <code>ACCESS_DENIED</code> for <code>abandonedCheckoutUrl</code>. Shopify's list example for <code>abandonedCheckouts</code> returns <code>data: null</code> for the whole query. A <code>node</code> or <code>nodes</code> lookup returns null for the affected checkout. Bulk operations that select the field also fail with an authorization error. Record the error and operation name so an authorization failure does not appear as an empty checkout list.
REST <code>checkouts.json</code> responses and <code>checkouts/create</code> and <code>checkouts/update</code> webhook payloads omit <code>abandoned_checkout_url</code> without a separate error. Check whether the key exists. If it is absent, stop the action that needs a link while allowing independent order reporting or status processing to continue.
Verify the actual entitlement in Dev Dashboard
If the app needs the URL, open its Settings and Access requests in Dev Dashboard. Under Protected customer data, use Manage to check name, email, phone, and address. Public apps must submit their use case and receive approval. Partner custom apps and merchant apps created in Dev Dashboard can enable the relevant fields as documented. If the app already has some fields, verify the rest. Ordinary Admin API scope checks do not show this protected data approval.
For development, choose a distribution method and select the fields needed for testing. Shopify states that development stores do not enforce this approval check. If a query returns the URL during development, still verify all four permissions for the production app in Dev Dashboard.
Test the failure paths with synthetic responses
Use a synthetic GraphQL response with an authorization error and <code>data: null</code>, plus REST and webhook fixtures without the URL key. Confirm the app records the authorization problem, stops messages that need the link, and keeps unrelated processing available. Use mock links in tests and logs to avoid copying real recovery URLs that carry customer details.
Sources
Frequently Asked Questions
Can I avoid this by pinning an older Admin API version?
Shopify's announcement covers all supported versions and unstable. Check the effective date for your app type and confirm all four permissions.
Can I read the URL if only email access is approved?
The URL requires name, email, phone, and address. Check each permission in Dev Dashboard.
Does a returned URL in a development store guarantee the live app has access?
Development stores do not enforce this check. Verify production app permissions and test how your app handles authorization errors and missing fields.