Odoo 19 documentation describes an integration between Point of Sale and Pricer electronic shelf labels. Odoo can send the product name, price, barcode and taxes to those labels, then trigger another synchronisation after a change.
For a Belgian or French retailer, the value goes beyond removing paper printing. The real challenge is preventing the shelf price, promotional price and amount charged from drifting apart. The integration removes some rekeying, but it does not replace price governance or operational controls.
How the Odoo–Pricer integration works
The account, stores and transceivers are configured in Pricer first. In Odoo, each Pricer store maps to a separate record. Labels are then linked to product variants, preferably by scanning their identifiers to reduce manual-entry mistakes.
Odoo documents an automatic synchronisation every twelve hours when a product name, price, barcode, customer tax, currency, store or label association changes. Two manual commands can update the affected labels or force an update of the entire label estate.
The critical caveat: displaying a promotion does not apply it at checkout
A pricelist can feed the promotional amount shown on a label, including the crossed-out old price and the new price. However, Odoo explicitly states that this association changes only the display: scanning the product in Point of Sale does not automatically apply the discount. Checkout pricing must be configured and tested separately.
Odoo also states that quantity discounts and pricelists derived from other pricelists are not supported for this promotional display. Before a campaign, teams must compare the intended commercial mechanism with the integration's actual limits.
What should business and IT teams verify?
One controlled price master
Teams must establish who creates, approves, schedules and retires a price or promotion. If headquarters, eCommerce, stores and an external interface can all change prices, electronic labels will also propagate mistakes faster. Taxes and currencies need particular attention in multi-company or cross-border environments.
A controlled physical mapping
A label identifier must point to the correct variant and store. Odoo recommends piloting one product before a broader rollout. Operations should also cover replacement labels, shelf moves and checks for orphaned associations.
An incident procedure
The documentation includes an essential nuance: when a request to Pricer fails, Odoo may still consider the product updated. Operations must monitor the last transmission status and provide for a full update after an incident. A “sent” status should not be confused with visual proof of the shelf price.
Underside analysis: manage price as a control chain
We recommend modelling four separate states: the approved price in Odoo, the price transmitted to Pricer, the price actually displayed and the price applied at checkout. The pilot must do more than display a value: it should prove that these four states agree during a normal change, a promotion and a network incident.
Start with one store, one product family and a simple pricing scenario. Measure delays, mapping errors, failed synchronisations and checkout discrepancies. This evidence helps decide whether standard configuration is sufficient or whether additional monitoring, integration or automated controls are justified.
Checklist before rollout
- Name the business owner for pricing and the incident-recovery owner.
- Map Odoo stores, Pricer stores, currencies, taxes and variants.
- Test one label and one product before any bulk import or association.
- Verify regular price, promotion, promotion expiry, tax change and return to the original price.
- Compare the label with the receipt for every scenario.
- Monitor update statuses and document the full-resynchronisation command.
- Test business continuity when Pricer or the network is unavailable.
- Train store teams to report discrepancies without editing several systems directly.
This work complements the design of Odoo Point of Sale and the governance of product and inventory master data. It belongs in end-to-end testing, not in a peripheral hardware checklist.
Official source
Underside helps teams scope, integrate and test Odoo store journeys. The goal is to connect hardware, price master data and operational controls without creating a new blind spot.