GDPR obligations for online businesses: a practical guide for small shops

What the GDPR requires of an online shop: lawful bases, privacy notices, processor contracts, data subject rights, breach deadlines and US data transfers.

Key points

  • Every processing activity needs one of the six lawful bases in Article 6, chosen before you start and recorded.
  • Most online shops rely on contract for orders, legal obligation for tax records and consent or legitimate interests for marketing.
  • Data subject requests must normally be answered within one month; personal data breaches must be reported to the authority within 72 hours where there is a risk to people.
  • The EU–US Data Privacy Framework remains valid as of November 2026, but an appeal is pending before the Court of Justice, so keep a fallback such as standard contractual clauses.
  • EU reform proposals, including the Digital Omnibus, are still under negotiation; the current GDPR text continues to apply in full.

An online shop handles more personal data than its owners usually realise: names and addresses for delivery, payment references, account logins, support emails, newsletter lists, analytics identifiers and, increasingly, data passed to advertising platforms. The General Data Protection Regulation applies to all of it whenever the business is established in the EU or targets people in the EU. This guide sets out what the regulation actually requires of a small or mid-sized online business, as the law stands in November 2026.

Who the GDPR applies to

The GDPR applies to any organisation established in the EU that processes personal data, regardless of size, and to organisations outside the EU that offer goods or services to people in the EU or monitor their behaviour there (Article 3). A UK or US shop that ships to Germany, prices in euros and runs ads aimed at French customers is within scope for those customers. A business caught by the territorial rule without an EU establishment must generally appoint a representative in the EU (Article 27), unless its processing is occasional, low-risk and does not involve sensitive data at scale.

The UK has its own version, the UK GDPR, amended most recently by the Data (Use and Access) Act 2025. The core concepts below are shared, but UK details differ, particularly on cookies; our guide to cookie consent and analytics covers the UK changes that took effect in February 2026.

Choosing a lawful basis for each activity

Every processing activity needs one of six lawful bases in Article 6(1): consent, contract, legal obligation, vital interests, public task or legitimate interests. The basis must be chosen before processing starts, recorded, and stated in your privacy notice. It is not interchangeable afterwards: a business that collected data on the basis of consent cannot quietly switch to legitimate interests when someone withdraws it.

For a typical online shop the mapping looks like this:

Activity Usual lawful basis Notes
Processing orders, delivery, customer accounts needed to buy Contract (Art. 6(1)(b)) Only what is genuinely necessary to perform the contract
Keeping invoices and tax records Legal obligation (Art. 6(1)(c)) Retention periods are set by national tax law
Fraud screening on payments Legitimate interests (Art. 6(1)(f)) Recital 47 recognises fraud prevention as a legitimate interest
Email marketing to new contacts Consent Also governed by the ePrivacy rules, see below
Email marketing to existing customers Legitimate interests, within the ePrivacy “soft opt-in” Must offer an easy opt-out every time
Non-essential cookies and tracking pixels Consent Required by Article 5(3) of the ePrivacy Directive

Legitimate interests requires a balancing test: identify the interest, show the processing is necessary for it, and weigh it against the individual’s reasonable expectations. Write that assessment down. It is the first thing a supervisory authority will ask for.

Transparency: what your privacy notice must say

Articles 13 and 14 list the information people must receive when their data is collected: your identity and contact details, the purposes and lawful basis for each, recipients or categories of recipients, any transfers outside the EEA and the safeguard used, retention periods, the individual’s rights, the right to complain to a supervisory authority, and whether providing the data is a contractual requirement. Where you rely on legitimate interests, you must say what those interests are.

In our assessment, the most common weakness in small-shop privacy notices is not missing headings but vagueness: “we may share data with trusted partners” does not identify recipients. Name the categories precisely (payment processor, carrier, email service provider, advertising platforms) and keep the list in step with the tools you actually use.

Records, processors and contracts

Records of processing

