Sold out at the counter, still showing online? Check each ordering channel first

Marking an item sold out, or 86'd, in your POS doesn't mean every online ordering channel hides it in the same way. Each connection behaves differently. Before changing settings or paying for a fix, run a short read-only check: one item, one channel, one location, written down with the time. Take any mismatch to the vendor that supports that connection.

Three different switches that get mixed up

• Item availability. One dish or product is unavailable right now.
• Menu hours. A menu or section is only offered at certain times.
• Store pause or snooze. The whole store stops taking orders on one channel for a while.

When a customer orders something you ran out of an hour ago, it's tempting to blame “the integration.” A more useful question is narrower: which switch did we use, and which channel didn't follow it?

What Toast documents

Product check: November 1, 2026.

Toast's guide to 86ing an item covers this exact symptom. Its first suggestion is that the same item may sit in more than one place on your menu, and each instance has to be marked out of stock separately. It also says changes can take a few minutes to sync across channels. Catering is separate: Toast uses Item Limits for catering instead of 86, so catering orders are outside this check.

Toast's general third-party limitations guide says the ordering partner controls how items are displayed. Partners differ on whether 86'd items still appear.

Its DoorDash direct integration guide describes near-real-time menu and 86 updates for that named connection. That connection is separate from aggregator setups and from Toast Delivery Services, and results depend on location, setup and supported menu features. Toast deducts DoorDash orders from its own inventory counts, but DoorDash's stock check only confirms an item isn't 86'd. It doesn't check how many are left, so an order can still come through for more than you have. Once the integration is live, the guide names DoorDash Merchant Support as the first contact for integration issues, and Toast Customer Care for menu re-syncs and other Toast-side setup.

That guide also describes menu hours in two ways we couldn't reconcile, so we're not giving hours advice here. If hours matter for your location, ask Toast or DoorDash how it is set up.

Not on Toast? The same principle applies. Find the help page for each specific connection, not just for the POS in general.

How to check without changing anything

1. Wait for an ordinary sell-out. When an authorized person marks the item unavailable in the POS as part of service, note the time. Don't mark anything unavailable just to run this check.
2. Look, without editing, at whether that item appears in more than one place on your POS menu.
3. After a few minutes, open each channel's public listing for your location, as a customer would see it. Don't place an order, and don't touch any settings.
4. Record what you see and the time you saw it. If a channel still shows the item, tell whoever is authorized for that channel straight away. The sheet is a record, not a reason to wait.
5. Note how each channel is connected: direct integration, through an aggregator, or a separate tablet. If you don't know, that is the first question for your vendor.
6. Repeat the check when the item comes back.

A copyable channel check sheet

These columns are our suggestion, not fields from any vendor.

Synthetic example, not a customer result

A counter-service restaurant sells out of its lunch special at 1:15pm. The shift lead, who is authorized to 86 items, marks it in the POS and sees that it appears only once on the menu. At 1:25 the shift lead checks three channels:

• Direct DoorDash listing: shows the special as unavailable.
• A second marketplace, connected in this example through an aggregator: still lists it.
• The restaurant's own ordering page: shows it as unavailable.

The shift lead records all three, changes no settings, and tells the general manager straight away. The general manager, who is authorized on the second marketplace account, decides what to do on that channel for the rest of service and raises the mismatch with the aggregator's support that afternoon. Any order already placed for the special goes through the restaurant's usual routine for that channel.

The sheet also notes a second point. The special is capped at a set number each day. Even with a count tracked in Toast, DoorDash's stock check doesn't look at how many are left, so someone still marks the special unavailable when the last one goes.

Owner at the counter or a staffed kitchen?

If you run the counter yourself, keep the sheet next to the POS and fill in a row when you are marking something unavailable anyway. If a channel is still showing the item, handle that channel as you normally would first, then write the row.

With shift leads, decide three things: who records, who contacts vendors, and who may change channel settings. These can be three different people. Only people authorized on each account make changes.

What this check is not

It records what each channel shows. It doesn't count portions, prevent overselling, decide whether food is safe to serve, confirm allergen information, or settle refunds and payouts. Those stay with the people and processes already responsible for them.

When automation is worth discussing

Only after the vendor has answered. A mismatch can come from setup, a duplicate menu item, sync timing, an unclear source or something else, and the vendor can tell you which applies to your connection. If the vendor confirms a repeated mismatch that the connection can't handle, that specific gap is worth examining, starting with options the vendor already offers.

Next step

Next time something sells out and is marked unavailable as usual, check two channels and fill in one row. If the row shows a mismatch, raise it with the vendor that supports that connection. If the gap is still there afterwards, Abundance Applied is glad to talk that one channel through with you. We don't need access to your accounts.