Busy restaurants live or die on the pass. When a POS session drives three receipt printers, a hot line, a cold station, and a bar, Odoo's stock printer setup starts to strain: devices are configured one at a time by IP, there is no reliable way to confirm a printer is reachable before service, and Self Order tickets do not always land where the kitchen expects them. Staff end up walking dockets by hand, re-firing orders, or discovering a dead printer mid-rush. Odoo's native pos.printer model covers the happy path — one or two ESC/POS network printers mapped to product categories — but it gives you no discovery, no health check, and no unified way to manage a growing fleet of stations across multiple pos.config records.

POS Kitchen Direct Printing is a made-to-order Odoo POS extension that ECOSIRE builds around exactly that gap. On the backend we extend pos.printer and the pos.config relation that binds printers to a session with a discovery routine that scans the reachable network segment for ESC/POS-capable devices and pre-populates candidate printers, so an operator confirms hardware instead of typing IP addresses. Category-to-station routing is modeled with fields.Many2many against pos.category and enforced with @api.depends compute logic, so every order line is directed to the correct kitchen or bar printer deterministically. A one-click test-print action — exposed both in the backend pos.printer form (an XML button wired to a Python method) and in the POS UI as an OWL component — fires a known test docket to a chosen device so staff verify every station before opening, not during the rush.

Technically, the module ships as a standard addon: a clean __manifest__.py declaring dependencies on point_of_sale (and pos_self_order where Self Order routing is in scope), server models under models/, POS front-end assets registered through the point_of_sale._assets_pos bundle, and backend views in XML. Access is locked down with ir.model.access.csv plus record rules so printer configuration stays with managers, while cashiers only trigger prints. Self Order support means kiosk and QR-menu orders resolve through the same routing rules as cashier orders, so a customer-placed item hits the correct station without a manual re-fire. Because ECOSIRE builds your copy from source, the print payload can be shaped to your hardware — ESC/POS command tuning, cut behavior, header/footer QWeb-style ticket layout, and multi-language item names — rather than forcing your kitchen to fit a fixed template. Everything is built and tested for Odoo 17.0, 18.0, and 19.0, on Community or Enterprise; where a capability differs between editions (for example Self Order availability or IoT Box printer transport), we confirm it against your edition during scoping.

Delivery is build-to-order, not an instant download. We start with a short scoping call to map your station layout, printer models and transport (direct network ESC/POS vs IoT Box), number of POS configs, and whether Self Order is in play. From confirmed scope, typical delivery is one working week: we build on a branch, hand you a staging build for UAT, then install on production with a rollback plan and a post-go-live support window. Pricing starts from $999 (indicative, single-company base scope); additional POS configs, multi-company setups, IoT Box transport, bespoke ticket layouts, or deeper Self Order and localization work increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise on the invoice.