Toast KDS Won’t Clear a Ticket When You Swipe Down? What Changed in POS 2.119

Quick answer: it's a deliberate change. In an announcement dated October 14, 2026, Toast says you can no longer fulfill a ticket on the new KDS view by swiping down on it. Toast made the change to prevent accidental fulfillment. If a cook swipes down and the ticket stays on the screen, the screen is working as Toast intends. Finish the ticket with whatever action that device is set up for. Toast names three: a double-tap, the fulfillment dialog or a bump bar, depending on your configuration.

Don't go looking for a way to bring the swipe back. Nothing in the announcement says a setting restores it. Changing Fulfill Items or guest text settings, or switching the screen to legacy view, isn't a fix. Each of those changes how the rest of your kitchen works.

Toast lists the change as first available in Toast POS version 2.119. The announcement covers the new KDS view only (Toast used to call it grid view). It says nothing about legacy KDS view, and its "Generally Available, All Locations" tag doesn't tell you whether a given screen already has 2.119.

One thing may confuse you if you check Toast's documentation. The Action to fulfill section of Toast's KDS overview, as it read on October 21, 2026, still says you can swipe down on the new view to fulfill or unfulfill a ticket. The October 14 announcement is the more specific statement about 2.119, and Toast's own check for it is a swipe that leaves the ticket on screen. We wrote this from those two Toast pages and Toast's linked fulfillment documentation. We didn't test any of it on a Toast device.

Find out what fulfills a ticket on each screen

Before a new crew's first shift, the manager should answer three questions for every KDS screen. Look at the settings. Don't change them.

1. Is it on new KDS view? Open Device Setup from the overflow menu (the ⋮ icon) on the KDS screen and look at KDS View. Toast's overview shows the two options as Legacy View and New Grid View. Back out without saving.
2. Is it on POS 2.119 or later? If you can't confirm the version on that device, treat the change as unconfirmed for it.
3. What is that device's fulfill action? The three actions in the announcement depend on configuration. They aren't three buttons every station has.

• Double-tap. This is set device by device. Toast's KDS configuration quick reference lists one Device Setup setting, Double-tap to Fulfill, Unfulfill, as the place to choose between fulfilling with a double tap and tapping to select a ticket, then tapping Fulfill. The same setting can make a double tap unfulfill instead. Double-tap is only the answer if that device is set to fulfill with it.
• Fulfillment dialog. What happens when you select a ticket depends on Fulfill Items, a Toast Web setting that applies to all devices. With individual item fulfillment disabled, selecting a ticket gives you the option to fulfill all of its items at once. With it enabled, a dialog opens where you pick specific items and select Fulfill.
• Bump bar. This only applies if one is connected. Toast says bump bars require new KDS view and the local data synchronization method. Toast's bump bar instructions give two ways to fulfill a ticket: press the ticket's number button twice in quick succession, or move to the ticket and press FULFILL.

Because double-tap is a device setting, the expo screen and a prep screen can behave differently. Write the answer down for each one.

Rehearse it on fictional tickets before service

This is our recommendation, not a Toast requirement. Use a training or test setup your manager has approved, with made-up orders. Each person who will work a KDS swipes down once on a practice ticket, watches it stay, then finishes it with that device's action. Write down what actually happened on each screen.

Check one thing before anyone touches a practice ticket. Toast documents that expediter fulfillment can send texts to guests or servers and on-screen alerts to server devices when those features are set up. The pages we read don't say that Test Mode stops texts, payments or reports. If you can't confirm that your rehearsal stays out of live guest messages and reports, stop and ask Toast before you run it. Never swipe or fulfill a real guest's ticket just to see what happens.

Use the rehearsal to teach the other rule too. A ticket leaving the screen doesn't make the food ready. In Toast's own new KDS view workflow, the expediter confirms that every item in the order is there before fulfilling the ticket. Fulfill when the station's work is actually done, not to clear the screen. Our soft opening checklist covers the rest of a pre-opening run.

When this change doesn't explain it

• The screen is on legacy view, an older version, or you can't tell. The announcement doesn't tell you how that device behaves.
• The configured action doesn't clear the ticket either. This release doesn't cover that. Toast documents two cases worth noting: preview tickets can't be fulfilled, and when sequenced fulfillment is on, fulfilling before the required station needs an override from someone with Manager access. Otherwise, record the device, view, version, action and what happened, and contact Toast. Don't keep swiping or change settings to make it clear.
• Someone fulfilled the wrong ticket. Toast's recall and unfulfill options have limits. Our Toast KDS multi-select guide explains them, along with the Fulfill Items trade-off, so we won't repeat it here. If guest texts fire on fulfillment, our order-ready texts guide covers choosing one trigger.

Copyable crew note

Print one for each KDS screen and have the manager fill in the blanks. It carries its own scope, stop rule and practice check, so it makes sense without this page.

KDS NOTE: SWIPE DOWN NO LONGER FULFILLS
Applies to: Toast new KDS view, POS 2.119 or later
(Toast announcement, Oct 14, 2026). Not confirmed for
legacy view, older versions or an unchecked screen.

Screen: ______________  View checked: _______________
Version: _____________  Checked by/date: ____________
To fulfill a ticket on THIS screen: _________________
(manager fills in, e.g. double-tap / tap ticket, then
Fulfill / bump bar)

1. Swiped down and the ticket stayed? That's expected.
   Don't keep swiping.
2. Fulfill only when this station's work is done.
3. Use the action written above. Don't change device
   or kitchen settings.
4. STOP and get the manager if the action above is
   blank, it doesn't clear the ticket, a ticket clears
   that shouldn't have, or this screen isn't on new
   KDS view and 2.119.

Manager: record screen, view, version, action and
result, then ask Toast.

BEFORE ANY PRACTICE (manager checks first):
- Made-up tickets only. Never swipe or fulfill a real
  guest's ticket to see what happens.
- Confirm the practice setup can't send live guest or
  server texts or alerts, or change live payments,
  reports or order records.
- Manager approval, made-up tickets or a "Test Mode"
  label don't prove that on their own.
- Can't confirm it? DON'T practice. STOP, get the
  manager, and ask Toast before anyone practices.
Practice only on made-up tickets in a training setup
the manager has approved, after the check above.