Toast Scheduled Third-Party Orders in All To-Go: Plan Ahead, Don't Fire Early

Quick answer: Toast's product update dated October 16, 2026 says that restaurants in the limited All To-Go release through Toast Test Kitchen, on Toast POS 2.119 or later, now see scheduled orders from third-party delivery services as soon as they're confirmed. They show up with their due time and channel. To find them, open Payment Terminal on the Toast POS app, select the All To-Go view, then the Scheduled tab. Before this, Toast says, those orders often arrived as ASAP orders shortly before they were due, which left the kitchen little time to prepare. The update doesn't name any delivery services, though. Toast's DoorDash and Uber Eats guides, updated October 20, still say viewing future scheduled orders isn't supported. Treat channel coverage as unconfirmed until Toast confirms it for your setup.

A row in the tab tells you one order exists, when it's due and which channel it's from. That's enough to name an owner and set a time to check again. Before you commit food or extra labor, confirm the order's items and current status in an order source you already use. It isn't a kitchen ticket. Toast's update doesn't say when these orders fire to the kitchen, whether prep times change, or what the tab shows if a guest cancels. Don't start cooking just because an order is sitting in Scheduled. And if you can't find the tab, treat it as an access question. Don't switch delivery channels off and on to make it appear.

We wrote this from Toast's update and support articles as they read on October 26, 2026. We haven't used the All To-Go view on a Toast device or placed a test order, so what's on your screen may differ.

Who has it, and who doesn't

Three things have to be true before anyone at your restaurant should expect to see scheduled delivery orders early:

• You signed up for All To-Go through Toast Test Kitchen. The update is written for restaurants that did, and it's in limited release with Test Kitchen.
• The device is on Toast POS 2.119 or later. That's the first version Toast lists. Read the version on the device rather than assuming it updated.
• You actually have access. Signing up isn't the same thing. Toast's Test Kitchen article, last updated October 2, 2026, says each beta is Instant Access, Waitlist or Early Access, and that Waitlist and Early Access betas have no committed timeline. The confirmation email after you sign up tells you whether you're on the waitlist or have instant access. Toast doesn't say which type All To-Go is.

One label can mislead you. The update's header is tagged "All Locations" and lists affected countries as "All," but its availability section says it's in limited release with Test Kitchen. Don't read the tag as meaning every Toast restaurant has the view.

Test Kitchen is in Toast Web under Toast account > Test Kitchen > Test Kitchen, and Toast says that page only works on a desktop. Joining a beta is the owner's decision, under Toast's beta participation agreement. Nothing here is a reason to join, and no one should sign the restaurant up just to try this.

Stop rule: if you can't confirm all three, don't tell staff that scheduled delivery orders will show up early. Keep handling scheduled orders the way you do now. Even with all three confirmed, you still don't know which delivery channels are covered. The next section explains why.

Where to look, and which channels it covers

Toast's path: on the Toast POS app, open Payment Terminal, select the All To-Go view, then the Scheduled tab. The update says the order appears with its due time and channel. That's all it documents about what's shown. It doesn't describe opening an order from the tab to see its items. If your screen shows more, don't treat it as confirmed order detail, because Toast doesn't document it.

The update says "third-party delivery services" and doesn't name any. Toast's DoorDash integration guide and Uber Eats integration guide, both last updated October 20, 2026, still list viewing future scheduled orders among the things those integrations don't currently support. Neither mentions All To-Go or Test Kitchen. They may only describe the standard integration, but they don't say so. Ask Toast through your normal support process which channels your setup covers, and treat channel coverage as unconfirmed until Toast confirms it. If you see an order in the tab, that tells you about that one order. It doesn't mean the channel's other scheduled orders will show up there, so keep checking the partner's orders the way you do now.

Orders Hub, a different POS mode, has its own Scheduled tab, and Toast's Orders Hub article has its own rules for it. Don't carry those rules over to the All To-Go view.