Article 30 requires a record of processing activities. There is an exemption for organisations with fewer than 250 employees, but it does not apply where processing is not occasional, is likely to create a risk, or includes special categories of data. Because an online shop processes customer data continuously, most cannot rely on it. A spreadsheet listing each activity, its purpose, lawful basis, data categories, recipients, transfers, retention period and security measures is usually sufficient. A Commission proposal from May 2025 would widen the exemption to organisations with fewer than 750 employees unless processing is high-risk; at the time of writing we could not confirm that it has been adopted, so plan on the current rule.

Processors and data processing agreements

Most shops rely on processors: hosting, the ecommerce platform, email marketing, customer-service software, payment gateways in some configurations. Article 28 requires a written contract with each processor covering, among other things, processing only on your documented instructions, confidentiality, security, use of sub-processors, assistance with data subject requests and breaches, deletion or return of data at the end, and audit rights. Large providers publish standard data processing agreements; your job is to check one exists, that it covers the service you use and that the sub-processor list is acceptable.

Not every supplier is a processor. A carrier that decides how to run its own delivery network, or an advertising platform that uses data for its own purposes, may be a separate or joint controller. The EDPB’s guidelines on controllers and processors explain how to make that call. Security obligations under Article 32 sit alongside these contracts; our data security basics for online retailers covers the practical controls.

Data subject rights and deadlines

Individuals have rights of access, rectification, erasure, restriction, data portability and objection, plus rights relating to automated decision-making. Article 12(3) requires a response without undue delay and in any event within one month of receipt. That period can be extended by two further months where requests are complex or numerous, but you must tell the person within the first month and explain why. Requests are normally free of charge; a reasonable fee or refusal is possible only for manifestly unfounded or excessive requests.

The right to object to direct marketing is absolute (Article 21(2) and (3)): once someone objects, marketing to them must stop, whatever basis you used. Keep a suppression list so that the address is not re-imported from another source.

Practically, decide who receives requests, how identity is verified proportionately (asking for a passport to confirm an email-only account is excessive), and how you search every system, including the email platform and helpdesk.

Personal data breaches: the 72-hour rule

A personal data breach is any security incident leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data. Under Article 33, the controller must notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to individuals. If the risk is high, the affected people must also be told without undue delay (Article 34). Processors must alert the controller without undue delay. Every breach, notified or not, must be documented internally.

The EDPB’s breach notification guidelines contain worked examples that are useful for training staff. Illustrative example: a misconfigured export leaves a CSV of 2,000 customer names, addresses and order histories publicly accessible for a weekend. That is likely notifiable; if it also contained account passwords stored without proper hashing, telling customers becomes necessary too. Account takeover is one of the most common incidents for shops, which is why protecting customer accounts is a data-protection issue as much as a security one.

International transfers and the EU–US Data Privacy Framework

Transfers of personal data outside the EEA need a legal mechanism under Chapter V. For the United States, the main route is the EU–US Data Privacy Framework (DPF), an adequacy decision adopted on 10 July 2023. It covers transfers only to US organisations that have self-certified under the framework; check the recipient’s listing on the official DPF list rather than assuming.

On 3 September 2025 the EU General Court dismissed the challenge brought by Philippe Latombe, a French member of parliament, against the DPF (Case T-553/23). He has appealed to the Court of Justice (Case C-703/25 P). As of November 2026 the appeal is pending and the adequacy decision remains in force. Its two predecessors, Safe Harbor and Privacy Shield, were both struck down by the Court of Justice, so a sensible precaution is to ensure your key US vendors also offer the Commission’s standard contractual clauses, so that a switch would not require renegotiating every contract at short notice.

Do you need a data protection officer?

Article 37 requires a DPO only where core activities consist of regular and systematic monitoring of individuals on a large scale, or large-scale processing of special-category or criminal-offence data. Most small shops do not meet that threshold. Some national laws go further: Germany, for example, requires a DPO where at least 20 people are regularly engaged in automated processing of personal data. If you appoint one voluntarily, the GDPR’s rules on independence and conflicts of interest apply in full.

