← All posts Launches

How to run a flash sale without losing your team

A flash sale does not break your store. Shopify handles the traffic fine. What breaks is the gap between the four people who each hold one quarter of the picture.

MK Maya KesslerCo-founder · 25 July 2026 · 11 min read

The eleven minutes

Our restock drop sold out in eleven minutes. That should be a good story. Here is what actually happened inside those eleven minutes, and the two hours after.

Our ads kept running for another 118 minutes on a product that no longer existed. Nobody was watching stock and spend at the same time, because those were two people looking at two dashboards in two rooms.

Support answered fourteen tickets promising a dispatch date the warehouse had already told ops was impossible, but ops was in the room with the founder, and support was in a different channel.

And a customer who had spent four thousand euros with us over two years received an automated apology written for a first-time buyer, because nobody flagged her order as anything other than an order.

Every person did their job correctly. The information just never crossed the gaps between them. That is the actual failure mode of a flash sale.

Decide two things before the sale starts

Most of the chaos on the day comes from decisions being made under time pressure by whoever happens to be looking. Make these two in advance, in writing, where everyone can see them.

  1. What is the stock floor, and who is allowed to breach it? Pick a number of units at which you stop selling a variant. Decide now whether oversell is acceptable, and if so, by how much and who can authorise it. On the day, this becomes a yes-or-no question instead of a debate.
  2. What is the promise support is allowed to make? Agree the dispatch window with the warehouse before the sale, not during it. Write the exact sentence support should use. Fourteen tickets with the same wrong promise is not a support failure. It is a briefing failure.
Write both into the room

Pin them at the top of whatever channel you are running the sale from. If a decision is not visible to everyone in the room, half the team will make a different one.

Who watches what

The mistake is assigning people to areas (ops, support, warehouse) and assuming coverage. Assign people to numbers instead, and say the number out loud on a cadence.

  • Stock per variant. One person. Their only job is to call out when any variant crosses the floor. They do not answer tickets.
  • Spend and traffic. One person, watching cost-per-acquisition and which creative is pointing at which SKU.
  • Inbound volume. One person watching the ticket queue depth, not the tickets themselves. Depth is the early warning that your promise is wrong.
  • The floor. Someone in the warehouse posting what is actually happening on the pick line, in a sentence, every thirty minutes.

Four numbers, four names, one room. If your team is three people, one person holds two numbers, but they still say both out loud.

The pause trigger

The single highest-value rule we have: spend pauses automatically at the stock floor, and it is nobody’s judgement call.

Pausing ads on a sold-out SKU seems obvious in retrospect and never happens in the moment, because the person watching stock is not the person with access to the ad account. Fix that in advance:

  • Give the stock-watcher the ability to pause, or put the ads person in the room with an agreed trigger phrase.
  • Write the trigger as a number, not a feeling: Sand/M under 10 → pause set 4.
  • Time how long it takes from call-out to paused. If it is more than two minutes, the wrong person has the permissions.

The hour after is the sale

The revenue is banked in eleven minutes. The margin is decided in the next three days: in refunds, in replacement shipping, in the support hours spent on delivery-date questions you created yourself.

So the room does not close when the product sells out. Give it one more hour and do three things:

  1. Reconcile what you actually sold against what you can actually ship, per variant, before anyone goes home.
  2. Flag the exceptions now: oversells, high-value customers, anything going to an address the carrier has failed at before. These are cheap to handle today and expensive on Thursday.
  3. Write the recap while it is fresh. What sold, what ran out first, what the queue depth peaked at, which promise turned out to be wrong. Fifteen minutes now saves you rebuilding the plan from memory next quarter.

The short version

  • Decide the stock floor and the support promise before the sale, in writing, pinned.
  • Assign four numbers to four names. Say them out loud on a cadence.
  • Make the pause trigger automatic and permission it to the person watching stock.
  • Keep the room open for an hour after sell-out. Reconcile, flag exceptions, write the recap.
  • Do it in one place where all four people can see all four numbers. This is the whole trick.

We built Store Huddle because that last point kept being the hard part. Everything else on this list is free. It just does not survive a group chat.

Run your next drop in one room.

Live stock counters, a checklist with owners, and a recap written for you when the room closes.