On a busy checkout counter, the Odoo Point of Sale shows the product's list price on the grid, but the price a customer actually pays after pricelist rules, loyalty tiers, or manual line discounts only resolves once the item is already in the cart. Cashiers second-guess whether a promotion applied, customers ask "wasn't this on sale?", and disputes slow the queue. Odoo core does apply pricelists and discounts correctly in the backend — but the POS UI was never designed to advertise the discounted price up front, on the tile, before the item is tapped. That gap is where signage, promotions, and price-match confidence quietly break down.

This is a build-to-order module that ECOSIRE designs and builds for you — it is not an existing download you install today. We extend the POS OWL frontend so each product card renders both the original price (struck through) and the effective discounted price computed from the active pricelist context, and we mirror the same clarity on the order line so the saving per line is visible while the sale is in progress. Technically, we hook the POS product-screen components (patching the OWL component and models.js product wrapper), reuse Odoo's own product.pricelist / product.pricelist.item resolution so the displayed figure is exactly what the order engine will charge (no parallel, drift-prone calculation), and respect the current partner, currency, and iface_tax_included setting so tax display matches your pos.config. Where you need promotional badges, percentage-off labels, or "was/now" formatting tied to specific pricelists, we drive those from configurable fields rather than hard-coded rules.

Because the price shown must never disagree with the price charged, we build defensively: the discounted figure is derived from the same server-side pricelist computation Odoo uses at line creation, guarded so that products with no applicable discount simply render their normal price with no visual noise. Access to any new configuration (which pricelists trigger the badge, rounding, label text) is governed through ir.model.access.csv and, where multi-store scoping is needed, record rules on pos.config. The extension ships as a proper module with a clean __manifest__.py, is compatible with your Community or Enterprise edition, and is validated against the specific Odoo series you run (17.0, 18.0, or 19.0) since the POS assets bundle and OWL APIs differ meaningfully between them.

Delivery is made-to-order. After a short scoping call we confirm exactly how your discounts originate (pricelist rules, loyalty, manual line discounts, or a combination), agree the on-screen treatment, then build against a staging copy of your database, run UAT with your team, and deploy with a rollback plan. Typical delivery is 2-4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company or multi-store rollouts, unusual pricelist logic, loyalty/promotion integration, and bespoke badge/label localization increase the quoted scope. You receive a fixed quote after the scoping call, never a surprise on the invoice.