Cashiers routinely need to grant a discount at the register — a manager waving through 10% on a slow afternoon, a line item marked down because the box is dented, a loyalty gesture keyed in by hand. Out of the box, Odoo POS handles discounts unevenly: the per-line discount field exists but is fiddly to reach on a touchscreen, there is no clean one-tap way to apply a single discount across the whole order, and there are no guardrails to stop a junior cashier from keying in 90% off. Teams end up training around the gaps, voiding and re-ringing orders, or disabling discounts entirely — which pushes markdowns back to the manager's terminal and slows the queue.

ECOSIRE builds a Point of Sale Order Discount extension that closes those gaps as a first-class POS action. We add an order-level discount control to the POS screen (OWL components layered over the standard point_of_sale frontend) that applies either a fixed cash amount or a percentage across every line, plus a streamlined per-line discount path so a cashier can mark down a single product without touching the rest of the ticket. On the backend, the discount is modeled cleanly on pos.order and pos.order.line with compute methods (@api.depends on quantity, price, and tax) so totals, tax bases, and the eventual account.move invoice all reconcile correctly — no phantom values, no rounding drift between the session and the posted journal entry.

Control is the point of the build. We wire discount limits and reason codes to POS configuration (pos.config) and to user groups via ir.model.access.csv and record rules, so you decide who may discount, up to what ceiling, and whether a reason or manager approval is required past a threshold. Every discount is captured on the order for reporting, so you can slice markdown by cashier, product category, or session in a QWeb receipt footer and in analysis views. Because it is built on the standard ORM and session sync, it works with your existing payment methods, receipt printers, and the offline-capable POS client, and it is compatible with both Community and Enterprise editions of the release you run.

Delivery is made-to-order, not an instant download. After a short scoping call we confirm the exact discount rules, permission tiers, and reporting you need, then build against your target Odoo version (17.0, 18.0, or 19.0), test on a staging copy of your database, and install to production with a rollback path. Typical delivery is 2 to 4 weeks from confirmed scope, depending on how many permission tiers, approval flows, and integrations are in play. Pricing starts from $249 (indicative, single-company base scope); multi-company rollouts, custom approval workflows, loyalty or ERP integrations, and localization or fiscal-receipt depth increase the quoted scope.