stat_info

Odoo stat buttons are the row of counters at the top of a form: Invoices, Tasks, Meetings. Each one is a <button> with the stat button class, and the number inside it is usually a field rendered with the statinfo widget.

One core view writes something slightly different. In the eLearning quiz module, the Go to Quiz stat button carries a widget="stat_info" attribute, with an underscore, directly on the button element. That name is not registered anywhere in Odoo, and buttons are compiled by the view compiler without any lookup into the field widget registry.

So the attribute is doubly inert: the name does not exist, and the element it sits on would not use it if it did. The button renders as a normal stat button with its label and icon, which is what it was going to do anyway.

The reason this page exists is that the name reads as meaningful. Someone searching Odoo's views for how stat buttons are built will find it and reasonably assume that is how you make a stat button display something. Copying it produces no error, no warning and no effect, and the misunderstanding can persist for a long time because nothing visibly fails.

It is also a good example of a general habit worth having in custom Odoo work. Widget names are strings, and a misspelled one is not a syntax error. On a field, a wrong widget name at least logs a console warning and falls back by type. On a button, there is no warning at all, because nothing was ever going to read it.

The practical takeaway: audit your custom views for widget attributes on non-field elements. They are always dead, and they usually mark a place where somebody expected behavior that never arrived.

The one core usage

<button name="action_view_quiz" type="object"
        class="oe_stat_button" string="Go to Quiz"
        icon="fa-question-circle" widget="stat_info"
        invisible="not quiz_id"/>

Identical in Odoo 16 through 19. Removing the widget attribute changes nothing.

What a counting stat button looks like

<button name="action_view_invoices" type="object"
        class="oe_stat_button" icon="fa-pencil">
  <field name="invoice_count" widget="statinfo"
         string="Invoices"/>
</button>

This is the pattern people are usually looking for. The widget goes on the inner field, and the name has no underscore.

A label-only stat button

<button name="action_open" type="object"
        class="oe_stat_button" icon="fa-cog"
        string="Settings"/>

No field, no widget, no counter. This is what the quiz button is, once you ignore the inert attribute.

Two separate mechanisms have to fail for a widget name to do nothing, and here both do.

The first is registration. Odoo resolves a widget name against the fields registry, and when it cannot find one it logs a console warning and falls back to the widget registered for the field's type. We searched the whole Odoo 19 source for any registration of this name and found none, then repeated the search on the 16, 17 and 18 branches with the same result.

The second is the element. That fallback only applies to <field> elements. A <button> is compiled through a different path that reads its name, type, string, icon, class and visibility, and never touches the field registry. So on a button the attribute is not even wrong, it is simply not read, which is why there is no console warning either.

The likely history is a copy from a stat button that did have an inner field, with the widget attribute surviving the deletion of the field it belonged to. That is the ordinary way this kind of leftover appears, and it is worth recognizing because a custom module can carry the same thing for years without a symptom.

The intended widget, statinfo, is a real field widget in the web module and one of the most used in Odoo. It renders a value with a label beneath it, sized for the button box, and it is used 197 times across core.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The development branch is unstable and this may still change; we re-verify the page after release.

Still there, still unregistered. Unlike some other leftovers being cleaned up in this cycle, the attribute survives on the development branch. The only change to that button is its icon, which moves to Odoo's newer icon set. There is still no registration under this name anywhere.