86 List Automation: Sync Every Ordering Channel the Minute the Kitchen Runs Out

Discover how 86 list automation syncs every ordering channel the moment your kitchen runs out of an item, cutting errors and saving staff time.

Running out of an ingredient is normal. What happens next is where restaurants lose money. If you sell food through more than one channel — a dining-room POS, a website ordering page, a QR-code menu, and third-party delivery apps like DoorDash and Uber Eats — then a single sold-out special has to be marked unavailable in every one of those places at once. In practice, that almost never happens by hand. This guide covers 86 list automation: what it is, why the manual version breaks down, what a good automated flow looks like, and how to build one end to end for your restaurant, bar, cafe, or food hall.

Why Manual 86ing Fails When You Sell on More Than One Channel

"86" is kitchen shorthand for an item that's out. The fish shipment came in short. The special sold through at 6:40 on a Saturday. The fryer went down mid-shift. Whatever the cause, the moment an item is unavailable, a clock starts ticking — and every minute it stays live on a channel you forgot to update, you're taking money for food your kitchen cannot cook.

Here's how the manual version of that process typically unfolds:

  1. The kitchen runs out. A cook calls it out, or a server comes back to the pass and finds out the hard way.
  2. Somebody marks it on one channel. Usually whichever channel is closest to whoever noticed. Often that's a handwritten 86 list taped near the expo station — a list the new host has never been shown and never checks.
  3. The other channels keep selling. The server keeps recommending it tableside because nobody told the floor. The website ordering page keeps accepting the item because that's edited in a completely different dashboard than the POS. The QR-code menu at the tables still shows it as available. DoorDash and Uber Eats keep charging customers for a dish the kitchen already knows it can't make.
  4. The fallout arrives in pieces. Orders get canceled or remade. Servers comp dishes to keep tables happy. Delivery customers request refunds and leave one-star reviews that mention the item by name. A driver made a trip for nothing.
  5. Re-listing gets forgotten. When the fish delivery arrives the next morning, or the fryer gets fixed at 9 p.m., someone has to remember to flip the item back on — on every channel, again. When they forget, the item sits invisible and unsellable overnight, and you've lost a full day of sales on a dish that was actually fine.

The deeper problem is structural, not personal. Each channel is edited in a different dashboard with a different login, a different menu editor, and a different set of steps. Nobody is lazy; the work is simply scattered across five places, and it has to be done instantly and simultaneously during the busiest hour of the night. A process that requires five people to remember five updates during a dinner rush will fail regularly. The only question is which channel gets missed — and it's usually the channel customers actually order from, rather than the channel somebody happened to remember.

There's also a visibility problem. When the 86 process lives on paper and in memory, nobody connects tonight's three 86s to the fact that the same item has been 86'd every Friday for a month. The pattern — an item that runs out at the same time, on the same day, week after week — is exactly the information purchasing and prep need to fix the root cause. A paper list can't surface it. A logged, timestamped record can.

What 86 List Automation Does Instead

A well-built automated flow replaces five dashboards and a paper list with one trigger and a set of automatic actions. The goal is simple: the kitchen makes one call-out, and every sales channel reflects reality within moments — then reflects it back when the item returns.

Here's what a complete flow covers:

The result is a shift where "we're out of it" takes effect everywhere in under a minute, comes back automatically, and leaves behind a record that makes next week's ordering smarter.

How to Build 86 List Automation End to End

You don't need a developer or a custom build. A no-code automation platform like Automate Anything connects your POS, your ordering channels, and your messaging tools with visual workflows. Here's the full build, step by step.

Step 1: Connect Your POS to Your Menu Platforms

Start by mapping every channel where the item can be sold:

For each one, connect it to your automation platform using whatever integration is available — most modern POS systems (Square, Toast, Clover, Lightspeed, and similar) offer native connectors or webhooks, and delivery platforms expose menu availability through their partner integrations or aggregator services. In your automation platform, authorize each connection once and note exactly which menu, location, and item IDs correspond to each dish. If you operate multiple locations or a food hall with several vendor stalls, set up the connection so each vendor stall's menu is a separate, clearly labeled scope — you'll see why that matters in the edge cases section below.

Practical tip: Create a test item ("ZZ Test Dish") on every channel first. Run your entire flow against the test item before you trust it with the salmon.

Step 2: Build the Trigger and the Fan-Out

The trigger is the moment an item is marked 86. You have two common options:

Then build the fan-out — one trigger, several parallel actions:

  1. Update the item's availability on the website ordering menu to unavailable (or hide it entirely, depending on your menu setup).
  2. Update the same availability on the QR-code menu.
  3. Push the out-of-stock status to each connected delivery platform.
  4. Send a text notification to the front-of-house team (more on this in Step 4).
  5. Log the event — item name, timestamp, day of week, time of day — to a spreadsheet or database for the reporting step.

Keep each channel's update as a separate action within the same workflow rather than chaining them in sequence. If one platform's update fails, you want the others to have already gone through, and you want to know which one failed.

Step 3: Build the Restock Flow

Re-listing deserves its own workflow, not an afterthought:

  1. Trigger: Either the reverse of the original trigger (the POS item is marked back in stock, or a "restocked" button is tapped on the kitchen checklist) or a scheduled job that checks for items flagged as restocked.
  2. Actions: Re-enable the item on the website menu, the QR menu, and each delivery platform — the same fan-out, in reverse.
  3. Confirmation: Send a message to the manager on duty or a kitchen channel: "Salmon re-listed on all channels at 9:14 p.m." That confirmation is the safety net. If any channel fails to update, the workflow sends an alert naming the specific channel, so a human fixes one thing instead of discovering a dark menu the next afternoon.

Consider adding one guardrail: require the restock confirmation to be acknowledged (a simple tap or reply), so a failed re-list can't silently sit overnight.

Step 4: Set Up the Front-of-House Notification

The floor team needs to know fast, in a place they'll actually see. A text message to a group — or a message to a shared Slack or team-chat channel — beats a chit at the printer, because servers aren't standing at the printer.

Build the notification with:

Send it to a distribution group that includes servers, hosts, and bartenders — anyone who talks to guests about food. Update the group roster whenever staff changes, and test it monthly by running an 86 on a harmless item.

Step 5: Build the Weekly 86-Pattern Summary

This is the step most operators skip, and it's where the automation pays for itself beyond just avoiding refunds. Once every 86 event is logged with an item name, a timestamp, and a day of week, set up a scheduled job that compiles a weekly summary:

Deliver the summary by email to the owner, kitchen manager, and whoever handles purchasing every Monday morning. Over time this turns 86ing from a scramble into a forecasting input: adjust prep counts for the Friday item, raise the par on the early-evening seller, and put the chronically short item on a standing order review.

If you'd rather start from a template than a blank canvas, the workflow guides in the Automate Anything blog walk through patterns like trigger-and-fan-out builds, notification routing, and scheduled summary reports that apply directly to this setup.

Common Mistakes to Avoid

Edge Cases Worth Planning For

Food halls and shared kitchens. In a food hall, each vendor stall runs its own menu, its own stock, and often its own POS, while customers may order from multiple stalls in a single transaction. Build the automation per vendor stall: each stall's 86 trigger updates only that stall's menus and delivery listings, and front-of-house notifications go only to that stall's team. A shared ordering page needs per-stall item availability, so confirm your ordering platform supports item-level status by stall before you commit to a design.

Equipment outages, not just ingredient shortages. A dead fryer or a down espresso machine can 86 a dozen items at once. Build a second trigger — a "station down" button — that marks a predefined group of items out simultaneously, and a matching "station back" flow that re-lists the whole group. This turns a fifteen-minute scramble into two taps.

Item variants. If the kitchen is out of the gluten-free bun but not the regular one, an all-or-nothing 86 hides a dish that's still half-sellable. Where your platforms support variant-level availability, 86 at the variant level; where they don't, your front-of-house notification should state precisely what's out so servers can offer the workaround.

Dayparted menus. A brunch item 86'd at 11 a.m. shouldn't appear unavailable on a dinner menu that shares the same underlying record — and vice versa. Confirm your menu platforms treat dayparted items as separate entries, and scope your triggers accordingly.

Delivery platform latency and limits. Some third-party platforms update availability quickly; others may take a bit longer or require updates through an aggregator. Treat the platform's own confirmation as the source of truth, and have your workflow alert you if a channel doesn't confirm within a reasonable window. Build the expectation into your front-of-house message ("apps updating now") rather than promising instant sync you can't control.

Preorders and catering. An item 86'd tonight may still appear in a preorder placed for Friday. Decide your policy explicitly — usually, preorder availability should follow the day the order is for, not the day it's placed — and make sure your 86 trigger only affects same-day channels.

How 86 List Automation Differs from Adjacent Automations

The food-service automation space is crowded with things that sound similar. It's worth drawing clean lines so you build the right thing:

You may eventually run all of these. They solve different problems, and 86 list automation is the one that directly protects the guest experience across your order channels.

A Checklist for Evaluating Your Setup

Before you consider your 86 process "done," work through this list:

If you can't check most of these boxes, you don't yet have automation — you have a faster paper list.

Frequently Asked Questions

Do I need to change my POS to automate my 86 list? Usually no. If your POS can fire a webhook or event when an item's availability changes, you can build on top of it as-is. If it can't, a kitchen checklist app with an "86" button works as the trigger instead. The automation platform handles the rest.

Will the delivery apps update instantly? Most platforms process availability updates quickly, but timing isn't something you fully control, and some channels route through aggregators. Design for resilience: confirmations, failure alerts, and a front-of-house message that says "apps updating" rather than implying the change is universally instant.

What happens if my internet goes down mid-rush? This is a fair concern. Your POS can usually keep selling offline, but channel pushes require connectivity. Keep a documented fallback — one person assigned to manually update the two or three most important channels — and treat the automation as your normal operating path, not your only one.

Can one workflow cover multiple locations? Yes, but scope it deliberately. Each location should have its own menu connections and its own notification group, driven by which location's POS fired the trigger. Never let one location's 86 hide an item at another location that still has stock.

Is this worth it for a small cafe with only two channels? Often, yes — two channels is still two places to forget, and the front-of-house notification plus the pattern log deliver value even at small scale. The build is the same; it's just shorter.

We're a food hall — do vendor stalls share one workflow? Each vendor stall should have its own scoped trigger, its own channel connections, and its own notifications. Shared infrastructure is fine underneath, but a stall's out-of-stock must never leak onto another stall's menu.

Putting It Together

The core insight is that 86ing is not a communication problem between your kitchen and your guests — it's a sync problem between your channels. Humans are bad at simultaneous multi-dashboard updates during a rush; software is good at exactly that. A single trigger, a fan-out to every sales channel, an automatic re-list with confirmation, an instant text to the floor, and a weekly pattern report turn an ongoing source of refunds, comps, and one-star reviews into a quiet, reliable process that also makes your purchasing smarter.

You can build this entire flow without writing code. Automate Anything's features cover the building blocks described here — triggers from your POS or checklist apps, multi-channel fan-outs, SMS and chat notifications, scheduled summary reports, and failure alerts — connected through a visual editor your team can maintain.

Start small: connect your POS to your two busiest channels, wire one item, and run it for a week. The pattern log alone will change how you order.

Build your first automation at https://automateanythingsoftware.com