Case study · Healthcare
The cafeteria closed at 7 p.m. The hospital didn't.
A Mountain West hospital network with 3 campuses and 1,100 beds replaced 14 legacy vending machines with 22 Kava Coolers and 4 Kava Lockers for hot meal pickup. This hospital smart cooler case study covers the first 6 months: real food on every floor cluster, all night, and temperature logs nobody writes by hand.
- revenue vs. prior vending
- +46%revenue vs. prior vending
- fresh-food waste
- −31%fresh-food waste
- fresh food on every floor cluster
- 24/7fresh food on every floor cluster
1,100 beds staffed around the clock. Food service staffed until 7.
Clinical staff across the network's 3 campuses work 24/7. The cafeterias didn't: they closed at 7 p.m. After that, the choice was 14 legacy vending machines built for chips, candy and soda, not for meals, and not always near the units that needed them.
Fresh food added a second job. Anything sold overnight needed temperature records an auditor would accept, and paper records depend on someone remembering to fill them in at the busiest moment of a shift.
- Night, weekend and holiday staff had the fewest real-food options.
- The old machines were built for snacks, not for meals.
- Temperature records relied on clipboards and memory.
What changed
Give the kitchen a night shift on every floor
Instead of one bank of machines near the lobby, the network placed Kava Coolers by floor cluster, close to where staff take their breaks. Kava Lockers handle hot meals: dishes are prepared and loaded into heated compartments held at 140–165 °F, and staff collect them with a code, a QR, a badge or the app.
Every cooler holds 33–41 °F and logs its temperature continuously. If the inside stays above 41 °F for 30 minutes, the door locks itself and an alert goes out, so warm food can't be sold. The record that used to live on a clipboard now builds itself, timestamped and ready for an audit.
- Vision plus per-shelf weight sensing charges for exactly what was taken.
- Expiry-aware markdowns move near-date items before they become waste.
- Ordering follows each floor cluster's own demand, not a network average.
From 14 machines to 26 connected devices
- Phase 1
Map the night
We mapped where staff actually are after 7 p.m. on each campus: floor clusters, break rooms and shift-change times, rather than wherever the old machines happened to stand.
- Phase 2
Prove it on one campus
The first campus went live with coolers and hot-meal lockers. Placement, assortment and meal loading times were tuned against real overnight sales before anything else moved.
- Phase 3
Roll out network-wide
The other campuses followed with the tuned layout. Legacy machines came out as their replacements went live, so no floor lost its food option in between.
- Months 1–6
Let the data run the menu
Kava OS forecast demand by floor cluster, flagged slow sellers and marked down near-date items. Revenue rose 46% against the prior program, and fresh-food waste fell 31%.
The same hospital, at 3 a.m.
| Prior vending program | With 8Kava | |
|---|---|---|
| Fresh food after 7 p.m. | Cafeteria closed | On every floor cluster, 24/7 |
| Hot meals overnight | Not available | Heated locker pickup at 140–165 °F |
| Equipment | 14 legacy vending machines | 22 Kava Coolers + 4 Kava Lockers |
| Temperature records | Written by hand | Logged automatically, audit-ready |
| Revenue | Baseline | +46% |
| Fresh-food waste | Baseline | −31% |
Night shift used to eat from a bag of chips at 3 a.m. Now they eat a real meal, and I get an audit-ready temperature log without anyone touching a clipboard.
What we'd tell the next hospital
Place by floor, not by front door
Lobby placement serves visitors. Clinical staff on a short break won't cross a building to eat. Put the food where the breaks happen.
Treat lockers as the kitchen's night shift
Hot food at midnight doesn't need a cashier. It needs a heated compartment, a pickup code and a meal prepared while the kitchen was open.
Make the audit log a byproduct
If compliance depends on someone writing it down, it gets missed on the worst night. A log that runs on its own is the only kind that survives a busy shift.
Who eats in your building after the kitchen goes dark?
Count the hours your food service is closed. Then count the people on shift during those hours. They aren't skipping dinner by choice; they're skipping it because the nearest real meal is locked behind a shutter. What would change on your night shift if dinner were down the hall?
Questions hospitals ask
Do smart coolers need special electrical work?
No. Kava Cooler runs on a standard 115 V outlet and connects over LTE, Wi-Fi or Ethernet. The single-door C2 is 30 inches wide by 32 inches deep, so it fits most alcoves and break rooms; the double-door C2-XL is 54 inches wide.
How do the coolers support food-safety audits?
Each cooler holds 33–41 °F and records its internal temperature continuously. If it stays above 41 °F for 30 minutes, the door locks and an alert goes out. The log is timestamped per device, which is what an inspector asks for. Our guide to temperature compliance covers the details.
Can staff pay with a badge or through payroll?
Yes. Kava Cooler accepts EMV contactless cards, mobile wallets, the Kava app or QR, employee badges and payroll deduct. Employer subsidies can apply at checkout, so a night-shift meal can cost staff less with no cash involved. See Payments & Loyalty.
Who restocks the coolers and lockers?
Your choice. Your food service team can keep stocking in-house and use Kava OS for forecasting and logs, or you can hand the whole program to Managed Operations. Both run on the same hardware.
Do the cameras record staff or patients?
Recognition runs on the device and looks at products, not people. No images of faces are stored or sent. See Security & Trust for how the data is handled.
Where to go next
Map your night shift's food gap.
Send us your campus map and your food service hours. We'll show you where coolers and lockers would go, and what the first 6 months could look like.