| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Point of Sale (point_of_sale) • Inventory (stock) • Invoicing (account) |
| Lines of code | 308 |
| Technical Name |
pos_cancelled_orders |
| License | OPL-1 |
| Website | https://arure.tech |
| Versions | 11.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Point of Sale (point_of_sale) • Inventory (stock) • Invoicing (account) |
| Lines of code | 308 |
| Technical Name |
pos_cancelled_orders |
| License | OPL-1 |
| Website | https://arure.tech |
| Versions | 11.0 19.0 |
For Odoo 19 · POS void log · Cashier audit · Restaurant-aware
POS Cancelled Orders Report
Every cancelled / voided / removed line on a Point of Sale order — logged with who, when, which product, which session, which shop, and why. Restaurant-mode aware. Per-shop reporting. Read-only for cashiers, mutable only by POS managers. Tamper-resistant audit trail your auditors will recognise.
v19 port of the proven v11 listing ($50, audit-feature continuity since 2018). Owl-rewritten frontend; tightened model; read-only User group; chatter on every entry.
$50
Per database
2 paths
Drop-line + drop-order
90 days
Refund window
5 reasons
Selection, group-by
support@arure.tech
WhatsApp +1 858 463 4405
What you get
Four guarantees on every install. Every void becomes a record; every record is signed; every cashier knows it.
Every void becomes a row
Backspace on a line with quantity. Order destroy. Manager override. Refund. All five paths captured to one read-only audit table with product, qty, price, time, cashier, session, shop.
Read-only for cashiers
POS user role gets read access only. They can search and filter the log to cover themselves before the manager asks, but they cannot edit or unlink an entry. Auditor-grade.
Chatter on every entry
Manager-only annotation post-hoc — "customer changed mind", "wrong size", "kitchen ran out". Standard Odoo chatter widget; messages are themselves audit-tracked.
Group by anything
Group by shop, session, cashier, product, reason, or day. Spot the cashier who voids before close-out. Spot the SKU that gets dropped from orders.
Who this is for
Restaurants & bars
High-volume restaurants where pre-payment voids are common — comp'd items, kitchen errors, customer changes. Need to spot patterns by cashier and by table.
Retail chains
Multi-shop retail where head office wants visibility into per-shop, per-cashier void behaviour without hiring a full audit team.
Compliance & loss prevention
You need a tamper-resistant log of pre-payment cancellations for internal audit, fraud detection, or regulator review. The User group is read-only by design.
Common scenarios
Three patterns this module catches every shift.
The cashier who voids before every close-out
Group the audit log by cashier and reason. The cashier who consistently voids high-value lines just before session close-out shows up as an outlier. You spot it on a kanban grouped by cashier in 30 seconds.
Restaurant kitchen rejection trail
Order goes to the kitchen, kitchen rejects (no stock, allergy issue, customer change). Cashier voids the line. The audit log captures table, product, cashier, time. Manager later attaches a chatter note explaining the kitchen-side reason.
SKU consistently dropped from orders
Group by product. The SKU that appears in 30+ drop-line entries this month is probably mispriced, mismatched, or out of stock too often. Surface signal you'd otherwise miss.
See it running
Real screenshots from a fresh Odoo 19 instance. Click any image to view full size.
Set it up
Where it lives — POS Reporting menu
Use it daily
Read-only audit list with all dimensions visible
Group by reason — instant pattern view
Trust it
Form view with manager note + chatter audit
Group by shop — per-outlet roll-up
Frequently asked
What exactly counts as a cancellation?
Five paths: (1) Drop Line — cashier presses backspace on a line with quantity > 0; (2) Drop Order — cashier destroys the entire in-progress order via the cancel button, keyboard shortcut, or ticket-screen delete; (3) Manager Void — manager-only override of a sent line; (4) Refund — line refunded after the order was paid; (5) Other — catch-all for ad-hoc cases. Each gets its own Selection value so reports group cleanly.
Does the module block cancellations?
No. This is an audit log, not enforcement. A cashier with permission to void a line can still do it; the act is just recorded. If you need enforcement (require manager-PIN before a void above $X), that's a separate Arure module on the roadmap (`pos_order_cancel`).
What if a cashier just trims a typed digit, not the whole line?
No log entry. The numpad patch detects whether the typed buffer is empty before logging — so trimming a digit (e.g. typed "23", pressed backspace, buffer becomes "2") does not log. Only line removals where quantity > 0 produce an audit row. The v11 ancestor logged every backspace including no-ops; v19 fixes that.
Can a cashier delete an audit entry to cover their tracks?
No. The POS User group has read-only access to the audit table. Only POS Manager can edit or delete entries — and the deletion event is itself recorded in the chatter. So even a manager covering tracks leaves a trail.
Restaurant mode — does it capture the table?
Yes. If the POS is configured in restaurant mode and the order is at a table, the table name is captured. For non-restaurant POS, `table_name` is empty and the column hides itself by default in the list view (you can re-enable it via the column-toggle).
Does it slow down the POS?
No. The audit-log RPC fires asynchronously — the cashier's UI doesn't wait for the server to acknowledge. RPC failures are swallowed to console so a slow audit-log writer can never freeze the POS during a busy lunch rush.
Multi-shop — can I see per-shop reports?
Yes. Every entry stores `config_id` (the shop). Group by shop for a per-outlet roll-up; filter by shop to scope a manager's view to their own outlet. Stored field, not computed — queries are fast even on large audit tables.
Will it work alongside other POS modules?
In most cases yes. Both JS hooks use the standard Owl `patch()` mechanism, which composes with other patches. If another module also patches `Numpad.onClick` or `PosStore.removeOrder`, both patches fire in load order. We test against a clean Odoo 19 install; conflicts with specific other modules can be reported and we'll publish a coexistence note.
I bought the v11 module ($50). Do I need to re-buy?
Yes — this is a separate App Store listing for Odoo 19, not an upgrade of the v11 listing. Email `support@arure.tech` with your v11 purchase reference and we'll apply a returning-buyer discount to your v19 purchase.
Does it survive Odoo upgrades?
The Owl POS surface changes between Odoo minor versions, so the JS patches occasionally need re-targeting. We re-patch within 5 business days of any reproducible breakage on a current Odoo 19.x release. Bug fixes and security patches committed for 12 months after Odoo 21 ships.
Will this work on Odoo Online (SaaS)?
No. Per Odoo's policy, third-party paid apps cannot be installed on Odoo Online. This module runs on Odoo.sh and on-premise (self-hosted Community or Enterprise) deployments.
Evaluate before you commit. Buy when you're confident.
90-day refund window. Reach us through any channel below — we reply within 1 business day.
WhatsApp
+1 858 463 4405
Quick questions, same-business-day reply.
More from Arure Technologies
What's New
Highlights from the most recent releases. The full CHANGELOG.md is included inside the module package.
v19.0.1.0.02026-05-09Latest · Initial v19 port
Port from v11.0.1.1 with model + frontend rewrite
Added vs. v11 ancestor
- Chatter on every cancellation entry — managers can attach context post-hoc.
- Per-shop reporting via stored `config_id` field.
- Selection field for `reason` (drop_line / drop_order / manager_void / refund / other) replacing free-text Char.
- Restaurant-mode `table_name` capture works on both classic and Owl POS.
Improved
- POS User group is now read-only on the audit table (was full CRUD in v11 — defeated the audit purpose).
- Numpad backspace patch correctly skips no-op trims (v11 logged every backspace press, padding the audit table with junk rows).
- Drop-order JS patches at the store level (`PosStore.removeOrder`) to catch every code path that destroys an order, not just one button.
- Quantity stored as `Float` (was `Char` in v11 — a long-standing field-naming bug).
Quality & safety
- Audit-log RPC is fire-and-forget; failures swallowed to console so the cashier flow can never freeze on a slow audit-log writer.
- Selection values defensively validated server-side — never trust raw frontend input.
- Smoke-test checklist included in the module package as
SANDBOX_SMOKE_TEST.md.
License
Odoo Proprietary License (OPL-1). Per-database license. Source code included; not redistributable.
Trademarks
Odoo is a registered trademark of Odoo S.A. This module is an independent extension developed by Arure Technologies and is not affiliated with, endorsed by, or sponsored by Odoo S.A.
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