loyalty_data_field

Loyalty on a sale order is a computed picture: how many points this order earns, what the customer already has, which rewards are within reach. None of it is a field the user edits, and all of it depends on program rules that live on the server.

This widget is the panel that shows it. The server computes a structured summary into a field, and the widget unwraps that value and hands it to a template that lays out the figures.

There is nothing else to it. No options, no interaction, no supported types declared. It is the thinnest kind of Odoo widget: a component and a template over a server-computed value.

Loyalty only changes behavior if the person taking the order can see it. A salesperson who knows the customer is forty points from a reward can say so; one who would have to open another screen will not. Putting the summary on the order is the whole mechanism by which a program influences a sale.

The planning point is the widget's fate. It is absent from the development branch, which means the loyalty summary on the sale order is being reworked. If your process or training depends on that panel, that is a change to check before upgrading rather than a rename to follow.

The usual usage

<field name="loyalty_data"
       widget="loyalty_data_field"/>

No options. What appears is entirely the server's computation.

When nothing shows

# an empty summary renders nothing
{}

The widget treats an empty structure as absent, so the panel does not appear on orders with no loyalty context.

A generic alternative

<field name="loyalty_summary_html" widget="html"/>

Computing the panel as markup server side needs no JavaScript at all.

There is one method. Before each render the widget reads the field's value, checks whether it has any keys, and if so unwraps it out of the reactive proxy the framework wraps record data in, storing the plain object for the template.

Doing that before every render rather than once at startup means the panel follows a recomputed summary, which matters on an order where adding a line changes the points earned.

The emptiness check is the other detail. An object with no keys becomes a falsy value, so the template can hide the whole block rather than rendering an empty panel with headings and no figures.

Everything visible, the labels, the layout and which parts of the summary are shown, belongs to the template and to the server-side computation. The widget contributes the unwrapping and nothing more, which is why its removal in the next version says more about the surrounding feature than about the widget.

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 this page after the release.

The widget is removed. There is no registration under this name on the development branch and the file is absent, which means the loyalty summary on the sale order is being reworked rather than renamed.

Because an unknown widget name falls back to the field's type, a custom view still naming it would render the raw structured value instead of the panel. Search custom sales views for this name before upgrading.