Change Logger
Who changed what, on which document and when — on one screen
A log that records the changes you choose to watch on any Odoo model: sales, purchases, invoices, transfers. It stores the user, the document and the values, and is searched by person and date instead of one record at a time.
How you get it
Every development works in all three Odoo environments. The only thing that changes is how we deliver it.
Odoo Online (SaaS)
You do not need the ability to install modules. A Millora consultant comes in with temporary access that you authorize and implements it with Odoo Studio. When they are done, you revoke the access.
Odoo.sh or your own server
You receive the module and the installation guide by email as soon as payment clears. Install it yourself, or we install it with you.
Installation · shell
# 1 · copia el módulo a tu addons_path
cp -r millora_logger /mnt/extra-addons/
# 2 · reinicia y actualiza la lista de apps
odoo-bin -u all -d tu_base --stop-after-init
# 3 · instala desde Apps
# busca "Change Logger"What it solves
The problem
When somebody asks "who changed this?", the answer in Odoo almost always arrives late.
Each document's chatter keeps something, but it is scattered: you open the record, dig through the messages, and even then you only see what Odoo decided to track. A price that moved, an invoice date that shifted, a transfer that changed warehouse — often there is no readable trace. And when the question is broader — "what did this person do on Tuesday?" — there is nowhere to look, because a user's activity does not live on any screen.
How it works
Two pieces answering two different questions.
The log stores one line per change you choose to watch: what was modified, on which model, by whom, when, and with which values. It is fed by automations configured on the models you care about — sales orders, purchase orders, invoices, transfers, or any other, including ones you built yourself — listening to the fields you care about.
Deciding what to watch is exactly what makes it useful. A log that records everything is as unreadable as no log at all; this one records what you defined.
And the detail is not a technical dump. Each event is written when it is configured, in business language: "Document X was modified. Customer, date, total, number of lines". Whoever reads it does not need to know what the fields are called underneath.
The list filters and groups by user, model, company and date, and respects the separation between companies. It is not typed by hand: the views do not allow creating or editing entries.
The user search answers the other question. You pick a person, a date range and a company, and get a table of every activity Odoo recorded under their name in the chatter: date, application, document and a button that opens the record directly. It reconstructs a working day without knowing in advance where to look.
What is included
The price covers configuring the log on four models, with the fields you choose on each and the wording that describes every event. Each additional model is quoted separately.
What it does not do
Better said up front. It does not undo changes: it is a record, not version control. It does not replace permissions: it leaves a trace of what happened, it does not stop it from happening. It logs modifications, not reads. It is not a tamper-proof log — an administrator with Settings rights can delete lines — so it serves internal audit, not forensic evidence. And the user search returns up to a thousand events per query: for long periods, narrow the range.
What changes
"Who changed this?" stops being an investigation and becomes a thirty-second search. On teams where several people touch the same document — sales adjusting a price, accounting fixing a date, the warehouse changing a destination — the argument about what happened ends, because the line is right there with the name and the timestamp.
What's included
- Records changes to the fields you choose, on any Odoo model, standard or custom
- Stores the user, the document, the date and the values behind every modification
- Describes each event with wording you define, in business language rather than field names
- Filters and groups the log by user, model, company and date from the list itself
- Looks up one person's activity over a date range, with a button that opens each document
- Keeps the log separated by company: each user sees only the companies they can access
- Blocks creating or editing log entries by hand from the interface
- Includes configuration on four models; each additional model is quoted separately
- Built with Odoo's own tooling, with no code and no external libraries
Requirements
- Deciding which models and fields to watch. That decision is what makes the log useful and is made with you
- On Odoo Online, the Studio app active: it is what allows creating the models and the automations
- A user with Settings rights to configure and maintain the automations
- Nothing else. No external libraries and no third-party modules
You might also need
Company Color Bar
Know which company you're in at a glance
Administration
User Profiles
Permissions defined by role, not by person
Administration
Payment Allocator
You decide how much goes to each invoice, not the order of the list
Accounting & tax