The eight questions that arrive first, answered in one line each
8 questions cover almost every case where a login is still open and a parcel is still somewhere in the chain. Two of the 8 have fixed answers that follow from the order of the stages; the other 6 end in the same place, which is a reply in writing from the agent. Read the table before you open a settings page, because the rows are ordered by when the steps happen, not by how often the questions arrive.
| Question | One-line answer | What it rests on |
|---|---|---|
| Can the account be deleted with an item still at the warehouse? | Ask in writing first; treat it as unanswered until a reply exists | Agent reply — not published |
| Does deleting the account cancel the order? | No. Cancelling is a separate action with its own window | Stage order |
| Does the warehouse storage clock stop? | The clock runs against the item, not against your login | Stage order |
| Can I still pay freight afterwards? | Only through an account that still exists, so pay the freight first | Flow dependency |
| What happens to the QC photos and the claim thread? | They live inside the order record; export them before anything closes | Flow dependency |
| Does my country data law force an erasure? | Read the official text for your jurisdiction and use its request route | Public regulation |
Rows 4, 5 and 6 are the expensive ones. Picture day 6: a 2 kg parcel sits in the warehouse, the freight invoice does not exist yet because the box has not been packed, and the QC set that would settle a wrong-size claim lives in the record you are about to lose access to. No settings toggle resolves any of that, and no stage window on the [warehouse-in](/steps/warehouse-in/) step covers a deletion either.
No agent page opened for this note in 2026 describes account deletion while a parcel is open. Every "ask" below means: get the answer in the support thread and keep it.
Questions that belong to the account record itself
Cancellation lives at the front of the chain. Across day 0 and day 1 the cancel route and the refund route are both available; the moment the item reaches the warehouse, cancel closes and a return path opens in its place. Deleting an account is neither of those two actions, which is why the [returns](/table/returns/) page tracks them separately. Three records usually sit behind one login: the credential, the address book and the payment reference. Ask which of the three a deletion touches.
Six things are worth exporting on the same afternoon, and none of them takes more than a few minutes. A claim filed 40 days later is judged on what you can still show, and a dated screenshot of a 1.8 kg parcel beats a description typed from memory in December.
- Order and parcel numbers, copied as text rather than as a picture
- The QC set at full resolution, not the compressed preview the page loads first
- The freight invoice, with the billed weight in kg printed on it
- Every support reply, including the two that only said the case was being checked
- One tracking number per leg, with the carrier name written next to it
Questions the parcel decides, not the account
Freight is charged on the parcel at a stage that comes after the item payment, and the amount cannot exist until the box is packed and weighed. Delete the account on day 5 and let the parcel be packed on day 9, and that invoice has nowhere to land. This single ordering problem is why the note opens with a table instead of a checklist.
Merging adds a second one-way door. Once 2 items are packed into one parcel, the address on that parcel cannot be changed, and unpacking it means opening a new shipment with its own freight. If an account action and a merge decision are both pending, settle the merge question first: a 3 kg merged parcel and two 1.5 kg parcels can end up on 2 different invoices with 2 sets of minimum charges.
Weight is what the freight line reacts to, and billed weight is not always the number on the scale. A 40 × 30 × 25 cm carton measures 30,000 cm³, which at a 6,000 divisor bills as 5.0 kg even when the contents weigh 4.2 kg. The divisor belongs to the carrier card, so read that figure as arithmetic rather than as a rate anyone published.
Merging and address edits close earlier than most people expect. Check both against the stage list before sending a deletion request.
Where only a written request counts as an answer
Send 1 message that names 4 things: the account identifier, the parcel number, the exact action you want, and the date you need an answer by. Asking for a reply within 5 working days is a request, not a service level, and nobody is obliged to grant it. What the message does buy is a dated record of what you asked and when.
- The account identifier as it appears in the profile, not the email you signed up with
- The parcel number and the item numbers packed inside it
- One sentence naming the action, plus the date the parcel must stay reachable until
- A reply address that will still exist after the account is closed
Data-protection law is the one part of this question with a public text behind it. Several jurisdictions let a person require an operator to erase personal data, and the operator notice has to say how to make that request and which records it must keep anyway. Read the official wording for your country instead of a summary, because a tax or accounting duty can outlast the erasure right: a paid invoice from 2023 may have to stay on file long after the login is gone.
Four situations that reorder the whole sequence
| Situation | What changes | First move |
|---|---|---|
| A claim or dispute is still open | The thread is the evidence file, and closing it early weakens the case | Get the claim decision in writing first |
| The parcel has already cleared customs | Address and merge options are gone; only the destination carrier can act | Log the problem with the destination carrier |
| Freight is unpaid and the storage window is running | The item can be handled under terms you accepted at signup | Pay the freight or request a written extension |
| A return is in progress | Credit usually lands in the account you are about to close | Move the credit out, then close |
The [receive-check](/steps/receive-check/) stage is the one that punishes impatience hardest. Its claim window keeps counting after delivery, and a deletion on day 15 of that window removes the thread the claim would be argued in. Wait for the decision, then act.
- Pay the international freight, or get a written extension on the storage clock
- Wait for any open claim to reach a written decision
- Export the records listed further up this page
- Ask for the deletion inside the same support thread, naming the date you need a reply by
- Try the login again 7 days later, and reopen the request if it still works
A single sentence holds the whole thing together. An account is a container; the parcel, the claim and the invoice are the contents. Empty the container first, and the deletion question stops being urgent, which is the only state in which it is safe to answer it — usually about 2 weeks after the parcel lands.
Flow dependency: the account record is the only thread holding the warehouse slot, the claim file and the freight balance at once, so deletion has to come after the freight is paid and the claim decision is written down — derived from the order of the stages, not from any published deletion policy.
This note explains the mechanics; the list is where the items are.