Terms and conditions, enforced not just displayed.
Block sign up, add-to-cart, and checkout until customers accept your terms, then log every acceptance with the exact document version and timestamp so you have real evidence, not just a checkbox.
Customers can sign up, add to cart, and check out without ever confirming they read your terms. When a chargeback or compliance question comes up, most stores have no record of who agreed to which version of their policy, or whether a checkbox was even required in the first place.
Website Terms and Conditions Consent blocks sign up, add-to-cart, and checkout until the customer ticks the box, then logs every acceptance with the document, version, touchpoint, and timestamp — a real audit trail across the whole customer journey, not just one step of it.
Everything you need for enforceable consent
Every capability below is implemented in the module.
Full-journey enforcement
Block sign up, add-to-cart, and checkout in one app instead of stitching together three single-touchpoint modules.
Real acceptance audit trail
Every acceptance logs the customer, document, version, touchpoint, and date — real evidence for disputes and compliance.
Version control and re-acceptance
Publish a new version and customers who already agreed are prompted again, so consent never silently goes stale.
Per-product and category scope
Attach specific terms to specific products or categories for regulated or custom items, alongside general store-wide documents.
Customer and internal audiences
Manage customer-facing storefront terms and internal staff acknowledgements from the same document model.
Inline or modal display
Choose a low-friction inline checkbox or a modal that isolates the legal text, with the label confirming once acceptance registers.
Multi-website and multi-language
Run independent terms per website and display them in the customer's website language for franchise and international sellers.
Acceptance analytics
Pivot and graph reports break acceptances down by document, version, and touchpoint so you can see where customers engage.
Seeded template library
Start from B2B, B2C, SaaS, and retail starter policies instead of a blank page, then edit the wording to fit your store.
How it works
Draft your terms
Write a document or start from a seeded template, then set its title, scope, and audience.
Choose your gates
Pick which touchpoints — sign up, cart, checkout — require acceptance and how the prompt displays.
Publish and enforce
Customers must tick the box before continuing, and the label confirms once acceptance registers.
Review the audit trail
Check the acceptance log and analytics anytime a dispute or compliance question comes up.
See it in action
The Documents, Acceptance Log, Analytics, and Template Library screens in a live Odoo 19 database.
The Documents list shows every term document with its publish state, audience, scope, website, version, and live acceptance count.
Opening a document reveals its full configuration: display mode, audience, scope, enforcement toggles for sign up, cart, and checkout, plus the rich HTML terms body.
The kanban view gives a quick visual overview of published documents, their audience, and acceptance counts.
The acceptance log is the audit trail: every acceptance is recorded with customer, document, version, touchpoint, and date.
The analytics pivot breaks acceptances down by document and touchpoint against version, so you can see adoption of the latest wording.
The analytics graph shows acceptance volume over time, grouped by touchpoint.
The seeded template library ships starter policies for B2B, B2C, SaaS, and retail sellers.
Each template includes an industry tag and a ready-to-edit multi-paragraph starter policy body.
Configuration lives inside Website Settings, where admins enable the acceptance gate and choose which touchpoints to block.
Frequently asked
Does this really block customers, or just display the terms?
It hard-blocks the workflow. Sign up, add-to-cart, and checkout submissions are rejected with a clear inline error until the customer ticks the required box for that touchpoint.
Can I prove which version a customer agreed to?
Yes. Every acceptance is logged with the exact document version, the touchpoint, the customer, and the timestamp, giving you a durable audit trail for disputes and compliance.
What happens when I update my terms?
Publishing a new version triggers re-acceptance: customers who agreed to the previous wording are prompted again before their next covered action.
Where do I configure this?
Everything lives inside Website Settings under Terms & Conditions, so you never need to leave the Website app to manage documents, touchpoints, or display mode.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Empowering growth through technology.
Website Terms and Conditions Consent enforces acceptance at sign up, cart, and checkout, and keeps a full audit trail of who agreed to what, and when.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
eCommerce (website_sale)
• Discuss (mail) • Website (website) • Invoicing (account) |
| Lines of code | 976 |
| Technical Name |
cerevantix_website_terms_and_conditions |
| License | OPL-1 |
| Website | https://cerevantix.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module