statinfo

Every Odoo form with smart buttons across the top, the row of boxes showing things like 2 Delivery or 1 Invoices, is using statinfo. The widget renders a field's value in large type with a small label underneath, inside a <button> element that navigates somewhere when clicked.

Two things make it unusual among display widgets. First, its type list: it accepts float, integer, monetary, char, one2many and many2one, so the same widget shows a count, an amount, or a name. Second, it never renders alone. It only makes sense inside a button in a form view's button box, and the value it shows is almost always a computed count field on the model, such as invoice_count.

Worth knowing: the widget formats its value with the standard formatter for the field's type. A one2many shows its record count, a monetary formats with the currency, a char prints as-is. That is read straight from the source, which picks the formatter from the registry by field type.

Smart buttons are the navigation your team actually uses. Nobody browses from a customer to their invoices through the menu; they click the Invoices button on the customer form. Every one of those buttons is a statinfo widget over a computed count.

That makes this widget the cheapest UX win in most Odoo customizations. When your operations lead asks "can I see how many open tickets this customer has without leaving the form", the answer is a computed field plus a statinfo button, a one-hour change that saves a lookup dozens of times a day. The pattern scales: counts of deliveries, running totals of purchases, hours logged, anything the model can compute can sit in the button box.

The discipline that matters is restraint. Forms with ten smart buttons stop being navigation and start being noise. Our rule on implementations is to show the three or four numbers a user of that form checks daily, and move the rest to list views and dashboards.

Studio never asks you to pick statinfo by name. It applies it automatically when you create a smart button.

1. Open the form in Studio.

2. Click the + in the button box (top-right area of the form) or choose Add Smart Button.

3. Pick the related model and the action the button should open, for example the list of this customer's projects.

4. Studio creates the computed count field on the model and the button XML around it, with statinfo as the display widget.

Studio builds the standard case: a count of related records opening a filtered list. Three common variations need XML.

A dynamic label, such as showing the related partner's name under the number, needs the label_field option.

Controlling decimals on a float or monetary stat, for example forcing one decimal on a hours total, needs the digits option or attribute.

A second value in the same button, the pattern account uses to show amounts alongside counts, is hand-written XML with multiple fields inside one button.

The standard smart button

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

The model side is a computed integer:

invoice_count = fields.Integer(compute="_compute_invoice_count")

def _compute_invoice_count(self):
    for rec in self:
        rec.invoice_count = len(rec.invoice_ids)

Dynamic label from another field

<field name="total_hours" widget="statinfo"
       options="{'label_field': 'stage_label'}"/>

The label under the number now comes from the stage_label char field on the record, so it can change with the record's state.

Controlling decimals

<field name="hours_spent" widget="statinfo" digits="[16, 1]"/>

One decimal place on the stat. The same value can be passed as options="{'digits': [16, 1]}"; both routes reach the formatter.

Number only, no label

<field name="ticket_count" widget="statinfo" nolabel="1"/>

The widget itself does not make the button clickable, count anything, or open anything. Those three jobs belong to three other pieces, and confusing them is the root of most statinfo questions.

The count is the model's job. statinfo displays whatever value the field holds. A wrong count is a bug in the compute method, not in the widget.

The click is the button's job. The surrounding <button> element's name and type decide what opens. A common mistake is putting the field outside a button and wondering why nothing is clickable.

The look is the class's job. The oe_stat_button class on the button gives the box styling; without it you get a bare number floating in the form.

One more source-level detail: isEmpty is hardcoded to false, which means statinfo always renders even when the value is zero. A smart button showing 0 Claims is intentional Odoo behavior; hiding zero-count buttons needs an invisible condition on the button element.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The changes below are read from the public development branch and are not final until release.

One new option appears: hide_trailing_zeros, a boolean that trims zeros to the right of the last significant decimal, so 1.20 renders as 1.2. It matches the option of the same name on the monetary widget, bringing the two formatters in line.

No options are removed and the registration name is unchanged, so existing views should carry over untouched. We re-verify this page against the shipped release before updating the option table.