Self-Order Kiosk and Kitchen Display (KDS) Integration

A self-order kiosk reaches the kitchen display system (KDS) in one of two ways: through the POS, or directly. In the usual design the kiosk posts the order to the POS through its API, and the POS routes it to the kitchen display exactly as it routes a counter order. In the direct design the kiosk software sends tickets to its own kitchen screens or printers and reports sales to the POS afterwards. Routing through the POS keeps one set of routing rules and one kitchen queue, so it is the right default for a restaurant that already has a KDS. Either way the kiosk must send four things with every order: the channel, the order type (dine-in, takeaway or curbside), the item modifiers in the form the kitchen reads, and an order number the customer can see. The kitchen’s “ready” tap should then drive the pickup screen and any customer notification. KioskForce builds this as a project-scoped REST API integration and holds no certified integrations with named POS or KDS vendors.

Updated 22 November 2026.

Where the kitchen display sits in a kiosk order

A kitchen display system (KDS) is the screen in the kitchen that replaces paper tickets. It shows each order, lets staff mark items and orders as done, and records how long each took. A self-order kiosk adds a new source of orders to that screen. The self-order kiosk guide covers the kiosk itself and the POS integration guide covers menu sync and payment. This page covers the last step: how the order reaches the kitchen and how the customer learns it is ready.

Two ways an order reaches the kitchen

  Through the POS Direct to the kitchen
How it works The kiosk posts the order to the POS through its API. The POS routes it to the KDS The kiosk software sends tickets to its own kitchen screens or printers
Routing rules Kept once, in the POS Kept in the kiosk software as well as the POS
Kitchen queue One queue for counter, kiosk, web and delivery orders A second queue unless the two are merged
Sales reporting In the POS as the order is placed Sent to the POS afterwards, or reconciled by hand
Depends on The POS vendor allowing outside orders through its API The kiosk vendor’s kitchen software
Best when The restaurant already runs a POS-driven KDS There is no KDS, or the POS cannot accept outside orders

One ordering-platform vendor describes the goal as POS, kiosk, web, mobile and delivery orders consolidating into one preparation queue in the order they arrive (Ordering Stack, accessed 22 November 2026). That is the test to apply to any design: after the kiosk goes in, does the kitchen still work from one queue?

What the kiosk must send with every order

Field Why the kitchen needs it What goes wrong without it
Channel (kiosk) Staff know no one took the order by voice, so the ticket is the only record Questions about the order go to a counter that never saw it
Order type (dine-in, takeaway, curbside) Changes packaging, tray or bag, and the hand-over point Dine-in food bagged, takeaway plated
Table, name, bay or order number Tells the runner where the order goes Food waits on the pass
Modifiers in kitchen wording “No onion”, “extra cheese” must read the same as on counter tickets Remakes and allergy risk
Allergen or note field, if you allow one Flags orders that need a separate prep The note is lost between systems
Time placed and paid status Sequencing, and proof the order is paid Unpaid or duplicate orders are cooked

Modifiers are where most kiosk-to-kitchen problems start. The kiosk shows customers friendly wording and photos, while the kitchen reads short codes. The integration has to map one to the other for every item, including combos, and it has to be retested whenever the menu changes.

Routing to stations

A kitchen with more than one station needs each item on the right screen:

  • By item or category. Burgers to the grill screen, drinks to the bar screen, desserts to the cold station. These rules already exist in a POS that drives a KDS, which is the main reason to route through it.
  • An expo screen. One screen shows the whole order so that someone assembles it and checks it is complete before it is handed over.
  • Timing. Some kitchens hold quick items so that everything in an order finishes together. If your KDS does this for counter orders, check that kiosk orders get the same treatment.
  • Several kitchens. A food court or food hall splits one basket into a ticket per vendor. See self-order kiosks for food courts, stadiums and food trucks.

Dine-in, takeaway and curbside

The order type is a flag captured on the kiosk’s first screen and carried to the kitchen ticket.

Order type What the kiosk captures How the order is handed over
Dine-in Table number, or a numbered table marker the customer takes A runner brings it to the table
Takeaway Order number, optionally a name The customer watches the pickup screen and collects at the counter or from a pickup shelf or locker
Curbside Bay number or vehicle description, and a phone number Staff bring it out when the customer arrives

Curbside orders mostly start on a phone, not at a kiosk inside the restaurant. What matters is that kiosk, web and app orders use the same order types in the POS, so the kitchen and the pickup screen treat them alike.

Telling the customer the order is ready

  • Pickup screen. Shows order numbers as “preparing” and “ready”. It needs a screen in view of the waiting area and a feed from the kitchen display.
  • Called number or table marker. No extra equipment, but it relies on staff.
  • Text message. The kiosk must collect a phone number, which adds a step and a privacy notice.
  • Pickup lockers. Staff load the order into a compartment and the customer opens it with a code. This suits prepaid takeaway at peak times.

