POS Kitchen Display System (KDS)

Name: POS Kitchen Display System (KDS)
Brand: ECOSIRE
SKU: pos-kitchen-display-system

核心功能

Real-time order streaming from Odoo POS to kitchen and bar screens the instant an order is placed, pushed over Odoo's bus/longpolling channel with no manual refresh

Per-station routing that sends each line to the correct screen (grill, fryer, bar, cold, dessert) based on POS product category mapping you define

Category and course filters per screen so each station only sees the items it is responsible for, reducing clutter and cook confusion

Color-coded prep timers computed live via @api.depends — tickets shift from green to amber to red as they approach and breach your configured SLA

SLA and overdue alerting with optional automated actions (ir.actions.server) that flag late tickets or notify a shift lead

One-tap order bumping to clear completed items, with a bump log so nothing is lost

Recall of recently bumped tickets to correct mistakes or handle a remake without re-firing from POS

All-day item view aggregating open quantities per product (e.g. '12 fries in progress') so stations can batch and prep ahead

Course sequencing so starters, mains and desserts fire in the right order instead of all at once

Full modifier, variant and note display (no onions, well done, allergy flags) rendered clearly on each ticket line

Multi-screen and multi-station support for busy kitchens, each screen independently configurable and touch-optimized as an OWL/QWeb interface

Station-scoped security via ir.model.access.csv and record rules — line cooks see only their station, expo and managers see the whole board

Configurable ticket layout, font sizing and columns tuned for wall-mounted displays and inexpensive tablets

Order status write-back so POS/expo can see when a ticket is started, in progress or completed

Works on Odoo Community or Enterprise across versions 17, 18 and 19 with data available over XML-RPC/JSON-RPC for future dashboards

按需定制，全程代劳

无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。

您下单

以一次性构建价格开始。我们在启动时与您共同确定范围。

我们构建与安装

ECOSIRE 在您的 Odoo 上构建、配置并安装。

上线 + 支持

约 2–4 周内上线，并提供上线后的支持期。

关于此产品

Paper kitchen tickets slow your line down: they jam, get lost, pile up during a rush, and give you zero visibility into which orders are late. The ECOSIRE POS Kitchen Display System (KDS) replaces that paper with real-time digital screens mounted at each kitchen and bar station, streaming every order the moment your staff hit "Order" in Odoo POS.

This is a build-to-order Odoo module. We do not sell an off-the-shelf download — ECOSIRE designs, builds, installs and supports a KDS tailored to your stations, menu categories, prep flow and screen layout, then hands you the source. It runs on your own Odoo Community or Enterprise instance (17, 18 or 19) and integrates natively with Point of Sale, so there is no third-party SaaS, no per-terminal subscription, and no external kitchen hardware lock-in.

Under the hood the module adds new Odoo models (models.Model) for kitchen orders, order lines and station configuration, with computed fields (@api.depends) that derive live prep timers, overdue/SLA states and all-day item counts. Real-time updates are pushed to the screens over Odoo's bus/longpolling channel so tickets appear instantly without refreshing. The kitchen screens themselves are built as OWL components rendered through QWeb, designed for touch use on cheap tablets or wall-mounted displays. Access is locked down properly with ir.model.access.csv and record rules so line cooks only see their station, and managers see everything. Automated actions can flag overdue tickets or notify a shift lead. Because it is a real Odoo module, the same order data is available over XML-RPC / JSON-RPC for any dashboard or reporting you want to bolt on later.

The result: orders route automatically to the right station (a burger fires to the grill, a mojito fires to the bar), prep timers turn yellow then red as they approach your SLA, cooks bump completed items with one tap, and expo sees a clean all-day view of everything in the pipe. Ticket times drop, walkouts drop, and mistakes from smudged or missing paper tickets disappear.

你得到什么

Complete, commented Odoo module source code (models, OWL/QWeb views, security, data files) delivered as an installable addon in a Git repository you own

A configured KDS mapped to your real stations, menu categories, courses and prep-time SLAs — not a generic demo

Installation and deployment on your Odoo 17/18/19 instance (or guided deploy to your hosting), including POS integration and screen setup

ir.model.access.csv access rights and record rules configured for your roles (line cook, expo, kitchen manager)

