Before a new direct ordering service opens, staff should practice receiving an alert, accepting an order, handling a problem, and handing the finished order to the right person. Each shift also needs to know who owns the next step when something goes wrong.
Start with a simulation that cannot charge a card, message a guest, or dispatch a courier. Then observe a separate, controlled live-service pilot once the team is ready and the owner has approved the process. The goal is to find gaps while someone is watching, not during the first busy rush.
Walk through alerts and order acceptance
Begin at the point where an order enters the restaurant. Show every shift where the alert appears or sounds, which device or screen staff should watch, and who is responsible for responding. Include a backup person for breaks, phone calls, and moments when the primary person is already serving a guest.
Have the owner or manager provide the service hours, pickup and delivery rules, expected preparation times, and the list of people authorized to make exceptions. The kitchen lead supplies realistic prep times and explains when the line cannot take another order immediately. Whoever sets up the ordering service shows staff how to recognize an incoming order and what actions are available in that setup.
Give trainees a sample ticket and ask them to say what they would check before accepting it:
- Is the restaurant open and able to prepare the order within the stated time?
- Are the items and requested modifications clear and available?
- Is the order for pickup or delivery, and where will the handoff happen?
- Who needs the ticket: the kitchen, the packing station, or both?
- What should happen if the alert is missed or the device is unavailable?
Decide how staff should acknowledge the order and how the kitchen will know it has been accepted. Do not assume that a printed ticket, a sound, and a screen notification will all appear. Walk through the actual devices and settings you intend to use. Ask the provider what happens when an order is not acknowledged and how staff can identify it afterward.
The person accepting the order should know when to pause and call the manager. For example, an unclear allergy-related request needs a defined escalation rather than a guess. Record who takes over if the manager is not on site.
Practice unavailable items and delayed orders
An unavailable item creates two separate decisions: whether the rest of the order can be prepared, and who can approve a change. Give staff a short list of permitted actions. It might authorize a manager to offer an alternative, but require the guest's agreement before changing the order. Explain how to record the outcome so the kitchen does not prepare both versions.
Hypothetical scenario: A guest orders two sandwiches for pickup. One filling is unavailable, and the remaining sandwich can be ready on time. The trainee should identify the affected item, tell the kitchen to hold it, and contact the designated manager. The manager decides how to reach the guest and whether a substitution, cancellation, or other remedy is appropriate under the restaurant's policy. In practice, the trainee describes or role-plays that contact; no real message is sent.
There is a trade-off. Starting the available sandwich may protect the pickup time, but it may also leave food waiting if the guest cancels the whole order. The manager should decide when to start the unaffected item based on its preparation time and how long a guest response may take. Put that decision on the ticket or in the team's chosen handoff record.
For a delay, have the kitchen lead identify a revised ready time and tell the order owner promptly. The order owner should know who may communicate that change and what to do if the guest cannot wait. Practice the handoff in both directions: the kitchen reports the delay, and the front counter confirms the decision back to the kitchen.
Delivery needs one more check. Identify who arranges the courier and who handles a late or failed pickup. Do not send a courier during training. Ask the provider which delivery arrangements are available for your location, who receives status updates, and who to contact when a driver is delayed.
Rehearse refund and support handoffs
Staff do not all need refund authority, but they do need a clear path to someone who has it. Write down who can approve a refund, where the request is recorded, and who follows up with the guest. Distinguish the decision to refund from actually processing it; an employee may be able to collect the details without being authorized to issue money.
For a practice case, role-play a guest reporting a missing side after pickup. The trainee gathers the order identifier, the missing item, and the guest's preferred contact method without promising a particular outcome. The manager reviews the restaurant's policy, decides on the remedy, and explains who will carry it out. Use fictional details and do not submit a real refund or send a real message.
Ask the ordering provider to demonstrate the available refund and support steps for your configuration. Find out whether a partial refund is possible, where staff can see its status, and whom to contact if the payment or order record needs investigation. Until those answers are clear, train staff to escalate rather than promise that a particular action can be completed.
Make a simple handoff note: order identifier, issue, action requested, person responsible, and next update. Store it where the relevant shift can find it, without putting unnecessary guest or payment details on an exposed counter. At shift change, the outgoing lead should name any open case and the incoming lead should acknowledge ownership.
Finally, separate restaurant decisions from provider support. A provider may help investigate an ordering issue, while the restaurant still needs to decide how to respond to the guest. Give staff both contact paths and a backup for periods when the usual contact is unavailable.
Observe a test order and record gaps
Use the following checklist on every shift, including the people who cover breaks. A manager can read a scenario card aloud while another person plays the guest or kitchen lead. The examples are practice prompts, not instructions to create real transactions.
| Scenario card | Staff action to observe | Record a gap if |
|---|---|---|
| New pickup order arrives during a rush | Name the alert owner, check the ticket, and pass it to the kitchen | No one owns the alert or the ticket handoff is unclear |
| An ordered item is unavailable | Hold the affected item and route the decision to the authorized person | Staff guess at a substitution or the kitchen receives conflicting instructions |
| The kitchen reports a delay | Get a revised time and identify who communicates and records the decision | The order owner or next update is unknown |
| A guest reports a missing item | Collect the relevant order details and hand the request to the refund decision-maker | A trainee promises a refund or cannot identify the approver |
The table checks ownership as well as button knowledge. Someone can know how to open an order screen and still be unsure who tells the kitchen about a change. Watch the complete handoff, then ask the trainee to repeat it with the backup person absent.
Before each simulation, confirm that the chosen practice method cannot create a real payment, guest message, or courier dispatch. If a safe test mode is not available, use a paper ticket and role-play the screen actions instead. The limitation is that a paper exercise cannot confirm the actual alert, device, or routing behavior; arrange a provider-supported check of those details before launch.
Use this shift checklist to close the loop:
- Assign coverage. Name the primary and backup order owner for each shift.
- Run the cards. Have staff explain or demonstrate each action using the safe practice method.
- Check the handoffs. Follow the ticket from acceptance to kitchen, packing, and pickup or delivery handoff.
- Log gaps. Record the problem, its owner, the fix, and when the team will practice it again.
- Repeat after a change. Rehearse again when staffing, devices, hours, or the support process changes.
Once the simulations are complete, plan a separate live-service pilot with management approval. Decide who will watch incoming orders, how staff will report problems, and when the manager will review the results. Real guest orders and any real payment or delivery activity belong only in that live setting, under the restaurant's normal procedures. A pilot can reveal problems a role-play cannot; it cannot guarantee a trouble-free launch.
If you are still comparing the overall setup, the online ordering buying guide can help frame the decision. Also check how guests reach ordering from your restaurant website, so staff can explain the path when someone calls for help.
Next step: Run the checklist with one person from each shift, assign an owner to every gap, and ask Fleksa about restaurant online ordering and verified availability in your US location.
Frequently asked questions
Who should attend online ordering training?
Include the people who monitor orders, prepare food, pack orders, handle guest questions, and approve refunds. Train backups and shift leads too, so the process does not depend on one employee.
Can we practice without placing a real order?
Yes. Use a safe practice method that cannot trigger payment, guest messages, or courier dispatch, or role-play with a paper ticket. A paper exercise does not verify that actual alerts and routing work.
What should we do if staff find a gap?
Record the issue, assign someone to resolve it, and repeat the affected scenario on each relevant shift. Escalate unresolved setup questions to the provider before relying on the process during service.
