An order can be finished in minutes, but the records behind it may matter years later. If a customer disputes a payment, a tax authority asks for supporting documents, or someone requests deletion of their personal data, can you find the right information—and explain why you still have it?
For most online stores, ecommerce record retention means keeping financial and transaction evidence long enough to meet applicable requirements, while deleting or anonymizing personal data when you no longer need it. There is no single retention period for every store or every record. Your location, where you sell, the type of record, and any active dispute all matter. Here’s a practical way to decide what to keep, for how long, and how to manage it without saving everything forever.
Which ecommerce records should you keep?
Start with records that substantiate your accounts, tax filings, customer transactions, and legal obligations. An order summary alone may not be enough: you may also need the invoice, payment reference, refund history, and evidence that an item was shipped or delivered.
| Record type | Examples | Why you may need it |
|---|---|---|
| Sales and payment records | Orders, invoices, receipts, payment processor statements, refunds, and chargebacks | Accounting, taxes, reconciliation, and dispute resolution |
| Tax records | Sales tax or VAT returns, exemption certificates, marketplace tax reports, and supporting calculations | To support amounts collected, reported, or exempted |
| Purchasing and inventory records | Supplier invoices, purchase orders, stock adjustments, and cost records | To substantiate expenses, inventory values, and product history |
| Fulfillment records | Shipping labels, tracking, delivery confirmation, and return documentation | To investigate lost parcels, returns, and payment disputes |
| Customer service records | Relevant messages about orders, complaints, warranties, and returns | To understand and resolve a specific customer issue |
| Business and personnel records | Contracts, payroll records, and business formation documents | To meet separate employment, tax, and corporate obligations |
Keep the evidence, not every copy. A reliable invoice and associated transaction record may serve a clear purpose; duplicate exports of the same customer list often do not. Your aim is a complete, retrievable record with as little unnecessary personal information as possible.
How long should an online store keep records?
Set retention periods by record type and jurisdiction, rather than applying one blanket rule to your entire store. The examples below are starting points, not universal deadlines:
- United States federal tax records: The IRS generally advises keeping records that support a tax return until the applicable period of limitations expires. That period is often three years, but longer periods can apply in some circumstances. Employment tax records generally need to be kept for at least four years after the tax is due or paid, whichever is later. State tax and sales tax rules may differ.
- United Kingdom VAT records: VAT-registered businesses generally must keep VAT records for at least six years, although exceptions and other recordkeeping rules can apply. Check the requirements for the particular records your business holds.
- EU VAT One Stop Shop (OSS) records: If you use an OSS scheme, transaction records generally must be kept for ten years from the end of the year in which the transaction took place.
- Personal data: Privacy rules generally call for keeping identifiable customer information only as long as necessary for a legitimate purpose, subject to legal retention duties. They do not give every ecommerce customer record one fixed expiry date.
Other obligations may extend your timeline. A supplier contract, warranty, ongoing chargeback, insurance claim, litigation hold, or local tax rule may require you to preserve relevant records longer. Conversely, you may have no good reason to retain old marketing data after a customer withdraws consent or stops engaging, depending on the law and your documented purpose.
If you sell across borders, ask an accountant or qualified legal adviser which rules apply to your entity and transactions. In particular, do not assume that the rules for your business address cover every tax registration or marketplace arrangement.
A practical retention schedule for an online store
A retention schedule is a short internal document that tells your team what is stored, why, where it lives, and when to review or delete it. It does not need to be complicated. Build yours in five steps.
1. Map where your records live
List your storefront, payment processor, accounting system, shipping platform, email inbox, customer support tool, cloud storage, and any marketplace accounts. Check whether each service stores its own copies and whether records remain available after you close an account or change providers.
2. Group records by purpose
Separate tax and accounting evidence from fulfillment records, customer support conversations, and marketing data. One order may appear in several systems, but those copies may have different purposes and access requirements.
3. Assign a rule to each category
For every category, document the applicable legal minimum, any business reason to keep it longer, and the event that starts the clock—such as the tax filing date, financial year-end, order completion, or end of a warranty. Record who approved the rule and when it will be reviewed.
4. Protect records while you retain them
Limit access to people who need it, use appropriate security controls and backups, and test whether you can actually retrieve an older record. A five-year retention policy is little help if a former employee’s inbox is the only place a supplier invoice exists.
5. Delete, anonymize, or review records at the right time
Set a recurring review rather than relying on someone to remember individual dates. Pause routine deletion for records relevant to a known dispute, audit, investigation, or legal hold. When the hold ends, reassess them under your normal schedule.
For example, a small apparel store might retain an order’s invoice and tax evidence under its applicable accounting rules, keep delivery confirmation while it remains useful for disputes, and remove an unrelated customer service note sooner. The same customer’s marketing preferences should be managed separately from the order’s tax record.
Record retention and customer privacy: what changes?
Customers may reasonably ask why their details are still in your systems after an order is complete. Your answer should reflect your actual practices: you may need certain transaction data for tax, accounting, fraud prevention, or legal claims, but that does not justify retaining every message, browsing detail, or export indefinitely.
Where privacy laws such as the UK GDPR or EU GDPR apply, storage limitation and data minimization are important principles. A deletion request also does not necessarily require you to erase records you must retain to meet a legal obligation. Assess the request against the law that applies to your business, delete data you no longer need, and explain any information you must keep.
Payment data deserves particular care. Do not store card security codes after authorization; payment-card security standards prohibit it. Use your payment provider’s transaction references and reports for reconciliation instead of collecting card details you do not need.
Common record retention mistakes to avoid
- Using one deadline for everything. Tax evidence, marketing contacts, and support tickets do not necessarily belong on the same schedule.
- Assuming your platform is your archive. Confirm what your providers retain, what you can export, and whether exports include the details needed for an audit or dispute.
- Keeping data “just in case.” Indefinite storage increases the amount of sensitive information you must manage and protect.
- Deleting an order record when a customer unsubscribes. Unsubscribing from marketing and retaining a legally required sales record are separate issues.
- Forgetting exceptions. Before scheduled deletion, check for open returns, warranties, tax inquiries, and legal holds.
Make your policy workable, not just written
A useful policy should let you answer three questions quickly: What do we have? Why are we keeping it? When can it go? Begin with your highest-risk records—orders, payments, tax documents, and customer data—then work through less critical systems. Review the schedule when you enter a new market, add a sales channel, change providers, or receive updated professional advice.
If you have not mapped your records yet, make that your next step. Export a sample order and trace its information through your storefront, payment, shipping, accounting, and support systems. That one exercise often reveals the gaps and duplicate data your retention schedule needs to address.
Frequently asked questions
Do I need to keep every customer email?
Usually not. Keep communications that support an order, complaint, warranty, dispute, or other defined purpose for an appropriate period. Set a separate review and deletion rule for routine or outdated messages.
Can I delete a customer’s order history if they ask?
You may need to keep some transaction information to meet tax or other legal obligations, even when a customer requests deletion. Review the request under the privacy law that applies to you, remove data you no longer need, and explain any lawful retention.
Are digital records acceptable for tax purposes?
Often, yes, but requirements vary. Your digital records should remain accurate, readable, secure, and retrievable for the required period. Check the rules that apply to your tax registrations and the types of records you keep.
Does a marketplace keep records for me?
A marketplace may hold transaction data, but you remain responsible for understanding your own recordkeeping duties. Download the reports you need, confirm what they contain, and check how long you can access them.