Record kits built
Use a negative quantity to correct a mistake or write off damaged kits.
Kit stock
| Kit | Age | Built | Sent out | Returned | Available | Cost | Trade | Retail |
|---|
New order
Kits on this order
| Kit | Sale / loan | Qty | Student (optional) | Unit price | Due back | Line |
|---|
Unit price is worked out by the server from the customer’s type and cannot be typed. An admin can tick override on a line to set it by hand — which is recorded on the order.
| Ref | Date | Customer | Requested by | Sold | Loaned | Due | Payment |
|---|
Deleted orders
Orders an admin has deleted, with who did it, when and why. A deleted order is gone from every other screen and its kits went back into stock; this is the record that it existed, and a full copy of it is kept.
| When | Order | Customer | Total | Deleted by | Why |
|---|
Unpaid orders
| Ref | Date | Customer | Requested by | Amount due |
|---|
By customer
| Customer | Type | Orders | Owed | Lifetime | Open loans |
|---|
Currently out
| Ref | Kit | Qty | Student | Customer | Requested by | Due back |
|---|
Bulk import customers
Only name and type are required. Type must be franchise, centre,
school or individual. Anything already on the list is skipped, so you can
re-upload a corrected file safely. Accepts .xlsx or .csv.
The template is a .csv — open it in Excel, fill it in, and upload it back.
Add one customer
Centres and franchises appear on invoices as Robocode + their name, so enter the place on its own and let the app add the rest. No example is named here on purpose: the one that used to be here was renamed and the sentence went on naming a centre that no longer existed. The address is what prints on the invoice.
Customers
| Name | Type | Contact | Address | Owed | Loans |
|---|
Add student
The class day and time are how a teacher tells two children with the same name apart in the kiosk, so fill them in.
Students
| Name | Customer | Course | Teacher | Class | Parent contact | Kits out |
|---|
Enter requests from teachers
For requests collected away from the kiosk — on paper, in a message, or over the phone. Every row lands exactly as a teacher's own request does: waiting, with no sale-or-loan decision made, so the office still rings the family. Put the date the teacher actually asked in Asked on, or the whole batch looks like it arrived today.
Choose a centre first — the list of children and the file both belong to it.
| Child | Kit or part | Qty | Reason | Needed by | Asked on | Teacher | Status |
|---|
Kit requests
| When | Teacher | Kit | For | Qty | Type | Needed by | In stock | Status |
|---|
Part requests
| When | Teacher | Part | For | Qty | Reason | Status |
|---|
Kit prices
Cost is what a kit costs us to make, and margin is worked out from it. Trade is what a franchise or one of our centres pays. A school pays a set amount over trade, worked out rather than typed, so a price change here carries through on its own. Retail is what a family pays, and a loan is never charged. Licensees buy through the partners portal, not here. Cost and prices save separately, on purpose.
| Kit | Cost | Trade price | School | Retail price | Trade margin |
|---|
Who can sign in
Everyone with a login here, and what they may do. A row can exist before its person has ever been in, so the last column says which. Admin is everything, including cost and prices. Staff is the day-to-day office job with no cost, no prices and no kiosk codes. Franchise sees only their own centre's screen — and only once a centre is linked below, because no centre linked means nothing at all rather than everything.
| Person | Can do | Centres | Last seen |
|---|
Teachers
Teachers sign in at kiosk.html with an 8-digit code — the kiosk has a number keypad, so codes are digits only. They have no account and never see this app, and the code decides which centre's children they can ask for. Codes are issued in the HR app, on the person's own record, under Kiosk access — their manager does it and the code is shown once. It is stored scrambled here, individually, so nobody can look it up afterwards, not even from a database backup. If somebody forgets theirs, their manager issues a new one and the old one stops working straight away. This screen is where you check who has one.
| Name | Centre | Active | Code issued by | When |
|---|
Viewing as: what was done
Every time an admin used View as…, and everything they changed while viewing as somebody. Each line names both: the admin who did it and the person they were viewing as. It lists which screen and which boxes were changed, not what was typed in them.
| When | Admin | Viewing as | Centre | What |
|---|
