Why the cashier screen speaks Urdu, Bengali and Pashto
This is not a diversity gesture. A cashier reading their own language makes fewer mistakes, and the difference shows up in your void and refund numbers within a month.
5 min read
In short: Much of the retail and hospitality workforce in Saudi Arabia reads Urdu, Bengali or Pashto more comfortably than English, but most POS systems offer only Arabic and English. A cashier working in a language they read slowly makes modifier errors, hesitates, avoids functions they cannot read and cannot self-correct; in the language they read fastest those problems fall. Wameed’s cashier interface is available inArabic, English, Urdu, Bengali and Pashto, set per user, so one terminal serves different staff; product names stay as you entered them and the customer’s invoice is always in Arabic and English. Ask each person, set their account, train in their language and check your void and refund numbers a month later.
A large part of the retail and hospitality workforce in Saudi Arabia is more comfortable reading Urdu, Bengali or Pashto than English. Most point-of-sale systems offer Arabic and English, and stop there.
Wameed offers cashier interfaces inUrdu, Bengali and Pashto as well. Here is the reasoning, which is operational rather than sentimental.
The error argument
A cashier working in a language they read slowly makes a predictable set of mistakes:
- Modifier errors. Selecting the wrong option from a list of similar-looking words, which is how the wrong item reaches the kitchen.
- Hesitation at the till. Half a second per screen, forty times an hour, at peak.
- Avoidance. A cashier who is unsure of a function avoids it. If they cannot confidently read the refund screen, they call a supervisor for every return — which is slower for everyone and hides the real problem.
- Errors they cannot self-correct. A mistake made and not understood becomes a void, a refund, or a customer complaint.
None of these are about capability. They are about reading speed under pressure, and they disappear when the interface is in the language the person reads fastest.
What we saw
Shops that switched their evening staff to an Urdu interface reported fewer voids and noticeably less hesitation on the modifier screens within the first weeks. It is not a subtle effect, and it costs nothing to try — the setting is per user.
The training argument
Training someone on a system in their second or third language takes longer and holds less. The same twenty-minute session in the language they think in produces a cashier who is independent by the second shift rather than the second week.
Seetraining staff.
What is translated, and what is not
Translated: the cashier interface — buttons, functions, prompts, error messages, the shift close, the return flow. Everything the person at the till reads.
Not translated: your product names. Those stay as you entered them, in Arabic or English, because they are what appears on the customer's invoice and on your shelf labels. A cashier reading an Arabic product name with an Urdu interface is the normal case, and it works — recognising a product name is a different task from reading an instruction.
The customer's invoice is always in Arabic and English as required, regardless of what language the cashier's screen is in. The interface language is an internal setting; the tax document is not.
How it is set
Per user, not per terminal. Each staff member's account carries their preferred language, so one terminal serves an Arabic-reading morning cashier and an Urdu-reading evening one without anyone changing a setting.
Where this sits in the market
Per our August 2026 audit, cashier languages beyond Arabic and English are present in Wameed and Odoo, and not in Foodics, NCR, Oracle, Rewaa, Marn, Revel, Geidea, Sapaad or Hala.
We think this is an oversight in the market rather than a deliberate decision by those vendors. The workforce is what it is, and building for the person who will actually use the software eight hours a day is not a feature — it is the job.
If you employ staff who read these languages
Three practical steps:
- Ask each person which language they read most comfortably. Ask rather than assume; some people prefer English and it is not always who you would guess.
- Set their account to it. Thirty seconds.
- Train in that language, and put the printed one-pager under the till in it too.
Then look at your void and refund numbers a month later. If they have not moved, nothing is lost. In our experience they move.
The broader point
Software is used by people, and the people using a point of sale are usually not the people who bought it. A system that is comfortable for an owner in a meeting and awkward for a cashier at 9pm on a Thursday is optimised for the wrong moment.
That principle shapes a lot of what we build, and this is one of the clearer examples of it.
See thelocalisation feature.
Related:training staff on a new POS,roles and permissions,peak hour speed andnew-employee onboarding.
Frequently asked questions
Which languages does Wameed’s cashier screen support?
Arabic, English, Urdu, Bengali and Pashto, set per user account.
Do product names and invoices change with the interface language?
No. Product names stay as entered, and the customer’s tax invoice is always in Arabic and English as required.
Why does the language of the screen affect errors?
Reading speed under pressure drives modifier errors, hesitation and avoidance of functions; the effect shows in void and refund numbers.
How do I switch a cashier to Urdu?
Set the language on that staff member’s account, which takes about thirty seconds; a single terminal can serve cashiers using different languages.
- #كاشير بالأردية
- #كاشير متعدد اللغات
- #لغات الكاشير
- #تدريب العمالة
- #Urdu POS
- #multilingual cashier
- #Bengali Pashto POS
- #staff training
Share this article
Ask about your own shop
Thirty minutes on your products, your tax setup and your hardware — not a slide deck.
Keep reading
7 min read
How we keep Wameed’s content honest: facts, limits, competitors and corrections
A vendor’s website is full of claims. Ours follow written rules: every product statement is checked against how the product works, limits are stated next to strengths, competitors are described only as far as public sources allow, and errors are corrected in the open.
7 min read
How Wameed keeps selling when the internet does not
Local-first, not cloud-with-a-cache. Here is what that actually means, what happens to the ZATCA signature, how two disconnected terminals are reconciled, and the one part that still needs the network.
6 min read
How Wameed’s accounting posts entries: from a till sale to a balanced, locked, auditable ledger
Accounting you can trust is about rules that cannot be bent. Here is how a sale becomes an entry, which documents post immediately, how the database refuses an unbalanced entry, and where the limits are.

