Most Odoo teams that sell over a counter or ship from a busy back office eventually hit the same wall: the standard A4 invoice PDF looks great on a desk but is unusable on a roll printer. The native account.move invoice report and the built-in QWeb templates (account.report_invoice_document) are laid out for full-width paper — margins, multi-column tables, and a company letterhead that all assume 210mm. Feed that to a 58mm or 80mm thermal printer and you get truncated columns, wasted paper, and cashiers who fall back to printing an A4 sheet and folding it. Odoo's Point of Sale receipt is thermal-native, but it is a POS order receipt — it is not your accounting-grade account.move invoice with tax breakdown, invoice number, and payment terms. That gap is exactly where teams get stuck.

We build a dedicated thermal invoice report as a proper Odoo module: a new QWeb report (ir.actions.report with report_type='qweb-pdf', plus an optional HTML/receipt paper format) bound to account.move, using a custom narrow report.paperformat sized to your roll (commonly 58mm or 80mm width, continuous length, minimal margins). The template is authored from the ground up for a single-column receipt flow — condensed header with your logo scaled to roll width, line items stacked with quantity/price/tax on tight rows, a running subtotal/tax/total block, and a footer for VAT/tax registration, return policy, or a QR/barcode. Because it is standard QWeb, it inherits your res.company branding, multi-currency, and per-tax grouping automatically, and it respects the invoice's language for multi-locale printing. We add a print action button on the invoice form (view inheritance via XML) so staff print the thermal copy in one click, and where you drive real ESC/POS hardware we can wire direct raw printing rather than a PDF round-trip. Everything ships with __manifest__.py declaring dependencies (typically account, optionally point_of_sale/stock), ir.model.access.csv and record rules so only the right roles trigger the report, and clean upgrade-safe data records.

Delivery is build-to-order. After a short scoping call we confirm your exact roll width, printer model/driver, which documents need a thermal variant (customer invoices, credit notes, POS-linked invoices, delivery slips), and any localization the footer must carry. We develop on a branch, hand you a staging build for UAT against your real printers and real invoices, then install on production with a rollback plan. Typical delivery is 2-4 weeks from confirmed scope, faster for a single-company single-width base and longer when several document types, languages, or direct ESC/POS integration are in play. You get the installable source for your Odoo major version (17.0, 18.0, or 19.0), a git repository handover, and a support window after go-live.

Pricing starts from $299 (indicative, single-company base scope); additional document types, multiple roll widths/printer models, direct ESC/POS raw printing, extra languages, and multi-company rollouts increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise line item.