Cashiers and shift supervisors constantly need a fast, glanceable answer to two questions during a sale: how many distinct products are on this ticket, and how many units in total are being sold. Odoo's native POS shows the per-line quantity and the order total, but it never rolls those lines up into a single "total items / total quantity" figure on the order screen. Staff end up mentally adding line quantities, which slows large baskets, invites miscounts at handover, and makes it hard to sanity-check a bag against a receipt. Once you try to expose that summary on the cashier UI, the payment screen, and the printed receipt, you are past what configuration or Studio can reach and into custom OWL components and QWeb overrides.

We build a focused POS extension that computes two derived values in real time — total_items (the count of distinct order lines) and total_quantity (the summed qty across all lines) — and renders them where your team actually needs them. On the front end the values live in a small OWL component patched into the order-widget, subscribed to the POS order store so they recompute reactively as lines are added, merged, or voided (including fractional and weighed quantities, and negative return lines handled per your rule). On the back end the same figures are exposed on pos.order via computed fields (@api.depends('lines', 'lines.qty')) so they persist to the database, flow into QWeb receipts and order reports, and are queryable over the XML-RPC/JSON-RPC API for downstream BI. Nothing is hard-coded to your data — the module is a clean, upgrade-safe addon with its own __manifest__.py, dependency on point_of_sale, and ir.model.access.csv entries scoped to your POS roles.

Because it is made to order, the behaviour is shaped to your operation during scoping: whether "items" counts distinct products or distinct line records, how combo/bundle lines and gift-card lines are treated, whether the counter appears on the receipt header or footer, whether it shows in the customer-facing display, and which POS configs it applies to. We build against your target Odoo major version (17.0, 18.0, or 19.0) and account for Community vs Enterprise differences in the POS module and receipt engine, so the extension installs cleanly on your edition without touching core files.

Delivery is build-to-order, not an instant download. After a scoping call we confirm the exact behaviour, edition, and version, then build and hand over installable source code with a git repository, deploy to your staging for UAT, and cut over to production with a rollback plan. Typical delivery is 2-4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company POS estates, additional receipt/display surfaces, deeper localization of receipt layouts, and integration with external BI or loyalty systems increase the quoted scope.