Do this first
Count genuinely open seats, confirm the customer is assigned, move the correct completed order into the serve state, and finish payment or collection. Only add seating after the existing path is usable.
Fix Customer Flow in Karinderya
Trace a waiting or unpaid customer through seating, assignment, order, serving, and collection without guessing a patience timer.
Troubleshooting One customer cycle
Step by step
Follow the current game state in order
Each step names the visible decision to make. Exact labels, prices, and timings remain tied to the interface in your current server.
- 01
Count real seating capacity
Compare waiting customers with seats that are open, reachable, and part of a usable table setup. Do not count a chair only because it looks empty.
- 02
Confirm assignment
Check whether each seated customer has reached the assigned and order-visible state. A seat problem and an assignment problem need different fixes.
- 03
Trace the correct order
Clear completed cooking work and move the matching order to the assigned customer. Avoid grabbing new work while a completed dish is waiting for its handoff.
- 04
Finish collection and recount
Confirm payment or collection before switching tasks. Then recount the two queues and use the new state for the next capacity decision.
If you're stuck
Recover from the visible state
Guests wait beside open-looking chairs
Inspect table/chair usability, route clarity, and the assignment step before buying more furniture.
The unpaid alert remains
Check that the correct completed order reached the correct assigned customer and that collection is finished.
The current interface looks different
Follow the live prompt and treat the checked date on this guide as a version warning.
Common mistakes
Avoid the expensive assumption
Assuming every empty chair is usable
Verify the full table-and-chair state.
Treating an unpaid alert as one universal bug
Trace assignment, order, serving, and collection in sequence.
Publishing a patience countdown
No stable public timer is established; use visible states only.
Why this method fits Karinderya
A customer problem can start at seating, assignment, kitchen handoff, serving, or collection. Treating every alert as a furniture shortage wastes cash and hides the exact state that needs attention.
FAQ
Questions about this task
Why are customers waiting with empty chairs?
A visible chair may not be part of a usable setup, or the customer may not be assigned. Verify the full seat state.
What causes an unpaid customer?
Recent gameplay shows the alert, but not one universal cause. Trace assignment, order, serving, and collection.
How long will a customer wait?
No reliable patience timer or probability was found.
Should I add more seats?
Only after confirming current seats are usable and the waiting-customer gap is larger than the kitchen gap.
Related pages
Back to Karinderya guides — Visible-state recovery