Every Odoo record — a sale order, a vendor bill, a helpdesk ticket, an employee contract — accumulates attachments in the chatter and the sidebar. But to actually read a PDF spec, check a signed contract, or glance at a delivery photo, a user has to click, wait for the browser to download the ir.attachment binary, hunt for it in a downloads folder, open it in a separate application, then switch back to Odoo. Multiply that across an accounts-payable, sales, or HR team handling dozens of documents a day and it becomes a constant, quiet drag on throughput — plus a data-governance concern, because sensitive files end up scattered across local disks. Odoo core renders image thumbnails in a few places, and Enterprise ships the Documents app, but out of the box there is no consistent in-record viewer that opens PDFs and Office files inline everywhere attachments actually live.

ECOSIRE builds Documents Preview as a made-to-order module that adds an embedded viewer to the models and records you nominate. Technically, it extends the attachment layer with an OWL client-side component that reads from ir.attachment and renders supported formats in a modal or a docked side panel without triggering a file download. PDFs render through a viewer bundled into the module's web assets, images (png, jpg, webp, svg) display natively, and common Office formats (docx, xlsx, pptx) are handled through a server-side conversion step so they appear as previewable pages rather than opaque blobs. The viewer is wired into the chatter attachment list and, where you want it, into a dedicated Preview button or an embedded widget on the form view via a small XML/OWL extension — so previewing is available exactly where your users already work, not in a separate app.

Because it reads through the standard ORM, the module inherits your existing access rules: ir.model.access.csv and record rules already governing ir.attachment and the parent document continue to apply, so a user can only preview what they are entitled to see. We can scope preview availability per model, per user group, or per record state; add optional watermarking or a download-disabled mode for sensitive documents; cache converted renditions to keep large files responsive; and expose the viewer over the JSON-RPC/XML-RPC API surface if a portal or a companion app needs it. The build targets Community and Enterprise alike — on Enterprise we can integrate cleanly alongside the Documents app rather than duplicating it — and is delivered for your exact Odoo 17.0, 18.0, or 19.0 version.

Delivery is build-to-order: it starts with a short scoping call to confirm which models, formats, and viewing behaviours you need, after which we return a fixed quotation and a UAT plan. We build against a staging copy of your database, you sign off on staging, and we deploy to production with a rollback path. Typical delivery is 2-4 weeks from confirmed scope, depending on the format set and integration depth. Pricing starts from $249 (indicative, single-company base scope); wider format conversion coverage, multi-company deployment, watermarking/DRM behaviour, and portal or external-app integration increase the quoted scope.