Odoo's Point of Sale ships a fixed receipt layout and a standard account.move invoice report, which is fine until your brand, your tax authority, or your marketing team needs more. Out of the box you can change the logo and a header/footer string in POS settings, but you cannot reorder blocks, add a loyalty or feedback QR code, print a compliant bilingual receipt, or run different footers per store. Restaurants and retailers routinely hit this wall — the ORL (OWL) receipt component and the QWeb invoice report are hard-coded, so any real change means patching core templates, which then breaks on the next upgrade. That is exactly the gap this module closes.

ECOSIRE builds a dedicated pos_receipt_designer module that introduces a configurable template model — a models.Model (e.g. pos.receipt.template) with fields for header, body, and footer blocks, logo, social/promo content, language behavior, and QR payload rules — linked by Many2one to pos.config so each store or POS session resolves its own template. On the receipt side we extend the OWL OrderReceipt component and its XSS-safe QWeb template so your configured blocks render in the exact order you set, with computed fields (@api.depends) generating the QR image (loyalty URL, feedback form, or e-invoice payload) as a base64 field. On the invoice side we inherit the account.move QWeb report to mirror the same branding, headers, and QR. Bilingual and multilingual text uses Odoo's translation layer and per-block language fields so an Arabic/English or Chinese/English receipt prints side by side. Everything is governed by proper ir.model.access.csv entries and record rules, and template data can be read or pushed through the standard XML-RPC/JSON-RPC API for headless configuration.

Because this is build-to-order, we scope to your Odoo edition and version first. The module targets Odoo 17.0, 18.0, and 19.0, and we handle the differences between them (the POS front-end moved substantially across these releases) plus Community vs Enterprise nuances — e-invoice/QR requirements and localization reports differ, and we align the design to whatever l10n_* localization you run. Nothing depends on Enterprise-only apps unless your compliance target requires it, in which case we tell you up front.

Delivery is straightforward and honest: this is not an instant apps.odoo.com download. After a short scoping call we confirm the exact receipt and invoice layouts, QR use-cases, languages, and per-store rules, then build against your version. Typical delivery is one working week from confirmed scope. You get the installable source, a UAT pass on a staging database with a rollback plan, install and configuration on your environment, documentation, a training session, and a post-go-live support window. The full git repository is handed over to you at the end — you own the code.