FleetbaseFleetbase

Operating Hours

Set per-location availability windows — customers cannot place orders outside operating hours.

Operating Hours

Operating Hours define when a store location accepts orders. Hours are set per location (not per store) using the schedule manager on the location's edit panel.

Each store has a timezone field — operating hours are evaluated against this timezone, not the customer's local time or the server's UTC clock. Set the store's timezone correctly before configuring hours, in Storefront → Settings → General → Timezone; a store without one uses the organization's.

The store's clock

Hours, booking slots and booked times are wall-clock times in the store's timezone, and everything that shows them reads them on the store's clock:

  • The console shows the store as open or closed, and every time on an order (placed, due, booked, the steps, messages), in the store's time, whatever the timezone of the browser.
  • The Storefront app shows open or closed, the booking days and times, and booked times in the store's time, whatever the timezone of the phone.
  • Order notifications and booking slots are written in the store's time by the server.

The API gives each store's clock as timezone and utc_offset, the store's current offset from UTC in minutes (east positive), on stores, networks, a food truck's store and cart items' store. A custom app should read store times with it (store time = UTC + utc_offset) rather than the device's timezone, which some runtimes cannot convert to another zone. The offset is the one in effect now, so it changes when the store's zone changes daylight saving time.

Setting Hours

Make sure the correct store is selected via the store switcher.

Navigate to Storefront → Settings → Locations and open a location.

In the schedule manager, add per-day Start and End time blocks.

Leave a day empty (no time blocks) to mark it as closed.

Save.

Hours are stored in the store_hours table linked to the location via store_location_uuid.

Multiple Time Blocks Per Day

A location can have multiple time blocks in a single day — useful for restaurants that close between lunch and dinner.

Example — Tuesday schedule:

Block 1: 11:00 AM → 02:00 PM  (Lunch)
Block 2: 05:00 PM → 10:00 PM  (Dinner)

During the gap (2pm–5pm), the store shows as closed.

Overriding for Emergencies

If you need to close the store immediately (e.g., a kitchen emergency):

  1. Open the store
  2. Toggle Online to off

This overrides the operating schedule and immediately stops new orders regardless of hours. Re-enable Online when ready to resume.

For planned closures like holidays, update the hours for the affected week manually and revert afterward. Storefront does not have a built-in holiday calendar.

Product-Level Hours

Individual products can also have per-product availability hours (e.g. a breakfast item available 7am–11am only). Configure them via the Availability panel inside the product editor. See Products.

Catalog-Level Hours

Catalogs assigned to food trucks have their own hours via the CatalogHour model. Use these to gate which catalog is active at a given time without editing each location or product. See Catalogs.

Operating Hours | Fleetbase