The problem this app solves

Product, price and customer changes made in the back office can leave open terminals working with older master data. A disconnection adds another problem: a terminal needs to catch up without disrupting the paid orders waiting to synchronize.

Choose automatic, review-first or manual updates for supported data classes. Retained changes support catch-up after disconnection, and existing draft commercial values are not silently repriced. Managers can inspect terminal health and recovery needs.

Features that support your daily work

• Per-class policy. Choose Auto Apply, Notify & Review, or Manual Sync independently for products, pricing/taxes, and customers.
• Durable catch-up. A monotonic server ledger recovers every retained event after missed bus wake-ups, browser suspension, or disconnection.
• Access-safe deltas. Private wake-up hints carry no records. Authoritative, bounded payloads follow the active POS domain, company, and cashier permissions.
• Native queue first. Reconnect flushes native pending paid orders and queued POS writes before this addon's master-data catch-up.
• Draft-safe refresh. Existing line prices, discounts, tax relation, and commercial values stay captured. Repricing is explicit and manager-authorized.
• Health and audit. Review terminal cursors, outcomes, retries, drift, retention gaps, errors, PDF health reports, and CSV audit exports.

A practical example

Illustrative workflow — the available actions depend on your configuration.

A manager updates a product while a terminal is disconnected. On reconnect, native pending paid orders synchronize first. The terminal then catches up on retained master-data changes according to its policy, while an existing draft keeps its captured commercial values.

How updates reach an open terminal

Configure data-class policies and retention limits per POS.

Open terminals register device clients and acknowledge the retained cursor.

Apply bounded, dependency-complete deltas only after IndexedDB persistence succeeds.

Review client health and event outcomes; recover stale cursors with a controlled snapshot.

Configuration and menus

• Point of Sale > Configuration > Settings: enable Live Master Data Sync and set policy, inactive-product, batch, debounce, and retention controls.
• Point of Sale > Configuration > Live Sync Clients: inspect terminal cursors, status, drift, retries, and recovery actions.
• Point of Sale > Reporting > Live Sync Audit / Live Sync Errors: review event outcomes and resolve sanitized errors.
• Product and customer forms: managers can explicitly Publish to Open POS.

Reports and exports

• POS Live Sync Health & Audit: printable PDF with terminal health, event outcomes, timings, and sanitized errors.
• pos-live-sync-audit.csv: event/client/error rows with cursors, outcomes, retries, duration, drift, and reload reason.

Offline safety is the boundary

The bus is only a wake-up hint. Native pending paid orders synchronize first on reconnect, extension data follows, and master-data cursor acknowledgement follows durable IndexedDB writes. Draft commercial values are not silently repriced, and a retention gap becomes an explicit recovery state.

See the workflow in Odoo

Explore the screens in sequence, from configuration to daily work and reporting. Each image includes a caption explaining its place in the workflow.

Per-POS policy and delivery controls. Terminal health at a glance. Cursor boundaries and recovery actions. Immutable event audit and outcomes. Manager report and export entry point. Touch-friendly POS status and Sync Now control.

Compatibility

Odoo: 15.0

Required native addons: point_of_sale, pos_hr, bus

Deployment: Odoo.sh and private/on-premise hosting

Odoo Online: not supported. This standard Python and POS JavaScript/OWL addon requires server-side models and browser persistence.

Compatible with Community and Enterprise where the declared dependencies exist. No other Corvus paid app is required.

Deliberate limits

• No real-time inventory quantity or reservation broadcasting.
• No cross-database synchronization or external broker/SaaS.
• No silent repricing or forced reload with pending local transactions.
• No full offline backend administration or guaranteed instant delivery when transport is unavailable.