← All tests

#33 — Clean up Odoo POS sync leftover (prod)

SHIPPED 2026-06-10 · nix-cafe c9398a6 · no migration · Gate 2 5/5 · regression 51/51

Notion test-run #33. The Registers page still showed dead Odoo-POS-sync artifacts on every register — an · Odoo N identifier plus SYNC ERROR / AWAITING ODOO SYNC badges. These are remnants of the old register→Odoo-POS-config push, which is meaningless now that Odoo POS is universally bypassed (close-shift writes account.move directly; the product push was disabled 2026-06-01). Removed the UI; the underlying data is untouched.

Before — Odoo ids + sync badges on the Registers page

Narong’s screenshot: each register shows Odoo 4 / 5 / 11 / 13, “Bakery Shop” a red SYNC ERROR, and “Get Coffee TK #2” an AWAITING ODOO SYNC badge.

Registers page with Odoo ids and sync badges
Before — dead Odoo-POS-sync identifiers + badges

After — clean register list

Same get-coffee “Get Coffee TK” shop (8 registers). The · Odoo N identifier and the sync badges are gone; each register just shows its NIX id + sales count. Gate 2 asserts this on the exact tenant where the leftovers showed: the DB still holds 7 Odoo ids + 2 sync_error states, but the rendered page surfaces none of them — proving the UI omits the dead data. A lumiere (Starter) baseline guards against regression.

Registers page with no Odoo ids or sync badges
After — get-coffee registers, no Odoo id / sync badge

Flagged follow-up (backend)

This removes the display. The register→Odoo-POS-config push queue still runs and is what sets the sync_error state on get-coffee. If Narong wants those errors to stop being generated (not just hidden), that’s a follow-up to disable register Odoo-POS pushes entirely — same treatment as the product push on 2026-06-01.