Toast KDS Multi-Select: Check Item Fulfillment and Guest Texts Before Switching

Quick answer: Toast's September 23, 2026 update lets staff select several tickets on the new KDS view and fulfill them together. To use it, Fulfill Items must be set to Disable individual item fulfillment. That setting also switches off item-by-item fulfillment, including food runner fulfillment on expediter screens. Before you change it, decide whether your kitchen gains more from batch bumping than it loses from item checks. Then write one rule for the pass: a ticket gets selected only when every item on it is physically there. In Toast, fulfilled is a status someone taps. It doesn't prove the food is ready, and when guest kitchen texts are configured, the designated expediter fulfillment triggers the message.

Who this is for, and access limits

This is for owners and kitchen managers at Toast locations already on the new KDS view, and for the expos and line cooks who bump tickets. Check these limits first:

• Version: Toast says the feature is first available in Toast POS 2.117.
• Availability is unclear: The announcement's header is tagged "Generally Available, All Locations", but its Availability section says "This change is in limited release. Not all Toast locations have access to this change." We rechecked on September 24 and the page still says both. Plan for limited access. If you can't find multi-select after updating, ask Toast before you change settings.
• New KDS view only: Toast's KDS overview says new KDS view works only with the local data synchronization method.
• Test Mode: Toast's own verification steps use a location in Test Mode.

This guide is based on Toast's documentation. We didn't run it on a live Toast account.

What changes when you switch the setting

Toast's reference also says restaurants that show all items from an order on a single ticket typically use Enable. If your runners send dishes out one at a time from the expo screen, switching to Disable changes how they work. It isn't just a new button.

Selecting a ticket isn't the same as the food being ready

Toast describes its expediter flow like this: prep stations fulfill items, the expediter ticket turns green, and then the expediter fulfills the ticket once the items are physically at the expediter station. Multi-select lets staff fulfill several selected tickets together. It does not check what is on the pass.

• Guest texts: Toast can send an SMS when the expediter marks an order fulfilled. The announcement does not document notification behavior for a batch. Treat early texts as a risk to test for each selected ticket; do not assume the batch sends one message or that every device role has the same trigger. If a counter tap in Orders Hub also sends a ready text, choose one trigger. Our Toast order-ready texts guide covers that choice, so we won't repeat it here.
• Unfinished tickets: In a batch, one wrong ticket gets fulfilled along with the right ones. Once a ticket is fulfilled, it disappears from the screen.
• Recovery has limits: Recall brings back the most recently fulfilled ticket on that device; repeated Recall brings back the next most recent ticket. Both Recall and Unfulfill are limited by the Recently Fulfilled Timeframe. To choose a specific mistaken ticket, use Show recently fulfilled and Unfulfill rather than assuming Recall will select the one you meant. The recall documentation doesn't say anything about retracting a text that was already sent, so treat a sent text as sent.

Fictional example: a takeout rush at the pass

An expediter screen shows four takeout tickets. Kitchen fulfillment texts to guests are on.

• #101, #102 and #104 are bagged and sitting on the pass.
• #103's ticket is green because the fry station bumped its item early, but the fries are still in the basket.

The expo selects #101, then adds #102 and #104, and fulfills all three together. #103 stays on screen until its fries are bagged. If #103 had been tapped by mistake, the fix is to recall or unfulfill it right away and tell the counter that the guest may already have a ready text. Do not assume recalling the ticket retracts a text already delivered.

Copyable pass rule and Test Mode check

PASS RULE: KDS MULTI-SELECT
1. Select a ticket only when every item on it is on the pass.
2. A green ticket means the stations tapped fulfilled. It does not mean the order is bagged.
3. Before fulfilling a batch, read every selected ticket number aloud.
4. Tapped a ticket by mistake? Recall or unfulfill it now, then tell the counter.
5. The expo lead owns the pass. One person bumps the expediter screen at a time.

1. In a Test Mode location, check that your devices are on POS 2.117 and new KDS view.
2. Write down your current Fulfill Items value (Kitchen > Printers, tickets, & KDS devices > Kitchen and ticket setup > Ticket Screens) so you can switch back.
3. In that Test Mode location, set it to Disable individual item fulfillment, then save and publish. Schedule any later production change outside service so staff can check the changed workflow first; that is our rollout recommendation, not a documented multi-select requirement.
4. Send several test orders using only a test phone number controlled by your team, never a guest number. Select one ticket, add two more, and fulfill them together.
5. Record what happened: which tickets cleared, how many texts arrived and when, and whether recall and unfulfill brought each ticket back. The pages we read don't say whether Test Mode sends texts. If none arrive, confirm with Toast which action triggers them before you go live.
6. Repeat on each device role you use. The announcement doesn't say whether prep stations and expediters behave differently.
7. If you route modifiers to a different prep station than their parent item, check the fire timers too. Toast's September 23 fix note says 2.117 corrects the negative fire times new KDS view used to show in that setup.

How to decide

Owner: Batch bumping is most useful where orders leave as whole tickets, such as counter service or takeout. Keep individual item fulfillment if your runners depend on item check marks. Manager: Change the production setting only after the ticket selection and recovery checks pass. If guest texts are enabled, also confirm the expected message count and timing; Test Mode silence does not establish production notification behavior. Resolve that gap with Toast before switching. Brief the pass rule before the first shift. Staff: If you aren't sure a ticket is complete, leave it on the screen.