Every printed and emailed POS receipt is a customer touchpoint, yet Odoo's stock receipt ships with a generic branding footer and a fixed layout that most retailers cannot fully control from the back office. For a business that has invested in its own brand — a boutique, a franchise group, a white-label operator — a receipt that advertises the underlying software instead of the store dilutes that brand at the exact moment the customer is holding proof of purchase. Odoo's native POS lets you toggle a logo and a header/footer text field, but the powered-by line, the block ordering, tax-summary presentation, QR/loyalty placement, and per-company variations are not exposed as configurable options. Teams end up patching the receipt template by hand on every upgrade, which breaks on the next -u point_of_sale.

ECOSIRE builds a dedicated POS receipt module that removes the powered-by message cleanly and turns your receipt into a configurable, brand-owned document. Technically, we override the OWL receipt component and the underlying QWeb/OWL receipt template used by the POS frontend rather than editing core files, so your changes survive upgrades. A new settings model — extending res.company and the POS config (pos.config) with fields for footer visibility, custom footer HTML, logo sizing, and section toggles — is exposed through the Point of Sale settings view (XML) and guarded by ir.model.access.csv plus record rules so only authorised roles can change branding. Where you need computed content on the ticket (for example a dynamic promotional line or a localised legal footer), we add compute methods with the right @api.depends so the receipt reflects live order state. The customer-facing render is driven entirely from these stored options, meaning your staff configure the receipt from the UI, not from source.

Because branding rules often differ across stores and legal entities, the module is designed for multi-company and multi-config setups from day one: each pos.config can inherit company defaults or override them, and the powered-by suppression, footer text, and layout blocks resolve per session. The same options flow through to the emailed/PDF receipt path (QWeb report) so a customer who asks for a copy by email sees the identical branded document. Everything is packaged as a proper Odoo module with a versioned __manifest__.py, so it installs, upgrades, and uninstalls predictably, and it is delivered separately built and tested against Odoo 17.0, 18.0, and 19.0 (Community and Enterprise), since the POS frontend stack differs meaningfully across those releases.

This is a made-to-order engagement, not an off-the-shelf download. After a short scoping call we confirm your Odoo version, edition, receipt layout requirements, and the stores/companies in play, then build, test on a staging copy of your database, and install into production with a rollback plan. Typical delivery is 2-4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); additional stores or legal entities, deeper receipt redesign, localization of legal/tax footers, and integration with loyalty or e-invoicing layers increase the quoted scope. You receive a fixed quote after the scoping call, before any build work begins.