integer

The integer widget is the input Odoo mounts automatically on every whole-number field, which is why explicit widget="integer" is rare in core views: the two occurrences that exist are pivot measures forcing a count back to plain integer rendering where another widget would otherwise apply. In readonly it prints the formatted value; in edit it renders a text input with inputmode="numeric", which brings up the number keypad on phones without the quirks of a native number input.

Formatting follows the user's language: thousands separators and digit grouping come from the locale, and can be disabled per field. Parsing is forgiving, accepting the localized format back, and since Odoo 19 also accepts arithmetic.

Whole numbers carry more configuration weight than they look. Inventory counts on a warehouse dashboard read faster with separators on; reference numbers like a year or an external id must have them off, 2,026 being wrong in every sense; and analytics screens full of large counters benefit from the compact human-readable form. All three are one option away on the same widget, so the choice is a view decision, not a data one.

The 19.0 typed-math addition is a real floor-level productivity feature: a stock clerk correcting a count can type +=12 instead of doing mental arithmetic, and the widget applies it on confirm. It works anywhere the integer widget edits, lists included, and needs no configuration.

Odoo Studio, available on Enterprise plans, handles the field itself without code.

1. Open the view you want to change and click Studio in the top menu.

2. From the Add a field panel, drag Integer where you want it. Studio creates the database column immediately.

3. In the field's Properties, set the label, default value, and whether the field is required.

4. To display it differently, change Widget to Percentage Pie or Progress Bar; leaving it on the default keeps this widget.

Tip: turn on developer mode before adding the field to control its technical name; Studio otherwise generates one like x_studio_integer_field_1 that reports and integrations then depend on.

Studio's properties panel covers label, default, and visibility, but not this widget's formatting knobs. Disabling the thousands separator with enable_formatting, compacting large values with human_readable, switching to a native number input, or bounding the spinner with the undocumented min and max all require editing the view XML, which is developer territory. If a report-critical number renders with the wrong grouping, that one-line options change is the fix, not a new field.

Reference numbers: kill the separator

<field name="fiscal_year" options="{'enable_formatting': False}"/>

Renders 2026, not 2,026. No widget attribute needed since integer is the default.

Big counters, compact display

<field name="page_views"
       options="{'human_readable': True, 'decimals': 1}"/>

Shows 1.2M until the user clicks in, then the exact value for editing. decimals only affects the compact form.

Native number input with bounds

<field name="priority_level"
       options="{'type': 'number', 'min': 1, 'max': 10, 'step': 1}"/>

Spinner arrows step by 1 and the browser blocks values outside 1 to 10. Note that formatting is disabled while editing in this mode.

Forcing integer rendering on a pivot measure

<field name="number_of_calls" type="measure" widget="integer"/>

The im_livechat analytics pivot does exactly this, one of only two explicit uses in core.

Odoo 19 changed the widget in three ways that do not appear in any release notes. First, the parser now runs with allowOperation, enabling the relative math syntax: an entry like +=10 is parsed as an operation against the current value and applied when the edit is confirmed. Second, empty values are handled explicitly: a false value renders as an empty string in the unformatted paths where earlier versions could leak false into the input. Third, the placeholder attribute is gone. Through Odoo 18, extractProps read attrs.placeholder and the template rendered it; in 19 both ends were removed, so a placeholder on an integer field is silently ignored. If a form relied on placeholder text as a hint, move it to the label, a tooltip, or a placeholder_field-capable widget like char.

One more subtlety worth knowing: human_readable formatting is suspended while the input has focus, using internal focus state, so users always edit the exact number. The compact form is a display skin, never the stored value.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The development branch is unstable and these notes are provisional until release, when this page is re-verified.

For this widget the branch shows a pure internals migration: props move to the new Owl typing API with an exported integerFieldProps object, and state and refs move to proxy and signal.ref. The option list, the undocumented min and max, the typed-math parsing, and the absent placeholder are all unchanged at the time of writing.