Executive summary
- What: As of November 10, 2026, customer data erasure requests are processed 5 days after submission rather than being held pending for 10 days.
- Why it matters: Your window to catch and cancel a mistaken erasure has halved, and downstream systems now receive redaction events sooner and on a predictable schedule.
- Who should act: Store admins and customer service leads who action privacy requests, plus anyone owning the integrations that mirror customer records.
What changed
Previously an erasure request sat in a pending state for 10 days, and the timing interacted with when the customer last ordered. That behaviour is gone. A request now processes 5 days after it was submitted, regardless of the most recent order date. One exception remains: if the customer is the recipient of a gift card scheduled to send, the request stays pending until the gift card has been delivered.
The cancellation window matches the new timing. After submitting a request you have 5 days to cancel it, and when the request originated in the Shopify admin only users in your store can cancel it. Erasure itself is unchanged in scope: Shopify redacts personal data such as name and address from the customer profile and propagates the request to apps and channels you installed from your admin. What was sold, and when, stays visible. Contacting any other party you shared that customer's data with is still your responsibility.
Why it matters
The old 10 day pending period was, in practice, a generous safety net. Support agents action erasure requests from inboxes and ticket queues, and picking the wrong customer profile is an ordinary human error. Halving the window halves the time to notice. Erasure is not reversible once processed, so the operational answer is a review step before submission rather than a reliance on catching it afterwards.
The second effect is on integrations. Because timing is now deterministic and detached from order history, redaction events arrive on a fixed 5 day clock. That makes reconciliation easier to reason about, and it also means ERP, CRM, and warehouse systems holding their own copy of customer PII will see those records go quiet earlier than before. Any process that assumed a longer grace period, such as a nightly export that backfills addresses for in-flight shipments, needs checking. This is the kind of cross-system dependency we work through in how Shopify Plus ensures security and compliance for enterprise e-commerce.
Role-specific impact
- Marketers: suppression and consent lists should be driven from your own records, not from the presence of a readable name on a Shopify profile, since redacted profiles persist with order history intact.
- Developers: confirm your customer redaction webhook handlers are idempotent and run reliably, and review any scheduled job that reads customer PII on a weekly or longer cadence. A 5 day clock can now outrun a weekly batch.
- Store admins: build a verification step into the erasure workflow. Confirm the customer identity against the request before clicking through, because you have 5 days rather than 10 to undo a mistake.
Use-case example
Real-world scenario
A retailer handling around 60 erasure requests a month ran a weekly privacy review every Monday, which comfortably caught errors inside the old 10 day window. Under the new timing, a request submitted on a Tuesday processes before the following Monday's review. Moving the check to the point of submission, with a second pair of eyes on any request not raised directly by the customer, costs about two minutes per request and removes the dependency on a review cadence that no longer fits.
Implementation checklist
- Document the new 5 day timing in your privacy response runbook and remove references to the 10 day pending period.
- Add an identity verification step before submission rather than relying on post-submission cancellation.
- Confirm who in your organization can cancel a pending request, remembering that admin-raised requests can only be cancelled by your own users.
- Inventory scheduled jobs and exports that read customer PII, and check none of them run on a cadence longer than 5 days where that matters.
- Verify downstream systems act on customer redaction events rather than ignoring them, since Shopify propagates the request to installed apps and channels.
- Note the gift card exception for scheduled sends so support does not treat a legitimately pending request as stuck.
FAQ
Q: Can we extend the window back to 10 days?
A: No, the timing is platform behaviour and not configurable. Shift your control earlier, to the point where the request is raised.
Q: Does erasure delete the customer's orders?
A: No. Erasure redacts personal data such as name and address while the profile and order history remain in your admin. Deleting a customer profile is a separate action with different consequences.
Resources
Processing customer data requests
Need guidance? Talk to Makro.