| 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 | 3971 |
| Technical Name |
pos_sentinel |
| License | OPL-1 |
| Website | https://neurodev.cl |
| Versions | 17.0 18.0 19.0 |
| 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 | 3971 |
| Technical Name |
pos_sentinel |
| License | OPL-1 |
| Website | https://neurodev.cl |
| Versions | 17.0 18.0 19.0 |
|
⚡ MAY 2026 LAUNCH PROMO ⚡
USD $299
USD $199
(-33%)
Limited launch pricing · Valid until May 31, 2026
Buy now and lock the discount — price returns to USD $299 on June 1.
|
POS Sentinel
Catch POS fraud before it grows
The cashier is no longer the only one watching the transaction. POS Sentinel logs every suspicious move with tamper-proof integrity and alerts you instantly by email, Slack, Telegram or WhatsApp.
What you're losing right now without knowing
28%
Of retail shrinkage comes from internal POS fraud (NRF Retail Security Survey 2022). CCTV shows you what happened. POS Sentinel tells you why it was suspicious.
USD 30K
Average loss per cashier per year when fraud goes undetected. One single post-payment void per day is enough to get there.
0
Immutable logs in standard Odoo POS. The data is in your DB, but nobody looks at it until someone starts stealing. By then, it's too late.
What it catches — with names attached
18 event types, automatically classified by risk level. Real examples from the log:
| CRITICAL | Sweethearting: "A cashier rang up products at $0 for a customer 7 times this month" |
| HIGH | Post-payment void: "A cashier voided 3 sales after handing back change" |
| HIGH | Excessive discount: "A cashier applied 80% discount without authorization" |
| CRITICAL | Below-cost sale: "Premium steak sold at $200/kg when cost is $8,000/kg" |
| HIGH | After-hours activity: "Cash drawer movement at 23:45 with store closed" |
| MEDIUM | Suspicious price change: "Whisky price changed 3 times today" |
Plus 12 more event types: refunds, cash in/out, unclosed sessions, sequence gaps, post-payment line modifications, etc.
How it works — 3 protection layers
Silent capture
Every POS event is logged without affecting the cashier or slowing the register. Runs in the background.
Scoring engine
Every event gets a risk score (Low / Medium / High / Critical) based on amount, frequency, and timing. Rules are 100% configurable.
Instant alert
Email, Slack, Telegram, Discord, WhatsApp or SMS. The owner finds out in real time, not at month-end closing.
Alerts wherever you are
Configurable pipeline that triggers on Critical-only or High+Critical thresholds. Five delivery channels out of the box:
The log is tamper-proof — forensic-grade
-
🔒 Triple-layer immutability — ORM overrides + ACL + record rules.
unlink,copy, and arbitrarywriteraiseUserError. Not even admin can tamper. - 🧬 SHA-256 chained hash with secret salt — Per-database cryptographic salt. Any modification breaks the chain and is detected.
-
✅ Automated weekly integrity check — Scheduled action recomputes hashes and flags any mismatch as
tampered. - 👥 Separation of duties — POS Auditor (read-only) vs POS Security Manager (config + justify).
- 🏢 Multi-company aware — Every event scoped to its company via record rules.
🛡️ Multi-Standard Compliance Audit Trail
SHA-256 chained hashing + 2-year retention + weekly automated verification. Ready for PCI DSS, SOX, ISO 27001, GDPR and regional cybersecurity laws.
Meets the standards your auditors check
| Standard | Requirement | Meets |
|---|---|---|
| PCI DSS Req. 10 | Tracking and monitoring of cardholder data access | ✓ |
| ISO 27001 A.12.4 | Logging and monitoring of security events | ✓ |
| SOX Section 404 | Internal controls over financial reporting | ✓ |
| GDPR Art. 30 | Records of processing activities | ✓ |
| NIST 800-53 AU-3 | Content of audit records | ✓ |
Compatibility
Tech stack
- Python 3 + Odoo ORM — backend events, scoring, integrity
- OWL 2 + Chart.js — reactive dashboard
- QWeb + xlsxwriter — reports
- Pure
point_of_saleextension — no external dependencies
License
OPL-1 (Odoo Proprietary License v1) — perpetual, single-database license.
Source code published on github.com/neurodev-apps for transparency
and community auditability.
Questions before installing?
Direct support from the developer. Remote installation available on request.
🌐 neurodev.cl · ✉️ contacto@neurodev.cl · 📱 WhatsApp +56 9 2837 4712
Built by NeuroDev — Chile · neurodev.cl
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