| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Point of Sale (point_of_sale)
• Employees (hr) • Discuss (mail) • Inventory (stock) • Invoicing (account) |
| Lines of code | 333 |
| Technical Name |
wt_pos_access_right |
| License | OPL-1 |
| Website | http://warlocktechnologies.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Point of Sale (point_of_sale)
• Employees (hr) • Discuss (mail) • Inventory (stock) • Invoicing (account) |
| Lines of code | 333 |
| Technical Name |
wt_pos_access_right |
| License | OPL-1 |
| Website | http://warlocktechnologies.com |
POS Access Right
Community
Enterprise
Explore this module
Overview
This module enhances the Point of Sale (POS) system by providing administrators with the ability to restrict specific features and actions for employees. It ensures better control and security of POS operations by allowing restrictions on the following:
- Control Buttons:
- Quantity modification
- Discounts
- Price changes
- Removing order lines
- Increment/Decrement (+/-) operations
- Action Buttons:
- Canceling orders
- Performing cash in/out operations
- Processing refunds
With these restrictions, the module ensures that employees have limited access to sensitive functions, providing better control over POS operations.
Features
Restrict quantity modification for employees.
Restrict discount application in POS.
Restrict price changes by employees.
Restrict removing order lines in POS.
Restrict increment/decrement (+/-) operations in POS.
Restrict canceling orders by employees.
Restrict cash in/out operations in POS.
Restrict processing refunds by employees.
Configuration
- Enable 'Log in with Employees' in POS configuration to make all employee restriction fields visible in the settings.
- After selecting 'Log in with Employees' in the Point of Sale, the restriction fields will appear in the POS settings, enabling you to assign and manage access permissions for employees.
- Once an employee is selected in the Basic Rights section, that employee will become visible across all restriction fields, allowing for tailored access control.
- When an employee is selected in the restriction fields, they will not have access to the corresponding control and action buttons. The following restrictions apply:
- Restrict Quantity: Selected employee(s) cannot modify quantities.
- Restrict Discount: Selected employee(s) cannot apply discounts.
- Restrict Price: Selected employee(s) cannot change product prices.
- Restrict Remove Line: Selected employee(s) cannot remove order lines.
- Restrict +/-: Selected employee(s) cannot perform increment or decrement actions.
- Additionally, for action buttons:
- Restrict Cancel Order: Selected employee(s) cannot cancel orders.
- Restrict Cash In-Out: Selected employee(s) cannot perform cash in or cash out operations.
- Restrict Refund Order: Selected employee(s) cannot process refund orders.
- Employees selected in the 'Restrict Quantity', 'Restrict Discount', 'Restrict Price', 'Restrict Remove Line', and 'Restrict +/-' fields will not have access to modify quantities, apply discounts, change product prices, remove order lines, or perform increment/decrement actions.
- Selected employees in the 'Restrict Cancel Order' field will not have access to process Cancel Order.
- Selected employees in the 'Restrict Cash In-Out' field will not have access to process Cash In-Out.
- Selected employees in the 'Restrict Refund Order' field will not have access to process Refund Orders.
sales@warlocktechnologies.com
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
There are no ratings yet!
Hello Mohamed Sharif,
Yes It's in development stage for all latest version and It will be published soon. You can contact us on sales@warlocktechnologies If you want to develop this module on urgent basis.
Thanks & Regards,
v17
Hi, do you have this module in odoo 17 CE
Subject: Issue with POS Restaurant Module Causing White Screen on Session Start
We have encountered a critical issue when using the Point of Sale Restaurant
When we activate the restaurant features in the POS configuration (i.e., enable "Is a Bar/Restaurant"), the POS session fails to load correctly. Instead of opening the POS interface, it displays a blank white screen.
However, when we switch back to a regular POS configuration (without the restaurant mode), the session loads and operates normally.
This issue persists consistently and only occurs when the restaurant mode is enabled. It prevents us from using the POS in restaurant environments, which is essential for our business operations.
Please advise on how to resolve or work around this issue. If this is a known bug, we would appreciate guidance on any upcoming fixes or patches.
Best regards,