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 $249.00 USD; request a quote for a scoped proposal.
ऐप मैनिफ़ेस्ट
आपके वर्कफ़्लो के अनुरूप बनाया गया
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.
स्वयं सेटअप की ज़रूरत नहीं — ECOSIRE द्वारा निर्मित, इंस्टॉल और समर्थित एक कार्यशील ऐप।
एक बार के निर्माण मूल्य से शुरू करें। किकऑफ़ पर हम आपके साथ मिलकर दायरा तय करते हैं।
ECOSIRE इसे आपके Odoo पर बनाता, कॉन्फ़िगर और इंस्टॉल करता है।
आप लगभग 2–4 सप्ताह में लाइव हो जाते हैं, लॉन्च के बाद समर्थन अवधि के साथ।
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 2–4 weeks from confirmed scope, depending on how many custom branded surfaces and themes are involved. Pricing starts from $249 (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.
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.
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.
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.
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.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Upgrade safety | Inheritance-based overrides survive module updates and -u runs | Depends on developer discipline; often breaks on upgrade | Usually inheritance-based but not tuned to your themes | |
| Coverage of all three surfaces | Website, portal, and all transactional emails in one module | Whatever you brief and pay to build | Common surfaces covered; custom themes often missed | |
| Edition & version fit | Built and validated for your exact 17/18/19, Community or Enterprise | Possible, but you own version-drift maintenance | Generic build; edition/version gaps are your problem | |
| Custom & multi-website themes | Extends the same approach to your theme footers and each website | Only if explicitly specified and budgeted | Typically only covers stock themes | |
| Reversibility & data safety | Presentation-only; clean uninstall, no security or data changes | Varies; risk of leftover records if done ad-hoc | Usually clean but rarely documented | |
| Support & accountability | Post-go-live window, git handover, and migration support | Tied to the individual developer's availability | Ticket queue with no context on your deployment | |
| Time to value | 2–4 weeks build-to-order with staging UAT | Weeks to months depending on hiring and spec | Instant install but unpredictable fit and rework | |
| Total cost clarity | Indicative from-price, fixed quote after scoping | Hourly, open-ended, scope creep risk | Low sticker price plus your integration and rework time |
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 2–4 weeks from confirmed scope. Deployments with many custom themes or multi-website setups sit at the longer end of that range.
Pricing starts from $249 (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.
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.
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.
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.
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.
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.
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.