Technical Specifications & Compatibility
Technical Module Name
Supported Odoo Versions
v17.0v18.0v19.0
License
Aura
Deployment Support
Odoo OnlineOdoo.shOn Premise
Lines of Code
2138 lines (Python / XML / JS)
Overview & Description
Aura Odoo Tech Supports:Odoo 19CommunityEnterprise POS Restaurant Access Management 19.0.1.0: floors, tables, split bill, kitchen Keep table moves and bills in the right hands. Extends Advanced POS Access Management with rules for the restaurant floor. Warn, block or ask for a manager PIN before a table is moved, merged or split, or before the kitchen is touched. ✓Table transfer and merge can need a manager PIN ✓Split bill, guests, kitchen and courses can be guarded ✓Same rules, same approval popup, same access log 10 Restaurant switches 3 Response modes 4 Log results why restaurants use it Guard the floor, not the staff Every switch is a checkbox on a rule. The rule form, popup and log come from the base module. Floor and tables Who may move guests around. Floor screen Guard the Tables tab itself. Table selection Guard opening a table from the floor plan. Transfer and merge Moving an order to another table or merging two tables can need a manager PIN. Order move Guard creating or moving a floating order. Service operations The steps between order and bill. Split bill Guard the Split screen and splitting an order into new bills. Guest count Guard changing the number of guests. Kitchen Guard sending to the kitchen, printing the bill and reprinting a kitchen ticket. Courses Guard adding, firing and transferring courses. One system, not two Built on the base module. Same rule form A Restaurant Restrictions tab appears on the rule form you already use. Same three modes Soft, Hard or Manager Approval, with the same targeting by terminal, user, employee or group. Same approval popup Manager, PIN and reason, exactly as for retail rules. Same access log Entries such as Transfer / Merge Table and Split Bill land in the base module's log. on the floor What the waiter sees These are live restaurant Point of Sale screens from a test database. Transfer needs a PIN. Transfer / Merge sits behind a manager approval rule. The popup names the action and asks for manager, PIN and reason. A wrong PIN changes nothing. The table stays where it is, the notice says Invalid manager PIN, and the attempt is logged as Rejected. Hard block. With a hard rule on Split Bill the button stays visible, and pressing it shows Split Bill is blocked by access policy. The attempt is logged as Blocked. After approval. With the right PIN the floor plan opens in transfer mode, ready to pick the destination table. the back office Same place, one more tab Rules and logs live under Point of Sale, Configuration, POS Access Management. Restaurant Restrictions. A new tab on the rule form. Floor and table switches on the left, operations on the right. One rule list. Restaurant rules sit next to the base rules, with the same mode badges. One access log. Transfer / Merge Table and Split Bill attempts appear with the rule, result and approving manager. how it works Four steps to a guarded floor 1 Install both modules This module needs POS Access Management and the Restaurant app. 2 Open or create a rule Choose the mode, then the POS terminal, users, employees or groups. 3 Tick the restaurant switches Use the Restaurant Restrictions tab, for example Table Transfer and Table Merge. 4 Try it at a table Open the POS. The rule applies on the next load, and to open terminals within about a minute. good to know Questions, answered Does a hard rule hide the button? Not in the restaurant switches. The button stays on screen and pressing it shows a blocked notice and writes a Blocked log entry. Hard rules from the base module, such as the customer button, do hide their buttons. Does it work without the base module? No. It depends on POS Access Management and POS Restaurant, and reuses their rule form, approval popup and log. Who can approve? Any employee with a PIN whose user is a POS manager or a POS Access Manager, as in the base module. Odoo versions? Odoo 19.0 only, Community and Enterprise. Technical Depends on pos_access_management_aura and pos_restaurant. Adds ten fields to pos.access.rule and patches the floor, table, split bill, kitchen and course actions of the 19 POS. License OPL-1. support We are here to help Written and maintained by Aura Odoo Tech. Email Questions, problems or a setting you need: write to us directly. odooaura@gmail.com Website More Odoo modules, documentation and customisation services. www.auraodoo.tech
Key Capabilities & Features
- The author can leave a single reply to each comment.
- This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
- If you want to start a discussion with the author or have a question related to your purchase, please use the support page.
Screenshots & Previews
10 images availableExpand Preview
Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview

Expand Preview
The AuraOdoo Quality Guarantee
100% Tested
Verified with Odoo 17, 18, and 19 test pipelines for stability and no conflicts.
Clean Architecture
Built according to official Odoo guidelines and PEP 8 standards with zero bloat.
Dedicated Support
Free installation assistance and quick bug turnaround from our team.