A build-to-order Odoo module that replaces the default sign-in screen with your own branded, security-conscious login experience — custom backgrounds, layout, copy, and UI controls. ECOSIRE builds, installs, and supports it after a short scoping call. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
Manifesto do app
Feito em torno do seu fluxo de trabalho
A build-to-order Odoo module that replaces the default sign-in screen with your own branded, security-conscious login experience — custom backgrounds, layout, copy, and UI controls. ECOSIRE builds, installs, and supports it after a short scoping call.
Sem configuração por conta própria — um app funcional criado, instalado e com suporte da ECOSIRE.
Comece com um preço único de desenvolvimento. Definimos o escopo com você no início.
A ECOSIRE cria, configura e instala no seu Odoo.
Você entra no ar em cerca de 2–4 semanas, com um período de suporte pós-lançamento.
Every Odoo deployment ships with the same generic /web/login screen: a centered card, the stock database picker, and Odoo branding baked into the template. For an internal tool that might be acceptable, but the login page is the first thing employees, franchise partners, and portal customers see every day — and out of the box you cannot change the background, restructure the layout, tune the copy, hide the database selector, or reflect your own brand without editing core templates. Odoo core exposes no settings screen for any of this; the moment you want it, you are into overriding the web.login QWeb template and the auth controllers, which is precisely the kind of change that silently breaks on the next -u base or version upgrade if it is not packaged as a proper module.
This is a made-to-order module that ECOSIRE designs, builds, and installs specifically for your instance. We deliver it as a clean, self-contained addon with its own __manifest__.py that inherits (never patches) the relevant web templates via XML <template> inheritance, so your look survives upgrades and can be uninstalled cleanly. Technically, we override the web.login and web.login_layout QWeb templates to inject your background image or gradient, restructured card, logo, custom heading/subheading, footer links, and language/theme controls; assets (CSS/SCSS, optional OWL widgets, images) are registered through the web.assets_frontend bundle in the manifest so they are bundled and cached the Odoo way. Configurable options — background source, show/hide the database selector, custom links, per-company branding — are stored as res.config.settings fields backed by ir.config_parameter, so administrators change them from Settings without a redeploy. Where you need behavioral control (for example suppressing the DB selector, adding a "reset password" nudge, or a compliance/consent notice), we extend the web.Home / Session auth controllers with a thin Python override rather than replacing them.
Security and correctness are treated as first-class, because the login page sits on an unauthenticated route. Any new fields carry proper ir.model.access.csv entries and, where multi-company or restricted visibility matters, record rules; user-supplied HTML in custom notices is escaped/sanitized so the branding surface can never become an injection vector; and we keep the change compatible with your CSP and reverse-proxy headers. The module is built and tested against Odoo 17.0, 18.0, and 19.0, and works on both Community and Enterprise (Enterprise's own web assets are respected, not overwritten). If you drive provisioning through the XML-RPC/JSON-RPC API or automated actions, the configuration parameters remain scriptable so branding can be applied consistently across staging and production databases.
Because this is build-to-order, nothing is pre-listed for instant download — we build your version after we understand your scope. The flow is a short scoping call to confirm the exact look, the options you need, and your target Odoo version and edition; a fixed written quote; development on a staging copy of your database; UAT sign-off with a documented rollback; then installation on production and a handover of the git repository and docs. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company branding, pixel-exact design replication, extra languages, or bundling with a broader portal/theme project increases the quoted scope.
Owns the Odoo instance and wants a branded, professional login screen without hand-editing core QWeb templates that break on every upgrade. Needs it delivered as a proper module they can maintain, uninstall, and carry across 17/18/19.
Cares that every employee- and partner-facing surface reflects the company's colors, logo, and voice. Wants pixel-consistent background, layout, and copy on the login page, ideally per-company for a multi-brand group.
Delivers Odoo to clients and wants a white-label, upgrade-safe login customization they can drop into projects. Needs clean source, documented inheritance points, and a git handover so their own team can extend it.
Needs the login page to carry a consent or policy notice and, in some setups, to hide the database selector — done in a way that keeps the unauthenticated route safe (sanitized HTML, proper access rules, CSP intact).
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| Delivery model | Built, installed, and supported for you in 2–4 weeks | You scope, build, and maintain it yourself | Instant download, then self-install and self-configure | |
| Upgrade safety | XML inheritance + manifest assets; survives `-u` and major-version jumps | Depends entirely on your discipline; core edits often break | Varies by author; may lag new Odoo versions | |
| Branding fit | Pixel-matched to your design, including per-company | Whatever you have time to build | Fixed set of preset options; limited layout control | |
| Security handling | Sanitized HTML, `ir.model.access.csv`, record rules, CSP-safe on the unauthenticated route | Your responsibility to get right | Generally styling-only; rarely addresses the auth route | |
| Source ownership | Full git repo handover with history and docs | You own it because you wrote it | Licensed binary/source per the vendor's terms | |
| Version coverage | Targeted and tested on 17.0 / 18.0 / 19.0, Community + Enterprise | Only what you build and test | Whatever versions the listing supports | |
| Ongoing support | Post-go-live window + optional migration retainer | Internal team time only | Author support quality and SLA vary | |
| Total cost of ownership | Fixed quote from $249 plus optional support; predictable | Low license cost, high hidden dev + maintenance time | Low upfront, but self-managed fixes and upgrades |
No. This is a build-to-order module. ECOSIRE designs and builds your version after a short scoping call so it matches your exact branding, options, and target Odoo version — it is not a pre-existing instant download. We then install it on your staging and production instances and hand over the source.
Typical delivery is 2–4 weeks from confirmed scope. The clock starts once we've agreed the visual design, the options you need, and your Odoo version/edition on the scoping call and issued a fixed written quote. Simple single-company branding lands toward the shorter end; multi-company or pixel-exact design replication toward the longer end.
Pricing starts from $249 (indicative, single-company base scope). After a short scoping call we send a fixed written quote — no surprises. Drivers that increase scope include multi-company branding, exact design replication from a mockup, additional languages, controller-level behavior changes, or bundling with a wider portal/theme project.
No. We use XML template inheritance and register assets through the manifest rather than editing core templates, so your branding is layered on top and survives `-u` updates. We build and test against Odoo 17.0, 18.0, and 19.0; a major-version jump is a small, quoted re-test rather than a rebuild.
Every build includes a post-go-live support window for defect fixes and questions, plus the full git repository so your team can extend it. Beyond the included window we offer ongoing support and version-migration retainers. Because you own the source, you are never locked in.
Yes. The module works on both. On Enterprise we respect and layer over the Enterprise web assets rather than overwriting them, so nothing in the Enterprise UI is disturbed. Tell us your edition on the scoping call and we target it precisely.
Yes. We can suppress the multi-database selector via a thin auth-controller override and add a consent or policy notice. Because the login route is unauthenticated, any custom HTML is sanitized server-side and access is governed by proper `ir.model.access.csv` rules and record rules so the branding surface stays secure.
A build-to-order Odoo module that replaces the default sign-in screen with your own branded, security-conscious login experience — custom backgrounds, layout, copy, and UI controls. ECOSIRE builds, installs, and supports it after a short scoping call.