Sales reps and customers read quotations by product name and internal reference, but text alone is a weak signal. On configurable products, variant-heavy catalogs, or long multi-line orders, a wrong line is easy to miss until goods are picked or the customer disputes the PDF. Odoo core already stores a product image (image_1920 plus its resized image_128/image_256 companions on product.product and product.template), yet the standard sale.order.line editable list view shows none of it, and the out-of-the-box QWeb sale report (sale.report_saleorder_document) prints a text-only table. Teams end up cross-referencing a separate catalog or spreadsheet just to confirm a line is right — exactly the manual step Odoo is supposed to remove.

We build a focused module that surfaces the product thumbnail where the work happens. On the model side we add an image field to sale.order.line — either a stored related='product_id.image_128' or a compute method with @api.depends('product_id'), chosen during scoping for the best list-render performance on your order sizes — and expose it as an image/binary widget column in the order-line tree/list view. On the document side we inherit sale.report_saleorder_document via QWeb and emit a correctly sized <img> per line so the same picture appears on the quotation and confirmed order PDF. All view and report changes ship as XML inheritance (xpath with position) layered over core rather than patched into it, so the module installs cleanly on Community or Enterprise and survives upgrades.

Because images are heavier than text, we engineer for scale rather than just correctness. We render the small resized variant (image_128) not the full image_1920, keep the column optional/toggleable so power users can hide it on hundred-line orders, and make sure the report image is constrained by CSS so wkhtmltopdf/QWeb-to-PDF rendering stays fast and the file size stays sane. Access is respected end to end: the line inherits its record rules and ir.model.access.csv from sale.order, so nobody sees an image on an order they could not already open, and the field is read-only where the line is read-only. Where you want the image to also flow to the portal quotation view or the backend order form header, we scope that as an explicit view extension too.

Delivery is build-to-order. After a short scoping call we confirm exactly which surfaces need the image (order-line list, order form, PDF quotation, portal, optionally delivery or invoice reports), agree the field strategy and Odoo series (17.0, 18.0, or 19.0), and give you a fixed quote. We build on a staging copy of your database, run UAT with your own products and templates, then install on production with a documented rollback. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); extending the image to additional reports (delivery slip, invoice, portal), multi-company report layouts, or bespoke image sizing/branding requirements increases the quoted scope.