Teams that run Odoo hit the same wall constantly: a record has attachments, but the built-in viewer only renders a narrow set of file types inline. Everything else — CAD exports, SVGs, Markdown, code files, EML/MSG emails, archives, less common image and office formats — forces users to download the file, switch to a desktop app, and lose the record context. On a busy Sales order, Project task, Helpdesk ticket, or Documents workspace, that friction multiplies across hundreds of attachments a day and quietly slows everyone down. Odoo core (ir.attachment plus the OWL/mail attachment viewer) is deliberately conservative about what it will render, and it does not give you an extension point to teach it new preview types without touching the framework.

Preview is a build-to-order module that ECOSIRE designs, builds, installs, and supports for your environment — it is not an existing apps.odoo.com download. We extend the attachment viewer component so that the file types your team actually works with open directly in the browser, inside the same side panel and full-screen viewer users already know. Technically, we register additional MIME-type and extension handlers against the OWL attachment viewer, add server-side helpers on ir.attachment (compute fields for detected type, thumbnail generation, and safe content streaming controllers) where a format needs pre-processing, and keep everything gated by Odoo's own access model — ir.model.access.csv and record rules — so a user can only preview a file they were already allowed to open. Where a format benefits from a lightweight rendered thumbnail, we generate it server-side and cache it on the attachment rather than re-rendering on every open.

Because it hooks the standard viewer rather than replacing it, Preview shows up wherever attachments already appear: the chatter/side panel on any model, the Documents app, and record forms. We scope which formats to support to your real files (so you are not paying for renderers you will never use), respect Community-vs-Enterprise differences in the underlying viewer, and ship the module with a clean __manifest__.py, versioned for your exact Odoo release. No sql.raw, no monkey-patches that break on the next minor upgrade — clean inheritance and documented extension points.

Build-to-order delivery works like this: we start with a short scoping call to confirm the exact file types, the models where previews matter most, your Odoo version (17.0 / 18.0 / 19.0), and Community vs Enterprise. We then build your version, test it on a staging copy of your database, run UAT with your team, and deploy to production with a rollback plan and a git repo handover. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); the number of file formats, server-side thumbnail rendering for heavier formats, multi-company deployment, and integration with an external document store increase the quoted scope. You receive a firm fixed quote after the scoping call — never a surprise bill.