Security questions to ask a POS vendor (and the answers that should worry you)
Your POS holds your customers, your prices, your margins and your invoices. Here are twelve questions worth asking, what a good answer sounds like, and what a bad one means.
5 min read
In short: A POS holds your customer list, cost prices (and therefore margins), supplier terms, staff records and every invoice, so ask the vendor twelve questions: can every employee have their own login, how granular are permissions, can a manager approve overrides without typing a password at the till, is there a real audit log, where is data stored and who can see it, is it encrypted in transit and at rest, what happens to card data (it should never touch the POS), how are backups tested, what is the breach-notification process, is there a status page, how is personal data handled under the PDPL, and can you export and delete everything. Walk away from shared logins, stored card numbers or paid export.
A point of sale holds more sensitive information than most merchants realise: your full customer list with phone numbers, your cost prices and therefore your margins, your supplier terms, your staff records, and every invoice you have ever issued.
Here are twelve questions worth asking a vendor, with what a reassuring answer sounds like.
Access and accounts
1. Can every staff member have their own login?
Good: yes, unlimited users, each with their own permissions.
Worrying: a per-user charge that pushes shops towards shared logins. A shared login means no accountability, forever.
2. How granular are permissions?
Good: separate permissions for discounting, refunds, credit notes, price changes, viewing reports, viewing cost prices, and closing shifts.
Worrying: "cashier" and "manager" as the only two roles.
3. Can a manager approve an override without typing their password in front of a cashier?
Good: a PIN, a badge, or an approval on the manager's own device.
Worrying: the manager's password gets typed at the till, which means every cashier eventually knows it.
4. Can I see who did what?
Good: an audit log covering logins, price changes, permission changes, refunds, voids and exports — with the user and timestamp.
Worrying: "you can see sales by cashier." That is a report, not an audit trail.
The data itself
5. Where is my data stored, and who can access it?
Good: a clear answer about region, plus a statement of which of their staff can access customer data and under what controls.
Worrying: vagueness, or "our engineers can access anything they need to."
6. Is data encrypted in transit and at rest?
Good: yes, with specifics.
Worrying: "it's secure" without detail.
7. What happens to card data?
Good: card data does not touch the POS; it is handled by the payment terminal and the processor. This is the right architecture.
Worrying: any suggestion that the POS stores card numbers.
8. How are backups handled, and have you tested a restore?
Good: automated, encrypted, with a stated retention, and a restore tested on a schedule.
Worrying: backups mentioned but restores never tested. A backup nobody has restored is a hope, not a backup.
When things go wrong
9. What is your breach notification process?
Good: a defined process with a timeline, and a commitment to notify affected customers.
Worrying: no process, or "that has never happened to us."
10. What is your uptime history, and where can I see it?
Good: a status page with history.
Worrying: a number in a contract with no way to verify it.
Saudi specifics
11. How do you handle personal data under the Personal Data Protection Law?
Your customer list is personal data. You are the controller; the vendor is likely a processor. You need to know:
- What they do with it
- Whether they use it for anything other than providing you the service
- How a customer's deletion request is handled
- What happens to it when you leave
Good: clear answers and a data processing agreement.
Worrying: having to explain what PDPL is.
12. Can I export everything, and delete everything?
Good: export is self-service and included; deletion on termination is defined with a timeline.
Worrying: export is a paid service, or deletion is undefined.
The answers that should end the conversation
- "We don't do individual logins, everyone uses the shop account."
- "The POS stores the card number for refunds."
- "You can't export the data, but you can view it any time."
- "We've never had to think about that."
What we do
Per-user accounts with granular permissions and an admin activity log; card data handled by the payment provider and never stored in the POS; data export self-service and included; a defined deletion path — there is adata deletion request page for exactly that; and aprivacy policy that says what we hold and why.
Ask us these twelve. Ask everyone these twelve.
Related:audit logs: who did what,roles and permissions,customer data and the PDPL andbackup and data export.
Frequently asked questions
What security questions should I ask a POS vendor?
Per-user logins and granular permissions, manager overrides without sharing passwords, an audit trail, where data is stored and who can access it, encryption, how card data is handled, tested backups, breach notification, uptime history, PDPL handling and export and deletion.
Should a POS store card numbers?
No. Card data should be handled by the payment terminal and processor, never stored in the POS.
What is PDPL and does it apply to my POS?
Saudi Arabia’s Personal Data Protection Law. Your customer list is personal data; you are typically the controller and the vendor a processor, so ask for a data processing agreement.
Can a POS vendor’s engineers see my data?
Ask which of their staff can access customer data and under what controls. “Our engineers can access anything they need” is a worrying answer.
- #أمان نظام الكاشير
- #حماية البيانات
- #نظام حماية البيانات الشخصية
- #صلاحيات الموظفين
- #POS security
- #PDPL
- #data protection
- #audit log
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
6 min read
The complete guide to a cashier system (كاشير) in Saudi Arabia: what it is, what it must do and how to choose
A cashier system is more than a screen that rings up a sale. In Saudi Arabia it must issue ZATCA-compliant invoices, take mada, keep stock honest, work when the internet drops and grow with you. This is the whole checklist.
5 min read
POS or ERP for a small business? When a cashier platform is enough and when you need more
ERP promises one system for everything; a POS promises a fast till. For a shop or restaurant, the modern answer is often a POS platform that already includes inventory, purchasing, accounting and HR. Here is how to decide.
5 min read
Customer display for a cashier (شاشة العميل): second screen, pole display and what to show
A customer display shows each item and the total as it is scanned. It builds trust, catches mistakes while they are cheap to fix, and gives you a place for offers. Here is how to choose and use one.

