Feature #10947
closedFocused on reliability and speed: fixed a stale-data bug on the POS screen, unified restaurant status across the customer site, and cut unnecessary backend load on every menu view.
Subtasks
Related issues
Updated by sairam machavarapu 2 days ago
- Due date set to 09/17/2026
- Status changed from New to Closed
- % Done changed from 0 to 100
POS reliability — stopped a bug where a slow, outdated response from the server could overwrite newer order data on screen mid-order, and reworked the settings and navigation pages to be more stable alongside it.
Consistent restaurant status — fixed the restaurant's open/closed status so every page on the customer site reads it from one shared source, instead of different pages disagreeing with each other.
Performance cleanup — removed a database write that was firing on every single menu page load (not just when data changed), and trimmed an oversized API response, both aimed at making the menu and order screens feel faster under normal use.
POS order page refinements — follow-up fixes and adjustments to the POS order screen after the stale-data guard above.