Most Odoo websites start collecting visitor data the moment a page loads. Analytics scripts, ad pixels, chat widgets, and embedded media all fire before anyone agrees to anything. Under GDPR, the ePrivacy directive, and newer regional consent rules, that is a compliance gap: you are expected to obtain informed opt-in before non-essential cookies and trackers run, and to be able to prove that consent later. Odoo core ships with no cookie consent mechanism at all, and a typical off-the-shelf apps.odoo.com module usually renders a cosmetic "accept" bar that never actually blocks the scripts it claims to govern. The banner ends up legally decorative while the trackers keep firing regardless of the click.

ECOSIRE builds a consent banner that behaves the way regulators actually expect. We implement a script-gating layer inside your Odoo website theme so that non-essential tags (Google Analytics 4, Google Ads, Meta Pixel, LinkedIn, chat and heatmap tools, embedded video) are held in a pending state and only injected after the visitor grants the matching category. On top of that we wire Google Consent Mode V2, pushing the consent signals (ad_storage, analytics_storage, ad_user_data, ad_personalization, functionality_storage, personalization_storage, security_storage) into your dataLayer with a correct default-deny state and an update event on the visitor's choice, so your tags run in cookieless/modeled mode until opt-in rather than dropping data silently.

Technically, the banner is delivered as a proper Odoo module. A __manifest__.py declares the theme assets and dependencies; a new model (models.Model with fields, and @api.depends computes where needed) stores the category taxonomy and, optionally, a per-visitor consent record with timestamp, IP hash, policy version, and the exact choices made, so you have an auditable proof-of-consent log. Access is locked down with ir.model.access.csv plus record rules so consent logs are readable only by the right groups. The front end is built with QWeb templates and OWL components for the banner, the granular preferences modal, and a persistent "cookie settings" re-open control; a website settings panel lets non-technical staff edit categories, copy, and links to your privacy and cookie policy pages without touching code. Consent records can be queried through the standard XML-RPC/JSON-RPC API for DSAR handling or exported to your data-warehouse. The module targets Odoo 17.0, 18.0, and 19.0 and works on both Community and Enterprise (Enterprise's extra website tooling is respected but not required).

Because this is build-to-order, we start with a short scoping call to confirm which trackers you run, which regions and consent frameworks you must satisfy, and your policy-versioning needs. We then build on a staging copy of your site, run UAT against your real tag stack, and deploy behind a rollback plan. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); multi-company or multi-brand deployments, additional tracker integrations, deeper regional/localization requirements (for example region-specific consent logic or IAB TCF alignment), and larger consent-log data-migration volumes increase the quoted scope. You receive a fixed quote after the scoping call, never a surprise on the invoice.