Jezzam uses an order-based booking structure. This means a customer can make one booking, or use the basket to add several bookings and complete them together as one order.
This article explains the difference between bookings, orders and baskets, and how they work together in Jezzam.
What is a booking?
A booking is an individual appointment or a place booked on a class, course, workshop or event.
For example, a booking might be:
One appointment with a staff member
One place on a class
One place on an event
One repeat appointment in a set of repeat bookings
One booking made through the Admin calendar
Each booking still has its own details, such as the service or event, date, time, customer, attendee information, payment status and booking workflow.
What is an order?
An order groups together one or more bookings.
A simple order may contain just one booking. For example, a customer books one appointment and completes checkout.
A larger order may contain several bookings. For example, a customer might add more than one appointment, several places on a class, or different events to the basket, then review the basket and place them together as one order.
Orders make it easier to group related bookings together, take one payment for multiple bookings where online payment applies and provide customers with a clear order history.
What is a basket?
The basket is used during online booking.
Customers can add one or more bookings to the basket, review them in one place and complete checkout when they are ready.
When checkout is completed, Jezzam creates an order from the contents of the basket.
If there is only one booking in the basket, the order will contain one booking. If there are several bookings in the basket, the order will contain multiple bookings.
Jezzam's basket feature can be controlled in your account settings. If it is not enabled, customers can still make single bookings as normal, and Jezzam will still create an order for each booking.
How bookings, baskets and orders work together
The general flow is:
The customer selects a booking.
The booking is added to the basket.
The customer can add more bookings to the basket, if needed.
The customer reviews the basket and amends it if needed.
The customer completes checkout.
Jezzam creates an order containing the booking or bookings.
An order email is automatically sent to the customer (and optionally, administrators of the account)
This flow supports customers making one booking or adding several bookings to the same order.
Single bookings
Customers do not have to make multiple bookings.
If a customer only wants to make one booking, they can do that. The booking goes through checkout and Jezzam creates an order containing that single booking.
This means the order structure applies consistently, whether a customer makes one booking or several bookings at the same time.
Multiple bookings
Customers can make multiple bookings as part of one order.
This can be useful when customers want to:
Book more than one appointment
Make repeat bookings more easily
Book multiple places on events, classes, courses or workshops
Make bookings across different events, classes, courses or workshops
Pay once for multiple bookings where online payment is required
The exact options available depend on how the account, services, events, payments and booking workflows have been configured.
Orders with different payment types
An order can include bookings with different payment types.
For example, the same order can include:
Pay now bookings
Pay later bookings
Free bookings
Where an order includes pay now bookings, the pay now total is calculated and paid during checkout.
Bookings that are set to pay later can still be managed separately in line with your normal business payment process.
Prices and order totals
Order totals are based on the bookings included in the order.
If a service, event, class, course or workshop has a price but is not set to show that price to customers, that price is not included in the customer-facing order total.
Admins can still view the internal payment information in the admin panel where needed.
Orders with different booking workflows
An order can also include bookings with different booking workflows.
For example, the same order can include:
Confirm now bookings
Bookings requiring admin approval
Pencilled in bookings
Each booking keeps its own workflow. This means one order can contain bookings that are confirmed immediately, bookings that need admin approval and bookings that need the customer to complete a pencilled in booking process.
Where customer action is needed, Jezzam automatically includes the relevant action buttons in the order email.
After the order has been placed, each booking is managed separately. This means emails about approval, confirmation, pencilled in bookings, rescheduling or other booking status changes are sent for the individual booking, rather than sending the full order email again each time. This keeps customer emails simple, focused and efficient, while the order email remains the main summary of the order as a whole.
Admin calendar bookings
Bookings made through the Admin calendar also create orders.
When creating bookings through the Admin calendar, admins can optionally send an order email to the customer.
Repeat appointment bookings made through the Admin calendar can be grouped into a single order. Bookings made across repeating events can also be included in a single order.
Where applicable, these bookings can use workflows such as online payment and pencilled in status, with the customer receiving an email so they can complete the relevant steps.
This makes it easier to manage more complex admin-created bookings, while keeping the customer communication clear. Instead of treating each repeat booking or repeating event booking in isolation, related bookings can be handled together as one order, with each individual booking still managed separately where needed.
Customer orders in the admin panel
The Customers section in the admin panel includes an Orders tab.
This lets admins view order information linked to a customer.
You can also resend the order email to the customer if needed. When resent, the email reflects the current state of the order.
As part of this update, orders have automatically been created for existing customer bookings, so older booking information can also be viewed in the new order-based layout.
This gives admins a simple, centralised way to review a customer's order history and send them an up-to-date copy of their order information when needed.
Orders in the user profile
Customers can view their bookings and orders through their user profile.
This includes:
Future bookings
Individual booking details
Past orders
Previous booking history
Customers who booked as guests can also access relevant booking and order information online. Instead of needing a full User Profile to log in, a one-time code is sent to them so they can confirm access to their booking information.
Order emails and single booking emails
When an order is first placed, Jezzam sends an order-based email.
The 'Order placed' email contains details of the order and the booking, or bookings, included in it. This gives the customer one email covering the order as a whole, rather than separate emails for each booking at the point the order is placed.
After that, single booking emails are used for actions relating to individual bookings, such as rescheduling. This means customers receive an email about the specific booking that has changed, rather than receiving the full order email again each time.
The order email can also be resent from the Customers section if needed. When resent, it reflects the current state of the order.
Summary
In Jezzam:
A booking is an individual appointment, event place, class, course, workshop or similar booking.
A basket lets customers collect one or more bookings before checkout.
An order is created when checkout is completed.
An order can contain one booking or multiple bookings.
Orders can include different payment types and booking workflows.
Admin calendar bookings also create orders.
Customers and admins can view order information more clearly.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article