If the tab is missing, or an order you expected isn't in it, don't change channel settings to chase it. Toast's third-party channel page covers turning channels on, off or snoozed, and says Toast Web saves and publishes your choice automatically. Turning a channel off stops guests ordering from it. It won't fix a view you may not have. Write down the device, its POS version and what you expected to see, then take it to Toast through your normal support process.

What the tab tells you, and what it doesn't

It tells you a scheduled third-party order exists, when it's due and which channel it came from. That's enough to flag the order, name an owner and set a next check. It isn't enough to commit food or extra labor, because the update doesn't say the tab shows what's in the order or whether it's still live. Get the items, quantities and current status from an order source you already use and are authorized to use, such as the delivery partner's own tablet or merchant portal if your restaurant has one. Write down where you got them and when. If you can't get them, write "unknown," ask the partner or Toast through your usual route, and handle the order the normal way when it arrives.

Toast's update doesn't establish:

• when the order fires to the kitchen, or what has to happen for it to fire
• whether your prep times or the partner's timing changed
• what the tab shows if the guest cancels or changes the order on the partner's side
• which delivery channels are covered, or that every channel behaves the same way

Toast's other help articles don't settle firing either. They describe it differently by partner, and they don't fully agree. The DoorDash articles, including Delays in DoorDash Order Firing, say a future DoorDash order auto-fires when the current time equals its expected fulfillment time minus the prep time, and can show HOLD on the kitchen display until then. The Uber Eats guide says incoming Uber Eats orders fire straight to the kitchen as ASAP, with Uber Eats managing prep time. Toast's older Schedule Future Orders article, last updated September 15, 2026, says DoorDash and Uber Eats scheduled orders fire on the prep time you configure. None of them mentions All To-Go. Our Toast course pacing guide can't fill the gap: it lists integration-partner and future-dated orders among the cases Toast's course pacing pages don't cover.

So keep two jobs apart. Planning means deciding staff, prep levels, packaging and who owns the order, using details you've confirmed. The tab is your prompt to start that work. Starting the food is a separate call. It happens when the order reaches the kitchen the way your orders normally do. The exception is a manager who makes an explicit decision to start it earlier, using confirmed details, under your normal prep and holding procedures. An order showing in Scheduled isn't, on its own, a reason to start.

A fictional example: 30 items due at 12:15

Juniper Row Kitchen is a made-up fast-casual restaurant, and the order below is invented too. The owner signed up for All To-Go through Test Kitchen, the confirmation email showed access, and the manager has read 2.119 on the counter terminal and seen the Scheduled tab. The restaurant has asked Toast which channels its setup covers and hasn't heard back. These are planning steps, not results we recorded.

At 9:30 on Friday morning, the opening manager opens Payment Terminal, then All To-Go, then Scheduled. There's a third-party order due at 12:15 p.m., with one of the restaurant's delivery partners shown as the channel. That's all the row shows. The manager logs it as one sighting: this order, seen at 9:30. It doesn't tell them that partner's other scheduled orders will show up here.

At 9:40 the sous chef, who already handles that partner's orders, looks the order up on the partner tablet the restaurant uses every day. It lists 24 grain bowls and 6 sides, so 30 items, and shows the order as active.

The manager doesn't fire anything. The handoff says: seen in Scheduled at 9:30, due 12:15; items and status confirmed on the partner tablet at 9:40 by the sous chef, 30 items, active. The sous chef owns the order. The plan is 30 bowls and lids pulled before 11:00, and the prep cook staying on the line from 11:30 to 12:30. Nothing gets cooked before the ticket. Kitchen state at 9:30: no ticket on the kitchen display. That's what they saw. Nothing Toast documents says when a ticket should appear, so it doesn't mean anything's wrong. Next check: 11:30, by the manager, in Scheduled and on the partner tablet.

At 11:30 the order is still in Scheduled and still active on the partner tablet, with no ticket, and the manager writes that down. At 11:45 a ticket reaches the kitchen display and the line builds the order the normal way. The packaging is already pulled and the extra cook is already on.

