How to connect Cookiebot to Shopware 6, what the tool costs per domain and when the Shopware cookie manager or an alternative is the better fit.
You can connect Cookiebot to Shopware 6 in a morning, and the easiest route is the free plugin from Usercentrics. You create a Cookiebot account, paste the script into the plugin configuration and switch off Shopware’s own cookie notice. The real work comes afterward: blocking scripts correctly, checking Google Consent Mode v2 and testing the banner on every page type.
For most stores, Cookiebot costs between 30 and 50 euros per month per domain. The price depends on the number of subpages. Cookiebot is only free up to 50 subpages, and a store with a few dozen products and categories passes that limit quickly. If you run several country domains, you pay for each domain separately.
Cookiebot is not the only workable option. Shopware ships with its own cookie manager, and the Shopware Store offers other consent plugins. The right choice depends on how many tracking services you use and how many countries and languages your store serves. If you would rather hand over setup, updates and operation of the whole store, take a look at the solution25 store subscription.
This article is for merchants, ecommerce managers and developers who want to use Cookiebot in Shopware 6 or are checking whether the tool pays off for their store. We cover the general privacy obligations of an online store in our article on data protection for online stores. Here we focus on setup, costs, common mistakes and alternatives.
Cookiebot is a consent management platform, or CMP, from the Munich-based provider Usercentrics. The tool scans your website, assigns the cookies and trackers it finds to categories, shows visitors a consent banner and records who agreed to which category and when. Technically, Cookiebot is a script that loads in the head of every page before other scripts run. Only once the visitor has consented does Cookiebot release the scripts of that category.
Cookiebot does not tell you whether a service legally belongs in the statistics or the marketing category. Its categorization is a suggestion that you need to review. The tool does not finish your privacy policy for you, and it does not fix tags that are misconfigured in Google Tag Manager. It also knows nothing about Shopware: if a plugin sends data to a service from the server, the scanner cannot see it, because no cookie is created in the browser.
One point is often missed: the Cookiebot script itself loads from the provider’s servers. That means Usercentrics belongs in your privacy policy and in your list of data processors.
The answer depends on what your store stores in the visitor’s browser. In the EU, the principle of the ePrivacy Directive applies: anyone who stores or reads information on a user’s device needs that user’s prior consent. The exception is anything strictly necessary for the service the user explicitly requested.
For a Shopware store, that means in practice:
A store that truly sets only technically necessary cookies does not need a consent banner. That is rare. A single remarketing pixel or one embedded product video is enough to make a banner necessary. So the question is almost never whether you need a banner, but which tool controls it reliably.
The rules above come from EU law. The US has no federal cookie consent law. Instead, several states have privacy laws, such as the CCPA/CPRA in California and the VCDPA in Virginia, which focus on the right to opt out of the sale or sharing of personal data. Cookiebot lists these laws among its supported frameworks and also supports the Global Privacy Control (GPC) signal. With geotargeting, you can show US visitors a different banner than EU visitors. If you run Shopware for the US market, keep in mind that most experienced Shopware partners are based in Europe, so plan for the overlap in working hours when you set up support. Sales tax is usually handled through a tax service integration rather than through Shopware’s tax rules alone. Prices in this article stay in euros, as shown on the providers’ pages.
Important: we are a Shopware agency, not a law firm. For the legal assessment of individual services and for your privacy policy, talk to a data protection officer or a lawyer who specializes in IT law.
Shopware 6 has its own cookie manager. It sorts cookies into four groups: technically required, comfort features, statistics and tracking, and marketing. Shopware stores the visitor’s choice in the cookie-preference cookie for 30 days. Plugins and apps register their cookies with the cookie manager so they appear in the banner.
Shopware has extended the manager in recent versions. Version 6.6.0.0 added the marketing group, and since then the storefront template sets a default consent through gtag to support Google Consent Mode v2. From version 6.7.3.0, Shopware calculates a hash of the cookie configuration. If the configuration changes, for example because a plugin registers a new cookie, the store asks for consent again.
The difference from Cookiebot is the principle behind it. Shopware only knows the cookies that plugins and apps register properly. Cookiebot scans the finished page and also finds scripts added through the theme, Tag Manager or Shopping Experiences.
| Criterion | Shopware cookie manager | Cookiebot |
|---|---|---|
| Cost | included in Shopware | free up to 50 subpages, otherwise from 7 euros per month per domain |
| Cookie detection | registered cookies only | regular scan of the live site |
| Script blocking | only scripts that respond to consent | manual or automatic, depending on the plan |
| Proof of consent | stored in the visitor’s browser | log for up to twelve months, CSV export |
| Google Consent Mode v2 | default consent since 6.6.0.0 | active automatically |
| Languages and countries | through Shopware translations | more than 47 languages, geotargeting |
| Maintenance effort | low as long as all services run as plugins | review categorization after each scan |
Our experience: a small store with Google Analytics through a clean plugin and no other trackers does fine with the Shopware manager. As soon as Tag Manager delivers several services, videos sit in Shopping Experiences or you need to prove to an authority who consented and when, a CMP like Cookiebot makes a lot of sense.
Cookiebot does not price by visitors but by the number of subpages per domain. The scanner counts once a month, and billing follows the highest number counted. If your store grows past the limit of a plan, Cookiebot upgrades the subscription automatically at the end of the billing period. You cannot switch between Premium tiers manually.
| Plan | Subpages | Price per month per domain | Note |
|---|---|---|---|
| Free | up to 50 | 0 euros | 1 domain only, no Premium features |
| Premium Lite | fewer than 50 | 7 euros | 1 domain, 1 language, consent valid up to 1 month |
| Premium Small | 50 to 349 | 15 euros | according to the provider, only from 4 domains |
| Premium Medium | 350 to 3,499 | 30 euros | typical for small and mid-size stores |
| Premium Large | 3,500 to 6,999 | 50 euros | larger catalogs |
| Premium Extra Large | 7,000 and up | 90 euros | large catalogs |
All prices exclude VAT, taken from the German pricing page in November 2026. At the time of checking, the annual prices equaled twelve monthly amounts, so 84 euros per year for Lite and 360 euros for Medium. You can test all Premium features free for 14 days without a credit card.
Every product page, category, CMS page and manufacturer page is a subpage. A store with 300 products and 40 categories is well above 50. In stores with variants and filters the count can be higher than you expect. You only see the binding number after the first scan during the trial.
The rule for the Small plan stands out: according to the provider’s FAQ, it requires at least four domains. Under that rule, a store with one domain and 50 to 349 subpages ends up on the Medium plan. Check this in your account before you set a budget.
A hypothetical merchant sells 1,200 products in Germany, Austria and Switzerland. Including categories and CMS pages, the scanner counts about 1,500 subpages per store. That means the Medium plan.
Keep in mind for planning: Cookiebot counts subdomains such as at.shop.de as separate domains. And if you add shop.de and www.shop.de separately, you pay for both, according to the provider.
Cookiebot is rarely the biggest cost, but it is one of many small subscriptions that add up in store operations: hosting, plugins, legal texts, maintenance. If you want to bundle these costs into one predictable fee, look at the solution25 store subscription. According to the current page there are three packages with a minimum term of 24 months: Scale for 299 euros per month with a fully set-up store, 200 products entered for you, hosting on servers in Germany for up to 10,000 visits per month, plus security and plugin updates, daily backups and monitoring. Pro for 499 euros per month with a design in your brand identity, up to 500 products, SEO basics with redirects, hosting for up to 50,000 visits per month and a dedicated contact person. Enterprise is available on request with integrations such as ERP, PIM and marketplaces. The page states a 10 percent saving for annual payment, and after 24 months the store belongs to you. Which consent solution the subscription uses is something we clarify in a conversation; the page does not specify it.
There are several ways to connect Cookiebot to Shopware 6. The right one depends on how many sales channels you run and whether you use Google Tag Manager.
Usercentrics offers the extension “Usercentrics Cookiebot Consent Banner” in the Shopware Store free of charge. According to the store it is compatible with Shopware 6.4.0.0 to 6.7.16.0. Setup is short: install and activate the extension, paste the Cookiebot script from your Cookiebot account into the configuration, save. For most stores with one sales channel, this is the simplest route.
According to the store, this app costs 3.90 euros per month or 39 euros per year, with a free trial month. It works with the domain group ID from Cookiebot and allows a separate Cookiebot connection for each sales channel. It also adds a Shopping Experiences block that shows a table of all cookies. According to its manual, you have to switch off Shopware’s own cookie notice yourself. The app is interesting for stores with several sales channels and separate domains.
Cookiebot provides a template in the Google Tag Manager template gallery. If all your tracking runs through Tag Manager, you add Cookiebot there with the consent initialization trigger. The advantage: marketing and tech maintain tracking in one place. The drawback: Tag Manager itself has to load before the banner, and scripts that sit in the store outside Tag Manager are not covered automatically. Our page on Shopware and Google Tag Manager shows how to add Tag Manager to Shopware.
A developer can also write the script into the page head through a custom theme or plugin. That gives full control over the order of scripts. Such changes belong in your own theme or plugin and never in Shopware’s own template files, or they disappear with the next update.
The following order has proven itself in our projects. It applies to the official plugin; the steps in the Cookiebot account are the same for every route.
A tip from practice: set everything up on a staging environment first. Banner preview on test domains is one of Cookiebot’s Premium features and is available during the trial.
Since March 2024, Google has expected advertisers who reach users in the European Economic Area to use a consent solution with Consent Mode v2. Without these signals, Google Ads lacks data for remarketing and audiences. Consent Mode v2 transmits four values: ad_storage, analytics_storage, ad_user_data and ad_personalization.
According to the provider, Cookiebot activates Consent Mode v2 automatically as soon as the script loads in the store. There is one Shopware detail to watch: since version 6.6.0.0, Shopware’s storefront template sets its own default consent through gtag if you use the built-in Google Analytics connection. If both mechanisms run at the same time, the store may send conflicting signals. Pick one source. If Cookiebot shows the banner, Cookiebot should control consent too.
Google distinguishes two variants. In basic mode, Google tags load only after consent. In advanced mode they load immediately but, without consent, send only cookieless signals that Google uses to model conversions. Advanced gives Google Ads more data but is more contested from a privacy standpoint. Marketing and your data protection officer should make this decision together, not the developer alone.
If GA4 is not yet connected cleanly, our article on integrating Google Analytics 4 with Shopware 6 will help.
A consent banner is the first thing a new visitor sees. It affects load time, bounce rate and the amount of data you can analyze later.
The Cookiebot script has to load before all other scripts so it can block them. Every millisecond it needs delays everything else. Keep the page head lean: no duplicate tracking scripts and no old pixels nobody looks at anymore. Measure Core Web Vitals before and after the switch, especially Largest Contentful Paint on mobile. A large banner that covers the content can also become the largest visible element. More on this in our article on optimizing Shopware 6 performance.
The consent rate determines how complete your analytics are. Do not try to push it up with tricks: a hidden decline button, pre-ticked boxes or gray text on a gray background. Data protection authorities in the EU object to designs like these regularly. What helps legally is a short, clear text that says what you use the data for, and a banner that fits the store and does not look like a warning.
Cookiebot shows opt-in and opt-out statistics in its dashboard. Watch the rate for a few weeks before changing texts or layout, and change only one thing at a time.
After switching to a banner that blocks properly, visitor numbers in Google Analytics often drop visibly. The store does not have fewer visitors; it only counts those who consented. Tell your team in advance so nobody suspects a sales slump after launch. Your order numbers from Shopware remain the reliable figure.
Cookiebot is widespread, but it is not the best choice for every store. These are the options we see most often in Shopware projects:
| Solution | Pricing according to the provider | Strengths | Good fit for |
|---|---|---|---|
| Shopware cookie manager | included in Shopware | no extra cost, no external script, Consent Mode v2 since 6.6 | small stores with few services, all running as plugins |
| Cookiebot | free up to 50 subpages, Premium from 7 euros per month per domain | scanning, automatic blocking, proof of consent, many languages | stores with Tag Manager, several tracking services or several countries |
| Usercentrics (Advanced) | on request | for multiple brands, regions and apps | companies with several stores and apps |
| ACRIS EU Cookie Policy Pro | 9.99 euros per month or 99 euros per year | detects cookies in the store, loads scripts only after consent, Consent Mode v2 | stores that want to manage everything inside Shopware |
| consentmanager | plugin free, plans on the provider’s site | automatic blocking, Consent Mode v2, IAB TCF v2.4 | stores working with ad networks that require TCF |
Before you install another plugin, review what you already have. Our article on Shopware 6 plugins shows what to watch for when choosing and maintaining extensions.
Most problems with Cookiebot in Shopware do not appear during integration but in the weeks after. These are the mistakes we see most often:
_ga, no _fbp, no _gcl_au.Repeat this test after every new plugin and every Shopware update. A new plugin often brings a new cookie, and then the categorization in Cookiebot needs updating.
The official Usercentrics plugin is free. Cookiebot itself is only free up to 50 subpages and for one domain. Most stores need a Premium plan, typically Medium for 30 euros or Large for 50 euros per month per domain, excluding VAT.
For small stores whose services all run as plugins and register correctly with the cookie manager, it can be enough. As soon as scripts come through Tag Manager, the theme or Shopping Experiences, or a consent log is required, it reaches its limits.
Yes. According to the Shopware Store, the official plugin is compatible with versions 6.7.0.0 to 6.7.16.0. Before every major Shopware update, check whether the installed plugin version is released for the target version.
Roughly all product, category, manufacturer and CMS pages together. Only the number the Cookiebot scanner finds during the trial is binding. Billing follows the highest value in a billing period.
Yes. Each domain needs its own subscription in Cookiebot, but domains can be grouped into domain groups with the same configuration. For separate configurations per sales channel, the Shopware Store offers an app that supports exactly that.
solution25 is a Shopware Platinum Partner based in Bremen, Germany, and has worked with Shopware since 2017. We integrate consent solutions such as Cookiebot into existing stores, clean up Tag Manager and old tracking scripts along the way and test the result on every page type. If Shopware’s own cookie manager is enough for your store, we will tell you that too.
If you want to know which services in your store load without consent today, write to us through our contact page. For live stores with urgent problems, Shopware support is the faster route. And if you would like to hand over building and running your store entirely, you will find the packages in our store subscription.

Besnik Bilalli is the founder and CEO of solution25, the Shopware agency from Bremen. Before founding the agency in 2017, he built his own online store and grew it to more than 500 orders a day. Since then he has been helping merchants with Shopware projects, from the first budget to ongoing operations. He’s happy to answer questions about this article personally: get in touch.
Responsible for content and updates: Besnik Bilalli. Last updated: November 2026. Next content review: February 2027.