The checkout flow
The last part of the booking process is called the checkout. Which screens a visitor sees there is not fixed: it is determined by two settings and by whether the visitor is already logged in. This article shows which combinations exist, so you can predict what your visitor sees.
The two settings that determine it
| Setting | Value | Effect |
|---|---|---|
| Merge confirmation (merge confirm) | On / off | When this is on, the customer details screen and the confirmation screen are merged into one page. |
| Save user mandatory (save user mandatory) | 0 – 3 | Determines whether an account screen appears and what the visitor may do there. See below. |
These settings live in the admin under the customer page configuration. To see it you need the menu_config_front_config right.
Save user mandatory
| Value | What the visitor can do |
|---|---|
0 | No accounts. The account screen is skipped; the visitor fills in their details per booking. |
1 | Free choice: log in, create an account, or skip and just fill in details. |
2 | An account is mandatory: log in or create a new one. Skipping is not possible. |
3 | As 2, but the system can also generate an account itself. |
The screens
| Screen | What is on it | Particulars |
|---|---|---|
| Account | Log in, create an account, or skip. | Does not appear with setting 0, nor when the visitor is already logged in. |
| Customer details | The customer form, editable. | — |
| Confirmation | The booking, the customer details for checking, captcha, remarks and gift voucher. | Via “back” the visitor can still change their details. |
| Merged | Customer details and confirmation on one screen. | Only when “merge confirmation” is on. |
| Final page | The confirmed booking, optionally with a payment block. | Going back is not possible. When “make another booking” is on, a link appears there. |
Which order does your visitor get?
The order follows from the two settings plus whether the visitor is already logged in:
| Logged in? | Merge | Account mandatory | Order |
|---|---|---|---|
| No | Off | 0 | Customer details → Confirmation → Final page |
| No | On | 0 | Merged → Final page |
| Yes | Off | any | Customer details → Confirmation → Final page |
| Yes | On | any | Merged → Final page |
| No | Off | 1, 2 or 3 | Account → Customer details → Confirmation → Final page |
| No | On | 1, 2 or 3 | Account → Merged → Final page |
Two rules explain every case:
- Merging replaces two screens with one. It changes nothing else about the order.
- The account screen only appears when accounts are switched on and the visitor is not yet logged in. If they log in there, that screen does not come back — if they create a new account without logging in straight away, it does, for instance when they press “back”.
See also
How the visitor reaches the payment page is described in Payment entry points. You set up the final page itself on Checkout final page.
On the merged screen the customer details behave slightly differently. If the details are already known, they are shown read-only at first, with a button to change them. They are always validated: if they do not meet the configured requirements, the visitor still has to correct them. That keeps the customer database in order.
