A new employee at the register: an onboarding checklist for the first shift

A new employee does not need to learn the whole register on the first day. Good onboarding for a first shift focuses on a personal login, a regular sale, checking a price, payment methods, stopping before an exceptional action and closing the station. Practice each step in a dummy transaction, define who to call when something goes beyond the rules, and only then allow independent work.

The goal is not to know every button, but to finish a shift without improvising

Register onboarding tends to fail in two ways. Sometimes the new employee is flooded with all the menus, reports and exceptions until no work sequence stays in memory. Sometimes the exact opposite happens: they watch an experienced employee for an hour, are then put in front of a real customer and everyone hopes they manage. In both cases there is no clear answer to the important question: what is the employee already allowed to do alone, and at what moment should they stop and call the supervisor.

The goal for the first shift should be limited and measurable. The employee logs in with their own user, opens the station according to the business's procedure, makes a regular sale, checks a product and price, accepts a payment method that was explained to them, issues the document the system allows, and hands over the station in an orderly way. Canceling a completed transaction, a refund, an exceptional discount, a permanent price change or opening the drawer without a sale stay outside initial independence until they are practiced and approved.

That way onboarding builds ability instead of false confidence. An employee who knows how to say "I'm stopping here and calling the supervisor" is safer than an employee who knows twenty screens but improvises in an exceptional moment.

Prepare the station before the employee arrives

Good onboarding starts before the shift. Open a personal user for the employee with the limited role needed, make sure the login works and prepare a practice environment that does not involve a real customer. There is no reason to waste the first minutes looking for a password, a manager code or a product you can scan without affecting stock.

Prepare one page, not a binder. It should include the order for opening the station, the names of the supervisors on shift, how to call for help, the payment methods the business accepts, and situations where you must not continue without approval. Add where to check price and stock, where to put a return, and what to do when the terminal or the printer does not respond.

It is also worth choosing practice products in advance: a regular item, a product with several variants, a product on promotion and an item that looks similar to another. If the business sells by weight, by unit or both, pick an example of each method. The goal is to practice the reality of the shop, not just demonstrate a perfect transaction.

Start with a regular sale from start to finish

The first part of onboarding is one complete path. The mentor demonstrates a transaction at a normal pace and explains out loud what they check: the user's identity, the branch and station, the product name, the quantity, the price, the promotion, the payment method and the amount that closes the transaction. Then the employee does the same sequence themselves in a dummy transaction.

Do not teach shortcuts at this stage. The employee needs to see the whole path, including fixing a mistake before payment, removing an item from the cart and checking that the amount changed. If there is a customer field, explain when to use it and when not to. Do not collect a phone number or email "because it might be useful" without a need, an explanation and a suitable process.

After the first transaction, repeat it with a small change: a different quantity, a similar item or a different payment method. Only when the employee can explain what they check at each step do you move to the next case. Speed comes from consistent repetition. It is not a goal for the first half hour.

Practice price, product and payment before a real queue arrives

Many mistakes at the register do not come from not knowing a button, but from identifying the wrong thing. So the employee needs to compare the product in their hand with the line on the screen: name, size, color, quantity, unit and barcode when available. For similar items, do not settle for a picture or a shortened name.

Create a scenario where the shelf price does not match the register. The employee does not invent a discount and does not send the customer off to prove it alone. They stop, verify the product and the label, call the supervisor according to the procedure and record what needs fixing. The guide on a gap between the shelf price and the register price details the check sequence and the difference between correcting the transaction and correcting the source of the price.

Payment methods also need a clear sequence. The employee needs to know what counts as an approval, what to do when the terminal shows a decline, and how to avoid a double entry when the response is delayed. If card processing is done on an external terminal, explain clearly that swiping the card and recording the payment on the register are separate actions that need to match each other. Do not guess whether a transaction went through. Check on the relevant screen and document.

Build a stop path for every exceptional action

The new employee is not expected to remember a solution for every exception. They do need to recognize the limit. Prepare a short list of situations where they stop: a price that does not match, a refund, a cancellation after payment, a discount above the threshold, a payment method change, opening the drawer without a sale, a product without a price, a terminal that does not respond, a receipt that did not print or a customer asking for an action the employee does not know.

