Takeaway and QSR pickup flow breaks down at the counter, not in the kitchen. Customers crowd the till asking "is my order ready?", staff shout numbers over noise, and the same order gets handed out twice or missed entirely. Odoo Point of Sale ships a kitchen/preparation display (pos_preparation_display / KDS in Enterprise) that tells the kitchen what to cook, but there is no native customer-facing screen that shows a guest their order number moving from preparing to ready. The KDS is staff-side; the receipt printer is one-shot; and the standard POS customer display mirrors the cart, not the pickup queue. There is simply no out-of-the-box now serving board in either Community or Enterprise, so venues resort to buzzers, whiteboards, or a spare tablet with a spreadsheet.

We build a dedicated pickup-display module that reads directly from your existing POS order lifecycle so no one has to re-enter anything. Technically it is a standard Odoo addon: a __manifest__.py declaring dependency on point_of_sale (and the preparation display where present), a models.Model that projects each pos.order into a lightweight display state (preparing, ready, called, collected) with @api.depends computes for estimated wait time, and an OWL front-end component served as a full-screen public route. When a kitchen ticket is bumped on the KDS, an automated action (or bus.bus push) auto-advances that order number from the Preparing column to the Ready column in real time — no polling refresh, no manual toggling. The Ready transition fires a browser chime and optionally speaks the order number, so guests look up when their number is called instead of hovering at the counter.

The screen itself is fully brandable: your logo, colors, fonts, and an optional promo/menu strip, laid out as QWeb/OWL templates you own and can restyle. Two columns (Preparing vs Ready) with large high-contrast order numbers readable across a food court, an audible chime plus configurable call-out, and a live estimated-wait-time figure computed from your recent throughput. Because it rides on Odoo's ORM and the JSON-RPC/XML-RPC layer, the same order states are queryable by other systems — a second screen, a mobile "your order is ready" SMS trigger, or a self-order kiosk — without duplicating data. Access is locked down with ir.model.access.csv and record rules so the public display route exposes only order numbers and status, never customer or payment data.

Because this is build-to-order, ECOSIRE builds it against your Odoo version and your POS configuration — we do not ship a generic zip and wish you luck. After a short scoping call we confirm the exact columns, chime behavior, wait-time logic, branding, and which screens run where, then develop and test on a staging copy of your database. Typical delivery is one working week from confirmed scope. You receive the full installable source, deployment on your Odoo 17.0, 18.0, or 19.0 (Community or Enterprise), user training, and a post-go-live support window. The git repository is handed to you at the end, so you are never locked to us.