Audit Trail Check

The answer is decided long before anybody asks

Somebody asks who changed a price, or when a customer's payment terms were last touched. Whether Odoo can answer was settled months earlier, and almost nobody knows which way.

Odoo does keep a change history — for the fields its own developers marked as tracked, and only on models that carry a chatter. Both conditions have to hold.

Per model: how many stored fields, how many are marked tracked, how many actually record — and which are marked but silent.

Most of it is not covered, and the number is the point

On a stock database the four models most people care about carry a little over two hundred stored fields between them, and around twenty are tracked. The rest change with no record of who changed them or what they were before.

That ratio is not a criticism of Odoo — tracking everything would be expensive and mostly noise. It is worth knowing the number before somebody asks a question the database cannot answer.

And the trap, where it applies

A field marked as tracked on a model with no chatter records nothing at all. A stock database has none of these; they turn up where somebody has added tracking to a custom model, or to one never built for it. The setting is there, it reads correctly, and nothing is being written down — so the check reports them separately and sorts them to the top.