sol_o2m

A quotation's lines are the most heavily worked table in Odoo. They carry products, sections, notes, quantities, discounts and taxes, and since Odoo 19 they also carry combos: a single sellable thing made of several products the customer chooses between.

A combo is awkward to represent in a flat list. It is one line from the customer's point of view and several rows in the database, and the rows underneath the combo are not independently editable, sortable or deletable. This widget is what makes that work.

It builds on the shared document line list that invoices and purchase orders also use, so sections, notes, drag ordering and product labels all behave the same way. What it adds is combo awareness: the styling that makes a combo read as a group header, the locking of its items, the group-wise reordering and the totals shown on the combo row.

Combos exist to sell a bundle without pretending it is one product. The customer picks a size, a color or a plan; the order still shows what they picked, and the pricing still adds up per item. That only works if the interface treats the group as a unit, which is what this widget provides.

The behavior to brief a sales team on is the locking. Inside a combo, only the description, the taxes and the delivered quantity are editable. Everything else, including quantity and price on the items, is controlled by the combo and its configurator. Users who try to edit an item price directly will find the cell inert, and the answer is to change the combo, not the row.

The second thing worth knowing is that combo totals shown on the header row are computed in the browser by summing the item rows. They are a display convenience, not a stored value, so they follow whatever is currently in the list rather than what the server last calculated.

The core usage, trimmed

<field name="order_line" widget="sol_o2m"
       mode="list,kanban">
  <list editable="bottom">
    <field name="sequence" widget="handle"/>
    <field name="product_template_id" widget="sol_product_many2one"/>
    <field name="name" widget="sol_text"/>
  </list>
</field>

The widget expects its companion cell widgets: the product picker and the label text field are part of the same design.

Aggregated columns on combo rows

<field name="order_line" widget="sol_o2m"
       aggregated_fields="price_subtotal"/>

The attribute is inherited from the shared section list. Fields named here are summed across a combo's items and shown on the combo row.

The two product columns

<field name="product_template_id" optional="show"/>
<field name="product_id" optional="hide"/>

Enabling the variant column automatically removes the template column, so users never see both at once.

The combo grouping is worked out by walking the list rather than by reading a relation. From a combo row the widget walks forward, collecting rows while they carry a combo item link pointing back at that combo, and stops at the first row that does not. From an item row it walks backward until it finds the combo it belongs to. Both directions handle unsaved rows by matching on the temporary identifier as well as the database one.

That walk is what powers everything else. Reordering a combo swaps the whole collected group against whatever is above or below it, and the neighbour is itself collected as a group if it turns out to be part of one, so a combo never lands in the middle of another. Dragging is disabled on those rows precisely because the drag would move a single row out of its group.

The locking is a straightforward override: a cell on an item row is read-only unless its column is the description, the taxes or the delivered quantity. Everything else, including price and quantity, is owned by the combo.

The totals on a combo row are computed by summing the item rows for each aggregated column and formatting the result with the column's own formatter. The widget also has to opt those cells into being formatted at all, because the combo row is otherwise treated as a section header, and section headers do not normally print values.

Deleting has a small but important extra step: before removing a combo row, the widget clears the stored selection of combo items on that record. Without it, a subsequently re-added combo would open its configurator with the previous selection.

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.

The widget survives, its companion cell does not. The order line label column moves from sol_text to a new widget in its own file, and the old name is no longer registered. A custom order line view still naming the old cell widget will silently fall back to the plain text field.

Internals move. The file imports the shared section record helper and the command helpers from their new locations, and adds a field specification helper, which suggests the combo handling is being reworked around explicit field loading rather than walking the loaded list.