Twelve portions of chili-crisp chicken. Eleven already committed to accepted tickets. One left to assign—and a viral video still sending people to the order page.
That is the inventory position in the fictional incident below. The problem is not whether the dish looks like its photo or whether the kitchen packed it correctly. Promotional demand has overtaken what the restaurant can actually serve.
DoorDash’s April 2026 merchant guidance describes how viral menu-item discovery can lead to rapid ordering decisions. For you, that creates a practical gap: a guest can discover, want, and order a dish faster than your team can reconcile inventory across ordering channels.
You need to stop making new promises while protecting the promises you can still keep.
A fictional 45-minute incident, shown in three lanes
This is an illustrative scenario, not a reported restaurant case study. Juniper Counter, its dish, ticket numbers, counts, and decisions are fictional. The timestamps show what you decide to do—not claims about how quickly platforms respond or how guests react.
You are the shift manager. Your kitchen lead controls the physical count; your counter lead handles order reconciliation and guest contact.
Read each timestamp across three parallel lanes:
- Kitchen availability: What can you still fulfill?
- Ordering channels: Where can someone still buy it?
- Guest communication: What are you telling people before and after purchase?
+00 minutes — Protect the last confirmed portion and freeze new promises
Kitchen availability → Count complete, usable portions—not containers of ingredients or a prep estimate. Your kitchen lead confirms 12 portions against 11 previously allocated tickets. Assign the last confirmed portion to ticket 1842, the next verified accepted order. Mark it on the production sheet so another ticket cannot claim it.
Ordering channels → Direct staff to stop selling the dish immediately at the counter and by phone. Begin disabling it in the POS, first-party ordering page, and delivery merchant tools. Treat each channel as a separate task; one switch may not control them all.
Guest communication → Tell the counter team: “No more chili-crisp chicken orders. Existing tickets need checking before we promise fulfillment.”
Do not announce that every existing order is safe. You have verified a limited set, not the entire queue.
+04 minutes — Make the stop-sale explicit on every ordering surface
Kitchen availability → Keep the 12 allocated portions separate from anything still in preparation. Do not count an unfinished batch toward availability unless the kitchen lead can commit to its yield and service time.
Ordering channels → Set the dish to unavailable using each channel’s supported controls. Check lunch specials, bundles, modifier groups, and duplicate listings that may still include it. Record each surface as change submitted, guest-facing change verified, or still unresolved.
Guest communication → Give staff one distinction to preserve: sold out for new orders does not mean all accepted orders are canceled. Ticket 1842 still has a portion assigned.
This is the stop-sale decision, not a claim that the entire internet has caught up.
+09 minutes — Remove invitations you can control
Kitchen availability → Keep the dish unavailable while you assess any possible replenishment. A speculative second batch is not a reason to reopen sales.
Ordering channels → Pause restaurant-controlled paid promotion for the dish. Remove its homepage feature and stop any scheduled promotional send that has not gone out. Check that your profile link leads somewhere with current availability information.
Guest communication → Update the caption or pinned comment on your own viral post, where editing is supported: “Chili-crisp chicken is sold out for today. We’ll post here when a new service date is confirmed.”
You cannot edit a creator’s video, every repost, or someone’s screenshot. Update controllable surfaces first; do not confuse limited control with no responsibility.
+15 minutes — Reconcile accepted tickets against portions, not assumptions
Kitchen availability → Match each allocated portion to a ticket. Keep the last portion attached to 1842 unless that order is canceled through a verified process.
Ordering channels → Compare the POS queue, first-party orders, and marketplace dashboards. Identify accepted orders without an assigned portion, including any that arrived while availability changes were pending.
Guest communication → Prioritize contact with those affected orders. State the problem plainly: “We accepted your order, but we cannot fulfill the chili-crisp chicken.”
Restaurant sold out communication needs to distinguish an unavailable dish from an unavailable whole order. A guest may still want their sides—or may have ordered everything around that one item.
+22 minutes — Offer choices without substituting by default
Kitchen availability → Ask the kitchen lead which alternatives are genuinely available and whether fulfilling them would overload another station. Do not turn one stockout into a second one.
Ordering channels → Use the ordering channel’s supported process for item removal, substitution, or cancellation. Check what staff can authorize before promising a particular adjustment or refund timing.
Guest communication → Offer the applicable choices: an explicitly approved alternative with any price difference explained, removal of the unavailable item where supported, or cancellation of the affected order through the appropriate channel.
Never silently replace chili-crisp chicken with tofu, another protein, or a different sauce. Preference, dietary restrictions, and allergens make “close enough” a guest decision.
+30 minutes — Verify visibility and account for unanswered contacts
Kitchen availability → Keep unassigned inventory at zero unless the kitchen lead confirms a change. A hoped-for cancellation does not create a sellable portion.
Ordering channels → Check guest-facing listings where possible. If the item remains purchasable, escalate through available merchant support or account controls. Consider broader pauses only after weighing their effect on orders you can still fulfill.
Guest communication → Record contact attempts and follow the channel’s process when a guest does not respond. Do not treat silence as consent to a replacement. If pickup guests arrive before contact succeeds, give counter staff the same choices and explanation.
+38 minutes — Separate recovery from the next promotion
Kitchen availability → Decide whether replenishment is feasible, with a confirmed quantity and realistic production window. If either remains uncertain, keep the dish unavailable.
Ordering channels → Do not schedule automatic reactivation based on a guess. Keep unresolved channel checks assigned to a named person.
Guest communication → If you offer a goodwill credit, explain its terms separately from any refund or adjustment owed. Restaurant stockout guest recovery starts with resolving the purchase; a discount on a future visit is not a substitute.
Avoid “back tomorrow” unless tomorrow’s ingredients, labor, and capacity are confirmed.
+45 minutes — Close the handoff, not the investigation
Kitchen availability → Leave a clear record of committed portions, affected tickets, and any verified replenishment decision.
Ordering channels → Hand over the channel status log, including surfaces still awaiting verification. Do not mark the incident resolved merely because you submitted every change.
Guest communication → Assign ownership of remaining contacts and the next public availability update. Keep the sold-out notice visible while older promotional content continues circulating.
The promise that matters after the spike
When your restaurant’s viral dish sells out, the most useful response is not the fastest apology. It is a controlled sequence: protect confirmed orders, stop new sales, correct promotional invitations, and give affected guests real choices.
Viral menu item demand may arrive through one video. The obligations spread across every ticket and every channel. At minute 45, success means knowing which promises you can keep—and who owns each one you cannot.