Order Management Training for Kitchen Staff

Order Management is the Eatsy product your kitchen actually runs from. It’s a separate app that lives on a kitchen tablet near the line, not the Orders log inside admin.eatsyorders.com. Every order from every channel (Branded App, Microsite, QR, iPad Kiosk) lands on the Order Management tablet in real time. Train your team in 20 minutes.

How it differs from the admin Orders log

• admin.eatsyorders.com → Orders: historical log, scheduled orders, active deliveries, and driver payments. Useful for managers and the back office.
• Order Management tablet: live kanban for the line cooks. Real time, audio alerts, action buttons. This is where the actual fulfillment work happens.

You should run both: the tablet for service, the admin log for after-the-fact analysis.

The four-status flow on the tablet

Every order moves through:

1. New: just arrived. Audio alert plays.
2. In progress: kitchen accepted, started preparing. Customer auto-notified.
3. Ready: done, waiting for pickup or delivery handoff. Customer auto-notified.
4. Completed: handed off to customer or driver. Closes the ticket.

Staff taps the status button on each ticket to advance it. The ticket moves visually across the kanban-style columns.

What’s on each ticket

• Order number (e.g. “Order #4231”)
• Channel badge (App / Web / QR Table 5 / iPad Kiosk 1)
• Customer name + loyalty status (if returning customer)
• Items with modifiers and special requests
• Total
• Pickup or delivery info (time, address)
• Action button (advance status)

Audio alerts

Configure on the tablet itself: Settings → Order Management → Audio.

Options: off, soft chime, loud bell. Loud bell is recommended for noisy kitchens.

The alert plays when:

• A new order arrives
• A ticket has been in “In progress” longer than the configured threshold (e.g. 20 min, which flags slow orders)

Language switching

Each staff member picks their language at login. Options: EN or ES. The tablet UI, ticket labels, and modifier names display in the chosen language. Customer-submitted special requests pass through verbatim (no translation, to preserve nuance).

Multi-location

Owners with multiple locations can switch between them on the tablet, or run a tablet per location (more common: one device per kitchen).

Most common day-one mistakes

1. Staff forgets to tap “Ready.” The customer doesn’t get the notification, and shows up too early or too late. Train explicitly.
2. Staff dismisses the audio alert without reading the ticket. Orders get missed. Configure the alert to require explicit acknowledgment.
3. Edits made on the tablet don’t sync back to your POS. If your POS is the source of truth (it should be), make edits there first.