Whichever you use, drive it from one event: kitchen staff marking the order ready. One vendor puts it as the kitchen’s tap being the single source that the lobby screen, the push notification and the web status page all follow (Ordering Stack, accessed 22 November 2026). If the pickup screen and the kitchen display can disagree, customers will ask the counter, and the kiosk has saved no labour.

Failure rules to agree before launch

Failure Recommended rule
The kiosk cannot reach the POS Stop taking orders and show a “please order at the counter” screen
The POS accepts the order but the kitchen display is down Fall back to a kitchen printer
An item sells out The POS marks it unavailable and the kiosk hides it at the next menu sync; agree how often that runs
The payment succeeds but the order post fails Retry, then alert staff and print a receipt the customer can take to the counter
The kitchen is overloaded Staff can pause kiosk ordering or lengthen the quoted wait from the POS or the kiosk’s admin screen

Questions to ask your POS and KDS vendors

  1. Can a third-party kiosk post orders through your API, and is there a fee or a partner programme?
  2. Do orders posted through the API follow the same kitchen routing rules as counter orders?
  3. Which order types can the API set, and do they print on the kitchen ticket?
  4. How are modifiers and combos represented in the API?
  5. Can an outside system read order status, so that a pickup screen can show “ready”?
  6. What does the API return if the kitchen display is offline?

Where a custom kiosk is the wrong answer

  • You want kiosk, POS and KDS from one vendor with one support number. Buy the POS vendor’s own kiosk. It will route to its own kitchen display without a project.
  • Your POS has no ordering API or will not open it. No third-party kiosk can reach the kitchen through it. Change the POS first, or use its own kiosk.
  • You need a certified, pre-built integration. We build integrations per project and hold no certified integrations with named POS or KDS vendors.
  • You need on-site installation and service from the manufacturer. KioskForce does not install or service on site. Installation is by your contractor or, in some regions, a local distributor. Our support is by email.

How KioskForce handles kitchen integration

Question KioskForce answer
Route to the kitchen Through your POS: the kiosk posts the order by REST API and the POS routes it to your kitchen display or printers
Certified POS or KDS integrations None claimed with named vendors
Order types Dine-in, takeaway and curbside flags are set up to match the order types in your POS
Pickup screen, text messages, pickup lockers Scoped per project. Locker compartments can be built into the kiosk; the standard K180-6C has six
Software Android ordering software designed in-house; integration scope agreed before the order
Engineering Custom integration work is USD 800 per person-day
Lead time 4–6 weeks for a modified standard model, 8–12 weeks for a fully custom enclosure; software scoped separately
Support By email; installation is optional and done by your contractor or, in some regions, a local distributor

Frequently asked questions

How do self-order kiosks integrate with a kitchen display system?

Usually through the POS. The kiosk posts the order to the POS through its API, and the POS sends it to the kitchen display with the same routing rules it uses for counter orders. Some kiosk software instead drives its own kitchen screens or printers and reports sales to the POS afterwards. If the restaurant already has a KDS, route through the POS so the kitchen works one queue.

Does a self-order kiosk need its own kitchen display?

Not if the restaurant’s POS already drives a kitchen display or kitchen printers and accepts orders through an API. Kiosk orders then appear on the existing screens, marked with their channel. A separate kiosk kitchen screen makes sense only where there is no POS-driven kitchen display, or where the POS cannot accept outside orders.

How do kiosks handle dine-in, takeaway and curbside orders?

The kiosk asks for the order type at the start and sends it with the order. Dine-in captures a table number or a table marker, takeaway captures an order number or a name, and curbside captures a bay number or vehicle description. The order type must exist in the POS and print on the kitchen ticket, because it changes packaging and where the order is handed over.

How does the customer know a kiosk order is ready?

By an order number shown on a pickup screen, a called number, a table marker for dine-in, or a text message if the kiosk collected a phone number. The status should change when kitchen staff mark the order ready on the kitchen display, so the pickup screen and any message follow one source.

What happens to kiosk orders if the kitchen display or network goes down?

Decide the rule before launch. The safest is for the kiosk to stop taking orders when it cannot confirm that the POS accepted the last one, so no customer pays for an order the kitchen cannot see. A kitchen printer as a fallback keeps the kitchen working if only the display fails.

Does KioskForce integrate kiosks with kitchen display systems?

We design kiosk hardware and Android ordering software in-house and integrate with a restaurant’s POS as a project-scoped REST API integration. Kitchen routing then follows the POS. We do not hold certified integrations with named POS or KDS vendors, and we scope the integration with your POS vendor’s API before the order.

References

  • Ordering Stack — “Kitchen Display System” (accessed 22 November 2026). https://orderingstack.com/kitchen-display-system

Get started

Tell us your POS platform, whether it drives a kitchen display or printers, how many stations you run, the order types you take and your peak orders per 15 minutes. We’ll propose a form factor and an integration scope to confirm with your POS vendor. Site requirements are in what a restaurant needs for a self-service kiosk.

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.

1What are you building?
2Roughly how many units? (optional)
3Where should we send your proposal?

Prefer email? sales@kioskforce.com