Skip to main content
Remove Powered by from Website, Email Template & Portal — A build-to-order Odoo module that cleanly removes the default platf — 1/1Illustrative preview

A build-to-order Odoo module that cleanly removes the default platform attribution from your website footer,

transactional email templates, and customer portal.

ECOSIRE scopes, builds, installs, and supports it for your exact edition and version.

What is Remove Powered by from Website, Email Template & Portal?

A build-to-order Odoo module that cleanly removes the default platform attribution from your website footer, transactional email templates, and customer portal. ECOSIRE scopes, builds, installs, and supports it for your exact edition and version. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.

Key Features

Neutralizes the website footer attribution via an inheriting `website.layout` view using `<xpath>` and `t-if` guards, not by editing core records
Removes the portal footer branding through inherited `portal.frontend_layout` and portal footer templates so logged-in customers see a clean UI
Strips the default sign-off from outbound email by inheriting `mail.notification.layout` and `mail.mail_notification_light`, covering all `mail.thread`-driven notifications
Applies consistently across transactional emails: sales quotations, invoices, delivery notices, portal invitations, and helpdesk/subscription mails
Ships as a proper addon with a versioned `__manifest__.py` declaring `website`, `portal`, and `mail` dependencies
Survives module upgrades and `-u website` runs because changes are inheritance-based, not one-off UI edits that get overwritten
Fully reversible — uninstalling the module restores standard Odoo behavior with no residual configuration or orphaned data
Handles multi-website deployments so each `website` record's footer is cleaned, including per-website theme footers
Extends to custom website themes and email themes that inject their own footer snippets or branded blocks
Version-correct template targeting for Odoo 17.0, 18.0, and 19.0, whose footer `xml_id`s and markup differ between releases
Validated on both Community and Enterprise, accounting for Enterprise-only mail layout variations
No changes to `ir.model.access.csv` or record rules required — the module is presentation-layer only and does not touch security or business data
Clean QWeb overrides that keep responsive layout, RTL, and accessibility markup intact after the attribution is removed
Optional replacement of the removed footer line with your own copyright or brand text where you want a branded footer instead of a blank one

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

  1. 1

    You order

    Start with a one-time build price. We scope it with you at kickoff.

  2. 2

    We build & install

    ECOSIRE builds, configures and installs it on your Odoo.

  3. 3

    Go live + support

    You go live in about one working week, with two weeks of go-live support. Defects in the code we deliver are fixed free of charge.

Technical Specifications

Odoo Compatibility
Odoo 17, Odoo 18, Odoo 19
Editions
Enterprise & Community
License
Licence confirmation required
Python Requirement
Python 3.10+
Database
PostgreSQL 12+

About this Product

Every stock Odoo deployment stamps a promotional attribution into the public website footer, the bottom of outbound email templates, and the customer portal pages. For an agency reselling an Odoo-based platform, a business emailing branded quotes and invoices, or anyone presenting a polished storefront, that leftover attribution quietly undercuts your brand at exactly the customer-facing touchpoints that matter most. The catch is that Odoo core exposes no single supported toggle to strip all three surfaces at once: the website footer text lives in a QWeb website view, the mail sign-off is baked into the notification layout used by mail.thread, and the portal footer is rendered by yet another set of portal views. Editing them by hand through the UI is fragile — a module update or a -u website upgrade re-applies the standard views and the branding quietly reappears.

We build a small, self-contained module scoped to your exact edition and version that removes the attribution cleanly and durably across all three surfaces. It ships as a proper addon with its own __manifest__.py declaring dependencies on website, portal, and mail, and it overrides the relevant QWeb templates using <xpath> inheritance rather than deleting or corrupting core records — so upgrades stay safe and the change survives future -u runs. The website and portal footer attributions are neutralized through inheriting views (website.layout, portal.frontend_layout and their footer blocks), and the outbound-email sign-off is handled by inheriting the mail.notification.layout and mail.mail_notification_light templates so that every transactional email — quotations, invoices, portal invites, delivery notices — leaves your system without the default footer line.

Because the change lives in one addon rather than in scattered UI tweaks, it is auditable, version-controlled, and reversible: uninstall the module and Odoo reverts to standard behavior with no residual data. Where your deployment adds extra branded surfaces — a custom email theme, a website theme with its own footer snippet, a multi-website setup, or Enterprise-only mail layouts — we extend the same inheritance approach to cover them. We validate against Community and Enterprise, and against your specific Odoo 17.0, 18.0, or 19.0 build, since the exact template xml_ids and footer markup shift slightly between versions and editions.

Delivery is build-to-order. After a short scoping call we confirm the exact surfaces in scope, your edition/version, and any custom themes, then build and test the module on a staging copy of your database before installing on production. Typical delivery is one working week from confirmed scope, depending on how many custom branded surfaces and themes are involved. Pricing starts from $999 (indicative, single-company base scope); additional websites in a multi-website setup, custom email themes or theme-specific footer snippets, and deeper localization of email layouts increase the quoted scope. You receive a fixed written quote after the scoping call — never a surprise.

What you get

  • Installable, version-pinned source code for the module built for your exact Odoo edition and version
  • Installation and configuration on your environment, including any per-website and per-theme wiring
  • Technical documentation covering the inherited templates, `__manifest__.py`, and upgrade-safety notes
  • Short user guide plus a walkthrough/training session for your admin team
  • UAT on a staging copy of your database with a documented rollback plan before production install
  • Post-go-live support window to catch any edge-case emails or themed pages that still show attribution
  • Git repository handover with the full commit history and tagged release
  • A verification checklist confirming website, portal, and email surfaces are all clean across your key documents

