--- title: "Kitchen Display Buying Guide" description: "Evaluate KDS tickets, station routing, priorities, statuses, timers, hardware and POS connections before linking online ordering to your kitchen." canonical: https://www.ordering.co/blog/kitchen-display-buying-guide/ --- # Kitchen display buying guide: follow a ticket through every station Evaluate KDS tickets, station routing, priorities, statuses, timers, hardware and POS connections before linking online ordering to your kitchen. 4 min read· Ordering.co· Guides ## A kitchen display system coordinates preparation A KDS turns accepted orders into kitchen tickets and helps staff track preparation. A pickup screen tells customers when to collect; an order-management dashboard helps staff manage orders. These surfaces may connect, but they serve different people and decisions. Begin with a kitchen map: prep stations, expeditor, packing and collection. Identify which team owns each item and which person confirms the complete order. Buying a larger screen will not resolve an undefined handoff. ## Tickets must carry the information cooks need Ask to see item quantities, required modifiers, removed ingredients, service mode, order reference, notes and promised time at the station. Check how edits, voids and duplicate-looking orders are distinguished. Staff need to recognize a change without confusing it with a new ticket. For a burger, fries and drink, decide whether separate stations receive only relevant items and whether an expeditor sees the combined order. A station marking fries finished should not inadvertently tell the customer that the entire meal is ready. The [Square KDS routing guide](https://squareup.com/help/us/en/article/7959-route-orders-with-your-kds) illustrates configurable routing from POS and online sources. It is a product-specific example; it does not establish the behavior of every KDS or a connection to Ordering.co. ## Make priority, states and timers explicit Choose a priority rule: oldest accepted order, promised pickup time, or an authorized manual adjustment. A scheduled order placed hours ahead may need a release time before it belongs in the active cooking queue. Demonstrate how late tickets are highlighted without relying on color alone. Define received, in preparation, station complete, ready for packing and handed off. Ask which are item states and which are order states, who can recall a completed ticket, and what happens after cancellation. Record which timestamps each timer measures: creation, acceptance, cooking start or readiness. Compare preparation time and lateness using the same start and stop events. A customer-facing estimate and a station timer measure different parts of service. ## Select devices for the actual kitchen Check supported device models and operating systems before buying displays. Square’s US routing guide specifies Android tablets for its KDS; do not assume an existing tablet will run a chosen product. Other providers need their own compatibility check. Evaluate viewing angle, readable ticket count, heat and grease exposure, cleanability, mounts, power and network coverage. Ask whether touch or a bump bar suits gloves and working position, then confirm support for the selected control. Establish a paper or alternate-device procedure and test restart, reconnect and ticket recovery. Price screens, mounts, controllers, licenses per device, network work, installation, replacement and support separately. Confirm what an outage preserves locally instead of assuming offline preparation works. ## Prove the POS and online-ordering connection Map the route explicitly: ordering channel to acceptance system, then POS or connector, then KDS and preparation station. Some implementations route through a POS; others use a different connection. Identify the owner and supported fields at each step. Native order handling is not proof of a native kitchen station workflow. Test a prepaid online order with modifiers, a scheduled pickup, an edit, cancellation and an interrupted connection. Confirm no duplicate cooking ticket appears during retry and that the ready status reaches only the intended destination. A connector must preserve item identifiers and status meaning, not merely transfer text. Use the [restaurant software map](https://www.ordering.co/blog/restaurant-management-software-guide/) to assign responsibilities and [Ordering.co restaurant solutions](https://www.ordering.co/solutions/restaurants/) to evaluate the ordering layer. [Book a demo](https://www.ordering.co/book-a-demo/) with your POS version, KDS model and a sample ticket to scope the connection before buying kitchen hardware. ## Keep reading. - ## [How an on-demand service business works: demand through fulfillment](https://www.ordering.co/blog/on-demand-services-guide/) Map an on-demand business from request to fulfillment: actors, booking, dispatch, payments, unit economics, support, and infrastructure choices. - ## [Digital restaurant order tickets: from staff entry to kitchen and payment](https://www.ordering.co/blog/restaurant-digital-order-tickets/) Design a restaurant order-ticket workflow for staff, modifiers, kitchen handoff, changes, and payment, and distinguish it from QR self-ordering. - ## [Restaurant orders through WhatsApp and WooCommerce](https://www.ordering.co/blog/restaurant-ordering-whatsapp-woocommerce/) Choose where a WhatsApp request becomes a WooCommerce order, with clear catalog, checkout, payment, and kitchen responsibilities. ## See it running on your own menu. The shortest way to understand any of this is to watch an order go from a storefront to a store to a driver, on your locations. [Book a demo](https://www.ordering.co/contact/?meeting=demo#book)[See a live demo](https://www.ordering.co/demo/)