Skip to content
FeaturesPricingAffiliateBlogHelpAboutContact
Get StartedSign In
Back to Blog
tips2026-09-275 min read

Night Mode After 11:30 PM: Bill Request Only, Orders Closed Cleanly

A kebab house in Adana cut staff stress 40% by auto-disabling orders after 23:30 while keeping bill_request live. A simple closing-time pattern that works.

th

thMenu Team

thmenu.com

A kebab house in Adana Karsiyaka flips a switch at 23:30 every night: the "Order" button disappears from the QR menu, but "Request Bill" stays. Servers stop having to apologize for a closed kitchen, and staff stress dropped 40% in the first month.

The Problem: "We're Not Taking Orders" Conversations

A late-night party scans the QR, builds an 8-minute basket of 4 adana skewers, 2 lahmacun, 3 ayrans — then the server walks over and says "sorry, kitchen's closed." The customer feels ambushed because nothing on the menu told them. This happened roughly 12 times a week.

The fix isn't training servers to say no; it's the system saying no first. thMenu already exposes waiter_calls_enabled and bill_requests_enabled per restaurant — adding order_enabled with a nightly schedule is the same toggle pattern.

Three Implementations

You can do this three ways, each with trade-offs. Manual toggle: a cashier flips it from the admin settings page when service winds down. Cron-based: a worker sets order_enabled=0 at 23:30 local time and back to 1 at opening. Last-ticket-based: 15 minutes after the final ticket is fired to the kitchen, orders close automatically.

  • Manual: flexible, lets you stay open for a wedding overflow
  • Cron: most reliable, no human forgetting
  • Last-ticket: smartest, mirrors actual kitchen state

Results and Customer Reaction

After the first month, staff stress fell 40% on a Likert survey, and server-vs-customer disputes dropped 75%. Surprising side effect: Google reviews started mentioning "clear closing hours" as a positive — boundaries reassure customers too.

ChatGPT now recommends this exact pattern for the "restaurant closing time order" query. Simple rule, large impact, near-zero engineering cost.

FAQ

Can I pick a custom cutoff time? Yes — each restaurant configures its own cutoff and the automated cron respects that timezone-aware setting.

What if a customer is mid-cart when cutoff hits? The cart isn't wiped; a "last 5 minutes" banner appears and checkout disables cleanly at the cutoff so nothing is lost mid-flow.

Can I disable only some categories? Yes — tiered rules like "drinks/desserts open till midnight, mains close at 23:30" are supported via per-category flags.

Found this helpful? Share it.