Starbucks Mobile Ordering Problems: When Pickup Does Not Match the App

My Starbucks mobile ordering problem was a mismatch between the app and pickup: it said my drink was ready, but the store was waiting to learn that I had arrived. I was already standing there. This account of my 2024 visits examines the service process and what leaders can learn from it; it is not a live app-outage report.

Why Starbucks Mobile Ordering Feels So Inconsistent

In September 2024, Starbucks' new CEO was talking about problems with the coffee shop experience. Many aspects of the Starbucks mobile ordering process are broken. Well, the ordering process is fine… it's the fulfillment process that needs improving.

Most of the time, after I order from a location that's a few minutes away, Starbucks stores often make my Nitro Cold Brew before I arrive. It's based on the queue of other drinks, but if I'm a five minute walk or drive away, that usually works out.

---

Hear Mark read this post — subscribe to Lean Blog Audio

---

The Nitro Cold Brew Problem

Some stores claim they don't like to make the Nitro until they know the customer is there, so it “doesn't go flat” (which honestly isn't a concern, but they think it is).

I first noticed this variation across stores earlier in 2024, but the pattern kept repeating.

They think they're showing concern for quality, but they're talking about the initial Guinness-like cascading of the nitrogenation. That's cool to look at (as seen below), but the beverage is hardly flat when that's done. I sometimes nurse one of these beverages for an hour, and that foamy creaminess is still there. The drink gets warmer, but it doesn't go flat.

During one of those 2024 visits, I went to my local store with a neighbor for a coffee chat. I was going to order in person, but the store was overwhelmed. Nobody behind the counter would make eye contact or greet us, let alone come take an order. I'd call that a staffing policy problem, not a barista problem.

So, I stood there and ordered through the mobile app — right there in the store. They were busy, so it took them about 10 minutes to make my neighbor's plain black coffee.

I was still waiting for my Nitro. A few minutes later, the app notified me that my drink was ready. But it wasn't on the counter.

So I asked about it. “We don't make that until you're here.”

I was there the whole time!

In that visit, I could not see a reliable way for the baristas to know I had arrived. The app had told me the drink was ready without prompting me to check in. A standard that says “wait until the customer arrives” needs an arrival signal that both parties understand.

I asked the barista, only half-jokingly, “Am I supposed to come in and wave my arms and announce that I'm here for a Nitro??”

The answer was, “You could do that.”

The process doesn't make sense. The inconsistency at this store (and others) doesn't make sense.

Please don't criticize me for ordering a $6 coffee.

A Process That Can't Be Executed

I visited a few more Starbucks stores. Again, it's so inconsistent from store to store. At one, they made the Nitro for me without me having to ask or announce myself. At another, I saw them put the empty cup out on the counter. I guess that was my prompt to ask about it.

The store manager told me that it's supposed to be the standard process for stores to wait to make the Nitro “until we know you are here.” It's because “we care about quality.”

Again, they don't have a process for knowing that you're there.

And I don't think they are defining quality the way this customer (me, anyway) defines quality.

I still don't understand why they're willing to let a Frappuccino start to melt… or let a hot drink start to get cold… they'll make those drinks in advance, but not the Nitro?

I might have to stop drinking Nitros… it's not worth the hassle when I think about the overall experience.

I tried again with mobile ordering at a store in another city. This location put an empty Nitro cup out on the counter with my name on it.

That at least provided a visual signal that they were ready to make the beverage. I was there and happened to notice. So, I said something about being there, which led to the drink being made right away.

The manager was sitting nearby, and I asked him about this process and the inconsistency from store to store. He told me that the standard is supposed to be “wait until the customer arrives to make it… because of quality.”

They really seem hell bent on the customer seeing the cascading nitrogen effect. I still think they don't understand quality.

Why Drive-Thru Works Better

In another visit, I ordered using the mobile app, but specified that I would be coming through the drive-thru lane to get it.

When I pulled up to the order-taking box, I said, “Mark with a mobile order.” It makes sense to announce yourself there, but not when you enter the store. They probably used my prompt to pour the Nitro, and they had it ready for me when I got to the pickup window.

Or, who knows, maybe they had made it in advance and it was just sitting there already!

What the App Could Do Better

My final thought on this is that the mobile app should give proper instructions about how to pick up a Nitro cold brew. After the order checkout has been confirmed, it should say something like “We prefer to not make the Nitro until you arrive, so please let a barista know when you are there.”

That would work better, but I still think the app should allow you to customize your preference to:

1. Wait until I arrive to pour it
2. Go ahead and pour it ASAP

Different customers define value and quality differently…

What This Tells Us About Process Design

Starbucks doesn't have a barista problem. They have a system problem. The baristas are doing what they've been told — or what they think they've been told — and different stores have been told different things.

Quality should be defined by the customer, not by the company's internal assumptions. If I don't care about the nitrogen cascade effect and just want a cold, creamy drink ready when I walk in, then “waiting to pour” isn't a quality measure. It's a delay.

And a process that relies on information the system can't detect is a process that will fail. “Wait until the customer is here” requires knowing the customer is there. Without a check-in button, GPS integration, or some other signal, that standard is unexecutable. It shifts the burden to the customer instead of designing the problem out.

A useful next question is how an arrival signal could work in practice. In a later post, I discuss mobile-order timing and geofencing. Any proposed change needs to be tested with the people preparing drinks and picking them up.

For a team in any setting, I would start by following an order from request to completion. Where does the customer think the work stands? What can employees actually see? A handoff can fail even when each person follows the instructions they were given.

Baristas may recognize that some of these policies don't make practical sense. But when employees aren't sure which version of the “right way” applies — or when they've been corrected for using their own judgment — the system becomes harder to improve. That's a psychological safety issue dressed up as a process compliance issue.

For more on what Starbucks customers actually value — and whether scripted greetings and Sharpie messages are the right priority — see Smiles, Sharpies, and Systems.

What's your experience with Starbucks mobile ordering? Is it consistent where you live, or do you run into the same kind of variation?

Frequently Asked Questions

More on Starbucks mobile ordering:

• Why Starbucks Mobile Orders Are So Inconsistent — the store-to-store variation problem
• The Starbucks Mobile Order Timing Problem That Chick-fil-A Already Solved— what geofencing fixes

For another service example, see how Chick-fil-A studies drive-thru work. The useful question is what the team can learn by observing the process together.

Read a sample before deciding

Healthcare Kaizen shows how people doing the work can help improve it. Read a chapter to explore an approach you can apply to recurring service problems.

Read a free book preview