Show dining hours and online ordering hours as separate schedules, with plain labels and a short explanation when they differ. Put the schedules near each other on your website, then repeat any important restriction next to the order button. A guest should not have to start checkout to discover that online ordering has closed.
Before posting a notice, confirm what each time means. A dining room may be open until 10 p.m. while the kitchen stops accepting online orders at 8:30 p.m. Those are both useful facts, but neither should be presented as the restaurant's only closing time.
Confirm each service schedule
Start with the hours guests can use, not just the hours employees are on site. Ask the manager when the dining room opens and closes, and ask the kitchen lead when the last online order can be accepted. If pickup and delivery have different cutoffs, record them separately. Check whether those times change by day.
For each schedule, settle on a definition. Does “dining until 10 p.m.” mean guests may enter until 10, or that the dining room closes then? If the last seating is earlier, say so. Likewise, distinguish the last time an order can be placed from the latest available pickup time. A guest placing an order at 8:25 p.m. may collect it later; the notice should not make those two times sound identical.
The person responsible for the ordering system should confirm which destination the website button opens and what guests see there. If an outside provider controls that destination, ask who can change its hours and how long an update takes. The website editor should know where the public hours appear, including the homepage, contact page and order button area.
Keep a short record with the schedule, its effective date, the person who approved it and the person responsible for posting it. For a temporary change, add an end date and a reminder to remove or revise the notice. This prevents yesterday's exception from becoming next week's misinformation.
Label dining and ordering hours separately
Use names that describe the guest's action: “Dine-in hours,” “Online pickup ordering” and, if applicable, “Online delivery ordering.” Avoid a single “Open” label when one service is available and another is not. “Kitchen hours” can be useful internally, but guests still need to know whether they can sit down, place an order or pick one up.
Hypothetical example: A restaurant serves dine-in guests from 4 p.m. to 10 p.m. on Friday. It accepts online pickup orders from 4 p.m. to 8:30 p.m. Its last dine-in seating is 9 p.m. These are assumptions for the examples below, not a claim about any software's settings.
A useful notice would read: “Friday dine-in: 4–10 p.m. Last seating: 9 p.m. Online pickup ordering: 4–8:30 p.m. Pickup times are shown when you order.” The last sentence directs guests to the ordering destination for available collection times without promising a particular slot.
If delivery follows another schedule, give it a separate line rather than allowing “online ordering” to imply that both services have the same hours. If guests can call after online ordering closes, provide that option only if staff have agreed to accept those calls. Otherwise, the notice creates a second expectation the team may not be able to meet.
Keep the regular schedule easy to scan on a phone. Group the days that genuinely share hours, but show a separate line for a day with a different cutoff. Do not rely on color alone to distinguish an open service from a closed one. Clear text helps guests who skim and staff who need to answer questions consistently.
Put exceptions where guests make decisions
A homepage notice is useful for a temporary change, but it may not reach someone who lands directly on the menu or ordering page. Place the exception alongside the regular hours and near the relevant ordering link as well. If you control the ordering destination, check what notice can be shown there. If another provider controls it, ask how the exception will appear before and after the cutoff.
For the hypothetical Friday above, suppose online pickup ordering will end at 7:30 p.m. for one date, while dine-in hours and last seating remain unchanged. A notice near the order button could say: “This Friday only: online pickup orders close at 7:30 p.m. Dine-in remains open until 10 p.m.; last seating is 9 p.m.” Add the actual date when publishing so “this Friday” cannot be mistaken for a later week.
The notice explains the change; it does not itself change the ordering destination. Coordinate the message with whoever controls order acceptance, then confirm both are ready before the exception begins. If the destination cannot be updated in time, agree on an operational response before publishing. Do not advertise an earlier cutoff while leaving staff unaware that orders may still arrive.
Give exceptions an owner and a removal time. When the regular schedule returns, check the homepage, hours page and order-button area together. Keep the explanation short, but retain the date and affected service: “Online pickup closes early” is more useful than “Hours changed.”
Compare the display and test the destination
The table below compares common ways to present the hypothetical Friday schedule. The strongest choice depends on where a guest enters the site, so use the rows together rather than treating one placement as a complete solution.
| Display | What the guest sees | What to check |
|---|---|---|
| Single “Open until 10” line | One closing time, with no service named | Replace it or add service labels; it could suggest online pickup is available until 10. |
| Hours page | Dine-in until 10; last seating at 9; online pickup orders until 8:30 | Make the page easy to find and list different days separately. |
| Beside the order button | Online pickup orders accepted until 8:30 | Repeat dated early-close notices here so guests see them before leaving the site. |
| Ordering destination | Current availability or a clear closed message | Confirm its behavior matches the published cutoff and any dated exception. |
For this scenario, the hours page plus a short order-button notice is a sensible baseline: the first explains the full service schedule, while the second reaches a guest who is ready to order. The destination still needs to agree. A clear website cannot compensate for a checkout that accepts orders after staff have stopped taking them.
Check the boundary in a simulated or non-transactional environment if one is available. For the regular 8:30 p.m. cutoff, inspect what a guest would see just before, at and just after 8:30. Check the dated 7:30 p.m. exception separately. Use a device-sized screen as well as a desktop view, and follow the actual website button to the destination.
In a simulation, do not submit a real card payment, send a guest message or dispatch a courier. If there is no safe way to simulate the boundary, ask the provider to demonstrate it using a test environment, or inspect the published hours and closed message without completing an order. Record what you can and cannot verify.
A simulation checks the display and configured behavior; it does not prove that staff can manage a busy shift. A separate live-service pilot can check the real handoff with the team, using genuine orders only during normal service and the restaurant's ordinary processes. Watch for mismatches between the notice, the order destination and staff expectations, and assign someone to correct any mismatch.
As you review your restaurant website and online ordering destination, ask who can edit each notice, whether temporary hours can be dated, and what guests see when ordering is closed. If you are considering a change of website provider, the restaurant website builder comparison can help frame the wider buying decision.
Use the checklist above to review your current pages and ordering link. Then ask Fleksa about online ordering, including current US availability and how your proposed hours notice would connect to the ordering destination.
Frequently asked questions
Should dining and online ordering hours appear on the same page?
Yes. Showing them together makes the difference easy to understand. Also put the relevant ordering cutoff near the order button, where a guest may encounter it without visiting the hours page.
What should a temporary hours notice include?
Name the affected service, the actual date, the changed time and any regular service that remains available. Assign someone to remove or update the notice when the exception ends.
How can I check the cutoff without placing a real order?
Use a simulated environment or ask the provider for a test demonstration. Do not make a real payment, send a guest message or dispatch a courier for practice. If simulation is unavailable, inspect the displayed schedule and closed message without completing an order.