Email and SMS marketing is governed by the ePrivacy Directive as implemented nationally, as well as the GDPR. Article 13 of the Directive requires prior consent for electronic marketing to individuals, with one exception, often called the soft opt-in: where you obtained the contact details in the context of a sale, you may market your own similar products by email, provided the customer was given a clear, free opportunity to object at the point of collection and in every message. National implementations vary in detail, so check the rules in each country you target.

Consent must meet the GDPR standard: freely given, specific, informed and unambiguous, through a clear affirmative act. Pre-ticked boxes do not count. Keep a record of when and how each person consented and what they were told.

Enforcement and reform

Fines for the most serious infringements can reach €20 million or 4% of worldwide annual turnover, whichever is higher. Small businesses are rarely fined at that scale, but complaints from customers and orders to change practices are real risks; our retrospective on Germany’s 2019 GDPR enforcement and the Delivery Hero fine shows how quickly basic failures, such as ignoring access and deletion requests, can escalate.

Two reform tracks are worth watching. First, Regulation (EU) 2025/2518 harmonises procedures for cross-border complaints and applies from 2 April 2027; it changes how authorities cooperate rather than your substantive obligations. Second, the Commission’s Digital Omnibus proposal of November 2025 would amend parts of the GDPR, including breach notification thresholds and cookie rules. The Council agreed its negotiating position in October 2026 and talks with the European Parliament are still to conclude. Until a final text is adopted and applies, nothing changes.

Practical checklist for a small online shop

Illustrative example: a ceramics shop with three staff selling through its own store to customers across the EU.

  1. Map your data. List every system holding customer data: store platform, payment provider, email tool, helpdesk, analytics, spreadsheets.
  2. Assign lawful bases. One per activity, recorded, with a written balancing test for anything relying on legitimate interests.
  3. Rewrite the privacy notice so that recipients, retention periods and transfers match the list from step 1.
  4. Collect processor agreements for every processor, and file the sub-processor lists.
  5. Check transfers. For each US vendor, confirm DPF certification and whether standard contractual clauses are available as a fallback.
  6. Fix marketing consent. Unticked boxes, a consent log, the soft opt-in only for existing customers and similar products, and a working unsubscribe link.
  7. Set up a rights process. A monitored inbox, a calendar reminder at day 20, and a template response.
  8. Prepare for breaches. A one-page plan naming who decides, the national authority’s notification form, and an internal breach log.
  9. Review annually, and whenever you add a new tool or market.

Bottom line

The GDPR asks small online businesses for discipline rather than complexity: know what data you hold and why, tell people clearly, contract properly with suppliers and respond on time. Businesses that keep a current data map and a short set of written decisions are well placed both for routine complaints and for whatever the reform negotiations produce. For the platform-specific rules that sit alongside data protection, see our analysis of EU digital-platform rules for online sellers.

This article is general information, not legal advice; for decisions about your business, consult a qualified adviser.

Sources and further reading

  1. Regulation (EU) 2016/679 (General Data Protection Regulation) — EUR-Lex
  2. Directive 2002/58/EC (ePrivacy Directive) — EUR-Lex
  3. Commission Implementing Decision (EU) 2023/1795 on the EU–US Data Privacy Framework — EUR-Lex
  4. Judgment of the General Court in Case T-553/23, Latombe v Commission — EUR-Lex
  5. Standard contractual clauses for international transfers — European Commission
  6. Guidelines 9/2022 on personal data breach notification under GDPR — European Data Protection Board
  7. Guidelines 07/2020 on the concepts of controller and processor in the GDPR — European Data Protection Board
  8. Regulation (EU) 2025/2518 on additional procedural rules for GDPR enforcement — EUR-Lex