Point of sale for every kind of institution.
A school canteen, a factory cafeteria and a sports club kiosk all repeat the same cycle: scan an item, deduct from stock, collect payment or draw down a balance. The only thing that changes is what to call the person at the counter — Student, Staff, Member. Tenderely BPM gives every institution a point of sale that plugs into its own records, tracks stock from movements and handles prepaid balances and credit without a separate system.
What does a canteen or kiosk repeat every day?
01
Recording a sale
Each transaction needs to capture what was sold, how many, at what price and to whom. When this happens on a slip of paper, the day's picture is gone by closing time.
02
Tracking stock
Items leave the shelf with every sale and arrive with every delivery. When those two movements are not counted together, a stock figure on a shelf label is already wrong.
03
Managing prepaid balances
A parent loads credit for a student, an employer loads an allowance for staff. Each sale draws from that balance, and both sides need to see what remains.
04
Running a credit account
Some institutions allow purchases to be settled later. The running total has to be visible in real time, not reconstructed at month-end from a handwritten ledger.
05
Identifying who is buying
The person at the counter is already in the institution's own records — a student number, a staff card, a membership ID. The sale should attach to that record, not duplicate it.
06
Closing and reconciling
At the end of a shift or day, cash collected, balances drawn and credit extended need to add up. When they do not, finding the gap takes longer than the day's trading did.
Where does this break down today?
Stock only gets counted at stocktake
Because sales are written on paper or entered into a separate spreadsheet after the fact, nobody knows what is actually on the shelf until someone physically counts it. By then something has already run out.
Balances live in a notebook
A parent asks how much credit is left and the answer involves finding a page in a register and adding up a column. When the register is with someone else, the answer is simply not available.
The buyer is recorded twice
The institution already holds student, staff or member data. The canteen keeps its own list. Names drift apart, old entries accumulate and reconciling a dispute means checking two separate sources.
The day's trading is a guess
Cash in the till, credit extended and balance draws are three separate numbers that only meet when someone sits down with a calculator. That calculation is itself a task that gets skipped on busy days.
What changes with Tenderely BPM
01
Stock follows every movement
Each sale reduces the count; each delivery increases it. The current stock figure is computed from those movements, not from a periodic count, so it is always up to date.
02
Balances update at the moment of sale
A prepaid balance is drawn the instant a transaction is recorded. The remaining amount is visible to staff and, if you choose, to the balance holder themselves through a linked record.
03
The buyer comes from your own records
Whether your institution calls them Student, Staff or Member, the person is already in Tenderely. The sale attaches to that existing record rather than creating a parallel list.
04
Credit accounts are always current
Every purchase on account adds to the running total in real time. There is no month-end reconstruction from handwritten entries — the figure is simply there whenever it is needed.
05
Approve on a phone, serve at a counter
The same flow runs on web and in the iOS and Android apps, so a manager can review a balance top-up or approve a credit limit from wherever they are, while sales continue at the counter.
06
The day reconciles itself
Sales, balance movements and credit entries are all structured records. The day's totals sit on a dashboard rather than emerging from a manual calculation at closing time.
FAQ
Can we use it in more than one kind of institution at the same time?
+
Yes. The point-of-sale setup is installed per workspace, and each workspace can define its own buyer type — Student, Staff, Member or anything else. A school and a factory site run independently, each attached to their own records, with no crossover.
How does the prepaid balance top-up work?
+
A top-up is a structured record that increases the balance on a buyer's account. Who can submit one, who must approve it and how the buyer or a parent is notified are all configured as steps in the flow, without code.
Can buyers or parents see their own balance and transaction history?
+
If you choose to allow it. A linked external user sees only their own record — balance, transaction history and any step awaiting their action — and nothing else in your system. You can also share a public form for top-up requests that does not require an account.
What happens when a product runs out?
+
Because stock is computed from movements, a low or zero stock level appears on the dashboard as soon as it happens. You can also set an SLA or threshold notification on the stock record so the responsible person is alerted before it becomes a problem at the counter.
Can we report on sales by product, buyer group or period?
+
Yes. Because every transaction is a structured record with a buyer, a product, an amount and a timestamp, the built-in reports and dashboards can slice that data by any of those dimensions. No manual aggregation is needed.