| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Point of Sale (point_of_sale)
• Discuss (mail) • Inventory (stock) • Invoicing (account) |
| Lines of code | 902 |
| Technical Name |
eh_pos_kds_core |
| License | OPL-1 |
| Website | https://www.erpheritage.com.au |
Kitchen Display Core
The shared foundation for the ERP Heritage Point of Sale display suite: the data model, the order routing engine and the realtime backbone behind the Kitchen Display and the Order Status Screen.
Why this module
The engine the displays run on.
Queryable routing
First class rules route each product to a board and lane by point of sale, category or attribute, so you can answer which station makes what.
Append only audit
Card state is the projection of a durable event log, so concurrent bumps are ordered by the server and nothing is lost to a clock skew.
No Enterprise needed
Builds on the standard Point of Sale and bus modules and installs on a clean Odoo Community.
What is inside
Built to do the job, end to end.
- Boards and lanes. Configurable display boards, each with its own lanes and routing.
- Tickets, items and cards. An original model where each card is the unit staff bump.
- Realtime push. A private per board channel keyed by a secure token.
Honest about the edges
What this does not do, so nothing surprises you.
- This is a backend dependency. The screens live in the Kitchen Display and Order Status Screen modules.
- Restaurant coursing and self order kiosk routing are planned for later releases.
odoo kitchen display backend, pos display engine, odoo kds core, pos routing engine, odoo community pos display
Languages
Available in 19 languages
The interface ships translated out of the box. Switch language in Odoo and the fields, menus, and messages follow.
Modules teams pair with this one.
Premium ERP Heritage modules that extend the same stack, each built to the same engineering bar.
Sync timesheet entries from the Employment Hero people and payroll platform into the standard Odoo Timesheets app...
Real-time MRA fiscalisation for Point of Sale receipts in Odoo 19 Community, mapping each paid POS order to the M...
Shared foundation for the ERP Heritage Employment Hero country packs
Bring Employment Hero onboarding workflows, employee goals and contractor flags into Odoo Community as real recor...
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Point of Sale (point_of_sale)
• Discuss (mail) • Inventory (stock) • Invoicing (account) |
| Lines of code | 902 |
| Technical Name |
eh_pos_kds_core |
| License | OPL-1 |
| Website | https://www.erpheritage.com.au |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module