Shopify customer data erasure now moves faster, and a recent order no longer postpones processing. For merchants, the practical job is to check what happens to customer information outside Shopify before an erasure request reaches those systems. A shorter pending period exposes slow handoffs between support and app owners. Here’s what changed, which workflows deserve attention, and how we’d build a deletion process that staff can actually follow.
What changed in Shopify customer data erasure?
According to Shopify’s customer data erasure announcement, the change took effect on November 10, 2026. Requests now process after 5 days rather than remaining pending for 10 days.
Shopify now processes customer data erasure requests 5 days after submission, regardless of when the customer’s most recent order was placed. The announcement includes an exception: for recipients of scheduled gift cards, the request remains pending until the gift card has been delivered.
That distinction matters during holiday trading. A scheduled gift card has an explicit exception. A recent purchase does not. Support teams shouldn’t assume that an order awaiting attention will hold an erasure request open.
The announcement describes Shopify’s processing timing. It does not establish a universal legal deadline for every merchant, or prove that every connected system deletes its copy at the same moment. Keep those questions separate when you update internal guidance.
Why this deserves attention beyond the privacy inbox
Shopify’s Fall ’26 developer announcement describes opening its catalog, cart and checkout to agents and apps, alongside new tools for securing apps and storefronts. More ways to build commerce experiences mean merchants need a clearer view of where their integrations send customer information.
Our view: adding a new customer-facing experience should trigger a data-lifecycle review, not just a conversion review. If an integration receives identifiable customer data, someone needs to know how that data leaves the system when it’s no longer needed.
The commercial tension is real. Criteo’s discussion of DTC differentiation puts first-party data at the centre of more precise growth. That makes a useful merchant question unavoidable: can you explain which customer data supports a current purpose, and which data simply accumulated?
Don’t treat all first-party data as permanently available marketing infrastructure. Build useful customer experiences with a defined retention policy and a workable removal process.
Map Shopify customer data erasure beyond the customer profile
Start with a data map rather than a new privacy app. A merchant can remove information in a core platform while a spreadsheet or support attachment still contains a copy. Your review needs to follow the information, not the navigation menu.
For each destination, record the data it receives, its business purpose, its retention rules and the person responsible for it. Also document how it receives an erasure instruction and how completion can be checked.
- Customer communication systems: Check email and SMS platforms, including audience exports and suppression records.
- Service systems: Review helpdesk conversations, attachments and any customer details copied into internal notes.
- Operational integrations: Inspect fulfillment connections and accounting exports. Identify records that may require restricted retention rather than routine deletion.
- Internal data stores: Include analytics warehouses, shared files and custom app databases.
These are audit destinations, not a claim that every system behaves identically. An installed app may have an established privacy workflow. A manually exported file won’t necessarily participate in it. Ask for evidence of the actual behaviour.
Pay particular attention to less visible copies. A customer address inside an error log may escape a review focused entirely on database tables. A downloaded support attachment may survive after the original ticket changes.
Separate erasure from unsubscribe and record retention
An unsubscribe request changes marketing permissions; an erasure request concerns personal data. Staff shouldn’t use either as shorthand for the other.
A customer might want promotional emails stopped while keeping their account. Another might request erasure while a service issue remains unresolved. Those situations need different handling, even if they arrive through the same support inbox.
Decide what must remain, and why
Some records may need to remain for legal obligations or the handling of claims. The applicable rules depend on jurisdiction and the record involved. Have your privacy or legal adviser define the exceptions rather than asking a support agent to improvise them.
Where retention is justified, document its purpose and duration. Consider whether access should be restricted and unnecessary identifiers removed. A finance record retained for a legal obligation shouldn’t automatically remain available for marketing segmentation.
Equally, don’t instruct developers to wipe every record with a matching email address without understanding the consequences. The goal is a defensible process that removes data where required and narrowly controls justified exceptions.
Give the request an owner before it reaches an app vendor
The shorter pending period makes informal handoffs less comfortable. An unanswered message to an app developer isn’t a completed workflow.
Assign a request owner who can see the whole process. That person doesn’t need access to every database. They do need a reliable way to find out whether each responsible team has acted and whether anything needs escalation.
We’d use a restricted request record with the submission time, affected systems and completion status. Store only the identifying information necessary to coordinate the work. Otherwise, your privacy tracker can become another unnecessary copy of the data you intended to remove.
Ask vendors operational questions
A vendor saying it supports privacy compliance doesn’t tell your team how to handle a specific request. Ask:
- How does your service receive and recognise a customer erasure request?
- What customer information does the process remove, and what does it retain?
- How do we confirm completion or detect a failed request?
- How do you handle backups and prevent restored data from re-entering active use?
For custom integrations, ask the developer to demonstrate the workflow with controlled test data. An architecture diagram is useful, but it doesn’t prove the deployed application behaves as intended.
Test the awkward cases, especially scheduled gifts
A basic test with an inactive customer won’t cover the situations most likely to confuse staff. Build a small set of approved test scenarios around the workflows your store actually uses.
Include a recent order and a scheduled gift card recipient. Shopify explicitly says recent order timing no longer changes the processing schedule, while scheduled gift delivery can keep a request pending. Your support instructions should reflect that difference without broadening the exception to other order types.
Also test a customer represented in multiple systems. Confirm that the process finds the relevant records without removing another person’s data. Shared household details and changed email addresses deserve careful matching rules.
Use a development or otherwise approved test environment where possible. Don’t submit destructive requests against real customers merely to check whether an integration works.
Stop deleted information from quietly coming back
A deletion workflow can appear successful until an old export runs through an import job. Restoring a database backup can create a similar problem if the recovery procedure ignores requests completed after the backup was taken.
Ask your technical team how it handles stale source data. Which system controls the active customer record? Can a delayed integration recreate information that was removed? What checks run after a recovery?
Where a minimal suppression or deletion marker is necessary, have its design and retention reviewed. Don’t preserve a complete customer profile simply to remember that the profile was deleted.
We’d also review support macros. Remove wording that promises every connected record disappears immediately, unless you can substantiate that promise. Explain the request process accurately and make any applicable exceptions understandable.
What to change now
Update internal guidance to reflect the 5-day processing period and the scheduled gift card exception. Then identify integrations whose erasure handling is undocumented. Those unknowns deserve attention before cosmetic improvements to a privacy request form.
A specialist privacy tool can help coordinate requests across a complicated stack. A simpler store may be better served by a maintained system register and clear ownership. Neither option replaces vendor verification or testing.
Measure completion through evidence from the affected systems, rather than the moment someone closes a support ticket. The ticket records the work; it isn’t proof that the work happened.
Takeaways
- Shopify’s erasure processing period changed from 10 days to 5 days on November 10, 2026.
- A recent order no longer postpones processing. Scheduled gift card recipients have a specific exception until delivery.
- Map customer information outside Shopify and confirm how each destination handles erasure.
- Define justified retention separately from marketing access, and test for stale imports that could recreate removed data.
Sources
- Customer data erasure requests updated from 10 days to 5
- From sameness to standout: The next era of DTC brands
- Bringing shopping into the future: The Fall '26 Edition for ...
Want this handled for you?
We're a Shopify Premier Partner and this is the work we do every day: performance, CRO, and store builds that pay for themselves. Book a free store review and we'll show you the three fixes we'd ship first.
Frequently asked questions
How long do Shopify customer data erasure requests take?
As of November 10, 2026, Shopify processes requests 5 days after submission instead of holding them pending for 10 days. Recipients of scheduled gift cards remain pending until the gift card has been delivered.
Does a recent Shopify order delay customer data erasure?
No. Shopify’s update says requests process after 5 days regardless of when the customer's most recent order was placed. The announcement separately identifies an exception for scheduled gift card recipients.
Does Shopify customer data erasure remove data from every connected app?
The timing announcement does not establish that every connected system removes its copies at the same moment. Merchants should verify each app’s erasure workflow and separately review exports, internal databases and other stored copies.
Is customer data erasure the same as unsubscribing from marketing?
No. Unsubscribing changes marketing permissions. Erasure concerns personal data and requires a separate assessment of affected records, connected systems and any justified retention obligations.
