Critical context in Odoo too often lives in the wrong place. A customer's "always call before shipping" note is buried in the chatter, a payment-hold warning sits in an internal comment nobody reads, and onboarding knowledge dies in someone's inbox. Odoo's native tools give you the mail.thread chatter, internal notes, and activities, but none of them puts a persistent, high-visibility message directly on top of the record where a mistake actually happens. The result is repeated errors, "I didn't know" excuses, and tribal knowledge that never scales past the person who holds it.

Sticky Notes closes that gap. ECOSIRE builds a module that pins indicative, colour-coded notes to any Odoo form view — res.partner, sale.order, stock.picking, hr.employee, or your own custom models — so alerts and internal messages appear the moment a record is opened. Under the hood we add a sticky.note model (models.Model) linked to the target record via res_model/res_id (a generic reference) or via an explicit Many2one, with fields for body, colour, author, pin/unpin state, and optional expiry. An OWL client-side component renders the notes as a floating layer over the chosen form views, injected through XML view inheritance and QWeb templates so it feels native rather than bolted on. Notes are read/written over the standard ORM, which means everything works identically through the web client and the external XML-RPC/JSON-RPC API.

Because it is built to your process, the behaviour is yours to define. We can scope model-level notes (one message shared across all sales orders) or record-level notes (specific to a single partner); role-based visibility so a finance-only warning never shows to the warehouse; @api.depends computed notes that appear automatically when a condition is met (credit limit exceeded, stock below reorder point); and automated actions or server actions that create or clear notes on state changes. Access is governed properly through ir.model.access.csv and record rules, so multi-company and department boundaries are respected rather than assumed. We support Odoo 17.0, 18.0, and 19.0, on Community or Enterprise — noting where Enterprise-only widgets or studio-created fields affect the design.

Delivery is build-to-order, not an instant download. After a short scoping call we confirm the exact form views, note types, visibility rules, and automation you need, then hand you a fixed written quote. We develop against your Odoo version on a staging database, run UAT with your team, and only deploy to production once you sign off — with a rollback plan in hand. Typical delivery is 2 to 4 weeks from confirmed scope, depending on how many models and rules are in play. Pricing starts from $249 (indicative, single-company base scope); additional target models, role-based visibility matrices, computed/automated note logic, and multi-company deployment increase the quoted scope.