All posts
Mon, 25 May 2026· 4 min read

The 4 PM rule — how skip-a-day works without losing a rupee

The 4 PM rule — how skip-a-day works without losing a rupee

The cook needs to know how many plates to make by ~4:30 PM the day before. So the customer's window closes at 4:00. Thirty minutes of slack is for emergencies.

Most meal subscriptions either don't let you skip at all, or let you skip with a "we'll adjust later" promise that quietly gets lost. We did it differently because it directly answers the only real objection to monthly plans: what if I'm not eating that day?

How it works in the app

  1. Open the customer console at bhukfoods.com/customer.
  2. Tap the green day you'll be away.
  3. Confirm. The day flips to dashed-outline.
  4. That day is not charged. Your "Plan ends" date moves one day forward.

What 4 PM IST actually does

At 4 PM, our database refuses any new cancellation for tomorrow. (It's enforced inside Postgres, not just in the front end — so a smart customer with a Chrome dev console can't bypass it.) At 4:30, the kitchen prints the final headcount sheet for tomorrow. By dinner, the cook has bought tomorrow's vegetables.

Edge cases we thought through

Why this is fair to both sides

The cook's daily life is calmer because she knows the number by dinner. The customer's wallet is calmer because they don't pay for food they didn't eat. The plan still gives you all 26 meal days a month — they just shift forward. You don't lose a rupee. You don't even lose a meal. You just lose the meal day you were going to skip anyway.

Want this in your life?

Two meals a day, Mon–Sat. Self-pickup, home delivery, or on-site at BLPGA. See pricing →

MORE FROM THE BLOG