Paper Rail, POS Kitchen Display, Dedicated Expo Software, and Hybrid Setups Compared
Four honest ways to run an expo pass, weighed against the five things the pass actually needs to do. No brand names, just the tradeoffs we hear about from kitchens every week.
Every restaurant runs the pass somehow, and the setups fall into a small number of patterns. Some kitchens use a printer, a ticket rail, and an expediter who calls everything out loud. Some use the kitchen display screens that came with their POS. Some add a dedicated tool built around course firing and cross-station coordination. Many end up with a hybrid, keeping paper at the pass and screens on the line or the other way around. None of these is wrong. The right choice depends on volume, how many stations have to coordinate on one plate, how much your menu changes, and how much timing data you actually want to look at. Below we compare the four approaches against the same five criteria so you can see where each one is strong and where it will frustrate you.
| Option | Visibility of open tickets | Station routing and modifiers | Course firing control | Timing and reporting | Setup effort and ongoing cost |
|---|---|---|---|---|---|
| Paper tickets with a rail and a calling expediterBest for: Small to mid-volume kitchens with a strong expediter, a stable menu, and a line short enough that one person can see and call every ticket. | Good as long as the rail is not full. Once tickets stack two deep or the expo steps away, visibility drops to whoever is closest to the printer. | Depends entirely on the expo reading and calling correctly. Station printers help, but split items and modifiers are easy to miss under load. | Fully manual and fully flexible. The expo decides when to fire by pulling or calling the ticket. Works well with a skilled expo, poorly with a new one. | Almost none. You know a ticket is late because it looks old on the rail or because a server is asking. No history to review after service. | Lowest to start: a printer, paper, and training. Ongoing cost is paper and the expo's attention, which is the scarce resource on busy nights. |
| Basic kitchen display system bundled with the POSBest for: Kitchens that want routing and timers without a separate vendor, and whose coursing needs are simple enough to run on order-time firing. | Good per station. Each screen shows its own items with age. The pass view is often just another station screen, which can be crowded when tickets pile up. | Solid for single-station items. Routing rules by category or item usually exist. Multi-station plates and modifier display vary a lot between systems and need testing after menu changes. | Often limited. Many bundled systems treat the whole ticket as one unit or offer basic course holds. Firing entrees on a table signal frequently still happens verbally. | Ticket age and bump times are usually available. Reports tend to be averages by day, which is useful but blunt for finding a specific station or course problem. | Moderate. Screens, mounts, and a per-screen subscription are typical. The routing map has to be maintained by someone, and it tends to drift after menu changes. |
| Dedicated expo and course pacing softwareBest for: Higher-volume or multi-station kitchens where the expo cannot hold every ticket in their head, and where tables eating together is a core standard. | Strongest. A pass view built for the expediter shows every open ticket, each course's state, and what is fired versus waiting, rather than a cook-oriented station list. | Designed for split items and lead-item timing, so both stations working one plate see that they share it. Modifiers travel with the item to every screen that needs them. | The core feature. Fire by course, hold a course, stagger a large party, and see the countdown from fire to expected plate up. Rules can differ by table size. | Segmented by station, course, item category, and day part. Lets you count tickets over target rather than chase an average, and find the constraint station. | Highest up front: menu mapping, coursing rules, target times, and training. Ongoing subscription on top of the POS. Only worth it if the pass is a real bottleneck. |
| Hybrid: paper at the pass with screens on the line (or the reverse)Best for: Kitchens transitioning between systems, or where one part of the line resists screens and the rest benefits from them. | Split. Whichever side has the fuller view depends on where the screens are. Two sources of truth can disagree, especially on voids and modifications. | Works if routing to screens is correct and the paper copy at the pass is complete. Changes made in the POS after send may reach one medium and not the other. | Usually manual at the pass with the screens following. The expo fires verbally and bumps or reprints, which adds a step under pressure. | Partial. Screens capture what they see, paper captures nothing. Reports understate the problem if the pass runs on paper. | Moderate and often accidental. Hybrids tend to grow rather than get designed, which means nobody owns the whole picture. |
- Paper tickets with a rail and a calling expediter: Paper works until the night it does not, and the failure usually arrives at the exact moment there is no time to change anything.
- Basic kitchen display system bundled with the POS: The biggest win is that every station sees the same ticket at the same time; the biggest gap is usually course-level firing.
- Dedicated expo and course pacing software: This is the category PlatePassr sits in, so weigh our view accordingly; the honest case for it is volume and coordination, not features for their own sake.
- Hybrid: paper at the pass with screens on the line (or the reverse): Fine as a bridge, risky as a destination, because reconciling two views of the same ticket is exactly the work the expo does not have time for.
Our verdict
If your expediter can see and call every ticket comfortably on your busiest night, paper is not a problem and switching to screens will not fix anything. If the pass is drowning on weekends, the honest question is whether the issue is visibility, routing, or firing. Visibility and routing problems are usually solved well enough by the kitchen display system bundled with your POS, provided someone maintains the routing map and tests it after every menu change. Firing problems, meaning tables not eating together, large parties landing in waves, and plates dying in the window, point toward a tool built around courses rather than tickets.
Whatever you choose, do the unglamorous work first: name who owns the pass on each shift, write down the coursing rules, and map every item to a station. Those three things make paper run better and make any software run much better. Then pilot on a slow shift, not a Friday. And if you find yourself running a hybrid, decide on purpose which medium is the source of truth at the pass, because the cost of two conflicting views shows up precisely when tickets are stacked.
Frequently asked questions
Can I run course firing on a basic KDS without dedicated expo software?
Often yes, with workarounds. Many bundled systems support holding items or courses and some support fire on demand. The limitation is usually that the fire has to be triggered per ticket by someone at a screen, and large-party staggering or lead-item timing is done in the expo's head. If that is working for you, keep it. If tables are still eating in waves, that is the sign the workaround has run out.
How do I know whether the pass or the line is the real bottleneck?
Watch where tickets pile up. If every station is caught up but plates are waiting at the pass for garnish, checking, or a runner, the pass is the constraint. If one station's items are always last to the window while the others wait, the line is the constraint and no expo system will fix it by itself. Segmenting ticket times by station is the fastest way to answer this with data rather than a feeling.
Read the complete guide for the full reasoning behind this comparison.