Teams that store images in Odoo — product photos, ID scans, signed delivery proofs, inspection snapshots, employee documents — keep hitting the same friction. To actually look at an image you either download the binary attachment, open it in a separate browser tab, or squint at a thumbnail too small to be useful. Odoo core gives you fields.Binary with the standard image widget, which renders a fixed thumbnail, but there is no built-in lightbox, no zoom, no gallery when a record carries several images, and no clean way to preview an attachment referenced from a related model. In image-heavy, high-volume workflows that quietly costs minutes on every record and pushes people out of Odoo into file explorers and email.

We build a made-to-order Image Preview Widget: a custom OWL component registered in the field-widget registry that you attach to any Binary or ir.attachment-backed field through the view XML — for example <field name="photo" widget="image_preview"/>. Clicking the thumbnail opens an in-app modal lightbox with zoom, pan, and next/previous navigation across every image on the record, plus an optional caption drawn from ir.attachment metadata (filename, mimetype, dimensions, upload date). Because it is an OWL widget layered onto Odoo's own asset bundle, it works inside form, kanban, and list contexts, honors the record's read/write access, and never surfaces a binary the user is not already entitled to see under your existing ir.model.access.csv and record rules. No new download path is created — the widget reads the same attachment the user could already open.

Technically, we deliver a self-contained module with its own __manifest__.py declaring the JS/CSS assets into web.assets_backend, the OWL component and its QWeb template, and any thin model glue needed — a compute/@api.depends helper to expose derived attachment metadata, or a small fields.Json payload when a record aggregates images from linked models. We can extend it to preview PDFs and other document types, wire a gallery onto one2many/many2many attachment lines, add a print-to-QWeb-report shortcut, or expose the preview data over the JSON-RPC/XML-RPC API for an external portal. We adapt to Community or Enterprise (Enterprise's web_enterprise asset differences are handled) and target Odoo 17.0, 18.0, or 19.0 to match your database.

Build-to-order delivery works like this: after a short scoping call we confirm the fields, models, and preview behaviors you need, then build against a copy of your database, hand off on a staging instance for UAT, and deploy to production with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope for one field/widget on standard Binary images); multi-model galleries, non-image document previews, external-API/portal exposure, and multi-company or localization depth increase the quoted scope. The final fixed quote is set after the scoping call — never a firm price before we understand your data.