How to Lock Down Your Clover POS Before You Hire for the Holidays
By Yan Payments
What should I set up before a new seasonal employee’s first shift?
Give every new hire their own PIN and a role with limited permissions before they touch the register, not after. On Clover, that means adding them as an employee with their own passcode, assigning a role that restricts refunds, and reviewing a report of voids and refunds by employee at the end of each shift. None of this takes more than a few minutes per hire, and it’s the difference between a system with accountability and one where anyone behind the counter can quietly undo a sale.
Give every employee their own login, never a shared PIN
Clover lets you add employees either from the Employees app on the device or from the web dashboard under Account & Setup, then Employees. Each person gets a short passcode, commonly four to six digits, that identifies them on every transaction they ring up or modify. The temptation during a holiday hiring crunch is to hand a temp the same PIN everyone else uses, or whatever code was left over from last year. Don’t. A shared PIN means that when something looks wrong on a report later, you have no way to know which of three people working that shift actually did it.
Set roles so a new hire can’t refund or void on their own
Clover ships with Admin, Manager, and Employee as default roles, and you can edit those or build custom ones. Under Settings and Employee Permissions, you can restrict or disable who’s allowed to process a refund, and in many setups require a manager’s override above a certain amount. A seasonal hire generally doesn’t need refund rights at all in their first weeks; routing refunds through a shift lead keeps that path limited to someone accountable for it. Worth knowing on the void side: Clover only processes a true void within about 25 minutes of the original transaction. After that window, cancelling a sale goes through as a refund instead, which means your refund permissions are effectively your main lever for controlling after-the-fact corrections, not a separate void setting.
Why this matters more during holiday hiring specifically
Temporary holiday staff are, by definition, less trained and less known to you than your regular crew, and they’re often handling more cash and card volume per shift than at any other time of year. The Association of Certified Fraud Examiners’ 2026 Occupational Fraud report found that register disbursement schemes, voids and refunds abused to pull cash or value out of a sale, make up roughly 6% of occupational fraud cases, and that proactive, automated monitoring catches only about 3% of schemes; most get flagged by a tip from a coworker or customer, if they get flagged at all. Surprise reviews of transaction activity cut the typical length of a fraud scheme roughly in half.
A simple pre-shift checklist
- Add the employee in Clover with their own name and PIN, never a recycled or shared code.
- Assign a role that limits or disables refunds; reserve refund rights for a manager or shift lead.
- If your plan supports it, set a dollar threshold above which any refund needs a manager PIN to approve.
- Pull an end-of-day report sorted by employee at least weekly during the season, and actually look at who’s processing refunds and how often.
- Walk new hires through what they can and can’t do on the register before their first customer, not during it.
Where to check the exact settings on your account
Clover’s permission options and exact menu wording can vary slightly by plan and by how your account was set up, so the fastest way to confirm what’s available to you is checking Settings and Employee Permissions directly on your device or dashboard. If you’re not sure your current Clover hardware and plan even has role-based permissions turned on, that’s worth a quick call before your holiday staff starts.
Sources:
← Back to all posts