How to Design a Reusable Cup Workflow for Mobile Orders and Drive-Thru

A reusable-cup program works when it is designed as a repeatable service workflow, not as a loose permission for customers to bring any vessel. Starbucks’ 2024 rollout across café, mobile order, and drive-thru offers a practical operating pattern: set a clear acceptance gate, keep customer cups out of the normal drink-building sequence, use a controlled handoff, and make the digital order signal visible before the customer reaches pickup.

For restaurant and coffee-chain operators, the first pilot should prove the physical handoff and recipe-control steps in café service. Mobile ordering and drive-thru can follow once staff can execute the same sequence reliably under real queue pressure.

Customer-owned cups are variable. They differ in height, opening diameter, insulation, markings, lids, cleanliness, and condition. A program that expects staff to build every drink directly into every cup makes those differences a production problem.

Starbucks used a different approach. Its personal-cup process accepts clean cups across standard beverage sizes and hot, iced, and blended drinks, while baristas build the beverage in dedicated smallware with measurement lines before transferring it to the customer’s cup. The operational lesson is simple: recipe accuracy should come from your calibrated tools and standard recipe, not from the geometry or markings of an unfamiliar cup.

For a restaurant group, this creates a more useful compatibility rule:

• Accept only clean, intact cups that staff can safely fill and return.
• Ask customers to remove and retain the lid before handoff.
• Build to the normal recipe in controlled equipment.
• Transfer the finished beverage into the cup only at the defined handoff step.

This is more scalable than trying to approve every cup shape in advance. It also separates two questions that are often confused: whether a cup can be accepted, and how a drink is made accurately.

A reusable-cup workflow needs a clear boundary between the customer’s vessel and the production area. Starbucks’ drive-thru and app workflows use a contactless vessel to collect and return a clean, lidless personal cup. It also states that baristas do not rinse personal cups in store equipment; dirty cups are not accepted.

That pattern can be translated into a short, teachable sequence:

1. **Declare the cup early.** The customer tells staff at the counter or order point, or selects a personal-cup option in the app.
2. **Check the acceptance condition.** Staff confirm that the cup is visibly clean, usable, and lidless. Define how staff should handle damaged, dirty, or unsuitable cups.
3. **Use a designated transfer tool.** Receive and return the cup with a tray, caddy, or other controlled carrier rather than treating it as normal barware.
4. **Build the beverage in standard tools.** Use the existing recipe, measurement, and quality-control process.
5. **Transfer, finish, and return.** Pour the beverage into the cup, complete the permitted finishing steps, and return it through the same controlled handoff.

The aim is not to claim that a particular object is automatically hygienic. The aim is to make the staff actions consistent, reduce unnecessary contact with the drinking surface, and avoid improvisation at busy stations.

Mobile ordering adds an information problem. A barista must know that a personal cup is coming before the order reaches the production queue, but the physical cup is not present when the order is placed.

Starbucks handles this through an app choice: the customer selects “Personal Cup” during customization, then brings the clean, lidless cup to the pickup area. For another chain, the exact interface may differ, but the operating requirements are the same:

• The order display must show a distinctive personal-cup signal.
• The customer must be told exactly where and when to present the cup.
• Staff need a decision rule for orders whose customer or cup has not arrived.
• The team must know which preparation can happen before handoff and which step waits for the cup.

Do not solve this only with an app toggle. Test the pickup experience. If the customer arrives at a crowded shelf without knowing whom to approach, the digital signal does not complete the workflow.

A sensible first version is a dedicated pickup handoff: the customer selects the option in the app, approaches a defined pickup point, presents the lidless cup, and receives the drink after the transfer step. This gives the operation a visible control point before attempting more automated staging.

Drive-thru makes timing and vehicle flow part of the design. Starbucks instructs customers to mention the cup while ordering, then to provide the lidless cup at the pickup window; staff collect and return it with a contactless vessel. That sequence matters because it tells the store early without requiring the cup to travel through the order-taking stage.

For a drive-thru pilot, specify the script and the physical motion in advance:

• At the speaker: “I’m using a personal cup.”
• In the production queue: the order receives a clear personal-cup marker.
• At the window: the customer presents the lidless cup in the agreed transfer carrier.
• At return: staff use the carrier again and confirm the drink before it leaves the window.

Test this at different demand levels. The relevant question is not whether one transaction can work; it is whether the process remains understandable when the bar, window, and queue are all busy.

Starbucks’ rollout followed testing, including a test at 200 Colorado drive-thru stores, and store partners helped co-design the smallware used for transfer. That supports a practical principle: involve the people doing the work and test the motion before scaling the promise.

Start with a limited group of stores and a small number of trained shifts. Validate the acceptance rule, transfer tool, drink-building method, refusal script, and customer signage.

Track:

• personal-cup orders as a share of eligible beverage orders;
• refusal reasons;
• added seconds at handoff;
• remakes, spills, and order errors;
• observed compliance with the sequence; and
• customer questions or complaints.

Add the app or POS flag only after the counter workflow is stable. Test whether the label reaches the right production point, whether customers find the pickup handoff, and how long orders wait for a cup.

Launch at a small set of sites with trained window teams. Compare personal-cup transactions with comparable standard-cup transactions by time of day, beverage complexity, and queue condition. Watch window time, missed declarations, spill events, and whether the transfer carrier is used correctly.

Do not begin by promising acceptance of every possible vessel. Expand the accepted range after real pilot data shows where fill level, stability, transfer, and return failures occur. Keep the policy simple enough that staff and customers can use it without a long judgment call.

A usable standard operating procedure should answer five questions without ambiguity:

1. What cups are accepted or declined?
2. Who receives the cup, and with which transfer tool?
3. Where is the drink built and measured?
4. What does the customer do at pickup or the drive-thru window?
5. What happens when the cup is dirty, missing, damaged, or incompatible?

Train the sequence as a physical routine, not only as policy text. Then observe it during a real rush. If staff must stop to interpret a rule, locate a tool, or ask where the cup should go, the workflow is not ready to scale.

A reusable-cup pilot may require disposable backup cups, cup-and-lid components, transfer tools, or branded customer communication. The specification should name the real service conditions: beverage type, target capacity, fill level, lid fit, handling route, order volume, branding requirements, and destination market.

TakeawayPack’s RFQ process is structured around product category, material, size or capacity, estimated quantity, print or logo requirements, and destination country or port. For a quote-ready packaging brief that captures those inputs, visit Takeawaypack.