POS operations guide
Tutoring centre lesson package and parent-payment POS workflow
A tutoring centre sells learning time, batch seats, parent payment promises, make-up lessons, tests, books and study materials before it sells ordinary products. The POS workflow has to keep enrolments, monthly tuition, lesson packages, attendance, missed lessons, tutor assignment, exam or test fees, material stock, payment proof, refunds and owner reports clear enough for the front desk, tutors, parents and adult students.
Evidence and review scope
Evidence reviewed 2026-09-02. Reviewed current Posnic stable release boundary, archived customer, sale and item data models, and adjacent academy, dance-school, martial-arts and music-school guide patterns.
Stable release: v1.6.1, source commit 567a176. No complete tutoring centre deployment, lesson timetable, attendance app, learning-management workflow, parent portal, recurring mandate, tutor payroll, live student migration, education-record/privacy review or accepted pilot week is established by this page. Reproduced evidence remains pinned to an archived source snapshot.
What the current evidence establishes
Student and parent records exist
Pinned source evidence contains customer identity, address, balance and payment-term fields that can be evaluated for student, parent or adult-student accounts. It does not prove consent management, education-record handling, progress notes or attendance history.
Tuition, package and payment records exist
Sale records can hold enrolment fees, monthly tuition, lesson packages, trial lessons, exam fees, books, worksheet packs, tenders and balances for synthetic tests. They do not prove automatic renewal, timetable management or payment settlement.
Book and material stock evidence exists
Item and stock-history paths can be inspected for textbooks, workbooks, guides, worksheet packs, stationery and learning materials. Lesson access, make-up credits and exam eligibility still need their own accepted process.
Scheduling and learning progress remain operational controls
Tutor availability, batch capacity, room allocation, make-up rules, exam preparation, reminders and local privacy requirements must be accepted against the exact tutoring centre workflow before automation is trusted.
Tutoring centre POS controls before rollout
Tutoring centres often mix parent payments, adult learners, batches, tutor schedules, lesson packages, missed classes, test promises and book sales at one desk. Keep each control separate so money, attendance, tutor work and owed lessons stay explainable.
| Area | Record to keep | Why it matters | Acceptance check |
|---|---|---|---|
| Student profile | Student, parent or adult learner, subject, level, batch, tutor, permitted follow-up, duplicate check and balance. | Front desk needs the right student without putting private learning or payment notes on receipts. | A student can be found and billed without exposing sensitive details. |
| Subject or course | Subject, course, exam track, level, batch or one-to-one rule, tutor and pricing boundary. | Tutoring centres need more structure than a generic tuition item. | Lesson sales can be grouped without free-text item names. |
| Enrolment fee | Registration item, start date, subject, batch, tutor, amount, payment state and staff owner. | Joining money should not be hidden inside the first tuition bill. | Enrolment is searchable separately from tuition. |
| Monthly tuition | Plan, month, validity dates, included lessons, tutor or batch rule, payment state and due date. | Parents and adult students ask whether lessons are active, expired, partial or unpaid. | Front desk can answer current tuition status quickly. |
| Lesson package | Package size, sale date, expiry, eligible subject, used lessons, remaining lessons and transfer rule. | A lesson package is owed value until lessons are consumed or expire by rule. | Each attendance redemption links to the original package sale. |
| Attendance | Lesson date, subject, batch, tutor, room, attended/no-show state and package deduction. | Attendance is not the same as payment proof. | A lesson reduces only the accepted package. |
| Make-up lesson | Missed lesson reason, allowed/denied state, expiry, eligible batch, tutor, room and approver. | Make-up promises leak value when they live only in messages. | Every make-up has a remaining value and expiry trail. |
| Tutor assignment | Tutor, subject, trial, package, exam preparation, revision class and delivered state. | Tutor responsibility should not require editing payment records. | Owner can review delivered work by tutor. |
| Batch or room capacity | Batch, room, tutor slot, student count and over-capacity rule. | A paid lesson creates a schedule promise. | Over-capacity cases are flagged before another promise is made. |
| Trial lesson | Trial date, subject, batch, tutor, free or paid state and conversion follow-up. | Trials are a sales funnel and capacity risk. | Trial students do not become paid students without payment proof. |
| Exam or assessment | Mock test, entrance exam, board fee, certificate, due date, approval and payment state. | Assessment money should not disappear inside monthly tuition. | Eligible, paid, partial and refunded states reconcile. |
| Books and materials | SKU, item type, quantity, price, tax group, stock movement and exchange rule. | Books, workbooks and worksheet packs are inventory, not tuition revenue. | Stock changes separately from service income. |
| Optional fees | Transport, meal, study room, lab, camp, holiday class or extra session fee with approval boundary. | Optional charges create arguments when hidden inside tuition. | Each optional fee is searchable and reversible by rule. |
| Payment proof | Cash, card, wallet, bank transfer, manual proof, failed attempt, refund and balance due. | Lesson permission or exam eligibility is not collected money. | Tender totals and unpaid balances reconcile before close. |
| Owner review | New students, renewals, dues, package balances, missed lessons, make-ups, tutor activity, test fees, refunds and stock exceptions. | Small centres leak revenue when review depends on notebooks and messages. | Owner sees money, attendance, tutor work and remaining value together. |
Practical workflow
Lesson attendance is not payment proof
A student may attend after paying online, paying at the desk, using a package, taking a trial, receiving a make-up lesson or owing a balance. Keep attendance state and payment proof visible but separate.
Tutor time needs its own trail
Tutor assignment affects lesson delivery, make-ups, exam preparation, revision classes and payroll review. Record the tutor and delivered state without rewriting the original payment.
Exam and assessment fees are promises
When a centre accepts a mock test, entrance exam, board fee or certificate fee, it creates a promise around capacity, date, tutor approval, materials and refund rules. The fee should not disappear inside a generic monthly tuition item.
Books and worksheet packs belong in stock
Textbooks, workbooks, guide books, worksheet packs, stationery and learning materials should not be buried inside lesson revenue. SKU, issue state, exchange rule and stock movement need their own trail.
Tutoring centre lesson package and parent-payment flow
Run the same short path for enrolments, tuition, lesson packages, trials, make-ups, assessments, worksheet packs and book sales before connecting booking apps, learning tools or reminder systems.
Create student
Capture only the details needed for billing, parent or adult-student contact, duplicate prevention, subject, level, batch, tutor and approved follow-up.
Sell tuition or package
Choose enrolment, monthly tuition, lesson package, trial lesson, test fee, certificate fee, worksheet pack, book or optional service as a distinct sale line.
Record attendance and tutor
Assign tutor, batch, room, subject, attended/no-show state and make-up eligibility only after the payment or package state is visible.
Record payment state
Mark cash, card, wallet, bank transfer, manual proof, balance due, failed payment or refund without storing card data in POS.
Review before next week
Owner checks dues, active packages, missed lessons, make-up promises, tutor activity, test balances, refunds and material-stock exceptions.
Hardware, data and payment setup
Hardware
- POS computer, laptop or tablet at reception.
- Receipt printer for tuition, packages, trial lessons, test fees, books, materials, optional fees and refunds.
- Barcode scanner only if books, stationery, worksheet packs or labelled learning materials are sold.
- Cash drawer or counted cash box where cash is accepted.
- Optional tutor tablet, QR attendance or lesson-booking device after attendance and make-up rules are accepted.
- Off-device backup location for student, payment, package, attendance, tutor, assessment and stock records.
Software and data
- Student profiles with parent or adult-student contact, subject, batch, tutor, level, package, balance and permitted follow-up fields.
- Enrolment, monthly tuition, lesson package, trial lesson, make-up lesson, exam fee, assessment fee, worksheet pack, book, optional fee and refund setup.
- Attendance, no-show, cancellation, make-up, pause, extension, tutor change, batch change and package-redemption controls.
- Payment modes and failed-payment follow-up without storing card data in POS.
- Reports for dues, package balances, missed lessons, make-ups, tutor activity, test balances, refunds and material stock.
- Export and restore workflow before importing real student lists.
Setup sequence
- Write centre rules before entering prices: fee cycle, included lessons, package expiry, make-up allowance, tutor change rule, batch capacity, exam fee rule, material issue rule, refund rule and renewal method.
- Create synthetic students first and test enrolment, tuition fee, package sale, lesson attendance, trial lesson, no-show, make-up, test fee, book sale, manual proof, failed payment and refund.
- Separate enrolment fees, monthly tuition, lesson packages, trials, make-up credits, test fees, books, worksheet packs, optional fees and private notes as different records or accepted boundaries.
- Record one failed payment and one manual payment proof case so staff know the difference between lesson allowed, payment pending and payment verified.
- Run a week-start review for dues, expired packages, unused lessons, absent students, make-up promises, test balances and tutor conflicts.
- Test book and worksheet stock by selling, exchanging and returning one item while keeping lesson income and package balances unchanged.
- If a booking app, learning tool or reminder tool is used, test duplicate attendance, over-capacity, tutor change, late cancellation, make-up expiry, failed reminder and offline fallback cases.
- Back up the test data, restore it on a clean device, and confirm students, packages, attendance, tutors, tests, payments, stock and reports survive.
- Approve a pilot only after owner, front desk, tutor, parent/privacy, payment and support responsibilities are written down.
What each person sees
Parent or student
Receives clear proof of what was paid, what remains, lesson status, exam or test balance, refund state and material purchase without private notes on the receipt.
Front desk
Can answer active, expired, unpaid, trial, package balance, make-up, tutor, batch and test-balance questions without searching messages.
Tutor
Sees assigned lessons, attendance, make-up or revision responsibility without changing billing or refund records.
Owner
Reviews dues, renewals, package liability, make-ups, missed lessons, test balances, refunds, tutor activity and material stock.
Product evidence to inspect
Mistakes to avoid
Avoid these during rollout
- Treating a lesson attendance mark as proof that payment was collected.
- Selling lesson packages without expiry, make-up and remaining-session rules.
- Changing tutors, batches or rooms without a date, approval and review trail.
- Letting test eligibility, worksheet fees and make-up promises live only in chat or staff memory.
- Mixing enrolment fees, tuition, exam fees, materials, optional fees and book stock into one generic item.
- Putting private child-data, learning, guardian or payment notes on receipts, exported billing files or broad owner reports.
- Importing real student lists before a disposable restore and export test passes.
- Buying booking, learning-management or reminder tools before the front-desk workflow is accepted.
Use the blank tutoring centre POS acceptance record
The CSV keeps 24 controls blank until the exact centre workflow is tested. It covers lesson packages, attendance, make-up lessons, tutor assignment, parent payments, exam fees, books, worksheet packs, failed payments, refund, backup and owner approval.
Primary sources used
Current Posnic stable release
Stable package boundary used for product review and download references.
Pinned Posnic source tree
Exact archived source commit used so product-boundary statements do not drift with later work.
Pinned customer model
Customer identity, address, balance and payment-term fields relevant to student, parent and adult-student accounts.
Pinned sale model
Sale fields relevant to tuition, lesson packages, exam fees, materials, payments and balance testing.
Pinned item model
Item, SKU, barcode, quantity, price, tax and stock fields relevant to books, worksheet packs and learning materials.
PCI SSC merchant process
Official merchant guidance for payment responsibilities. It is used as a payment-scope reference, not a Posnic certification.
Related Posnic pages
Questions
Is tutoring centre POS the same as school management software?
No. Tutoring centres may need learning records, timetables and parent portals, but this guide focuses on front-desk POS controls: fees, packages, attendance, payment state, materials, refunds and owner reports.
Should lesson attendance automatically mark fees as paid?
No. Attendance, package redemption, tutor work and payment proof should stay separate until the exact workflow is accepted. A student may attend after a paid package, a trial, a make-up lesson, a manual payment proof or an approved exception.
How should make-up lessons be handled?
Record the missed lesson reason, allowed or denied state, expiry, eligible batch, tutor, room and approver. A make-up lesson is owed value until it is used, expires or is cancelled by rule.
How should exam fees and worksheet packs be handled?
Record test date, eligibility or tutor approval, capacity, fee state, materials, certificate rule and refund boundary. Treat books and worksheet packs as material stock where possible.
What should the owner review every week?
New students, overdue fees, expiring packages, unused lessons, missed lessons, make-up credits, tutor activity, test balances, refunds, failed payments and material-stock exceptions.
Where does Posnic fit in this workflow?
Archived Posnic evidence can be evaluated for customer records, sale lines, payment labels, stock history and reports. It does not prove complete lesson scheduling, learning-management automation, parent portals, tutor payroll, recurring payments or a live tutoring-centre rollout.
Where Posnic fits
Posnic Community Edition can be evaluated for front-desk billing, student or parent records, payment labels, books, worksheet packs, material stock and owner reports. Keep lesson booking, attendance apps, learning-management automation, parent portals, automatic renewals, reminder campaigns, tutor payroll, child-data/privacy review and full tutoring-centre automation outside the accepted scope until the exact workflow passes the blank record. Posnic Cloud helps only when the centre needs remote dashboard access, managed backup, multi-outlet visibility or scoped custom work.