### Apply number of customers

The number of customers (also called number of guests or number of guests) is mainly used for evaluations. There are different methods to capture this number. To obtain this information on the financial report, the switch for the **average display in the financial **report must be switched on in the **Front Office report settings**.

Each completed transaction can be counted and the transaction average can be calculated as the divisor of the turnover:

Total sales / number of operations = average of operations

However, since several customers can participate in a transaction, it is important to enter the number of customers per transaction for the average revenue per customer. For this there is the cash register function Number of customers. You can enter a number at any time when the process is open and activate the checkout function Number of customers. You can also overwrite the number again.

Unfortunately, in practice the number of customers is usually not entered because the operators are not used to it or find it annoying and in fact some of them deliberately enter wrong numbers. This results in the number of transactions remaining as divisor and the average per customer being calculated higher, or even completely wrong numbers being entered.

One way to safely enter the number of customers is to force the operator to enter the number of customers per operation when creating a new operation. Should this change later, the operator has the option of entering a different number at any time until the process is completed. To do this, you must setthe option Number of customers to Force in the operator authorizations. A too early compulsion is particularly annoying if the operator does not yet know how many guests it will actually be.

You can also simply use the average per transaction in evaluations. To do this, choose the setting **Number is determined**per activity in the Report Manager.

The number of customers can be corrected after completion of the procedure in the Master Procedure Overview program.

The number of customers is also taken into account if it is a reopened transaction (for example, from the previous day).

Best practice Number of Customers

(When working with an integrated reservation system, there is another method: Turning best practice walk-ins into check-ins).

If you want your operator to have a little more freedom when entering the number of customers, you do not need to force their entry when creating the process. You can allow the operator time to enter a number of customers until the operations are completed. To do this, you also place the Checknumber of customers cash register function on the end keys. If, in the meantime, a number of customers has been entered, the process can be completed immediately, but if an attempt is made to complete the process without entering a number of customers, the entry will be forced upon completion. This allows the operator to determine when the best time to enter the number of customers for the operation is (this function can also be activated for mPOS and CLOU MOBILE). In addition, the plausibility of the number should be checked:

Plausibility check of the number of customers...

A plausibility check can also be used to protect the operator from accidental and relevant incorrect entries.

To do this, you define valid values for a minimum and maximum average receipt in the global settings for ward management. When entering the number of customers, the current average receipt is calculated and checked against the specified limits.

- If the average is outside the specified range, the dialog for entering the number of customers is displayed again with the (possibly incorrect) number of customers entered. The operator can now check his entry and confirm or correct it. If the input is repeated with the same number, the number is also accepted outside the limit values. If the input has been changed, the plausibility check is carried out again, which then decides whether the number is accepted.
- If there is only one single item booking in the process, the average is not checked, so it is saved immediately even if it is outside the specified range.

Further documentation:

Number of customers when merging...

Changing the number of customers

Special feature: Number of customers for splitting

When splitting a process, the operator must take into account the existing number of customers.

All systems support the entry of the number of customers during closing and the plausibility check (see **Best Practice** above). Especially for mobile devices, we recommend entering the number of customers at the end of a process or at the end of a splitting process. In general, the number of customers with open processes can also be entered again and repeatedly for these processes.

Here is an overview of the handling of the different systems:

At the Hypersoft POS System...

If there is a number of customers in the process, the number of customers is queried again during splitting, and the answer then applies to the split portion. The remaining source transaction receives the difference from the original number of customers minus the number of customers of the split share entered during splitting.

On the Hypersoft CLOU MOBILE for Windows, mPOS Handheld and Tablet...

mPOS also queries the number of customers for the split. After the split, the number of customers for the remaining bookings is queried again so that a correct number of customers is immediately available in the open transactions.

On the Hypersoft CLOU MOBILE for Orderman...

An already entered number of customers is transferred to the target operation and remains unchanged in the source operation. If you split an transaction with customer number 2 into two transaction , the number of customers would be 4.

Special feature: Transactions without number of customers or without sales volume

In the advanced options, you can set whether transactions without number of customers (with 1) or transactions without sales (with any number of customers) should be included in the calculation.

Special Case: Determine Customers Based on Items

In the Report Manager, you can select items from which the number of customers can be determined. These can be covers or other special items. These evaluations can only be carried out in the Report Manager. Further documentation: Options: Advanced Options

Special feature: customer cards in the cashless area

If you work with customer cards in a cashless area, every customer receives a card. When leaving the area, it can happen that one of a group of people alone has the bookings on his customer card, because he wants to invite his companions. If you were to use the other cards for payment now, there would be no bookings on them and thus no completed process would be counted - the number of these customers would be lost. You can counteract this by merging all cards with the card that carries the bookings when paying. With this method, the paying card receives the total number of cards, which thus represents the number of customers.

Evaluations of the number of customers

The number of clients is a standard value that is included in many reports. In addition, you can view the G Customer count and transaction evaluations section in the Report Manager.

If you want to evaluate the number of customers together with the shifts, use thePoint of sale report by number of customers and shifts.

While posting to an open transaction, the number of customers can be overwritten as often as desired. After closing a curtain and also after a daily closing, the number of customers can also be corrected from the master transaction overview. For this, see the description Change the number of customers with the master transaction overview.

Further documentation:

Turning best practice walk-ins into check-ins

Average display in the financial report...

G Customer count and transaction evaluations

Back to the parent page: