lna_checklist

Local network access is how a secure Odoo page is allowed to talk to hardware sitting on the shop's own network. Getting it working is a sequence of environment steps rather than Odoo settings: browser flags, certificates, addresses.

This widget is the checklist for that sequence. It sits on the Point of Sale configuration and lets whoever is doing the setup tick items off as they go.

What is unusual is where the ticks live. They are not a field on the record; they are kept in the browser's own storage, so they follow the machine rather than the database.

The checklist is a support artifact more than a business feature. Its value is that a partial setup is visible: someone returning to a half-finished job can see where they stopped.

The limitation follows directly from the storage choice. Because the ticks are per browser, they are a personal working note, not a record of what was configured. For anything that needs to be auditable, a field on the configuration is the right home.

Placing it

<widget name="lna_checklist"/>

No attributes. It reads and writes browser storage.

Where the ticks live

localStorage["pos_lna_checklist"]
# a JSON object of item id to boolean

Per browser, not per database.

When they are written

# on save, before the record's own save runs

Ticking alone does not persist them.

Three lifecycle hooks do the work, and the middle one is the interesting part.

Before the first render, the stored value is read and parsed. The parse is wrapped so that anything unreadable produces an empty checklist rather than an error, which matters because browser storage can hold whatever a previous version wrote.

On mount, the widget replaces the record's save method with its own function. That function writes the current ticks to storage and then calls the original save with the same arguments. It is a deliberate patch of another object's method, which is unusual in Odoo and worth recognizing when reading the file.

On unmount, the original save is restored. Without that, the wrapper would persist on the record after the widget was gone, holding a reference to state that no longer exists.

The ticks themselves are a plain object keyed by the element identifier of each checkbox, which means the checklist items are defined in the template rather than anywhere in this file.

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.

Converted to the newer state convention. The development branch swaps the state hook for its Owl 3 equivalent. The storage key, the save patch and the restore on unmount are unchanged.