counted_quantity_widget

A physical inventory asks a warehouse to walk the shelves and write down what is there. The awkward case is zero: a line where somebody looked and found nothing is completely different from a line nobody has reached yet, and both would be a zero in a plain number field.

Odoo solves that with a companion flag on the quant, set when a count is genuinely entered. This widget is what sets it. When the user types a value and commits it, the widget writes the quantity and the flag together, so the record carries both the number and the fact that somebody produced it.

The display follows the same distinction. A read-only cell with no value and no flag renders empty rather than as zero, so an inventory in progress shows at a glance which lines have been counted and which have not.

This is the difference between an inventory you can act on and one you cannot. Adjusting stock to zero because nobody visited that aisle is an expensive mistake, and it is invisible if the interface shows the same zero either way.

The Odoo 19 change matters operationally. In Odoo 18 the counted flag was set as soon as the user typed a character, so tabbing through a list and touching a cell without changing it marked the line as counted. On a large count that quietly converts unvisited lines into confirmed zeros. Odoo 19 defers the flag until a value is actually committed.

The keyboard handling is worth mentioning to anyone running a count: Enter and Tab both commit, so a counter can work down a list without touching the mouse, which is how counts are actually done.

The core usage

<field name="inventory_quantity"
       widget="counted_quantity_widget"/>

No options. The companion flag is written automatically alongside the value.

The companion field it writes

# on the quant, written by literal name
inventory_quantity_set
# true once a count is committed

The same field drives the blank display in read-only mode.

Formatting the number

<field name="inventory_quantity"
       widget="counted_quantity_widget"
       options="{'digits': [16, 2]}"/>

Inherited from the decimal field, and unaffected by the counted-flag behavior.

The source opens with a comment explaining why the widget exists in this shape: the standard input hook does not let it override the input and change handling it needs, so it installs its own listeners on the numeric input for input, keydown and blur, and removes them when the element goes away.

Those three handlers implement one rule between them. Typing sets a local flag saying the field has been touched. Blurring commits only if that local flag is set, then clears it. Pressing Enter, Tab or Shift+Tab commits and re-arms, so continuing to type in the next cell behaves the same way.

Committing parses the typed value and writes both the quantity and the counted flag in a single record update, with the parse wrapped so an unparseable entry is ignored here and handled by the normal validation path instead.

The display rule is a small override on the formatted value: when the field is read-only and both the value and the counted flag are falsy, it returns an empty string. Worth noting for anyone reading the code, the condition uses a bitwise operator between the two negations rather than a logical one; it evaluates the same way here, since both operands are booleans, but it is not the operator you would expect.

The Odoo 18 version wrote the counted flag directly from the input handler, on the first keystroke. That is the behavior Odoo 19 replaced with the local flag, and it is the single most consequential change in this widget's history.

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.

Same rules, newer plumbing. The commit-on-blur behavior, the paired write of quantity and flag, and the blank display for uncounted lines are all unchanged. The listener and state handling move to the newer helpers, which affects code that patches the widget rather than views.