Kitchen order tickets

Multi-kitchen management with kitchen-wise KOT printing

Assign menu items to kitchen stations. Station tickets contain that station's lines, quantities, modifiers and notes; kitchen-to-outlet mapping also matters in multi-outlet mode.

Station-specific ticketsLocal printer setup requiredKDS needs connectivity

Start free Open demo

Installing at a Windows counter? Test your actual printer, driver and a queued sale before the first shift. Prepare the Windows counter

Description reviewed: 2026-10-04 · Check your installed version and hardware in a demonstration.

Capabilities, setup and operating boundaries

Use these workflows as a demonstration checklist for your account, devices and service. A product description is not a compatibility test of your printer or installed app version. Detailed plan comparison

Kitchen-wise KOT routing and printing

Assign menu items to kitchen stations. Station tickets contain that station's lines, quantities, modifiers and notes; kitchen-to-outlet mapping also matters in multi-outlet mode.

Free, Starter, Growth, Pro — account limits, permissions and the setup conditions below apply.

Workflow and demonstration: Illustration: a burger assigned to the hot kitchen and a coffee assigned to the drinks station produce separate station tickets. Test an added item, failed print and authorized reprint.
Prerequisites: Configure each station's printer. Network ESC/POS needs a reachable printer address and venue app/agent; a locally attached Windows printer needs its driver and desktop mapping.
Connectivity and offline behavior: Browser configuration and server station jobs need internet. A prepared Windows counter KOT is a separate local print path, not offline cross-device routing.
Limitations: Server-generated station jobs need connectivity to reach the venue. Raw network Bengali depends on printer/font support; the Windows-rendered path must also be tested. Failed jobs and reprints do not guarantee paper physically emerged.

Invoice, KOT and labels: test each print path separately

One working print type does not validate another. Internet, local network and power are separate dependencies. Scroll the table horizontally on a small screen.

Print type	Client and hardware	Connectivity and offline boundary
Customer invoice and receipt printing	Compatible hardware, Windows driver or supported raw-print path, correct paper and a prepared device. Hardware is purchased separately.	Local Windows printing can use prepared sale data during internet failure; printer connectivity and power must still work.
Kitchen-wise KOT routing and printing	Configure each station's printer. Network ESC/POS needs a reachable printer address and venue app/agent; a locally attached Windows printer needs its driver and desktop mapping.	Browser configuration and server station jobs need internet. A prepared Windows counter KOT is a separate local print path, not offline cross-device routing.
Windows item and cup labels	Compatible Windows label printer and driver, matching label stock, gap and margins. Confirm the installed app version in a demonstration.	Prepared local sale data can be used without internet. Local printer connection and power are still required; server sync is separate.

Check the operating system and current release

Kitchen order tickets

Who this feature is for

For restaurants that need an accountable counter-to-kitchen handoff

Kitchens replacing handwritten slips
Counters that print both KOT and customer receipts
Restaurants routing work by kitchen station
Operators standardising print layouts across branches

Operational benefits

What this changes in daily service

Use the order’s preparation details

The ticket uses item quantities, variations and notes from the order. Check that every menu item has the intended station before service.

Route the mixed order

Each configured station receives its assigned lines. Printer routing and the outlet’s send-to-kitchen or pay-first settings need a demonstration with your menu.

Choose paper, screen or both

Use printed preparation slips, live KDS or a tested combination. A locally printed ticket does not prove another device’s screen updated during an outage.

How it works

The workflow, step by step

1. Map the menu and stations

Assign each test item to its kitchen station. Configure the intended printer connection and running desktop app or print agent. Confirm the app version, permissions and outlet payment rule.

2. Print a sample before service

Use Test print with the exact printer, driver and paper width. Include Bangla dish names and notes; a correct browser preview is not a successful paper test.

3. Send one mixed order

Send a test order with items from two stations. Check the order reference, quantities and notes on both tickets, with each station receiving only its assigned lines. For pay-first settings, test payment before kitchen release.

4. Distinguish paper from the live screen

If using KDS on Starter or above, follow the same order’s preparation status on the connected kitchen screen. A local print during an outage does not establish a live KDS update.

5. Test failure and reprint

Disconnect the test printer and inspect the job status. Restore it, check what actually printed, then use an authorised reprint and inspect the REPRINT label and log. Explain the duplicate copy to the kitchen; the label alone cannot prevent duplicate preparation.

What is included

KOT from a POS order
Station-specific items with prices omitted
Automatic station printing with configured local software
Item variations and notes
Order number and order-type context
Branch and station print settings
Reprint marking and log
58mm, 80mm and A4 receipt layouts

Current limitations

These boundaries are published so you can evaluate the feature accurately.

Automatic station printing needs a running Rosuii desktop app or print agent and a configured printer connection. Confirm the available app version and supported connection before buying hardware.
Supported paths include network ESC/POS and an operating-system printer through the desktop app. A browser-only setup does not provide unattended network socket printing.
Direct ESC/POS text needs a printer capable of the chosen script. Check actual Bangla dish names, quantities and roll width on your chosen print path; a browser preview alone is insufficient.
A failed connection can be reported, but software cannot guarantee paper emerged, was readable or was acted on. Include a paper-out, reconnect and controlled-reprint drill. Hardware is purchased separately.

Last verified against the product: 2026-09-22

Frequently asked questions

How are KOT and KDS different?

KOT is a preparation ticket. KDS is the kitchen queue on a screen with preparation states. Core KOT follows POS access; live KDS starts on Starter. Decide whether the kitchen needs paper, screens or both, and test the same order in each.

Does automatic printing work from a browser alone?

No. A configured local Rosuii app or print agent must reach the printer. Network printers use an address and port; desktop-attached printers use the operating-system print path. Confirm the exact device and app version.

What should we do when printing fails?

Check the job and station status, the local app or agent, connection and paper. Reprint through the supported order action and check the REPRINT marking and log. Tell the kitchen it is a copy, so it is not prepared twice.

Will Bangla print on every thermal printer?

No. The result depends on the print path, fonts, driver and hardware. Direct text printing needs script support on the printer. Run a Bangla ticket on the exact model and paper width before purchasing.

Can a kitchen ticket be sent before payment?

It depends on the outlet’s configured order flow. A pay-first outlet can require payment before the order reaches the kitchen. Include both your table-order and counter-payment rules in the demonstration.

See this workflow in your restaurant

Start on the Free plan or open the demo, then choose a plan only when you need higher limits or connected modules.

Start free See current pricing