Cookies and consent in your webshop
You need consent for cookies and similar technologies that are not strictly necessary, such as marketing cookies and many analytics cookies. You do not need to ask consent for functional cookies, such as the shopping basket. Check the current rules with the Autoriteit Persoonsgegevens (the Dutch Data Protection Authority).
Almost every webshop places cookies, but not every cookie requires a notice with a choice. If you mix these up, you either show a needless banner that annoys customers, or you place cookies without valid consent. In this article you will read, in broad terms, when you need consent, which cookies fall under it and what you can do first to get your webshop in order. This is general information and not legal advice for your situation.
The distinction: functional or not
The core is simple: cookies that are needed to deliver the service the visitor asks for are allowed without consent. Everything else requires an active choice from the visitor beforehand. The rules come from the Telecommunicatiewet (the Dutch Telecommunications Act) and the GDPR (in Dutch: AVG), and the Autoriteit Persoonsgegevens (the Dutch Data Protection Authority) supervises them.
Think of the difference between a cookie that remembers what is in the shopping basket and a cookie that tracks which pages someone clicks on in order to show ads later. The first is needed to place an order. The second serves your interest or that of a third party, and for that the visitor must choose.
It is also not only about cookies. Similar technologies, such as pixels, local storage and reading device data, fall under the same rules. A webshop that uses no cookies but does load a tracking pixel may therefore still need consent.
Cookies for which you do not need consent
Strictly necessary cookies are allowed without consent. These are cookies without which the webshop does not work the way the visitor expects. You are still required to explain in your privacy statement that you place them and what for.
Pay attention to the word strictly. A cookie is not functional just because you find it handy. It must really be necessary for the requested service. An example is a cookie that keeps a customer logged in after they have logged in, but not a cookie that analyses behaviour in the background.
- Remembering the contents of the shopping basket during the ordering process
- Maintaining a customer's login session
- Security cookies that prevent abuse or fraud
- A cookie that stores the cookie choice itself
Cookies for which you do need consent
Marketing and tracking cookies require prior consent. This applies, for example, to social media advertising pixels, remarketing and cookies with which you follow visitors across different websites. Without a yes from the visitor, these may not be loaded.
Analytics cookies are more nuanced. Under certain conditions, some forms of statistics with little privacy impact can be used without consent, but that depends on how you set it up, for example whether data is shared with third parties. Check the current conditions with the Autoriteit Persoonsgegevens or ask your adviser.
Preference and personalisation cookies often also require consent, such as a cookie that recommends products based on earlier behaviour. Merely remembering a language choice can be functional, if the visitor made that choice themselves.
What valid consent looks like
Consent must be freely given, specific, informed and unambiguous. In practice that means: the visitor makes an active choice themselves, not by simply scrolling on or leaving a pre-ticked box as it is. Cookies that require consent are loaded only after that yes.
Refusing must be as easy as accepting. A banner with a big Accept button and a hidden link for settings is generally not sufficient. Put a button to refuse everything at the same level as the button to accept.
Also explain clearly, in understandable language, what you use the cookies for. State which parties are watching along. Visitors must also be able to change or withdraw their choice later, for example via a link in the footer.
A practical example
Suppose you sell ceramics via WooCommerce. You have installed Google Analytics, a Facebook pixel for advertising and a chat widget from an external party. The shopping basket and login work with your own session cookies. This is an example, not an assessment of a specific tool.
The session cookies do not need consent. The advertising pixel does, so you load it only after a yes. For the analytics and the chat widget you need to check what exactly they place and share. If they track visitors or send data to third parties, consent is needed. You check that with the provider's documentation.
Many business owners discover during such an inventory that a plug-in or theme loads extra scripts without them knowing. That is why it is worth not relying on what you think you have installed, but actually measuring what the site does.
Common mistakes
The best-known mistake is a banner that only informs, such as This site uses cookies, while the scripts have long since been loaded. The notice then suggests a choice, but the cookies have already been placed. That is not valid consent.
A second mistake is using a cookie banner that looks neat but does not block technically. After setting it up, check that nothing is really placed before the visitor chooses. You can see this in your browser's developer tools under storage and network.
Finally, many shops forget to update their privacy statement. It should state which cookies you place, for what purpose and for how long. If you change tools or add a new advertising channel, the statement and the banner must change with it.
First steps for your webshop
Start with an inventory. Open your webshop in a private window, look at which cookies and scripts are loaded before you click anything, and note the origin and purpose of each cookie. Ask the providers of your plug-ins and external tools what they place.
Then divide the list into necessary and non-necessary. Choose a cookie tool that really blocks scripts until consent is given, and test it yourself. Only then adjust your privacy statement, so that it matches what you do.
If you are unsure about a specific tool, for example regarding analytics or sharing data with third parties, consult the current guidance of the Autoriteit Persoonsgegevens or a privacy adviser. What exactly is permitted can change, so schedule a periodic check.
- Load the shop in a private window and see which cookies appear immediately
- Note for each cookie who places it and why
- Block everything that needs consent until the visitor chooses
- Update your privacy statement and schedule an annual check
More on Webshoptiger
Official sources
Rules, amounts and deadlines change. Always check the current details with the authority itself:
Frequently asked questions
Do I need a cookie notice if I only use functional cookies?
Then you do not need to ask for consent. You must still inform visitors about the cookies, for example in your privacy statement.
May I place cookies if visitors keep clicking on without choosing?
No, clicking on or scrolling does not count as valid consent. There must be an active choice, and until then you do not load cookies that require consent.
Do the cookie rules also apply to a small webshop?
Yes, the rules apply regardless of the size of your business. Even if you only have a few visitors, you must ask for consent for non-necessary cookies.
Who checks whether my cookie notice is correct?
The Autoriteit Persoonsgegevens (the Dutch Data Protection Authority) supervises compliance. If you are unsure about your situation, ask a privacy adviser or lawyer to take a look.