Recommendations

None of this is required. All of it prevents the problems people actually run into.

Everyone

Add a second sign-in method today. The single highest-value minute you can spend in any Sitora app. Most lockouts are one method lost.

Set your language once. It is per person, not per device, so a shared tablet shows each person their own.

Read the status strip before acting. Stale and offline are stated plainly. Acting on an old picture is the root cause of most “the app did the wrong thing” reports.

Believe missing buttons. An absent action is an unavailable action. Looking for a hidden setting wastes time that asking someone would not.

Guests

• Check the branch name before ordering. Wrong branch is the most common ordering mistake.
• Pick your spot carefully. It is how the food finds you.
• Use the order chat, not a phone call. The person replying can see your order.
• Rate deliveries honestly. It is recorded once and it is how couriers’ records are built.
• Save your address. Two taps next time.

Waiters

• Confirm table orders quickly. Until you do, the guest and the kitchen are both waiting.
• Clear the Released queue before you leave. It is the shortest list in the app and the most expensive to ignore.
• Leave notes on sessions you hand over. Left after a partial serve saves the next person a conversation with a guest who has already gone.
• Sort by urgency during a rush. That is what it is for.

Cashiers

• Work the pending queue continuously. Every entry is an order that cannot proceed.
• Look at the proof before confirming. Confirming a wrong amount cannot be undone; it can only be corrected with a second record.
• Bind a station before collecting, release it when you step away.
• Confirm courier cash the same day. Overnight cash pauses that courier’s offers.
• Give a real reason when rejecting. The guest reads it.

Kitchen

• Report problems instead of improvising. Reporting reaches someone who can fix it; guessing reaches the guest.
• Sort by most late in a rush, oldest first otherwise.
• Tell the inventory manager when something runs out. Otherwise the next ten guests order it.
• Treat robot loading as an attestation. You are the only evidence the tray matches the order.

Service managers

• Read the signals together. Ready-waiting high with kitchen idle is a floor problem, not a kitchen one.
• Keep urgent unread at zero. The cheapest complaint prevention available.
• Record why, not just what. Next week’s version of the same incident is answerable only if you did.
• Use quality signals after service, not during. They are patterns, not alarms.

Inventory managers

• Switch an item off the moment it runs out. Faster than any adjustment and it stops the next order.
• Adjust with the honest reason. Waste, spoilage and count correction are different problems; collapsing them destroys the value of the record.
• Record restocks when they arrive, not at the end of the day.
• Tune thresholds until alerts mean something. A permanently red list is an ignored list.

Branch admins

• Remove access the day someone leaves. The one genuinely urgent access task.
• Add a second role rather than swapping when someone covers another job.
• Work the warnings list. It is short because it only contains real problems.
• Check branch, membership and warnings, in that order, when someone says Pro is empty.

Dispatchers

• Confirm handover when the food is actually in the courier’s hands. That confirmation is the evidence in any later dispute.
• Check the Couriers tab before re-dispatching. If nobody is on shift, re-dispatching changes nothing.
• Rate deliveries promptly and honestly. It is recorded once.

Couriers

• End your shift when you stop. Expired offers count against you; being off shift does not.
• Decline rather than ignore.
• Finish what you accept. Completion rate is the measure that leads to suspension.
• Report problems immediately and honestly. A reported failure is a fact; an unreported one is an abandoned job.
• Hand cash in the same day.
• Use a decent thermal bag. The negative reason most within your control.
• Work for more than one restaurant.

Owners

• Two sign-in methods, and not the only administrator. A lost phone should not be a business continuity problem.
• Work Readiness on a new branch before opening it. Missing payment configuration is the usual reason a new branch shows no revenue.
• Set delivery pricing before enabling delivery, and set the maximum distance to what you can serve hot.
• Tune your alerts once, properly. An ignored alert stream is worse than none.
• Compare branches over the same range. Different ranges produce confident wrong conclusions.
• Approve enough couriers. One approved courier means deliveries stop the day they are ill.
• Export before big changes, and keep the archive password.

Next

• Troubleshooting · FAQ