twimco.Let’s talk ↗︎
Menu
Field notes / Operations

Shopify now erases a customer's data five days after the request. Decide who checks for open subscriptions first

A customer asks you to delete their data on a Monday. By Saturday, Shopify has done it. Nobody on your team may have looked at what that customer still had open, or told the other tools that hold their email address.

Editorial engraving of a candle-maker opening a drawer of index cards while an assistant holds a five-day paper calendar in a bright studio.

As of November 10, 2026, Shopify processes a customer data erasure request five days after it is submitted, instead of holding it in a pending state for ten days. In that window a store user can still cancel it. Name one person to check the customer's open subscriptions, pre-orders and returns on day zero, and one list of every other system that holds the customer's details.

What changed

Shopify's developer changelog posted a short note on November 11. As of November 10, a customer data erasure request is no longer held in a pending state for ten days. It's processed five days after it was submitted, whatever date the customer's last order was. If the customer is the recipient of a gift card that's scheduled to send, the request waits until the card has been delivered.

That's the whole announcement, and it's easy to read past. It also removes an assumption some stores may have been making: that a customer who ordered recently would sit in the queue for a while, because the clock no longer depends on the date of the last order. For a store with a handful of requests a year, the old ten days gave you a long, forgiving gap to remember to look at things. Five days is a working week. If the request lands on a Thursday afternoon, you have until the following Tuesday.

Day zero: someone presses the button

The request begins in your admin. Per Shopify's Help Center, a store owner, or a staff member with the right customer permissions, opens the customer, chooses More actions, then Erase personal data. Shopify does the processing. You don't contact Support.

So the moment that matters is the one before the click. A customer emails to say "please delete everything." Someone on your team forwards it to whoever has admin rights. What's the first thing that person does? Usually it's press the button, because the request is clear and nobody wants to be the person who sat on it.

Make day zero a short routine instead, something a person can finish in ten minutes with the customer's profile open. Open the customer's profile and look for three things. Is there a subscription? Is there a pre-order or a payment that hasn't been collected yet? Is there a return or a warranty question still open? Shopify's help page is blunt about the first two: when you erase the data of a customer with active pre-authorized payments, such as pre-orders or subscriptions, the remaining payments aren't charged, subscription contracts are canceled, and you take the loss on the partial sale. That may be exactly what the customer wants. It shouldn't be a surprise to you.

Sequence of work

The five days, as Shopify describes them

  1. Day 0

    A staff member submits the erasure request in the admin. Check open subscriptions, pre-orders and returns.

  2. Days 1 to 4

    The request is pending. A user in your store can cancel it. List the other systems that hold the customer's details.

  3. Day 5

    Shopify processes the request and redacts the customer's personal data.

  4. Afterwards

    The profile and order history remain, without name and address. Anyone you shared the data with is still your job.

Dates from Shopify's changelog and Help Center; the checks on each day are an illustrative suggestion.
The window is five days. Decide on Monday who looks at the account.

Days one to four: the cancel window

The pending days exist for a reason. Shopify's Help Center says you have five days to cancel a request after you submit it, and if it was submitted from the admin, only users in your store can cancel it. Cancel it from the customer's profile, in the section showing the erasure request.

Use that time for two jobs, and do the first one before you touch the second. First, finish the real work with that customer: refund the return, settle the dispute, send the warranty replacement. Once the data is redacted, the order history stays but the name and address don't, so any follow-up gets harder. Second, make the list of everywhere else the customer's details live.

Here the help page matters. Shopify erases personal data from your store and from the apps and channels you've installed from the admin. It also says it's your responsibility to contact any other companies you've shared the customer's data with. Think about where else a customer's email address ends up. The helpdesk. The email marketing tool. A warehouse or 3PL that has the shipping address. A review tool. A spreadsheet somebody exported for a promotion. None of those hear about the request unless you tell them.

Day five: what's gone and what stays

When the five days pass, Shopify redacts details such as the customer's name and address. It keeps what was sold and the date and time of the sale. The customer profile and the order history stay in your admin, which is different from deleting a profile outright. Shopify's help page also notes that erasing a customer from your store doesn't erase data Shopify holds from the customer's own relationship with it, through Shop and Shop Pay. Those customers can use the Shop app settings or Shopify's privacy portal.

Two practical things follow. If a customer calls back next month about an order, your team will find a record with no name on it. Decide in advance what they say. And if accounting asks why a subscription vanished from the list in the middle of the month, the answer should be one note on the customer, not a hunt through the logs.

This isn't legal advice. Shopify's own help page says as much and points you to your own counsel for what the laws where you sell require. What the platform's timing changes is the part you control: how many days your team has to look before it happens.

Decision guide

What Shopify handles, and what stays with you

ConsiderationShopify doesYou still do
Personal data in the storeRedacts details such as name and addressDecide whether you still need to reach this customer first
Installed apps and channelsErasure also goes to those you installed from the adminCheck the apps that don't connect that way
Other companiesDoesn't contact them for youTell the helpdesk, email tool, warehouse and anyone else you shared data with
Subscriptions and pre-ordersCancels contracts; unpaid pre-authorized payments aren't chargedNotice the lost revenue before day five, not after
Shop and Shop Pay dataNot erased by your requestTell the customer that part goes through Shopify
Decision framework drawn from Shopify's Help Center page; not legal advice.

Who owns the five days

The window is five days. Decide on Monday who looks at the account. Choose a person, and a back-up for when they're out. Write down what they check on day zero. Keep the list of other systems somewhere the whole team can find it, and name the person who emails each one. If a store uses an agency or has staff in different time zones, say who's allowed to press the button and who has to be told first.

Then rehearse it once, early in the week, on a Monday if you can, using a real customer who's agreed, or a test one. Time how long the systems list takes to work through. If it takes longer than four days, you've found your problem before a real request did. If it takes ten minutes, write the steps down anyway, because the person who runs it next time may be someone who's never seen the list.

Finally, keep a short log of each request: the date it arrived, who handled it, which systems you contacted and when each confirmed. If a customer or a regulator ever asks what you did, that log is the answer.

If requests like this arrive in several channels, and the answer to "where does this customer's data live?" takes an afternoon of searching, we can help you build that list and the routing behind it. It's part of our ecommerce work, and a good first conversation. Talk to us.

Related work: Paddle8

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Paddle8 ↗︎