For each situation, attach three details: what the employee does right away, who they call, and what they must not do while waiting. For example, when a printout is missing, do not run the transaction again automatically. First check whether the sale was already recorded. When a price is unknown, do not choose a similar product to move the queue along.

The guide on employee permissions on the register explains how to separate a regular action, an action that needs approval and a system change. In onboarding you use this map in practice: the employee tries an action that is supposed to be blocked, the supervisor approves with their own user, and both check that the reason and the identity were saved.

Teach privacy as part of service, not as a separate lecture

A register may show names, phone numbers, purchase history or employee details. The employee needs to know that information on the screen does not become material you can photograph, send to a group or open out of curiosity. Teach them to look up a customer card only for the service being given at that moment, to verify identity according to the business's procedure and to avoid collecting details that are not needed.

The Privacy Protection Authority's questions and answers on the information security regulations (in Hebrew), checked on 29 September 2026, explain that an authorized user is someone who was given access to information as part of their activity in the organization. In onboarding this means a simple rule: access is given by role and for the needs of the work, not because the screen is in front of the employee.

Also practice small habits: do not share a password, lock the station when you leave it, do not use another employee's account and do not leave customer lists on the counter. If the employee needs more information to solve a case, they turn to someone who is authorized to see it instead of trying to get around the restriction.

Connect onboarding to customer rights and records

A new employee needs to know which cases may turn into a complaint, without being expected to make a legal decision in front of the customer. The Consumer Protection Authority's public inquiries service, checked on 29 September 2026, lists among other things overcharging, price display, product marking and canceling a transaction, and notes that receipts, invoices and photos may support an inquiry.

So onboarding should include three habits: do not promise an answer the employee has no authority to give, do not delete or change records to "sort out" the case, and give the customer a clear explanation of the next steps. The employee records the product, the transaction and the exception according to the business's procedure, without collecting unnecessary personal details.

The point is not to scare the employee with the law. They need to know that the receipt, the reason for a cancellation, the approver's identity and the price correction are part of a service that can be reconstructed. When there is a dispute or a legal question, pass it to the right person and do not improvise a rule in front of the queue.

Finish with a station handover, not just "got it?"

Before the employee leaves the shift, they need to do a handover. Check open transactions, pending returns, equipment problems, cash according to the business's procedure and exceptions that still need handling. The employee says out loud what is still open and who it was passed to, instead of settling for a general message that "everything is fine".

The mentor uses a short checklist: personal login, regular sale, correction before payment, spotting a price gap, calling the supervisor, protecting privacy and handing over the station. Next to each item, mark "done alone", "done with guidance" or "not yet practiced". Do not grant independence by the number of hours that passed, but by actions that were observed.

The KupaLi features page describes role-based permissions, shifts, controlled discounts and bringing exceptions together on the relevant plan. These can support onboarding, but they do not replace a business procedure and an available mentor.

Check again after the first shift

At the end of the shift the mentor asks concrete questions: at which stage did you feel unsure, which action took too many steps, which product was hard to identify, and was there a moment when it was not clear who to call. Answers like these are more useful than "it was fine".

On the next shift, repeat exactly the points that were not completed. If the employee knew how to sell but got stuck on a payment decline, practice a decline. If they called the manager for every small correction, check whether the permission or the procedure is too narrow. If they tried to get around a block, check whether the limit was explained and whether the approval path is available at busy times.

Good onboarding also gets better for the next employee. Keep problems and notes without unnecessary details, fix the onboarding page and update the practice scenarios. That way the knowledge does not depend on one experienced employee, and every new employee gets the same clear starting point.

What to take to the next shift

• Define in advance which actions the employee must do alone and which need approval.
• Open a limited personal user and prepare a dummy transaction and practice products.
• Practice a full sale, a price gap, a payment decline and a blocked action.
• Write a stop path: what to do, who to call and what not to do in the meantime.
• Check privacy, records and the station handover as part of the same onboarding.
• Give independence based on observed performance, not on time that passed.

This is a general operational guide, not legal, accounting or information security advice.