Who this is for

Odoo-based SaaS reseller / agency

Runs a white-labeled Odoo platform for their own clients and cannot afford the default attribution appearing on customer-facing sites, portals, or transactional emails. Needs a durable, upgrade-safe removal across multi-website tenants.

Brand-conscious SMB operations lead

Sends quotations and invoices from Odoo daily and wants every outbound email and the customer portal to look fully owned by their brand, without fragile manual view edits that break on the next update.

In-house Odoo administrator

Manages the deployment and has tried removing the footer through the UI only to see it return after an upgrade. Wants a clean addon they can install, version-control, and uninstall, with documentation on exactly what it overrides.

Marketing / web manager

Owns the public website and portal experience and needs the footer and email chrome to match the company's visual identity across Community or Enterprise, including custom themes and RTL layouts.

How Remove Powered by from Website, Email Template & Portal Compares

CriterionECOSIRECustom BuildCompetitorOdoo Native
Upgrade safetyInheritance-based overrides survive module updates and -u runsDepends on developer discipline; often breaks on upgradeUsually inheritance-based but not tuned to your themesNo native toggle; UI edits get overwritten on upgrade
Coverage of all three surfacesWebsite, portal, and all transactional emails in one moduleWhatever you brief and pay to buildCommon surfaces covered; custom themes often missedNo single feature covers all three at once
Edition & version fitBuilt and validated for your exact 17/18/19, Community or EnterprisePossible, but you own version-drift maintenanceGeneric build; edition/version gaps are your problemBehavior and template ids differ per version with no removal
Custom & multi-website themesExtends the same approach to your theme footers and each websiteOnly if explicitly specified and budgetedTypically only covers stock themesEach theme re-adds its own branding independently
Reversibility & data safetyPresentation-only; clean uninstall, no security or data changesVaries; risk of leftover records if done ad-hocUsually clean but rarely documentedManual edits risk corrupting core views
Support & accountabilityPost-go-live window, git handover, and migration supportTied to the individual developer's availabilityTicket queue with no context on your deploymentNo vendor support for this specific need
Time to valueone working week build-to-order with staging UATWeeks to months depending on hiring and specInstant install but unpredictable fit and reworkImmediate but incomplete and reverts on upgrade
Total cost clarityIndicative from-price, fixed quote after scopingHourly, open-ended, scope creep riskLow sticker price plus your integration and rework timeFree but hidden cost in repeated manual fixes

Frequently Asked Questions about Remove Powered by from Website, Email Template & Portal

How long does delivery take?

This is a build-to-order module, not an instant download. After a scoping call to confirm your edition, version, and the exact branded surfaces in scope, typical delivery is one working week from confirmed scope. Deployments with many custom themes or multi-website setups sit at the longer end of that range.

How does pricing and scoping work?

Pricing starts from $999 (indicative, for a single-company base scope). Drivers like multi-website setups, custom email or website themes with their own footer snippets, and deeper email-layout localization increase the quoted scope. You get a fixed written quote after the scoping call — the from-price is a starting point, not the final number.

Will the branding come back after an Odoo update?

No. Because the module removes the attribution through QWeb `<xpath>` inheritance rather than editing core records in the UI, the change survives module updates and `-u` upgrade runs. UI-level edits are exactly what tend to get overwritten on upgrade; this addon does not.

What support and updates are included?

Every engagement includes a post-go-live support window to fix any edge-case email or themed page that still shows attribution. Beyond that window, we offer ongoing support and version-migration work — for example rebuilding the overrides when you move from Odoo 17 to 18 or 19, since the underlying template ids change between versions.

Does it work on both Community and Enterprise?

Yes. We validate against both, and against your specific Odoo 17.0, 18.0, or 19.0 build. Enterprise ships some additional mail layouts and themed surfaces, so the exact templates we inherit differ — that is part of what the scoping call confirms.

Is it safe and reversible?

Yes. The module is presentation-layer only: it touches QWeb views, not your business data, `ir.model.access.csv`, or record rules. Uninstalling it restores standard Odoo behavior with no residual configuration. We also test on a staging copy first and provide a rollback plan before touching production.

Can you replace the removed footer with our own branding instead of leaving it blank?

Yes. As an optional part of scope we can swap the removed attribution line for your own copyright, company name, or brand text in the website footer, portal, and email templates, so the space reads as intentionally yours rather than empty.

Request a quote

Remove Powered by from Website, Email Template & Portal

A build-to-order Odoo module that cleanly removes the default platform attribution from your website footer, transactional email templates, and customer portal. ECOSIRE scopes, builds, installs, and supports it for your exact edition and version.

  • Neutralizes the website footer attribution via an inheriting `website.layout` view using `<xpath>` and `t-if` guards, not by editing core records
  • Removes the portal footer branding through inherited `portal.frontend_layout` and portal footer templates so logged-in customers see a clean UI
  • Strips the default sign-off from outbound email by inheriting `mail.notification.layout` and `mail.mail_notification_light`, covering all `mail.thread`-driven notifications
  • Applies consistently across transactional emails: sales quotations, invoices, delivery notices, portal invitations, and helpdesk/subscription mails

Request a Quotation

Tell us about your Remove Powered by from Website, Email Template & Portal requirements and we'll send pricing, licensing options and a tailored proposal — usually within one business day.

No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.