Change one fact: at 9:40 the partner tablet doesn't show the order's items, or the sous chef can't get into it. The handoff says contents: unknown. The manager asks the partner through the restaurant's usual route. They don't pull packaging or add hands for the order on the strength of the Scheduled row alone. If a ticket arrives first, the line handles it like any other order.

Change another: at 11:30 the order is gone from Scheduled and there's no ticket. The manager doesn't conclude it was cancelled or that it fired somewhere else. They mark it unknown and check the partner tablet, then the delivery partner through the usual route if that doesn't settle it. Until then nobody starts anything for it, and if a ticket arrives it's handled the normal way.

One more: the ticket arrives at 12:08 marked ASAP. That's the old pattern Toast's update describes. The manager records the times and channel for Toast. Packaging and the extra cook are in place anyway, which is the point of confirming the order early.

Copy this handoff note

Use one per large scheduled order. Write down what you saw, not what you expect. Leave guest names, phone numbers and addresses off it. The order number is enough.

SCHEDULED THIRD-PARTY ORDER HANDOFF
Toast: Payment Terminal > All To-Go
  > Scheduled tab
Per Toast's Oct 16, 2026 update:
limited All To-Go release (Test
Kitchen), POS 2.119+. Not tested
on our devices.

STOP unless the manager confirmed:
[ ] All To-Go access (Test Kitchen)
[ ] POS version on device: ______
    (2.119 or later)
[ ] Scheduled tab visible
Any box empty: don't expect early
  orders. Handle scheduled orders
  the usual way.
Channels covered: NOT CONFIRMED
  unless Toast confirmed for us.
  One order seen = that order only.

SEEN IN SCHEDULED (row only)
Order # (no guest name): ________
Channel shown: ________
Due time: ________
Seen by / time: ________

CONFIRMED OUTSIDE THE TAB
Source (our usual order system):
  ________
Checked by / time: ________
Items and qty: ________
Status: ACTIVE / CHANGED / UNKNOWN
Unknown? Ask partner or Toast. No
  food or extra labor for it yet.

PLAN (confirmed details only)
Prep owner: ________
Extra staff / station: ________
Prep and packaging: ________
Next check (time, who): ________

KITCHEN STATE (each check)
Time: ______
Ticket on KDS or printed?
  YES / NO / NOT CHECKED
Still in Scheduled?
  YES / NO / NOT CHECKED

NOT KNOWN FROM THIS TAB:
- items, quantities, live status
- which channels are covered
- when or how it fires
- prep time changes
- partner cancels or changes

THE LINE:
- Scheduled is NOT a ticket. Don't
  cook or fire from it.
- Cooking before a ticket: manager
  call, normal prep/hold rules.
- Don't cancel, void or change
  channel settings.
- Order gone, no ticket, anything
  odd: tell the manager.

If you want to see it work

Toast's update suggests verifying it by placing a scheduled order through a third-party delivery service. That's a real order on a real platform, with real charges, so it's the owner's call and should follow whatever test procedure your restaurant already approves, with no real guest details. We didn't place one.

There's a simpler check. Write down the next few real scheduled orders as they come in: when each first showed up in Scheduled (or that it never did), when a ticket reached the kitchen, and whether it came through as ASAP, by channel. That's a record of what happened to those orders. It doesn't confirm that a channel is supported, because only Toast can confirm that for your setup. If something doesn't line up, bring those times to Toast.

Sources

Toast product updates, "View and manage scheduled third-party delivery orders in the All To-Go view in Payment Terminal", October 16, 2026 (CPPL-303). Toast Support, "Beta Testing and Feedback With Toast Test Kitchen", last updated October 2, 2026. Toast Support, "Get Started With the DoorDash Integration" and "Get Started With the Uber Eats Integration", both last updated October 20, 2026. Toast Support, "Delays in DoorDash Order Firing", last updated September 17, 2026. Toast Support, "Schedule Future Orders", last updated September 15, 2026. Toast Support, "Manage Off-Premise Orders With Orders Hub", last updated September 17, 2026. Toast Platform Guide, "Managing orders from third-party online ordering channels", undated. All read October 26, 2026.