POS Customer-Facing Display (Dual Screen)

We build a true dual-screen customer-facing display as a proper Odoo POS extension. The module ships as a standard addon with a __manifest__.py declaring the point_of_sale dependency and its own assets bundle, so it loads inside the POS runtime rather than as a bolt-on. On the technical side it registers OWL components and a POS store subscription that listen to pos.order / pos.order.line changes in the running session, then push cart lines, quantities, the computed running total, taxes, applied loyalty/pricelist promotions, and the selected payment method to a second browser window or an external screen. Idle-state behavior (a branded promo/ad carousel), theming, currency and language, and which fields are shown are all driven from a configuration model backed by ir.model.access.csv and record rules so store managers — not developers — control the layout per POS config.

Because it is real Odoo code, it behaves the way your team expects. The customer name and live loyalty-points balance are pulled from the same res.partner / loyalty records the cashier selects, computed fields use @api.depends so totals stay consistent with the order, and the display reacts to payment registration to show amount tendered and change due at the moment the cashier takes payment. The second screen can run on the same machine (a second monitor), a customer-side tablet on the LAN, or an Android/Windows mini-display, and the data path uses the POS's existing session state — with an optional JSON-RPC/XML-RPC hook when you need to drive an external signage device. It is built for Odoo 17.0, 18.0, and 19.0, and we confirm your Community vs Enterprise edition during scoping because the POS asset pipeline differs between them.

This is a build-to-order product, not an instant apps.odoo.com download. You request a quotation, we run a short scoping call to lock your exact fields, branding, hardware, and edition, and then ECOSIRE builds, tests, and installs it for you. Typical delivery is 2 to 4 weeks from confirmed scope. You receive the full source, a staging UAT before anything touches your live POS, a rollback plan, training, and a post-go-live support window — and the git repository is handed over so the code is yours to keep.