On this page
Why this happens or what changed
The old ten-day hold is no longer a safe timer for CRM cleanup, customer support escalation, or third-party deletion jobs. An order placed recently does not restart the new five-day window. This changes Shopify’s processing schedule; it does not eliminate an app’s separate obligations under privacy laws or Shopify’s mandatory compliance webhook requirements.
Practical fix
- Search job queues, support macros, documentation, and dashboards for hard-coded ten-day customer deletion assumptions.
- Use the request submission timestamp and actual platform events as authoritative signals rather than calculating a deadline from the most recent order.
- Review how the integration handles
customers/data_request,customers/redact, andshop/redactcompliance topics where applicable. Do not conflate a data access request with erasure. - Ensure deletion handlers are idempotent, record minimal audit metadata, and remove personal data from downstream services according to applicable requirements.
- Handle scheduled gift-card recipients as a distinct pending case; do not assume every request will complete exactly five days after submission.
Production considerations
Keep privacy handling separate from ordinary customer lifecycle webhooks such as customer updates or account activation. A support ticket being marked resolved does not prove that copies in analytics, marketing, support, or fulfillment systems have been addressed. Confirm any lawful retention exceptions with the appropriate privacy owner.
How to test this
- Submit a controlled erasure request using a permitted test process and record the submission timestamp.
- Verify the workflow no longer waits on a ten-day timer or a customer’s latest order date.
- Test webhook signature verification, retry behavior, and duplicate event handling.
- Check downstream deletion jobs and their audit trail without storing the erased personal data.
- Review the scheduled gift-card exception and escalation handling.