Written admin and end-user documentation covering station setup, routing rules, bump/recall workflow and the all-day view

A live training session for kitchen, expo and management staff plus a short recorded walkthrough for future hires

A post-launch support and bug-fix window (typically 30 days) covering defects and reasonable configuration adjustments

Odoo version-compatibility notes and a handover guide so your team or ours can maintain and extend the module later

这是给谁的

QSR / fast-casual owner

Runs a high-volume quick-service kitchen where ticket speed is everything. Needs orders to hit the right station automatically and cooks to see, at a glance, which tickets are running late — without a manager babysitting the pass.

Multi-station restaurant operator

Manages a full-service kitchen with separate grill, fryer, cold and bar stations. Wants each station to see only its own items, drinks to route straight to the bar, and courses to fire in sequence so plates land together.

Odoo POS admin / IT lead

Already runs Odoo Point of Sale and wants kitchen display built into the same system — one database, native security, no extra SaaS subscription or kitchen-printer hardware, and data reachable over JSON-RPC for reporting.

POS Kitchen Display System (KDS) 如何比较

标准	伊科西尔	定制建造	竞争对手
Native Odoo POS integration (one database, no third-party SaaS)	包含	部分支持	部分支持
Per-station routing (grill / fryer / bar / cold) by category	包含	部分支持	部分支持
Real-time streaming to screens via Odoo bus (no refresh)	包含	部分支持	部分支持
Color-coded prep timers with SLA / overdue alerts	包含	部分支持	不包括在内
Bump, recall and all-day item view	包含	部分支持	部分支持
Course sequencing and full modifier / note display	包含	部分支持	部分支持
Station-scoped security (ir.model.access.csv + record rules)	包含	部分支持	不包括在内
Tailored to your stations, menu and prep flow	包含	包含	不包括在内
You own the source; no per-screen subscription	包含	包含	不包括在内
Installed, trained and supported by the vendor	包含	不包括在内	不包括在内

关于POS Kitchen Display System (KDS)的常见问题

How long does delivery take, and what happens after I buy?

This is a build-to-order module, not an instant download. Typical lead time is 2 to 4 weeks depending on how many stations, menu categories and courses you have. After purchase we run a short discovery call to map your stations and prep SLAs, then build, configure and install the KDS on your Odoo instance, run acceptance testing with you, and train your team before go-live.

What support and updates are included after launch?

Every build includes a post-launch support window (typically 30 days) covering bug fixes and reasonable configuration tweaks — for example adjusting routing rules or SLA timers once you see it in real service. Because you receive the full source in a repo you own, you can maintain it yourself, or we offer ongoing support and version-upgrade retainers to keep it running smoothly across future Odoo releases.

Does this work with Odoo Community, and which versions are supported?

Yes. The KDS is a standard Odoo addon that runs on both Community and Enterprise editions, and we build it against your specific version — Odoo 17, 18 or 19. It integrates with the standard Odoo Point of Sale app, so you do not need any additional Odoo enterprise licence purely for the kitchen display.

What hardware do the kitchen screens run on?

The screens are built as touch-friendly OWL/QWeb web interfaces, so they run in a browser on inexpensive tablets, all-in-one touchscreens or wall-mounted displays — anything that can open your Odoo URL on the same network. There is no proprietary kitchen hardware and no per-screen licence fee; you can add stations by adding screens.

How do orders know which station to go to?

During the build we map your POS product categories to stations — for example, all 'Burgers' and 'Grill' items route to the grill screen while 'Drinks' route to the bar. Routing is configuration-driven, so as your menu changes you (or we) can reassign categories without changing code. Modifiers, variants and kitchen notes travel with each line so cooks see the full instruction.

Can we keep our existing POS receipt printers as a backup?

Yes. The KDS reads orders from Odoo POS without disabling anything you already use, so you can run digital screens as the primary workflow while keeping a printer as a fallback during the transition. Many kitchens start with both, then retire paper once staff trust the screens.

Is the order data available for reporting or other systems?

Absolutely. Everything lives in real Odoo models in your own database, so prep times, bump events and ticket history are queryable directly and over Odoo's XML-RPC / JSON-RPC API. That means you can build Odoo dashboards or feed a BI tool for metrics like average ticket time per station without any extra integration layer.