Real-time updates for kitchen and orders
Keep order and kitchen changes in sync so the operation doesn't depend on manually refreshing a screen.
Last updated: 2026-09-18 · Owner: Flexora engineering team
Alternatives considered
- Discarded
- Require manual refresh of operational screens.
- Chosen
- Push status changes in real time, scoped per branch.
Decision made
Use real-time updates for orders and kitchen boards, scoped per branch.
Rationale
Lets kitchen and floor staff receive status changes as they happen, with no manual refresh action needed.
Frequently asked questions
- What did Pyae decide about "real-time updates for kitchen and orders"?
- Use real-time updates for orders and kitchen boards, scoped per branch.
- How does the kitchen see orders without refreshing the screen?
- Pyae pushes order and kitchen status changes in real time, scoped per branch. Kitchen and floor staff get updates as they happen, with no one needing to manually refresh a screen.
- What happens if two branches share the same kitchen display?
- That doesn't happen in Pyae: real-time updates are scoped per branch, so each kitchen display only receives the changes that belong to that specific branch.
- What's the alternative to real-time updates?
- Requiring someone to manually refresh the screen to see status changes. Pyae ruled that out because it introduces delays and human error in an operation where kitchen and floor need to stay in sync instantly.
This kind of decision applies to your project too
If your operation needs custom software with technical decisions that are documented and built to last, we can help you define them.