Skip to content
Staff & rotas

Retail staff scheduling software for repair and electronics shops

Let the shop use the system without handing over the shop. SlickCell is retail staff scheduling software built into the same system as your till, repairs and stock: weekly shifts, clock-in, leave and payslips, with roles the database enforces, so a Saturday assistant can book a repair in without seeing what the parts cost.

Sound familiar

Where rotas, hours and access go wrong

Usually not through malice. Through everyone having one login because splitting it was too much trouble.

Everyone signs in as the owner, so the audit trail says the owner did everything.

A technician can see the cost price of every part on the shelf.

Anyone can void an invoice, and nobody can say who did.

Hours are on a paper rota and re-typed into a spreadsheet at month end.

A pay rate changed mid-month and the whole month got paid at the new one.

Who is actually busy is a question you answer by walking to the bench.

The workflow

From the weekly rota to a payslip

The same record carries the person, what they may do, what they worked and what that cost.

  1. 01Add the personAn employee record, with their documents kept against it.
  2. 02Give them a roleOne of five, deciding what they can see and do.
  3. 03Set their shiftsWeekly start and finish times, changed from a date, never overwritten.
  4. 04Set the ratePay rates are effective-dated, so a rise starts when it starts.
  5. 05Work the queueJobs are assigned, and load is measured from real assigned work.
  6. 06Record attendanceHours and leave against the employee, with adjustments audited.
  7. 07Run payrollAttendance is priced at the rate in force on each day.
  8. 08PayslipA document produced from the run, and a cost the reports can see.

Because the rate is effective-dated, a mid-month rise is applied from the day it took effect rather than being smeared across the whole month.

Product proof

Permissions that are actually enforced

The part most systems get wrong.

The SlickCell workforce screen showing staff, their roles and what each role is allowed to do.
Five roles

Owner, manager, technician, sales, accountant

Each role gets its own view of each area (none, read, or full) and on top of that, whole groups of fields can be hidden. That is how a technician works a ticket without ever seeing what the part cost. The rules live in the database, so they hold whether the request comes from the app or not.

Permissions are enforced by database policy, not by hiding a button.

The SlickCell workforce screen listing staff with their role, hours and current load.
Real workload

Who is busy, measured from actual jobs

Technician load comes from the minutes of work actually assigned and still open, against the capacity of a day. It is a figure derived from the queue, so it moves when the queue moves.

Load is computed from assigned work, not entered by hand.

What it changes

Staff scheduling and payroll inputs in one system

The audit trail names a person
Because everyone signs in as themselves, 'who did this' has an answer.
Costs stay behind a role
Field-level visibility keeps cost and margin away from the roles that do not need them.
Hours become a payroll input
Attendance is priced against the rate that applied on the day, not the rate today.
Workload is visible
Who is loaded and who is free comes off the job queue rather than off a guess.

Every SlickCell feature is included on every plan: plans differ by team size, locations, discounts and support.

Edge cases

The ones that decide whether staff access works

A technician needs to order a part but not see its cost
Role permissions are per-area, and field groups are separate again, so the action and the figure are two different decisions.
Someone's pay rate changes mid-month
Rates are effective-dated. The days before the change are priced at the old rate and the days after at the new one.
A leave balance was wrong and needs correcting
The correction is an adjustment with a record behind it, not an edit to a number that leaves no trace.
The accountant needs the figures but should not issue refunds
That is exactly what the accountant role is: financial reporting without the operational actions.
Someone leaves
Their access is removed while their history stays intact: the work they did does not detach from the record.
A manager covers a shift at another branch
Membership is per-shop, so access follows where they actually work.
In the module

What workforce carries

Employee records

The person, their details and their documents in one place.

Five roles, server-enforced

Owner, manager, technician, sales and accountant: enforced by database policy.

Attendance and leave

Hours and absence against the employee, with corrections recorded as adjustments.

Effective-dated pay rates

A rise applies from the day it takes effect, not across the whole month.

Payroll runs and payslips

Attendance priced into a run, producing a payslip and a cost the reports can see.

Output and load

What each technician completed, and how loaded they are right now.

Objections

Staff scheduling and payroll: what owners ask

Yes. Every employee has a profile with shifts, attendance and leave, including staff who never sign in. Hours are priced at the pay rate in effect on the day and produce a payslip, which you hand to your payroll provider or accountant for tax and filing. Roles decide what each person can see and do.

Set each employee's weekly shifts with start and finish times, and staff clock in against them. SlickCell records attendance, lateness, absence and leave for every employee, including people who never sign in, and the hours feed the payroll run and the labour cost in your reports.

Real. The rules are mirrored into database policy, so a role that cannot do something cannot do it regardless of how the request arrives. Hiding the button is the presentation of the rule, not the rule.

Yes. Beyond area-level permissions there is field-group visibility, and cost and margin are one of those groups. A technician can consume a part on a job without the cost being on their screen.

Four people is exactly where it starts to matter, because it is the size where everyone shares one login and the audit trail becomes useless. The value is not restriction, it is being able to answer who did something.

From the work actually assigned and still open, measured in minutes against a day's capacity. It is derived from the job queue, so it reflects what is really on the bench.

Bring your staff list and how you want it split

We will set up the roles, show you what each person can and cannot reach, and run a month of hours through payroll.