CODEerts POS Manager Authorization | PIN Card Authenticator OTP Approval for Odoo POS | Refund Discount Delete Price Lock
by CODEerts https://www.codeerts.com$ 79.00
POS Manager Approval
A manager has to sign off before a cashier can refund, discount,
change a price, delete a line or void an order.
Approve with a manager PIN, a printed QR or barcode card, or a code from Google or Microsoft Authenticator. PIN and card work offline, and every attempt is logged.
|
10
Gatable Actions
|
3
Approval Methods
|
2
Work Offline
|
Every
Attempt Logged
|
Per POS
Opt-In
|
The register risks every owner knows
|
Anyone can discount or refund
A cashier can give a discount, change a price, refund or void an order with nobody signing off, and the losses are hard to trace. |
No record of overrides
When something is written off there is no trail of who approved it, which action it was, or how it was authorized. |
Controls break when offline
Registers drop their connection during the day, and a control that needs the server leaves the till unprotected exactly when it matters. |
What this module does
POS Manager Approval puts a manager gate in front of the sensitive actions on the Odoo Point of Sale. You pick which actions need sign-off, Refund, Line Discount, Delete Line, Manual Price Change, Quantity Change, Void Order, Change Customer, Reprint Receipt, Cash In or Out and Close Session, and the register asks for a manager the moment a cashier reaches for one.
A manager approves in one of three ways: their POS PIN or password, a printed QR or barcode card they scan, or a six-digit code from Google or Microsoft Authenticator. PIN and card are verified offline at the register, so the gate keeps working when the connection drops, while the authenticator code is verified on the server where the secret never leaves. Each manager enrolls their own authenticator from their user Preferences, every attempt is written to an audit log, and it is all configured per Point of Sale.
|
🔒
Sign-off on the risky actions
Lock refunds, discounts, price and quantity changes, line deletes, voids and more. Turn each one on or off per Point of Sale. |
🔑
PIN, card or authenticator
Approve with a manager PIN, a scanned QR or barcode card, or a code from Google or Microsoft Authenticator. PIN and card work offline. |
📋
A full audit trail
Every approval and every denial is logged with the manager, the action and the method, so overrides are never a mystery. |
See it in action
From setup to the prompt at the till and the audit log, here is the whole flow.
Manager approval at the till, before the cashier can discount or refund
Turn it on per Point of Sale and choose exactly which actions need sign-off
Set up each manager: a POS PIN, a printable card and an authenticator
Enroll the authenticator by scanning the QR into Google or Microsoft Authenticator
Managers enroll themselves from their own Preferences, with no admin round-trip
Approve by scanning a printed QR or barcode card
Or approve with the current six-digit code from the authenticator app
A full audit trail of who approved what, and every denied attempt
Everything in the box
|
🔒 Manager approval gate
Sensitive POS actions stop and ask for a manager before they go through. |
✅ Ten gatable actions
Refund, discount, delete line, price and quantity change, void, change customer, reprint, cash in or out and close session, each toggled on its own. |
|
🔑 Three approval methods
A manager PIN or password, a printed QR or barcode card, or an authenticator code. Pick a default; the approver can switch. |
📱 Google and Microsoft Authenticator
Standard time-based codes from the apps managers already use. The secret stays on the server. |
|
📶 PIN and card work offline
PIN and card are checked right at the register, so the gate holds when the connection drops. |
🧑💻 Self-service enrollment
Each manager sets up their own authenticator from their Preferences by scanning a QR. No admin handles the secret. |
|
📋 Full audit log
Every attempt, allowed or denied, with the manager, the action and the method used. |
⚙ Per-POS opt-in, offline policy
Configured per Point of Sale, with a choice to allow offline-capable methods or block gated actions when disconnected. |
How it works
1 |
Turn on authorization for a Point of Sale
In Settings, enable it for the registers you want, then tick the actions that need sign-off, choose the methods and add your managers. |
2 |
Set up each manager
Give them a POS PIN, print an authorization card, or have them enroll their own authenticator from their Preferences by scanning a QR. |
3 |
The gate fires at the till
When a cashier triggers a gated action, the register shows a manager prompt and the sale waits. |
4 |
A manager approves
Any authorized manager enters a PIN, scans a card, or types the current authenticator code, and the action goes through. The offline policy decides what happens with no connection. |
5 |
Review the audit log
Open Manager Authorizations to see who approved what, which method they used, and every denied attempt. |
Technical information
|
Version
18.0
|
License
OPL-1
|
Editions
Community & Enterprise
|
Dependencies
Point of Sale, Employees
|
Technical name: codeerts_pos_manager_auth · Built on: the standard Odoo Point of Sale and the built-in authenticator, enabled per register
Frequently asked questions
Turn on authorization for the Point of Sale, then tick the actions that need sign-off, such as Refund and Line Discount. When a cashier triggers one, the register shows a manager prompt and the action only proceeds after a manager approves with their PIN or password, a scanned card, or an authenticator code.
Three: a manager PIN or password, a printed QR or barcode card the manager scans, and a six-digit authenticator code. You enable the methods you want per Point of Sale and choose which one is offered first. The approver can switch to any other enabled method at the prompt.
Yes. The authenticator method uses the standard time-based codes that Google Authenticator, Microsoft Authenticator and similar apps generate. Each manager enrolls once by scanning a QR from their own user Preferences, and the secret is kept on the server and never sent to the register.
PIN and card approvals are verified right at the register, so they keep working with no connection. The authenticator code is checked on the server and needs a connection. An offline policy setting lets you either allow the offline-capable methods while disconnected or block the gated actions until the register is back online.
Refund or Return, Line Discount, Delete Line, Manual Price Change, Quantity Change, Void or Delete Order, Change Customer, Reprint Receipt, Cash In or Out, and Close Session. Each one is switched on or off independently for the Point of Sale.
If their employee is an authorized manager on a Point of Sale, a Set Up Authenticator button appears on their own Change My Preferences screen. They scan the QR with their authenticator app and confirm a code once. No administrator has to handle the secret.
Use the version selector at the top of this page to pick your Odoo release. Each branch is published as its own listing for that exact version, and it works on both Community and Enterprise.
The team behind this module
About CODEerts
Full-Service Odoo ERP Agency · Solutions That Scale
Every module in our store is built from real client work, tested in production and maintained long-term by a team of Odoo certified consultants. When you need more than an app, we deliver the full solution.
|
🏗️ Implementation
Full Odoo roll-outs from requirements to go-live, across any industry and company size. |
🧩 Custom Development
Bespoke modules, OWL components and business logic built precisely to your workflow. |
🔄 Migrations
Zero-data-loss upgrades from older Odoo versions with full custom module porting. |
|
🔌 Integrations
Payment gateways, shipping carriers, biometric devices, eCommerce and third-party APIs. |
🔍 Odoo Audits
Performance, security and code-quality reviews that surface risks before they become problems. |
🧑💻 Support & Training
Ongoing helpdesk, user training and monthly retainers so your team stays productive. |
Odoo Certified |
6+ Years |
50+ Projects |
10+ Industries |
40+ Published Apps |
More from CODEerts
Other apps we build to make Odoo do more. Tap any card to open it on the Odoo Apps Store.
 FREE Archive Anything |  FREE Transaction Flow Visualizer |  FREE Smart Mail Rebrand |  FREE Duplicate Record Detector |
 AI Dashboard Builder |  Advance Payment Pro |  Dual Book & Tax Depreciation |  Smart Duplicate Detector |
| 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 | 1242 |
| Technical Name |
codeerts_pos_manager_auth |
| License | OPL-1 |
| Website | https://www.codeerts.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