A build-to-order Odoo Point of Sale extension that surfaces each product's discounted price directly on the POS product grid and order lines, so cashiers and customers see the real, post-discount amount at a glance. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17/18/19. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
App manifest
Built around your workflow
A build-to-order Odoo Point of Sale extension that surfaces each product's discounted price directly on the POS product grid and order lines, so cashiers and customers see the real, post-discount amount at a glance. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17/18/19.
No DIY setup — a working app, built, installed and supported by ECOSIRE.
Start with a one-time build price. We scope it with you at kickoff.
ECOSIRE builds, configures and installs it on your Odoo.
You go live in about 2–4 weeks, with a post-launch support window.
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.
Runs one or more physical stores on Odoo POS and needs the discounted price visible on-screen so cashiers stop misquoting promotions and customers trust the price. Wants the display to match invoices exactly and to be scoped per store.
Owns the Odoo instance and pricelist setup and needs a clean, upgrade-friendly module that reuses native pricelist logic instead of a fragile client-side hack. Values the git handover, technical docs, and per-series compatibility.
Designs pricelist rules, seasonal campaigns, and loyalty tiers and needs the POS front end to advertise 'was/now' pricing and percentage-off badges so promotions actually land at the counter and drive conversion.
Delivers Odoo to retail customers and wants a proven build-to-order POS price-display extension, built and supported per client edition and version, with UAT and rollback so rollouts stay low-risk.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Discounted price on POS product grid | Built to show effective price + struck-through original on each tile | Possible but you design and maintain the OWL patch yourself | May show it, but with vendor-fixed behavior you cannot alter | |
| Matches invoiced price | Derived from Odoo's own pricelist computation — one source of truth | Depends on your implementation; easy to drift if calc is duplicated | Usually yes, but internals are opaque | |
| Odoo version/edition fit | Built and validated for your exact 17/18/19, Community or Enterprise | Whatever you build it for; you own cross-version testing | Listed versions only; may lag on new releases | |
| Configurability (badges, labels, pricelists) | Config-driven 'was/now', %-off, rounding, and per-store scoping | As flexible as you build, at your cost and time | Fixed to the module's own options | |
| Fit to your discount sources | Scoped to your pricelists, loyalty, and manual discounts | Fully bespoke but entirely your effort | Generic assumptions; may not cover your setup | |
| Delivery model | Build-to-order: scoped, staged UAT, rollback, 2-4 weeks | Your internal backlog and timeline | Instant download but no fit-to-you guarantee | |
| Support and handover | Training, post-go-live support window, full git repo handover | Self-supported | Vendor ticket queue; source often obfuscated | |
| Total cost of ownership | From $249 indicative; fixed quote after scoping | Developer time to build, test, and maintain across upgrades | Low sticker price, but rework if it doesn't fit |
No. This is a build-to-order module. ECOSIRE designs, builds, installs, and supports it for your specific Odoo instance after we scope your requirements together. It is not an off-the-shelf apps.odoo.com download.
Typical delivery is 2-4 weeks from confirmed scope. The timeline depends on how your discounts originate (pricelists, loyalty, manual line discounts), the number of stores or companies, and any bespoke badge or localization work. We commit to a delivery window once scope is locked after the scoping call.
No — that is the core design principle. The displayed figure is derived from the same server-side `product.pricelist` computation Odoo uses when it creates the order line, so the on-screen price and the invoiced price come from one source of truth. Products with no applicable discount simply show their normal price.
We build and validate against Odoo 17.0, 18.0, and 19.0, for both Community and Enterprise. Because the POS assets bundle and OWL component APIs differ between series, we target your exact version — you tell us your version and edition on the scoping call.
Pricing starts from $249 (indicative, single-company base scope). Drivers such as multi-company or multi-store rollouts, complex pricelist or loyalty logic, and custom badge localization increase the quote. After a short scoping call we give you a fixed, written quote — no surprises on the invoice.
Every engagement includes a post-go-live support window for defect fixes and questions. Because you receive the full git repository and technical docs, your team can maintain it, and we can quote a separate upgrade engagement when you move to a newer Odoo series.
Yes. 'Was/now' formatting, percentage-off badges, rounding, and label text are driven by configuration rather than hard-coded rules, and we can localize label wording. Which pricelists trigger the badge and how it reads are agreed during scoping.
A build-to-order Odoo Point of Sale extension that surfaces each product's discounted price directly on the POS product grid and order lines, so cashiers and customers see the real, post-discount amount at a glance. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17/18/19.