percentage

Percentages have a storage convention problem: is 15% stored as 15 or as 0.15? Odoo core answers firmly, the fraction, and this widget is the translation layer that lets humans keep thinking in percent. The formatter multiplies by 100 and appends the symbol for display; the parser divides typed input back down; and while the field is being edited the symbol is dropped so users type against a clean number, all visible in the source's formatPercentage and parsePercentage wiring.

Decimals follow the digits setting, which, like a couple of other formatting widgets, the source accepts from either an option or an attribute, with its own comment admitting the duplication.

The fraction convention is not pedantry; it is what keeps computed money right. A margin stored as 0.15 multiplies straight into amount * margin; stored as 15 it silently produces numbers a hundred times off the first time someone forgets the /100. Adopting this widget is really adopting the convention, and the payoff is that discounts, probabilities and rates all compose the same way across your models and reports.

The trap to brief your team on is imports and integrations: a spreadsheet column saying 15 loaded into a fraction field means 1500%. The widget can only translate at the UI; pipelines must respect the storage convention themselves.

Studio applies this widget without code.

1. Open the view in Studio and select the float field.

2. In Properties, set Widget to Percentage.

Decimal precision via digits is the XML step, and so is the judgment call the widget cannot make for you: whether the field's existing data already follows the fraction convention. Switching the widget on a field storing whole percents shows 1500% and needs a data migration first.

A margin field

margin = fields.Float(string="Margin")  # stores 0.15 for 15%

<field name="margin" widget="percentage"/>

One decimal place

<field name="probability" widget="percentage"
       options="{'digits': [16, 1]}"/>

Displays 12.5%. The same value can be given as digits="[16, 1]" on the element; the attribute takes precedence when both exist.

Computed money staying honest

commission = fields.Monetary(compute="_compute_commission")

def _compute_commission(self):
    for rec in self:
        rec.commission = rec.amount_total * rec.margin  # fraction: no /100

The whole widget is one convention applied in three places, and the places are worth naming because that is where bugs hide.

Display multiplies by 100 and appends %. Editing shows the percent number without the symbol, so what users type is what they mean. Parsing divides back to the fraction on save. UI round-trips are therefore lossless at the displayed precision.

Everything outside the UI bypasses all three: imports, XML-RPC writes, SQL, server actions. Whatever writes 15 into the field has written fifteen hundred percent, and the widget will faithfully display it as such. When a percentage looks absurd, the first question is which pipeline wrote the value raw.

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.

Nothing changes for this widget. Same types, same digits handling, same formatter behavior. Internal syntax moves to the new Owl props system, affecting JavaScript patches only. We re-verify once Odoo 20 ships.