Training staff on a new POS: twenty minutes each, and a rehearsal

The standard approach is a four-hour session with everyone in a room and a projector. By Thursday nobody remembers anything except that the new system is confusing.

Here is what works instead.

Three short sessions, not one long one

Session 1 — twenty minutes: the ordinary sale. Ring up three items, apply a discount, take cash, take card, print the receipt. Repeat until it is automatic. That is the whole session.

Session 2 — twenty minutes, next day: the exceptions. A return, a split bill, a held sale, a void, a price check, finding a product by name.

Session 3 — twenty minutes, day after: the shift. Open with a float, record a cash drop, close the shift, count the drawer, read the report.

Three days, an hour total per person. Spaced repetition beats a single long session by a wide margin, and it is easier to schedule.

Train on the real system with the real catalogue

Not a demo database with sample products. Your products, your prices, your modifiers, your receipt template.

Staff learn theshape of your catalogue as much as the software — where the karak button is, which category the pastries live in. Training on sample data teaches none of that, and the first real shift becomes the actual training.

The five tasks that cover 95% of a shift

Focus everything here:

1. Ring up and take payment — cash and card
2. Find a product that is not on the main screen
3. Apply a discount within their limit
4. Hold and resume a sale
5. What to do when something goes wrong — who to call, which button

Everything else — reports, stock, purchase orders — is for supervisors and can wait.

The rehearsal day

One full day of fake trading before go-live, ideally a week before.

Fifty sales, five returns, a shift close and a drawer reconciliation. Every problem that would appear on day one appears here instead, at no cost and with time to fix it.

Shops that skip the rehearsal find the problems in front of customers. It is the highest-value day in the whole project.

The printed one-pager

Laminate it, put it under the till:

• How to take a return
• How to split a bill
• How to hold and resume
• What to do when the internet drops — seeoffline rules
• What to do when the printer jams
• Who to call, with the number

One page. Anything longer is not read.

Language

If your staff are more comfortable in Urdu, Bengali or Pashto, train in that language and set the till interface to it. Wameed supports cashier interfaces in Urdu, Bengali and Pashto in addition to Arabic and English.

This is not a courtesy — it is an accuracy measure. A cashier reading their own language makes fewer mistakes on modifiers and prices, and the difference shows up in your void and refund numbers.

The first week

• A manager on the floor for the whole first shift, not in the office
• Collect complaints in one place — a sheet by the till
• Fix the top three by day three. Usually button layout, a missing product, or a permission that is too tight
• Do not add features in week one. Loyalty, promotions and reports can wait until the basics are automatic

What to measure

• Transactions per hour, compared to your old system after two weeks
• Voids in week one versus week four — it should fall sharply
• Support calls per day — should trend to near zero by week three
• Cash variance — should stabilise by week two

If voids are still high in week four, the button layout is wrong, not the staff. Go back and rearrange the screen from the sales data. Seepeak hour speed.