Cafeteria Intelligence · camera-based meal billing

Meal billing you can defend — no biometrics, no coupons, no arguments.

Cameras count entries, plates, meals served and waste — per meal window, calibrated against a manual count before you ever bill from it.

ENTERED 0 PLATES 0 SERVED 0
Book a demoCalculate your leakage
The problem

Every uncounted meal is loss incurred.

5–15%

gap between claimed and actual meals

Manual counts drift — and someone pays for the gap.

2 people

often do nothing but count

A full-time job that still produces disputable numbers.

100%

of disputes are about evidence

Whoever has data wins. Usually nobody has data.

The maths

What is leakage costing you?

Type your numbers — nothing leaves this page.

LEAKAGE / MONTH
LEAKAGE / YEAR
SAUCEIT (4 CAMERAS)
₹11,996/mo
Compared honestly

Cameras vs. QR apps vs. biometrics

QR / app-basedBiometricSauceit (camera)
Employee action neededScan every mealEnroll + touch/face dailyNone — walk in, eat
Biometric / PII riskPhone dataFace/fingerprint database (DPDP-sensitive)No enrollment, anonymous counts
Catches proxy mealsCodes get sharedPartiallyCounts actual people & plates
Verifies the invoiceTrusts self-reportsAttendance ≠ meals servedEntry vs plates vs served vs waste
New hardwareKiosks/phonesReaders at every gateYour existing CCTV
Questions we get asked

Straight answers.

How does camera-based meal billing work?

Cameras over the entrance, plate stack and serving counter count each person once per meal window — unique person identification means nobody is counted twice: who entered, who took a plate, who was served, what went to waste. The counts become finance-ready reports you reconcile against your invoice.

Do employees need to enroll biometrics?

No. No fingerprints, no face registration, no cards, no coupons. Counting is anonymous and camera-based — which is exactly why adoption is instant and unions don't object.

Can cameras really count meals accurately?

Each deployment includes a calibration day: our counts run side-by-side with a manual tally and we publish the measured accuracy to you before you bill from it. A billing number without a stated error rate is a dispute waiting to happen — so we state it.

How do you separate staff meals from visitor meals?

People groups: you teach the system uniforms or markers (a photo and a few taps) — green-shirt staff billed to the company, visitors billed directly. Fully configurable per contract.

Does it track what people brought from home?

Yes — served meals are separated from brought-from-home eating, so the bill covers only meals actually served.

Which reports do we get?

Per meal window and per day: footfall, plates picked, meals served, live cafeteria occupancy, home-food eaters, after-hours consumers, waste-area activity — on a live dashboard and exportable as CSV for finance.

How long are counts retained?

Billing numbers at least 12 months for reconciliation; evidence frames briefly per the retention schedule. Your finance team can pull history any time.

What does it cost?

₹3,499 per camera per month, or ₹2,999 on the annual introductory offer — most cafeterias need 3–5 cameras (entry, plate stack, counters, waste). Against monthly leakage on thousands of meals, the maths usually settles itself. Outside India, billing is in USD — see pricing.

Do we need new cameras?

Usually not. Any HD CCTV camera (1080p or better) from the mainstream makes — Hikvision, Dahua, CP Plus, Uniview — works well; a clear view of the entry, plate stack and serving counters matters more than the brand. We check camera positions and quality during onboarding and tell you honestly if one needs repositioning or upgrading.

Run the calibration day. Then decide.

We count alongside your manual tally and publish the measured accuracy — before you bill a rupee from it.

Book a demo