loyalty_one2many

The loyalty_one2many widget renders the Rules and Rewards sections of a loyalty program form: the conditional rules that earn points and the rewards points can buy. Under the hood it is a thirteen line file: a component extending the standard X2ManyField with a replacement template, and a descriptor spreading the standard x2ManyField unchanged.

The template inherit does one thing: where the base x2many shows its control panel buttons, this widget renders an <h4> carrying the field's label, then the button area with a single secondary Add button wired to the standard add flow. That is why each block on the program form reads as a titled card with its own Add action even though the field itself has nolabel="1".

For marketing and sales teams the payoff is readability: a loyalty program is really two lists, what earns points and what spends them, and this widget gives each list a heading and an unmissable Add button inside the form body. Program managers add buy X get Y rules, promo code conditions or gift card rewards without hunting for the tiny inline add link a plain kanban sub view would offer.

Because the descriptor is the stock x2many, administrators keep all the usual control: crud options can forbid deleting rules on running programs, and record rules apply unchanged. The widget adds presentation, not policy.

<!-- Core usage on the loyalty program form (loyalty module) -->
<field name="rule_ids" colspan="2" mode="kanban" nolabel="1" add-label="Add a rule"
       class="o_loyalty_kanban_inline" widget="loyalty_one2many"
       context="{'currency_symbol': currency_symbol, 'program_type': program_type}"/>

The context keys are consumed by the rule and reward sub views and dialogs, which adapt wording and defaults to the program type; the widget itself passes them through untouched.

The interesting engineering fact is how little there is. The registration has survived four major versions with only cosmetic edits: Odoo 16 registered the bare component class, 17 switched to the descriptor spread pattern, 18 reformatted the class body, and 19 dropped the module pragma. No behavioral line has changed since 16, making this one of the most stable custom widgets in core.

One detail worth knowing when restyling: the heading uses the field's string, so relabeling the field in the view (or via Studio's label edit on the field) renames the card heading too. And since the template only replaces the control panel buttons block, everything else, pager, kanban quick add, dialog flows, is rendered by the base x2many machinery documented on our one2many page.

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.

The development branch file is byte-identical to Odoo 19.0: no new options, no template change, no rename. Whatever Odoo 20 changes in loyalty, it is not this widget. We re-verify after the release.