$ 10.00
In-App Purchases| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Employees (hr)
• Point of Sale (point_of_sale) • Discuss (mail) • Inventory (stock) • Invoicing (account) |
| Lines of code | 153 |
| Technical Name |
pos_order_access |
| License | OPL-1 |
| Website | https://www.linkedin.com/in/amrsalah07/ |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Employees (hr)
• Point of Sale (point_of_sale) • Discuss (mail) • Inventory (stock) • Invoicing (account) |
| Lines of code | 153 |
| Technical Name |
pos_order_access |
| License | OPL-1 |
| Website | https://www.linkedin.com/in/amrsalah07/ |
POS Access Rules Management
The only POS access control app that binds rules to your session configuration — not to individual employees. One flexible rule set per terminal, shared across multiple staff.
This module provides comprehensive control over Point of Sale operations, define access rules per POS session configuration. Assign multiple employees to each rule profile. Every terminal in your business can have completely different security policies — all managed from one place.
Why We’re Different
Instead of binding rules to an individual employee — making them rigid and inflexible across multi-terminal environments. We took a smarter, session-first approach.
Bound to Session Config
Access rules are attached to the POS session configuration. Each terminal or store can have a completely independent security policy — without touching individual employee records.
Assign Multiple Employees
Each access rule profile supports multiple employees. Onboard new staff in seconds by simply adding them to an existing profile — no need to reconfigure each person individually.
Different Policies Per Terminal
Store A can strictly block order creation. Store B allows managers full flexibility. The same employee can have different permissions depending on which terminal they log into.
Reuse Rules Across Sessions
One access rule profile can be linked to multiple POS sessions at once. Define your policy once and apply it to all relevant terminals — updates take effect everywhere automatically.
Key Features
Restrict New Orders
Control who has the ability to create new orders at the terminal. Ensure only authorized staff can initiate new transactions.
Restrict Delete Orders
Prevent unauthorized removal of active or floating orders. Secure your terminal against accidental or malicious order deletions.
Screenshots
Support & Contact
For any inquiries, bug reports, custom development, or feature requests.
Email Us
amrsalahshahin@gmail.com
Connect with Amr Shahin
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