External market reference
Robot Baristas at Cologne/Bonn Airport
An external European airport reference documenting two automated coffee points, their terminal positions, customer journey, and named operating party.
- Location
- Cologne/Bonn Airport, Terminal 2, Cologne, Germany
- Environment
- European airport, with one public departures location and one baggage-reclaim location
- Automation form
- Two robot-controlled coffee stations with on-device or app ordering and cashless payment
- Business model
- The airport's May 2024 announcement identifies Denis and Dino Mutic, through MyCoffeeTech GmbH, as franchisee operators of the two stations. Concession terms, equipment financing, revenue allocation, and demand risk are not disclosed.
- Operating model
- Customers order at the station or through the MyAppCafe app and pay cashlessly. The named franchisees operate the stations; the source does not assign cleaning, replenishment, monitoring, maintenance, airport access, or escalation tasks.
- Observable result
- Cologne/Bonn Airport publicly documented the launch of two units in May 2024 and specified their locations and offer. The reviewed source contains technical and offer descriptions but no post-launch utilization, uptime, repeat-use, labor, service, or Unit Economics results.
Relationship: External case. BeverageAutomata did not deliver, operate, or partner on this installation.
Reference snapshot
Cologne/Bonn Airport announced two MyAppCafe robot baristas in Terminal 2 on May 13, 2024. One was placed in the publicly accessible departures area, and one at baggage reclaim. Customers could order at a station or through an app and pay cashlessly.
The airport named MyCoffeeTech GmbH franchisees Denis and Dino Mutic as the operators. That role attribution makes the case more useful than a machine-only announcement, although many operating responsibilities remain undisclosed.
What the source confirms
- Two stations were announced at named Terminal 2 positions.
- The offer included coffee and cocoa drinks, iced coffee, multiple sizes, and paid extras.
- Ordering was available at the device or through an app, with cashless payment.
- The airport identified the franchisee operators.
The official page also gives technical capacity and preparation-time figures. This Reference treats those as described specifications, not observed passenger throughput.
What the source does not prove
The announcement does not report:
- Relevant traffic or conversion at either position
- Transactions, menu mix, or repeat use
- Ordering completion, payment failure, or refunds
- Uptime, stockouts, incidents, or service response
- Cleaning and replenishment labor
- Airport concession, site, support, or downtime costs
- Current status beyond the launch announcement
It would therefore be unsupported to call the deployment commercially successful or to project its result to another airport.
Market Formation reading
Demand & Site
Departures and baggage reclaim are different demand environments. A transferable proof would analyze them separately by users, dwell time, dayparts, visibility, alternatives, and service access.
Experience & Offer
The documented multi-size menu, optional extras, app or device ordering, and cashless payment show an offer designed beyond a single fixed drink. Accessibility, language use, allergen communication, queue behavior, and failed-order recovery are not reported.
Operations
The franchisees are named as operators, but the airport announcement does not publish the daily responsibility matrix. Airport security and service-access requirements are also absent.
Unit Economics
The source publishes consumer price ranges but no demand, concession, ingredient, labor, payment, support, financing, or downtime data. Price alone cannot establish viability.
Ecosystem & Regulation
The public record identifies venue, technology brand, and franchisee operator. It does not describe food-business responsibility, local service levels, facilities approvals, data roles, or supplier arrangements.
Transferable lesson
BeverageAutomata inference: Airports should be evaluated as a collection of nodes, not as one traffic number. The two Cologne/Bonn positions could test different demand and operating hypotheses. Transfer depends on preserving the distinction between site zone, customer journey, operator role, service access, and full economics.
Evidence needed for a stronger Reference
- Venue- or operator-confirmed current status
- Traffic, transactions, conversion, and dayparts by station
- Repeat use, including airport employees where relevant
- Ordering completion, accessibility, and customer recovery records
- Uptime definition, incidents, stockouts, and service logs
- Cleaning, replenishment, monitoring, and maintenance workload
- Full site-level economic model and commercial purpose
- Permissioned role and progression statements from the parties
Source
Source review date: July 14, 2026.
Transferable conditions
- A clearly defined passenger or employee demand hypothesis for each terminal position
- Airport approval for utilities, placement, customer flow, security, and service access
- Ordering, payment, language, allergen, and accessibility design for international users
- A named operator for daily cleaning, replenishment, monitoring, and customer recovery
- Local maintenance coverage that can work within airport access constraints
Limits
- The source is the airport's launch announcement, not an independent performance evaluation
- No post-launch transactions, conversion, repeat-use, uptime, incident, labor, or economic data
- Technical capacity in the announcement is not evidence of realized demand or throughput
- Current operating status after the May 2024 announcement was not independently confirmed during this review