When your restaurant is outside ordering hours, show guests that ordering is closed, explain when the relevant service opens next, and offer a next step that actually works. If advance ordering is available, say which future pickup or delivery times guests can choose. If it is not, do not leave an active checkout button on the page.
The goal is to answer a simple question without making guests guess: can I order now, and if not, when can I? A useful closed-state page also helps staff avoid orders arriving when the kitchen or delivery service cannot fulfill them.
Show the status for each service
Start with the restaurant's operating schedule, but do not assume it is the same as its ordering schedule. A dining room might open before the kitchen accepts online orders. Delivery might stop before pickup. A location may also stop taking orders before closing so staff can finish the orders already received.
List the inputs that determine what a guest sees:
- Location: Which restaurant is the guest ordering from?
- Local time: What time and date is it at that location?
- Service: Is the guest looking for pickup or delivery?
- Ordering window: When does that service accept orders, including any cutoff before closing?
- Exceptions: Are holiday hours, a private event, or a temporary schedule change in effect?
- Future ordering: Can the system accept an order now for an eligible later slot?
The owner or manager should approve the schedule and exceptions. The person maintaining the ordering system should enter them and check how they appear. Ask your provider where these rules live, which settings take priority, and whether pickup and delivery can have different hours.
Use specific wording. “Online pickup is closed” is more useful than “We are closed” if the dining room is still open. If delivery is unavailable but pickup is open, let the guest choose pickup rather than blocking the entire ordering page. If neither service is available, say so plainly.
Keep the restaurant's website and ordering page consistent. A guest who sees “open until 9” on one page and “ordering closed” on another needs an explanation, such as “Online orders stop at 8:30 p.m.” That difference can be legitimate; leaving it unexplained creates unnecessary doubt.
Offer future ordering only when it is supported
Advance ordering can give a guest a useful alternative to leaving the page. It also creates a commitment: the restaurant must be ready to receive and fulfill the order at the chosen time. Before displaying that option, ask how the system handles future slots, menu availability, changes to hours, and orders that staff need to see before service begins.
Hypothetical example: A restaurant stops accepting pickup orders at 8:30 p.m. and resumes at 11 a.m. the next day. At 9 p.m., a guest visits the ordering page. If the system supports advance pickup orders and the restaurant has enabled them, the page could say: “Pickup ordering for tonight is closed. Schedule pickup for tomorrow from 11 a.m.” The button should lead to eligible future slots, not an immediate-order checkout.
If the restaurant does not accept advance orders, a better message is: “Online pickup is closed. Ordering reopens tomorrow at 11 a.m.” Remove or disable the order action, and give the guest a useful alternative, such as viewing the menu. Do not suggest that a guest can reserve a slot or submit an order unless the system can complete that action.
Future orders also need boundaries. Ask whether staff can set the earliest available slot, limit how far ahead guests can order, and prevent a slot from exceeding the kitchen's capacity. Decide what happens if an item is unavailable on the fulfillment day. If those controls do not fit the operation, reopening the ordering page at service time may be a better choice than taking commitments staff cannot reliably manage.
Payment timing matters too. Ask when a future order is charged or authorized, how a cancellation is handled, and what the guest sees if a scheduled order must change. Those are vendor and operational questions to settle before making advance ordering prominent.
Make the next opening time unambiguous
Show the next time the guest can perform the relevant action, not just the next time the building opens. Include the day and local time. Around midnight, holidays, and multi-day closures, an actual date can be clearer than “tomorrow.” If a guest may be in another time zone, identify the restaurant's time zone as well.
For example, a message might read: “Delivery ordering reopens Monday, December 28 at 5 p.m. Central Time.” That wording tells the guest which service will return and when. It does not promise that a delivery slot will be available at that exact moment unless the restaurant has configured one.
Keep the message close to the ordering controls. A guest should not have to search a footer or a separate hours page to understand why checkout is unavailable. If pickup and delivery reopen at different times, show both or clearly tie each time to its service.
Choose a fallback for situations where the next opening time cannot be calculated reliably. “Online ordering is currently closed. Please check our hours or contact the restaurant” is less precise, but better than displaying a date the restaurant has not approved. Link to an accurate hours page if your site has one; otherwise, keep the approved hours visible on the page.
This is a scheduled closed state, not a substitute for an outage message. If the restaurant should be accepting orders but the ordering service is unavailable, the guest needs a different explanation and a working alternative. Do not label an unexpected failure as normal closing hours.
Run a closed-state display checklist
Use a staging environment, preview mode, or another provider-approved simulation that cannot submit a real order. Confirm that the simulation will not charge a card, send a guest message, or dispatch a courier. If a setting cannot be checked safely in simulation, ask the provider to demonstrate it without creating those real-world actions.
The table below gives a starting set of scenarios. The expected result is the display you want to see; adapt the times and services to each location. A pass means the message and available actions agree with the approved schedule, not merely that a page loads.
| Scenario | What to set or simulate | Expected display and action |
|---|---|---|
| Before opening | Check shortly before the pickup ordering window starts. | Pickup is closed; the next pickup ordering time is shown. No immediate pickup checkout. |
| At the cutoff | Check just before and at the configured last-order time. | Ordering is available before the cutoff and closed at it, according to the restaurant's rule. |
| Different service hours | Set delivery closed while pickup remains open. | Delivery is labeled closed; eligible pickup ordering remains available. |
| Holiday exception | Apply an approved closure over a normally open day. | The normal schedule does not override the closure; the next valid opening is shown. |
| Future ordering | Simulate closed hours with advance orders enabled, then disabled. | Enabled: only eligible future slots appear. Disabled: no future-order action is offered. |
| Time zone change | Check a location near a daylight-saving clock change and from a device in another zone. | The displayed day and time match the location's approved schedule and identify its time zone where needed. |
Also check a closure that crosses midnight, a shortened holiday service, and a location with different hours from another location. Review the page on a phone as well as a larger screen. Buttons, dates, and service labels need to remain easy to read without relying on color alone.
Assign one person to record the result of each check and another to approve the schedule if possible. Note the location, simulated time, service, displayed message, and available buttons. Repeat the relevant checks after changing regular hours or adding an exception. A correct weekly schedule can still produce the wrong message if a holiday rule takes priority in an unexpected way.
A simulation checks the rules without creating an order. If you later run a live service pilot, use an approved real operating window and have staff monitor actual orders and fulfillment. Do not treat a simulation as proof that every part of live service will work.
Decide who maintains the page
A good setup needs an owner. Decide who changes regular hours, who enters exceptions, and who checks the guest-facing page after a change. For multiple locations, give each manager a way to confirm local hours while keeping a central record of who approved them.
Ask vendors whether staff can preview the closed message for a chosen location and service, and whether schedule changes take effect immediately or require another step. Also ask what staff will see when a future order arrives. The online ordering buying guide covers broader system questions; for this decision, focus on whether the displayed status follows your actual service rules.
Use the checklist on your current setup and bring any failed scenarios to your provider. If you are evaluating a new system, ask Fleksa about restaurant online ordering, the closed-state controls you need, and current availability for your US location.
Frequently asked questions
Should a closed ordering page still show the menu?
Showing the menu can help guests plan a later visit. Make it clear that browsing does not mean immediate ordering is available, and avoid an active checkout path when the service is closed.
Should the page say when the restaurant opens or when ordering opens?
Lead with the next ordering time for the selected service. If the dining room has different hours, label those separately so guests understand the distinction.
Can guests place an order while the restaurant is closed?
Only offer that option if the system and restaurant support advance ordering. Show eligible future fulfillment slots and make the timing clear before the guest submits an order.
