A build-to-order Odoo Point of Sale extension that auto-detects and manages POS receipt and kitchen printers, routes order lines to the right station, and adds a one-click test print with Self Order support. ECOSIRE scopes, builds, installs, and supports it for Odoo 17.0/18.0/19.0. 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
Auf Ihren Workflow zugeschnitten
A build-to-order Odoo Point of Sale extension that auto-detects and manages POS receipt and kitchen printers, routes order lines to the right station, and adds a one-click test print with Self Order support. ECOSIRE scopes, builds, installs, and supports it for Odoo 17.0/18.0/19.0.
Keine Selbsteinrichtung — eine funktionierende App, die von ECOSIRE erstellt, installiert und betreut wird.
Starten Sie mit einem einmaligen Entwicklungspreis. Den Umfang legen wir beim Kickoff gemeinsam fest.
ECOSIRE erstellt, konfiguriert und installiert sie auf Ihrem Odoo.
Sie gehen in etwa 2–4 Wochen live, mit einem Support-Zeitraum nach dem Launch.
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 2–4 weeks: 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 $249 (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.
Runs a kitchen with separate hot, cold, and bar stations and needs each order line to hit the right printer automatically, with a way to confirm every device is alive before the dinner rush.
Manages several `pos.config` records across locations and wants printer discovery, health checks, and manager-locked configuration instead of hand-typing IPs and chasing dead devices.
Takes kiosk and QR-menu orders and needs customer-placed items to route through the same station rules as cashier orders so nothing gets re-fired by hand.
Delivering a hospitality rollout and needs a clean, upgrade-safe printing extension with source handover and documented security rather than a black-box off-the-shelf module.
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| Printer discovery | Network scan pre-populates ESC/POS candidates | Whatever you build; discovery is extra effort | Usually manual IP entry only | |
| Station routing | Per-category Many2many routing, cashier + Self Order | Buildable but you design and test it | Category mapping, often cashier-only | |
| Test print / health check | One-click backend + in-POS OWL test print | Only if you scope and build it | Rarely included | |
| Self Order support | Kiosk/QR items follow the same routing rules | Requires bespoke `pos_self_order` work | Often unsupported or partial | |
| Fit to your hardware | ESC/POS payload and ticket layout tuned to your devices | Fully yours, at full build cost | Fixed template, take it or leave it | |
| Source & ownership | Full source + git repo handover | You own it, you maintain it | Vendor-locked, often obfuscated | |
| Version/edition coverage | Built and tested for 17/18/19, CE & EE | Only the versions you fund | Varies; upgrades lag | |
| Support model | Scoped build + post-go-live support window | Your team or contractor on demand | Generic ticket queue, no SLA |
No. This is a build-to-order productized service. ECOSIRE builds your copy from source against your Odoo version and station layout, then installs and supports it. It is not an existing apps.odoo.com download, and we never claim an instant download.
Typical delivery is 2–4 weeks from confirmed scope. We build on a branch, hand you a staging build for UAT, then install on production with a rollback plan. Larger scopes — multiple POS configs, multi-company, or deep Self Order work — sit at the longer end, which we confirm on the scoping call.
Pricing starts from $249 (indicative, single-company base scope). Drivers such as additional POS configs, multi-company setups, IoT Box transport, bespoke ticket layouts, or localization increase the quoted scope. After a short scoping call we send a fixed quote — the indicative figure is a starting point, not the final invoice.
We build and test for Odoo 17.0, 18.0, and 19.0 on both Community and Enterprise. Where a capability differs by edition — for example Self Order availability or IoT Box printer transport — we confirm it against your specific edition during scoping so nothing is assumed.
Every build includes a post-go-live support window for defect fixes and configuration adjustments, plus a git repository handover so you own the code. Migrating the module to a future Odoo major version, or adding new stations and features later, is quoted as a follow-on engagement.
Yes, where `pos_self_order` is in scope. Kiosk and QR-menu orders resolve through the same category-to-station routing as cashier orders, so a customer-placed item prints at the correct kitchen or bar station without a manual re-fire.
Printer setup and station mapping are restricted to managers via `ir.model.access.csv` plus record rules, while cashiers can only trigger prints and the in-POS test print. This keeps routing configuration out of reach of front-of-house staff during service.
A build-to-order Odoo Point of Sale extension that auto-detects and manages POS receipt and kitchen printers, routes order lines to the right station, and adds a one-click test print with Self Order support. ECOSIRE scopes, builds, installs, and supports it for Odoo 17.0/18.0/19.0.