| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 72 |
| Technical Name |
field_audit_logger |
| License | LGPL-3 |
| Website | https://github.com/mypacksoft/field_audit_logger |
| Versions | 16.0 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 72 |
| Technical Name |
field_audit_logger |
| License | LGPL-3 |
| Website | https://github.com/mypacksoft/field_audit_logger |
| Versions | 16.0 17.0 18.0 19.0 |
Critical Field Change Logger
Log every field change with user, timestamp, and old value
Starts at 1.99 USD
You configure which fields to track. Odoo logs every change with the user name, timestamp, old value, and new value. No custom development. No database overhead.
Sales manager changed a discount from 15% to 22% on invoice INV-2401? You see it. Warehouse lead reset a delivery date? You see it. Compliance officer needs proof nobody touched the regulatory checkbox? You export the log in two clicks.
You pick the models and fields during install. The addon starts recording. When someone edits a tracked field, the log updates. You search by user, date range, or record. You export to CSV for audits.
Works on sales orders, invoices, purchase orders, inventory moves, partners, products â any Odoo model. One install covers your entire database. Your compliance team gets the trail they need. Your IT team spends zero hours building it.
See it in action
What you get
- Track any field on any model without code
- See user, timestamp, old value, new value per change
- Export logs to CSV for audits or disputes
- Configure once during install, logs run forever
- Search by user, date, or record in seconds
Compatibility
Odoo 18 · License: LGPL-3 · Category: Tools
Installation
- Copy the
field_audit_loggerfolder into your Odoo addons path. - Restart your Odoo server.
- Activate developer mode and click Update Apps List.
- Search for Critical Field Change Logger and click Install.
Support
Open an issue on the GitHub repository â we triage every report within two business days.
Please log in to comment on this module