Get startedGet started
Get startedContact support

TableSync Kitchen

Clarity at the pass, round by round.

TableSync Kitchen is a Kitchen Display System (KDS) for restaurants: dispatched work, preparation detail, elapsed time and protected state changes.

AndroidRelease testingReviewed .
Get startedCompare pricingProduct support
Kitchen board with three preparing tickets; Table 12 round 2 has elapsed six minutes.
Dispatched kitchen board · Demonstration data

Operational detail, kept together.

Kitchen board with three preparing tickets; Table 12 round 2 has elapsed six minutes.

Dispatched tickets with table and round

Kitchen ticket HV-2412: Table 12, round 2, six minutes elapsed, burger modifiers and No onion note.

Elapsed-time bands measured from dispatch

Dispatched tickets with table and round

Built around the work of service.

The kitchen needs to know what is ready to prepare, what belongs to this round and what has been waiting.

TableSync Kitchen keeps dispatched work separate from unfinished order entry, with preparation context on the ticket.

  1. Dispatched work reaches Kitchen; an open draft does not.
  2. Prepare with the table, round, choices and notes in view.
  3. Mark preparation ready. Delivery fulfilment remains a separate restaurant workflow.

Look closer at the operation.

Dispatched kitchen board

Kitchen board with three preparing tickets; Table 12 round 2 has elapsed six minutes.
Dispatched kitchen board · Demonstration data

Kitchen ticket detail

Kitchen ticket HV-2412: Table 12, round 2, six minutes elapsed, burger modifiers and No onion note.
Kitchen ticket detail · Demonstration data

What the product supports.

Detail at the pass

  • Dispatched tickets with table and round
  • Variants, modifiers, quantities and notes
  • Service-type context

Kitchen tickets do not expose guest contact or payment details.

Time, attention and action

  • Elapsed-time bands measured from dispatch
  • Active, Recent and Check views
  • Expected-state actions protect against conflicting device updates

Elapsed time is measured from dispatch; it is not a predicted preparation time. Station filtering is available; a filtered device cannot complete work it cannot see. There is no independent bump, undo or recall workflow. Physical audible-alert acceptance remains under validation.

Part of the same restaurant operation.

Product and platform availability.

TableSync product availability by platform
ProductPlatformsStatus
TableSync KitchenAndroid application in release testing.
Android
Release testing

Reviewed . Availability depends on the product, approved release and device setup. Public store listings are not provided.

View platform availability

Questions about this product.

When does work appear in Kitchen?

After dispatch. Unsent rounds and unfinished drafts are not preparation tickets.

Is elapsed time a preparation estimate?

No. It is the time since dispatch, with bands that call attention to older work.

Can filtered devices complete an entire order?

A station-filtered device cannot complete work it cannot see. This is not an independent station-completion system.

What happens if two devices act together?

Actions carry expected-state checks to help devices converge without silently overwriting one another.

Which devices are supported?

The Android application is in release testing. Physical device and audible-alert acceptance must be confirmed for the intended setup.

See the operation

Find the right setup for your restaurant.

Explore the products, discuss your setup and confirm the availability that applies to you.

Get startedBook an optional demo