POS Staff Access Control: Roles, Discounts and Voids

In many Indian stores, everyone uses the same POS login, often the owner's. It is convenient until something goes wrong: a bill disappears, a 40 percent discount appears on a regular customer's bill, or the drawer is short. Then nobody knows who did what. POS staff access control fixes this by giving each person their own login or PIN and limiting what they can do based on their role. Honest staff are protected, mistakes are traceable, and the few dishonest actions become visible. This guide shows how to design roles, set limits that do not slow the counter, and run the routines that make access control work.

Why Shared Logins Are Risky

• No accountability: every void, discount and refund shows the same user.
• Over-permission: a new helper has the same powers as the owner, including deleting bills and changing prices.
• Former staff access: people who left still know the password.
• Disputes: when a drawer is short, honest cashiers cannot prove it was not them.

Suppose a hypothetical store gives away ₹1,200 a day in unrecorded or unauthorised discounts because anyone can type a price. That is ₹36,000 a month. Role-based limits alone often recover a large part of that.

Designing Roles

Start with a few roles that match how your store works:

Role	Typical permissions	Typical restrictions
Cashier	Billing, payments, own shift open and close, reprint last bill	No price changes, no voids after payment, discounts within a small limit, no reports beyond own shift
Senior cashier or captain	Cashier permissions, plus returns against bills, moving items between tables	Voids and cancellations need manager approval above a value
Store manager	Approvals, voids, larger discounts, stock adjustments, staff shift reports	No changes to tax settings or user roles
Owner or admin	Everything, including settings, roles, prices and reports across stores	Should not be used for daily billing
Pharmacist (for medical stores)	Scheduled drug sales, prescription records	As per role

Keep the number of roles small. Five well-defined roles are easier to manage than fifteen.

Individual Logins and Counter PINs

Everyone who uses the POS should have their own identity. For counters, a short PIN that a cashier enters when starting or switching is faster than a full username and password. Rules:

• PINs are personal and never shared; say this in training and mean it.
• Lock the screen automatically after a period of inactivity, so the next person has to sign in.
• Change PINs when someone may have seen them, and when staff leave.
• Owners and managers should have full passwords and, where available, two-step verification for back-office access.

Setting Limits That Do Not Slow the Counter

Too many approvals frustrate customers and staff, and managers start sharing their PIN to avoid being called. Set limits based on value and risk:

• Line void before payment: allowed for cashiers (customers change their minds), but logged.
• Line void or bill cancellation after payment: manager approval always.
• Discounts: cashier up to a small percentage or fixed value; manager above.
• Price override: manager only, with a reason.
• Returns: cashier against a linked bill up to a value; manager for no-bill returns or high values.
• No-sale drawer open: logged, and reviewed if frequent.
• Reprint of an old bill: logged, because reprints can be misused to "return" items.

Manager Approvals Done Right

When an action needs approval, the manager should enter their own PIN on the cashier's screen. The log then records both: who requested and who approved. Avoid letting managers give cashiers their PIN "to save time". If approvals are slowing the counter, adjust the limits rather than sharing PINs.

For restaurants, the same applies to KOT cancellations after printing, moving items between tables, complimentary items and discounts on bills. See our restaurant KOT system guide for the restaurant-specific controls.

Activity Logs and Exception Reports

Access control works only if someone looks at the logs. Each week, review an exception report showing, by user:

Exception	What to look for
Voids after payment	Any at all should have a reason
Discounts given	One person far above others on the same shift
Returns processed	Cash refunds without matching customers
Price overrides	Repeated overrides on the same items
No-sale drawer opens	Frequent opens without bills
Bill reprints	Reprints of bills from earlier days

Look for patterns rather than single events. The weekly review takes 15 minutes and, once staff know it happens, the numbers usually improve on their own. Our guide to cash drawer reconciliation covers how these exceptions show up at shift closing.

Common Fraud Patterns That Roles Prevent

