A hotel pantry does not sell like a store. It sells like a gap.
Nobody walks into a lobby at 3 p.m. hunting for ibuprofen. They buy it at 11:40 p.m., after a delayed flight, when the pharmacy two miles away closed at nine. The shelf and cooler next to the front desk earn precisely because everything else nearby is shut.
Which is the awkward part. The hours the pantry earns are the hours the desk is thinnest — one clerk, often the night auditor, often mid-audit, sometimes on a bell run or walking a late arrival up to a room. At a fifty-key property the revenue shows up exactly when the labor doesn't.
Most small properties resolve this one of two ways, and both leak. They charge it to the room, or they set out a box and hope.
Charging it to the room schedules an argument
A folio post is not a completed sale. It is a promise to argue later.
At the moment the guest takes the item, they agree to nothing. No card, no signature, no receipt in hand. The disagreement gets scheduled for checkout morning — when the guest is in a hurry, a different clerk is on, and the only record is a line typed by someone who went home eight hours ago.
Three things make that worse at a small property:
- The person who posted it is gone. The night auditor rang it at 2:14 a.m. The morning clerk defending the charge was asleep at the time and has nothing to defend it with.
- The line item is generic. A folio line reading "SUNDRY" and an amount tells nobody what was bought. It is not evidence, it is a number.
- The cost of arguing exceeds the charge. Most front-desk managers will comp a small dispute rather than risk the review. So the leak is not theft — it is policy. You wrote the sale off to protect the score.
There is a fourth problem, and it is the one operators underrate: room-charging only works for people who have a room.
The guests the folio cannot serve
Stand at the cooler for one evening and count who cannot buy from you:
- The wedding-block guest whose room is billed to someone else's card
- The person sitting in the lobby waiting to meet a guest
- Day-pass pool users, a contractor between jobs, a driver waiting on a pickup
- A prepaid third-party booking where incidentals were never set up
- Anyone who declined an incidentals hold at check-in
Every one of them is a customer standing in front of your shelf holding money you have no way to accept.
Settle it where it happens
The alternative is to close the sale at the shelf, at the moment the guest decides.
A tablet sits at the end of the shelving. The guest taps it and scans the barcode on a sports drink — that read happens on the device itself, no round trip. For the muffin from the local bakery that has no barcode, they tap to take a photo and TallyTill's AI matches it against your catalog. Tax applies by jurisdiction. They pay on the spot: Tap to Pay on the Android tablet, or a Stripe reader. Which wallets and buy-now-pay-later options you accept are settings on your Stripe account, so you switch on what suits a lobby shelf. A receipt goes out by email or SMS immediately, to an address the guest typed themselves.
One thing worth stating plainly, because the category is full of marketing that implies otherwise: the camera is not watching the shelf. It does not sit there recognizing items as guests pick them up, and nothing is ever added to a cart on its own. Every line on that receipt is there because the customer scanned it or photographed it. That is a design choice, and at a hotel it is the useful one — the thing you can point at during a dispute is an action the guest took.
One caveat: is anyone actually on the property?
The 2 a.m. sale described above assumes what most properties have — a night auditor at the desk. That makes the pantry semi-attended in Stripe's terms: the guest works the card reader independently, but staff are on site if they are needed. Stripe certifies its readers and Tap to Pay for attended and semi-attended retail, so a property with an overnight desk can run the flow exactly as described.
Some smaller properties do not have that. If the desk closes entirely overnight, or you run remote or virtual check-in with nobody on site, those hours are unattended by Stripe's definition — and the test is whether a person is on the property, not whether anyone is watching the tablet. The same lobby can be semi-attended at 8 p.m. and unattended at 2 a.m.
That does not cost you card payments. A QR payment opens a Stripe-hosted checkout in the guest's own phone browser: an ordinary online card payment, with no attendance restriction attached to it. Guests still pay by card, and the itemized receipt, the authorization and the audit trail below all work the same way. What is unavailable with nobody on site is card-present capture on the tablet — the reader and Tap to Pay — not cards. Which of your hours fall where is worth settling before you order a reader: attended, semi-attended and unattended — how Stripe's rules work.
At nine the next morning, the argument mostly cannot start. The guest already has the itemized receipt, and you have the authorization and the trail. The comp-to-keep-the-peace reflex stops costing you sales you actually made.
The clerk who is not standing at the desk
A few settings matter more overnight than they do at noon.
Kiosk mode is Android screen pinning. It locks the tablet to the checkout screen so a guest can't wander into settings or open a browser. Be clear-eyed about what it is: it keeps the device on task, an admin can exit it, and it holds properly only once you have done the one-time hardening — a device PIN, and requiring that PIN to unpin. It is not a vault and it is not tamper-proof. Tether the tablet physically — that is what actually keeps it on the wall.
Manager PIN gates refunds, discounts and voids. A night clerk can fix a mis-scan without holding the keys to your catalog, and the override lands in the audit trail with a name and a timestamp.
Cart photos attach an image of the checkout to the sale, which is the single most useful piece of dispute evidence you can hold. It is a setting, and it means photographing guests in your lobby at 2 a.m. Some properties will want that and some won't, and it may be a question for whoever handles your guest-privacy policy. Decide it on purpose — the rest of the evidence chain above works either way.
"Hey Tally" is a configuration setting you can switch on if you want it — a guest with full hands can ask out loud what something costs. It is off unless you turn it on, and plenty of properties never do.
Restock from what sold, not from a walk-round
Ask a night clerk to eyeball the shelf and you get the worst inventory signal in the building: a guess, made at 4 a.m., about a shelf that gets restocked by someone on a different shift.
Sales data replaces it. The portal shows what sold, when, and at what price, in real time. You order to demand instead of to memory, and you find out whether the late-night basket actually looks different from the early-evening one at your property rather than assuming it does. Slow items stop taking up facings. The pantry starts being managed instead of merely refilled.
Two shelves, two devices, two sets of numbers
If you also run a cooler on the pool deck, do not let it share a till with the lobby.
Register each location as its own device. Each reports its own sales, so a seasonal pool cooler doesn't get quietly subsidized by a lobby that runs year-round, and you can decide independently whether either one earns its floor space. Adding a till is a QR scan — see Adding a New Till.
The honest note about connectivity
At a farm stand, offline capability is the whole ballgame. At a front desk, it usually isn't — the lobby is typically the best-connected spot in the building, often hardwired and on the same network as the property management system. So sell yourself the right benefit: what a lobby pantry buys is the dispute evidence and the audit trail, not the offline story.
Still, know where you stand when the circuit does drop. Barcode scanning and tapping an item on screen are local and work with no signal at all. AI photo recognition needs a connection. Cash and check, if you enable them, always work. Card sales can complete offline only under specific conditions — you have to have turned on offline card payments, the sale has to run through a Bluetooth Stripe reader rather than Tap to Pay, and that reader must have been connected online at the location beforehand. You set a per-sale cap and a total cap, and a card that declines after the fact is your loss. Queued sales forward automatically on reconnect, and emailed receipts do not send until you are back. The full conditions are in Taking card payments when the internet goes down.
What it doesn't do
TallyTill runs on Android tablets and in Chrome. There is no iOS build. There is no scale integration, so nothing sold by weight. AI photo recognition requires a connection, and the camera never identifies anything the guest didn't ask it to.
If your question is whether an unattended shelf pencils out at a small headcount at all, that math is in Micro market "lite", and the cooler-hardware question is covered in starting a self-serve fridge. This piece assumes you already have the shelf and the problem is the till.
The pantry is one of the few pieces of a small property that can earn while nobody is watching it. It just has to stop generating arguments to do so. We are transparent about what TallyTill costs — current pricing is here.