Updated 27 October 2026.
Beyond the single restaurant lobby
Most self-order kiosk advice assumes one quick-service restaurant: one kitchen, one POS, one queue. The self-order kiosk guide covers that case. This page covers the three settings that break those assumptions:
- Food courts and food halls: one kiosk, many kitchens.
- Stadiums, arenas and event venues: short, extreme peaks, with mobile ordering alongside.
- Food trucks and pop-ups: no fixed power, no fixed network, and daylight on the screen.
It also answers a question that crosses all three: how a kiosk handles dine-in, takeaway and curbside orders.
| Setting | What changes | The deciding question |
|---|---|---|
| Food court | Order split across kitchens; one payment, several vendors | Who is the merchant of record, and how is each vendor paid? |
| Stadium or venue | Peak load at breaks; mobile and kiosk orders together | Can the kitchen and pickup flow absorb the surge? |
| Food truck | Power, network and sunlight | Is a tablet kiosk from your POS vendor enough? |
Food courts: one kiosk, many kitchens
A shared kiosk in a food court or food hall lets a customer order a burger from one stall and a drink from another, and pay once. That convenience creates three problems that a single-restaurant kiosk never meets.
Splitting the order
The basket must be split into a separate ticket for each vendor’s kitchen display or printer, with its own order number. The pickup screen needs to show each part separately, because the burger and the drink will be ready at different times. If each vendor runs its own POS, the kiosk must post each vendor’s share to that vendor’s POS, which means one integration per POS platform in the hall. POS vendors’ API access policies vary, so check each one; see the kiosk POS integration guide.
Settlement: who gets paid, and how
| Model | How it works | What to settle before launch |
|---|---|---|
| Operator as merchant of record | The landlord or food-hall operator takes the payment and pays each vendor its share | Payout timing, fees, refunds and chargebacks; each vendor’s tax reporting |
| Split payment at the acquirer | The acquirer divides each payment between vendors’ merchant accounts | Whether your acquirer supports it, and fees per split |
| Separate checkout per vendor | The customer pays each vendor separately at the same kiosk | Simplest accounting, but slower for the customer |
Agree the model with the operator, the vendors and the acquirer first. Tax treatment of a shared payment differs by market, so take accounting advice. The kiosk software follows the settlement model you choose; it can’t choose it for you.
Counter self-order checkout in a food court
Some food courts put a countertop self-order kiosk at each stall’s counter rather than shared kiosks in the seating area. That keeps each vendor’s ordering, payment and POS separate and avoids the settlement question entirely. The trade-off is that customers queue at each stall. For a hall with independent vendors on different POS platforms, counter kiosks per stall are often the more practical start.
Stadiums and venues: designing for the surge
Venue food service is quiet for most of an event and overwhelmed at a few moments: before the start, at breaks and at the end. Kiosks add ordering points without adding cashiers, which is where they help most. The limit then moves to the kitchen and the pickup counter.
- Mobile and kiosk together. Many fans order on their phones. Kiosks serve those who don’t. Both channels should feed the same kitchen queue and the same pickup screens, so staff work one queue, not two.
- Fixed menus at peak. A shorter menu at breaks keeps orders fast at the kiosk and in the kitchen.
- Network. Wire the kiosks where you can. Venue Wi-Fi and mobile networks can congest when the crowd is largest, which is when the kiosks are busiest.
- Offline rule. Decide whether kiosks stop or queue orders if the connection drops. Most operators stop, so they never take payment for an order the kitchen can’t see.
- Age-restricted items. If alcohol is sold, your licence conditions decide how age is checked. Usually that means a staff ID check at pickup.
- Accessibility. Venues serve large, varied crowds. Specify at least one accessible kiosk at each concession, with speech output, a tactile keypad and a headphone jack, and the screen and card reader within the 15–48 inch reach range of the 2010 ADA Standards (section 308, accessed 27 October 2026) in the US.
Dine-in, takeaway and curbside: order-type flags
“Which kiosks support both curbside and dine-in?” is really a question about the software and the POS, not the hardware. The kiosk asks for the order type at the start, because it can change price, tax, packaging and where the food goes. It then carries the type through to the POS and the kitchen display.
| Order type | What the kiosk captures | What the kitchen and pickup need |
|---|---|---|
| Dine-in | Table number, table tent or buzzer | Plates, and delivery to the table or a call to collect |
| Takeaway | Name or order number | Packaging, and a pickup screen |
| Curbside | Bay number or vehicle description | Packaging, a runner, and an alert when the customer arrives |
| Delivery to seat (venues) | Section, row and seat | A runner route and a handover check |
Curbside orders mostly come from web and app ordering, not from a kiosk inside the building. What matters is that kiosk, web and app orders use the same order types in the POS and show on the same pickup and runner screens. Check with your POS vendor that its API accepts each order type you plan to offer.
Food trucks: power, 4G and daylight
A food truck changes the hardware brief more than the software brief.
- Form factor. A floor-standing kiosk such as the K180-6C (about 1830 × 750 × 400 mm) does not fit most trucks. A countertop unit at the serving hatch, a wall-mounted unit on the truck’s side or a tablet on a secured stand is more realistic. It must be fixed so it survives the drive between sites.
- Network. 4G is the normal link. KioskForce kiosks have Ethernet with optional Wi-Fi or 4G/5G. Check signal at your regular pitches, and decide what the kiosk does when the signal drops.
- Daylight. An outdoor or hatch-mounted screen needs high brightness and an anti-glare finish to stay readable in sunlight. We specify brightness and the outdoor rating per project. We don’t publish a standard IP rating.
- Power. Generators and inverters don’t always deliver clean, stable power. Specify the supply voltage for your market, and plan for surge protection or a small UPS. See power and compliance.
- Payment. A terminal approved for unattended use under the PCI PTS POI standard (accessed 27 October 2026), on your acquirer. Payment options on our kiosks are listed on payments.
For one truck on a mainstream cloud POS, the POS vendor’s own tablet kiosk is usually the cheapest and quickest option. A custom kiosk earns its cost for a fleet that needs consistent branded hardware, or for an unusual flow.
Where a custom self-order kiosk is the wrong answer
- A food hall that hasn’t agreed settlement. Until the operator, the vendors and the acquirer agree who takes the money and how vendors are paid, no kiosk can be configured.
- A venue that needs a pre-certified integration with its concessions POS. Buy from a supplier that holds that certification. We build integrations per project and hold no certified integrations with named POS vendors.
- A single food truck. A POS vendor’s tablet kiosk usually does the job for less.
- A venue that needs on-site installation and same-day service from the manufacturer. KioskForce does not install or service on site. Installation is by your contractor or, in some regions, a local distributor, which also handles warranty and service where it supplied the kiosk. Our support is by email.
- Projects requiring US-made hardware. Our kiosks are built in several partner factories in China; see manufacturing.
How KioskForce builds for these settings
We design kiosk hardware and Android ordering software in-house and integrate with POS systems as a project-scoped REST API integration. A floor, countertop or wall-mounted unit can be built to your specification. Lead time is 4–6 weeks for a modified standard model and 8–12 weeks for a fully custom enclosure, plus freight. For a self-service build where staff refill compartments from behind, see the Bread Wall bakery case study. If the kiosk should also hand over pre-packed items, see kiosk vending machines. Site readiness is covered in what a restaurant needs for a self-service kiosk.
Frequently asked questions
How does a self-order kiosk work in a food court with several vendors?
The customer builds one basket from several vendors’ menus and pays once. The ordering software then splits the order into a separate ticket for each vendor’s kitchen display or printer, and records each vendor’s share for settlement. Who is the merchant of record, how each vendor is paid and how refunds work must be agreed between the landlord or operator, the vendors and the acquirer before launch.
Which self-order kiosks support both curbside and dine-in ordering?
Any kiosk whose software asks for the order type at the start and whose POS accepts that type through its API. Dine-in usually captures a table number or a buzzer, takeaway captures a name or order number, and curbside captures a bay number or vehicle description. Curbside orders mostly come from web and app ordering, so the kiosk, web and app orders should share the same order types and pickup screen.
What kind of self-ordering kiosk suits a food truck?
Usually a countertop or tablet kiosk mounted at the serving hatch, connected over 4G, with a high-brightness screen readable in daylight and a payment terminal approved for unattended use. Power must be clean and stable, which a generator or inverter does not always provide. For a single truck on a mainstream cloud POS, the POS vendor’s own tablet kiosk is often the cheapest choice.
Do stadium ordering kiosks need to work with mobile ordering?
They should feed the same kitchen queue and pickup screens, so staff work one queue rather than two. Kiosks serve fans who did not order on their phones and help most at peak moments such as breaks in play. Use wired network connections where possible, because venue Wi-Fi and mobile networks can congest when the crowd is largest.
Can KioskForce build a multi-vendor food court kiosk?
We design custom kiosk hardware and Android ordering software and integrate with POS systems as a project-scoped REST API integration. A multi-vendor order split and settlement design is scoped per project with the operator and its acquirer. We do not offer a ready-made multi-vendor platform or certified integrations with named POS vendors.
Get started
Tell us the setting (food court, venue or truck), how many vendors or kitchens, your POS platforms, your acquirer and your peak orders per 15 minutes. We’ll propose a form factor, an order-split and settlement approach to agree with your acquirer, and an integration scope. Background on specifying the kiosk itself is in the self-order kiosk guide.
Project brief · 60 seconds
What are we building together?
Three quick steps. Your brief goes straight to the engineers who design, build and support KioskForce systems.