• Sweethearting: a cashier scans only some items for a friend or relative. Controls: customer display, random bag checks, and comparing items per bill by cashier.
• Void after payment: the bill is printed and paid in cash, then voided, and the cash pocketed. Control: manager approval for any post-payment void.
• Fake returns: a return is created for a non-existent customer. Control: returns only against linked bills, with cash refunds above a limit approved.
• Price override: an expensive item is billed at a lower price. Control: block overrides for cashiers.

Back-Office Access

Counter permissions are only half the picture. Restrict back-office functions too:

• Changing item prices and tax rates: owner or a designated manager.
• Creating items and barcodes: a trained person, to keep the item master clean.
• Stock adjustments: store manager, reviewed by the owner.
• Customer data export: owner only, to protect privacy.
• User and role management: owner only.

Onboarding and Offboarding Staff

When someone joins

1. Create their user with the right role; never copy the owner's role.
2. Issue a PIN and explain that it is personal.
3. Train on billing, payments, returns and closing under supervision.
4. Review their first week's exception report together.

When someone leaves

1. Deactivate their user on their last day, before they leave the premises.
2. Close any open shifts in their name.
3. Change any shared credentials they knew, such as Wi-Fi or a shared device lock.
4. Keep their historical records; do not delete the user, as logs must remain.

A Worked Example: Reading One Week of Exceptions

Suppose a hypothetical store with four cashiers reviews its weekly exception report:

Cashier	Bills	Voids after payment	Discounts (₹)	Cash refunds (₹)
A	620	1	1,850	400
B	590	0	1,620	0
C	540	6	5,300	2,900
D	610	1	2,010	350

Cashier C stands out on all three measures. That does not prove wrongdoing; C may work the shift with more returns, or may not have understood the discount rules. The right first step is a calm conversation and a look at the specific bills, not an accusation. Often the answer is training. When it is not, the log gives you the facts.

Explain the Why to Your Team

Staff sometimes read access control as distrust. Explain it as protection: individual logins mean no one can be blamed for someone else's mistake, and approvals mean a cashier is never alone when a difficult customer demands a large discount. Teams that understand this usually support the system.

Multi-Store Considerations

In a chain, users should be limited to the stores they work in. A cashier in Store A should not be able to bill or see reports in Store B. Area managers may have access to several stores. Owners see everything. Check that your POS supports location-based access, not just role-based access.

Common Mistakes

• One shared login for all staff.
• Managers sharing their approval PIN with cashiers.
• Limits so strict that every bill needs approval.
• Never reviewing activity logs.
• Leaving former employees active in the system.
• Owners using the admin account for daily billing.

Access Control Setup Checklist

1. Roles defined and documented.
2. Every user has an individual login or PIN.
3. Discount, void, return and price override limits configured.
4. Manager approval flow tested at the counter.
5. Weekly exception report scheduled and owner assigned.
6. Onboarding and offboarding steps written down.

Practical Questions Owners Ask

Can managers approve actions remotely?

Some systems allow remote approvals from a phone, which helps when the manager is not at the counter. Use it carefully, because the approver cannot see the customer or the goods. For high-value voids and refunds, an in-person approval is safer.

How many user roles does a small store need?

Usually three to five: cashier, senior cashier or captain, store manager and owner, plus specialist roles such as pharmacist where relevant. Fewer, clearer roles are easier to manage than many narrow ones.

How Fininvo Fits

Fininvo's Retail & POS workspace includes a staff and access area with people, access presets, counter PINs and a sign-in log, plus an activity record of counter actions. Some modules are switched on per account, so confirm on the pricing page, and explore Fininvo ERP.

Frequently Asked Questions

Why should each cashier have a separate POS login?

Separate logins make every bill, void, discount and refund traceable to a person. This protects honest staff and helps identify mistakes or misuse.

What discount limit should a cashier have?

It depends on your margins and offers. Many stores allow a small fixed or percentage discount for cashiers and require manager approval above it.

Should cashiers be allowed to void items?

Voiding a line before payment is normal and can be allowed with logging. Voids or cancellations after payment should always need manager approval.

How often should I review POS activity logs?

A weekly review of exceptions by user is a practical minimum, with daily checks for high-value voids or refunds.

What should I do when a staff member leaves?

Deactivate their user immediately, close their open shifts, change any shared credentials they knew, and keep their history for audit.