Services and reservations

Ordering.co Customer App can present professional selection, service products, and table reservations as separate journeys. What a customer can select depends on the business, the current order context, schedule, and configuration. A visible choice is not a confirmed booking, reservation, cart, payment, or order.

Availability

The Reservations entry, table-only booking, and preorder choice appear only when the current business and project make them available. Date and time choices are candidates until the current reservation and checkout flow accepts them.

Choose the right journey

Journey	Customer purpose	Important boundary
Professional filter or profile	Find a professional and open the available booking entry.	Opening a profile or selecting Book does not reserve a time or establish calendar capacity.
Service product	Review service-specific choices, including an available professional or date.	A product form, local selection, or cart change does not by itself confirm the service reservation.
Table reservation	Request a table for a party, date, and time.	A displayed slot, completed form, or checkout page is not a confirmed reservation until the owning flow accepts it.

Service customization, cart updates, calendar reservation, and table-reservation cart creation can settle separately. If the app returns to a previous screen or an editor closes, do not assume that a booking, reservation, or cart update finished.

Customer table-reservation journey

When a business offers reservations, customers can follow this journey:

1. Open the business they want to visit.
2. Select Reservations from the business profile when the control is shown.
3. Choose the available reservation method:
   • Table reservation to request a table only.
   • Table reservation & preorder to request a table and choose available menu items in advance.
4. Enter the requested party size.
5. Choose an available date and time.
6. Review the checkout fields and the final action that the current experience presents.

The checkout layout, amount, confirmation, mapping, and tracking details can vary by configuration. Do not promise a zero-cost reservation, payment result, directions handoff, or confirmation merely because a screen displays one. A visible date or time can change with the business schedule, time zone, interval, duration, lead time, capacity, existing overlaps, open state, order context, or current server validation.

The linked table reservations demo is historical. Its external destination and content have not been verified as a current procedure.

Configure the supported reservation journey

An administrator should first make the reservation order type available for the project where it is supported:

1. In Dashboard, open Settings.
2. Open Standard settings.
3. Open Order Type Settings, then Order Types Allowed.
4. Enable Reservation when it is available for the project, then save the configuration.

See Available order types for the current Dashboard configuration boundary.

For business-specific rules, open Stores → Stores, select the business, and look for Reservations in that store's configuration. The historical source describes this area after scrolling down the selected business. The current store workspace shows Reservations only when its reservation and Website 2.6 conditions are met; see View and edit a store.

The historical configuration listed these business-level rules. Confirm the exact current fields and labels before saving any of them:

• minimum and maximum guest count;
• how far ahead customers can book and how soon a reservation can be made;
• a grace or table-hold period for late arrivals; and
• whether preorder is available with a table reservation.

Set these rules to match the business's seating process, staff coverage, and current availability. A historic example used a 10–15 minute late-arrival window, but that is an operating choice, not a universal setting.

Locate and manage reservations

Open Orders → Orders list to review the order records available to your role; see View and manage an order. The historical workflow describes reservations in that list with a dedicated status badge. Use that badge to locate a reservation only if the current project still shows the corresponding record and label.

The historical workflow also says staff could log details, track upcoming arrivals, and modify a booking from the operational list. Confirm the current status labels and allowed actions in the project before making a change. A visible record or control does not by itself confirm a reservation, a booking change, or a notification outcome.

For table reservations with preorder, treat the table request and menu choices as related but separate outcomes. Do not tell a customer that food will be prepared, a table will be held, or an order is complete until the current reservation and order surfaces confirm their respective outcomes.

Recognize incomplete or changed states

Situation	What to do
The reservation form closes	Return through the supported flow and review the current reservation or cart state once.
The professional, date, or time changes	Treat the new context as a new candidate; availability can be rechecked.
A cart changes but the reservation does not	Treat the result as partial.
A reservation form clears or shows an error	Do not infer rollback, capacity, or booking status.
A response is lost	Keep the service, reservation, cart, calendar, provider, and order outcome unknown until the owning surface reconciles it.

Do not repeat a selection, booking request, reservation, cart action, or provider action simply to force the screens to agree.

Accessibility and privacy

Reservation controls need clear names, selected and unavailable states, error messages, and predictable focus return. Customers must be able to understand party size, date, time, preorder, loading, and error states without relying on color or motion alone.

Reservation details can include customer contact information, a professional, date, time, party size, and cart context. Keep those details inside the authorized customer or operational flow. When reporting a problem, describe a value-free state such as “reservation request unresolved” rather than sharing customer or reservation data.

Related guides: Browse businesses · Customize a product · Schedule and preorder · Review your cart