Square KDS, routed the way your kitchen works

Square KDS in your operation

Kitchen displays make the incoming order visible where preparation happens. Roots helps map Square KDS station routing to your menu and kitchen layout, so the team can distinguish the work each station owns and keep the order moving toward a complete handoff.

Treat delivery of the purchase as part of the transaction

A kitchen, machine or self-service station needs more than a successful charge: it needs to know what to deliver. Map the message or ticket that connects payment to fulfillment, and decide which staff member or system confirms the handoff. Physical placement and connectivity belong in that operating plan.

The important exception is a payment that completes while delivery does not. Define how the operator finds the transaction, confirms what the customer received and authorizes the next action. Record the order and payment references together so a customer-service case can be resolved without charging again or issuing an unexplained refund.

Decisions to make before setup

Test orders with items prepared at different stations, a modifier and a cancelled item. Follow the ticket through each preparation step and confirm what happens when a display is unavailable or staff need to review an earlier order.

Use the setup discussion to settle kitchen stations, ticket routing, preparation ownership and order channels. Put the decisions into the staff procedure and test transactions, so the configuration can be checked against actual work. Identify which records already exist in your software and which will need to be created, imported or connected during the project.

Reporting and day-to-day review

Focus the review on order queues, preparation exceptions, item routing and service bottlenecks. Decide who checks those records, which exceptions require action and where the final totals are reconciled. Keep a payment or order reference attached to every correction so the next employee can understand the history rather than reconstructing it from an amount and a date.

Plan the setup around your business

Prepare a representative transaction and the records your team uses today, including the reports that must match after a payment. Roots uses the free review to define the workflow, the systems involved and the handoffs that need to improve. A concrete transaction is more useful than starting with a list of unrelated features.

Request a quote for the setup or project you need. The scope should identify configuration, migration or development work, staff training and the checks used to confirm readiness. Agree the operating owner for each handoff before launch, then review the first working period against the same cases used in the setup.