Quick facts
- Price
- $299.00 USD
- Odoo versions
- 17, 18, 19
- Setup time
- 30 min
- License
- One-time perpetual
- Languages
- 11 languages
One-time Purchase
Front Desk
A build-to-order Odoo reception system with a self check-in kiosk and live patient queue management. ECOSIRE designs, builds, installs, and supports it for your Odoo 17/18/19 instance after a scoping call.
$299.00USD
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Key Features
`frontdesk.visit` arrival model with a `checked_in → waiting → called → in_consultation → done` state machine and computed `@api.depends` wait-time fields
Self check-in kiosk built in OWL/QWeb: lookup by appointment code, phone, or name against `res.partner`, with on-screen confirmation of contact and consent fields
Live queue board as an auto-refreshing kanban/list of `frontdesk.visit` records, ordered by arrival time and priority
One-click 'call next patient' action that transitions state and stamps the calling user and timestamp
QWeb-rendered waiting-room display board showing now-serving and next-up, drivable on a signage screen or spare tablet
Automatic linkage of walk-ins and booked patients: arrivals bind to their `calendar.event`/Appointments record when one exists
Room and provider routing so a checked-in patient is assigned to the correct queue and consultation location
SLA/wait-threshold automated actions (server actions on state change) that flag or escalate patients waiting past a configurable limit
Role-scoped access via `ir.model.access.csv` plus record rules for receptionist, triage nurse, and provider profiles
Multi-company / multi-site aware — every visit carries `company_id` so branches keep separate queues and reporting
XML-RPC/JSON-RPC endpoints and web controllers so the kiosk and board can be driven headlessly or integrated with external signage/badge hardware
Configurable check-in field set (insurance, reason-for-visit, priority flag) defined per your intake process, not hard-coded
Daily throughput and average-wait reporting via a QWeb report and pivot/graph views over `frontdesk.visit`
Optional SMS/notification hooks on 'called' state so patients who step away are alerted when it's their turn
About this Product
Clinics, hospitals, and multi-specialty practices lose the most goodwill in the first ten minutes of a visit — the front desk. Patients queue at a single counter, receptionists key the same demographics twice, and nobody has a real-time picture of who has arrived, who is waiting, and who the doctor should see next. Odoo core gives you res.partner for patient records and calendar.event or the Appointments app for bookings, but it has no concept of a physical arrival event, no self-service check-in surface, and no living queue that a waiting-room display or a nurse's screen can watch. Receptionists end up bridging that gap with sticky notes and shouted names.
Why Choose Front Desk
`frontdesk.visit` arrival model with a `checked_in → waiting → called → in_consultation → done` state machine and computed `@api.depends` wait-time fields
Self check-in kiosk built in OWL/QWeb: lookup by appointment code, phone, or name against `res.partner`, with on-screen confirmation of contact and consent fields
Live queue board as an auto-refreshing kanban/list of `frontdesk.visit` records, ordered by arrival time and priority
One-click 'call next patient' action that transitions state and stamps the calling user and timestamp
QWeb-rendered waiting-room display board showing now-serving and next-up, drivable on a signage screen or spare tablet
Automatic linkage of walk-ins and booked patients: arrivals bind to their `calendar.event`/Appointments record when one exists
Front Desk is the reception layer ECOSIRE builds on top of your existing Odoo to close that gap. At its core is a new frontdesk.visit model (a models.Model with @api.depends computed wait-time and status fields) that captures each arrival, links it to the patient's res.partner and their scheduled calendar.event, and moves through a state machine — checked_in → waiting → called → in_consultation → done. A kiosk-mode OWL/QWeb front end lets patients (or a greeter on a tablet) check themselves in by appointment code, phone number, or name lookup, confirm or update contact fields, and drop straight into the correct queue. Staff work from a live kanban and list view of frontdesk.visit records, call the next patient with one click, and route them to a room or provider; a QWeb-rendered waiting-room display board and optional SMS/notification hooks keep everyone informed. Access is controlled through ir.model.access.csv plus record rules so a receptionist, a triage nurse, and a provider each see the right slice, and everything respects company_id for multi-site groups.
Because it is native Odoo, Front Desk reuses what you already run: appointments feed the queue automatically, completed visits can trigger the invoicing or Odoo Health/clinical flow you use, and automated actions (server actions on state change) handle escalations like flagging a patient who has waited past an SLA threshold. The kiosk and display board are exposed through controllers and can be driven headlessly via the XML-RPC/JSON-RPC API for integration with a scheduling screen, a badge printer, or a third-party signage system. We build against your edition — Community or Enterprise — and target Odoo 17.0, 18.0, or 19.0, matching the ORM and OWL conventions of the exact version you run.
Front Desk is made to order, not an off-the-shelf download. After a short scoping call we confirm your check-in fields, queue routing rules, provider/room model, and any integrations, then build, test on a staging clone, and deliver the installable module with documentation and training. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $299 (indicative, single-company base scope); multi-company or multi-site queues, extra integrations (SMS gateway, signage, badge/label hardware), and deeper clinical-workflow ties increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise invoice.
What you get
- Installable, version-matched Odoo module source (your build for Odoo 17.0, 18.0, or 19.0) with a clean `__manifest__.py` and declared dependencies
- Installation and configuration on your instance (or a guided install), including kiosk and display-board setup
- Technical documentation: data model, `ir.model.access.csv`/record-rule matrix, state machine, and integration/API notes
- End-user guide plus a live training session for reception, nursing, and provider staff
- UAT on a staging clone of your database with a documented rollback plan before go-live
- Post-go-live support window for defect fixes and configuration adjustments
- Git repository handover with full commit history and tagged release
- Seed configuration data: queue definitions, room/provider mapping, and check-in field layout matching your scope
Who this is for
Clinic Operations Manager
Runs a multi-provider practice on Odoo and needs to cut waiting-room chaos, measure average wait time, and give reception a single screen for the queue instead of paper lists.
Hospital IT / Odoo Administrator
Owns the Odoo instance and wants a maintainable, native module — proper access rules, `company_id` scoping, and an API surface — rather than a black-box app or fragile customizations.
Front-Desk / Reception Lead
Manages daily patient flow and wants self check-in to absorb arrivals, a clear 'call next' workflow, and a display board so patients stop crowding the counter.
Group Practice Owner
Operates several sites and needs per-branch queues, consistent check-in across locations, and throughput reporting to justify staffing decisions.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Front Desk module ZIP from your account dashboard.
Upload to Odoo
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Install the module
Activate Developer Mode, open Apps, click Update Apps List, search for Front Desk, and press Install.
Configure settings
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Verify & go live
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
How Front Desk Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Delivery model | Built to order for your Odoo version, installed and supported by us | Built once by your team or a freelancer, from scratch | Generic download, install as-is | |
| Self check-in kiosk | OWL/QWeb kiosk with appointment/phone/name lookup, tailored fields | Possible, but design and edge cases are on you | Fixed kiosk if offered, limited configurability | |
| Live patient queue | `frontdesk.visit` state machine with kanban, board, and 'call next' | Whatever you specify and can afford to build | Basic queue, hard to alter routing | |
| Multi-site / company scoping | `company_id`-scoped per-branch queues by design | Only if explicitly engineered | Often single-company assumptions | |
| Access control | Role-mapped `ir.model.access.csv` + record rules to your structure | You design and maintain the security matrix | Preset groups, limited adjustment | |
| Version fit (17/18/19) | Built and tested against your exact version and edition | Whatever version you target; migrations are your job | Supported versions vary; may lag releases | |
| Support & handover | Post-go-live window, training, docs, and full git repo | Depends entirely on the builder's engagement | Vendor ticket queue, no source ownership | |
| Total effort to running | Scoping call, then we deliver a working system | Full spec, build, test, and maintenance cycle on you | Install fast, then fight configuration limits |
Frequently Asked Questions about Front Desk
Is this an app I can download and install right now?
No. Front Desk is build-to-order. We design and build it for your Odoo edition and version after a scoping call, then install and support it. There is no instant download — you get a module engineered to your intake and queue rules.
How long does delivery take?
Typical delivery is 2–4 weeks from confirmed scope. Simpler single-site builds land toward the shorter end; multi-company queues, hardware integrations, or deep clinical ties sit toward the longer end. We agree the timeline in writing before work starts.
How does pricing and scoping work?
Pricing starts from $299 as an indicative single-company base. We hold a scoping call (15–45 minutes) to confirm your check-in fields, routing, sites, and integrations, then issue a fixed quote. You approve the fixed quote before any build begins — the from-price is a starting point, not the final number.
Do you support Odoo Community or only Enterprise?
Both. We build against whichever edition you run and target Odoo 17.0, 18.0, or 19.0, matching that version's ORM and OWL conventions. During scoping we confirm your exact edition and version so the module installs cleanly with no unexpected dependencies.
What about updates and support after go-live?
Every build includes a post-go-live support window for defect fixes and configuration tweaks. Beyond that, we offer ongoing support and version-migration work (for example moving your build from 18.0 to 19.0) as a separate engagement. You also receive the full git repository, so your own team can maintain it.
Can the kiosk and queue integrate with our existing systems?
Yes. Arrivals bind to your Odoo Appointments/`calendar.event` records, and the kiosk and display board are exposed through web controllers and the XML-RPC/JSON-RPC API, so they can drive external signage, badge printers, or an SMS gateway. We confirm the specific integrations in scoping.
Will it respect our access and privacy rules?
Access is enforced with `ir.model.access.csv` and record rules, so receptionists, nurses, and providers each see only the appropriate data, and all visits are scoped by `company_id`. We map your role structure during scoping and encode it in the security layer.
Related Modules
Request a quote
Front Desk
A build-to-order Odoo reception system with a self check-in kiosk and live patient queue management. ECOSIRE designs, builds, installs, and supports it for your Odoo 17/18/19 instance after a scoping call.
- `frontdesk.visit` arrival model with a `checked_in → waiting → called → in_consultation → done` state machine and computed `@api.depends` wait-time fields
- Self check-in kiosk built in OWL/QWeb: lookup by appointment code, phone, or name against `res.partner`, with on-screen confirmation of contact and consent fields
- Live queue board as an auto-refreshing kanban/list of `frontdesk.visit` records, ordered by arrival time and priority
- One-click 'call next patient' action that transitions state and stamps the calling user and timestamp