Last updated: May 12, 2026, 2:20 PM
If third-party orders fail or show as "canceled," follow this article’s troubleshooting steps to resolve the issue.
In this Article:
Applies to: Toast Web, Toast POS, DoorDash, Grubhub, Uber Eats
Permissions needed:
What you'll accomplish: Identify whether orders are blocked at the partner side, the Toast side, or the POS device, and apply the right fix in under 15 minutes for the most common causes.
For most cases, this three-step path resolves the issue:
If the test order doesn't arrive, continue to the Quick Fix table to match your symptom to a cause.
| Symptom | Most Common Cause | Quick Fix | Self-Service? |
|---|---|---|---|
| Orders aren't coming through, channel shows closed or snoozed | Third-party channel set to All off or snoozed | Set the channel to All on in Toast Web > Takeout & delivery > Third-party ordering | Yes |
| Orders show on the partner site but not on the Toast POS | Menu visibility, menu incompatibility, or archived marketplace facilitator tax | Verify channel visibility, resync the menu, or unarchive the tax (see Step 2) | Yes |
| Orders show "canceled" or "not synced" with the partner account | Account linking issue at the partner side | Verify the integration in Toast Web; contact the partner to confirm account linking (see Step 2) | Mixed |
| Orders are in the Orders Hub but not printing or appearing on the kitchen display | Ticket display options, prep station routing, printer, or auto-fire device | Check KDS ticket display, prep station routing, and auto-fire device (see Step 3) | Yes |
| You've never received an order from this partner | Onboarding checklist not complete or integration not purchased | Complete the Setup checklist in Toast Web (see Step 2 → Never received) | Yes |
| All channels (DoorDash, Grubhub, Uber Eats) show closed at once | POS offline, Internet outage, or Toast service disruption | Check internet, POS device status, and the Toast status page | Mixed |
| Outage on the partner side | Partner platform service disruption | Check the partner's status page (links in Before You Contact Customer Care) | Yes |
| Orders worked yesterday and stopped today, no other changes | Snooze or auto-pause from inventory or hours | Toggle the channel off and back on; check Online Ordering Hours | Yes |
Start at the POS device that should be receiving the orders. The Orders Hub tells you whether orders are reaching Toast at all — that single check decides which branch to follow next.
Expected outcome: You can confirm whether the missing orders are present in the Orders Hub or not.
If no third-party orders are visible in the Orders Hub, the issue is upstream of the POS — either at Toast Web (channel disabled, menu out of sync, mapping incomplete) or at the partner (account linking, onboarding incomplete).
The next check depends on whether you've ever received an order from this partner:
Work through the causes below in order. After each step, place a test order through the partner app to confirm whether the issue is resolved before moving to the next step.
This is the most common cause. The channel can be paused individually or in bulk, and a snoozed channel won't deliver orders to the POS until it's reactivated.
Expected outcome: The channel reactivates immediately, and the partner site shows your restaurant as accepting orders again.
For more on snooze and on/off controls, see "Manage Third-Party Availability With Snooze and On/Off Functions."
If the menu isn't marked visible to online-ordering partners, the partner site has nothing to display and orders won't sync.
Expected outcome: The sync completes within five to ten minutes and your test item disappears from the partner site.
For more, see "Adjusting Menu Visibility for a Third-Party Online Ordering Channel."
Some menu and pricing settings — like time-specific pricing, pre-modifiers, subgroups, prompt-for-quantity, Pizza Menu Management, and time-restricted menus — can't sync to third-party partners and will silently fail.
Expected outcome: The sync completes within five to ten minutes and the menu appears correctly on the partner site.
This applies only if your restaurant uses Toast Multi-Location Management (MLM) and integrates with Grubhub. If you don't recognize the term "target/owner" for dining options, you most likely don't use MLM and can skip this step.
Expected outcome: Each partner has takeout and delivery dining options mapped to its account, and a test order successfully routes to the right option.
Note: If you're part of a restaurant group and don't have edit access to dining options, contact your restaurant operations team. If you are restaurant operations and can't add the options, contact Toast Customer Care.
Each third-party partner needs a payment option in Toast Web. These are added automatically during setup; if one was removed, orders from that partner can't post.
Expected outcome: Each partner has its corresponding payment option configured, and orders post correctly to that method.
If marketplace facilitator taxes are missing or archived, orders that depend on them won't post to the POS.
Expected outcome: Both Marketplace Facilitator Tax rates are active in your tax rates list.
Uber Eats accounts can stay linked to a previous integration (an old POS, or an aggregator like Chowly, ChowNow, Checkmate, or Otter), which blocks the Toast integration from delivering orders.
Expected outcome: The Uber Eats account shows Toast as the sole active integration, and orders begin flowing to the Toast POS.
If someone updated the menu or hours directly on the partner platform, those changes can override the Toast sync until the partner re-ingests the Toast menu.
Expected outcome: The partner-side menu matches the Toast menu, and new orders flow through correctly.
Some partners require a manual menu sync after configuration changes. After completing the steps above, sign in to the partner site and run a menu sync.
Expected outcome: The partner site reflects the latest menu, and a test order succeeds.
If none of the above resolve the issue, continue to Before You Contact Customer Care.
If this is the first partner integration and no orders have arrived yet, the issue is almost always in setup. Work through the causes below in order.
The integration won't go live until every checklist step is finished — and for Uber Eats and Grubhub, the checklist stays marked incomplete until your first order arrives.
Note: Grubhub onboarding can take one to two weeks to complete after the checklist steps are done.
Expected outcome: All checklist items are marked complete (DoorDash) or all action items are done (Uber Eats and Grubhub will mark complete after the first order arrives).
Verify the integration is on your account.
Expected outcome: The integration appears in Takeout & delivery > Third-party ordering and is set to All on.
Each partner has its own onboarding requirements (EIN, bank account, business documents) separate from the Toast checklist.
Expected outcome: The partner confirms your account is active and integrated.
If your online ordering hours don't cover the time orders are being placed, orders won't reach the POS.
Expected outcome: Your online ordering hours match the times you're available to accept orders.
If you operate multiple Toast locations, each one needs its own active partner account. A single partner account shared across two Toast locations causes orders to land at the wrong location or not at all.
Expected outcome: Every Toast location has a corresponding active account on the partner side.
Same as the Uber Eats account-linking step above. Sign in to your Uber Eats portal and contact Uber Eats customer support to confirm Toast is the only active integration and that menus are purged and re-ingested.
If none of the above resolve the issue, continue to Before You Contact Customer Care.
If you can see the orders in the Orders Hub but they aren't printing or appearing on a kitchen display, the issue is on the device side — KDS routing, prep station mapping, printer, or auto-fire device.
If you use the Kitchen Display System (KDS), the screen that should receive third-party tickets needs to be configured to display them.
For more, see "Configure Ticket Routing and Filter Tickets on Your KDS Device."
Expected outcome: New third-party tickets appear on the configured kitchen screen.
If items on the third-party menu aren't mapped to a prep station, the order won't print or display.
Expected outcome: New third-party orders route to the correct prep station and appear on the corresponding screen or printer.
If a printer is dedicated to third-party tickets but isn't printing — and you haven't confirmed the printer works for any tickets — the issue is likely network, hardware, or configuration.
See "Get Help: My Printer Isn't Working" for model-specific troubleshooting.
Expected outcome: The printer prints both Toast and third-party tickets reliably.
The auto-fire device must be online and configured correctly for third-party orders to fire to the kitchen automatically.
Expected outcome: The auto-fire device is online and orders fire to the kitchen automatically.
If none of the above resolve the issue, continue to Before You Contact Customer Care.
If you've worked through every step above and still can't receive orders, the issue likely needs Customer Care or partner-side intervention. Before you reach out, gather the information below — it speeds up resolution and rules out the most common backend causes.
Empty menu structures (a menu, group, or item with no children) can silently break the sync. Customer Care can check for empty objects on your account.
An active change of ownership or legal entity can delay third-party integration setup. If your business is transitioning, contact Toast Customer Care to confirm account status.
Reach the Grubhub Onboarding Fulfillment team at onboarding@grubhub.com or call (877) 585-7878 for the Grubhub Account Owner. Confirm a Grubhub account exists before contacting Toast.
When you contact Toast Customer Care, include:
To check whether your integration is active, sign in to Toast Web and navigate to Takeout & delivery > Third-party ordering. If the partner appears with a status of All on, the integration is active and accepting orders. If the partner doesn't appear, navigate to Integrations > Configure Integrations to confirm the integration is purchased.
If you update your menu in Toast Web and select Save and Publish all changes, the change syncs to all connected third-party partners automatically within five to ten minutes. To test, toggle an item's show/hide status, save, publish, and refresh the partner site to confirm the change.
If every third-party channel shows closed at once, the most common cause is that your POS is offline or your internet connection has dropped. Check your network connection and POS device status first. If the POS is online and the channels still show closed, navigate to Takeout & delivery > Third-party ordering in Toast Web and confirm each channel is set to All on.
If the Toast POS is canceling DoorDash orders, this isn't covered by the standard third-party troubleshooting steps and usually requires Customer Care to review your account. Gather the affected order numbers and the time of cancellation, then contact Toast Customer Care so they can investigate the cancellation triggers on your account.
Recovery depends on the partner. DoorDash and Grubhub may sync some pre-outage orders to your POS once your restaurant is marked online again — you should start preparing those orders as they arrive. Uber Eats orders placed during an Uber outage will not sync to the POS, even after the partner recovers.