Every Odoo team that runs more than one database eventually posts the same invoice twice, edits a real customer in a staging clone, or confirms a test sale order against production — because staging, UAT, dev, and live all look identical in the browser. Odoo core gives you no visual cue about which database you are in: the backend chrome, the menus, and the record forms are byte-for-byte the same across environments. The only signals are the URL and the database name in the login selector, and neither is visible once you are three clicks deep into a form view. It is a small gap that produces expensive, hard-to-reverse mistakes, and it gets worse as your team grows and people keep several tabs open at once.

Environment Ribbon closes that gap by painting an always-visible, color-coded banner across the Odoo web client on any database you designate as non-production. We build a lightweight module whose __manifest__.py depends only on web, with configuration stored in ir.config_parameter (surfaced through res.config.settings) so an administrator sets the ribbon label, color, and corner position per database without touching source. On the client side an OWL component reads those parameters from the session-info payload and injects a fixed-position ribbon into the web client layout — for example amber for staging, red for dev, blue for UAT — with a z-index tuned to sit above dialogs but never intercept clicks (pointer-events: none). Because the flag lives per database rather than in the codebase, the same restored dump can be promoted from staging to production and the ribbon simply disappears once the production database has no override set.

Beyond the base banner we build the guard rails teams actually ask for after the first near-miss. We can gate high-risk operations behind the environment flag — a confirmation interstitial when a user tries to send email, post a journal entry, or run a mass action on a database tagged non-production — and optionally neutralize outbound ir.mail_server and scheduled ir.cron jobs on clones so a staging copy never emails real customers or charges real cards. Ribbon visibility, label text, and the color map can be driven by hostname pattern, by database name regex, or by an explicit ir.config_parameter key, and access to change those settings is locked down with ir.model.access.csv plus a record rule so only administrators can flip an environment's identity. Everything renders server-side-safe and degrades cleanly: if the parameter is unset, no ribbon shows and nothing changes.

Because this is build-to-order, you receive a module built and tested against your exact Odoo version (17.0, 18.0, or 19.0) and edition (Community or Enterprise — the web client injection differs subtly between them, and we account for it), not a generic download you have to adapt. We start with a short scoping call, confirm your environment topology and color conventions, build on a branch, and deliver onto a staging database for UAT before promoting to production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); additional environments, host/regex-based auto-detection, outbound-email and cron neutralization on clones, and multi-company or Odoo.sh-specific behavior increase the quoted scope.