POS operations guide
Language school course package and certificate-fee POS workflow
A language school sells learning time, course levels, placement tests, student promises, certificate fees, books and payment proof before it sells ordinary products. The POS workflow has to keep enrolments, monthly or term fees, course packages, attendance, make-up classes, teacher assignment, exam and certificate charges, material stock, refunds and owner reports clear enough for the front desk, teachers, parents and adult learners.
Evidence and review scope
Evidence reviewed 2026-09-03. Reviewed current Posnic stable release boundary, archived customer, sale and item data models, and adjacent tutoring, music-school, sports-academy and after-school centre guide patterns.
Stable release: v1.6.1, source commit 567a176. No complete language school deployment, timetable, attendance app, LMS, student portal, parent portal, recurring mandate, teacher 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, parent and learner records exist
Pinned source evidence contains customer identity, address, balance and payment-term fields that can be evaluated for student, parent, guardian or adult-learner accounts. It does not prove consent management, learning-progress history, assessment records or attendance history.
Course, package and payment records exist
Sale records can hold registration fees, monthly or term fees, course packages, trial classes, placement tests, certificate fees, exam fees, books, materials, 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, flashcards, printed packs, stationery and certificate materials. Course access, make-up credits and certificate eligibility still need their own accepted process.
Teaching and certificate controls remain operational
Teacher availability, level placement, room capacity, exam dates, certificate rules, reminder wording and local privacy requirements must be accepted against the exact language school workflow before automation is trusted.
Language school POS controls before rollout
Language schools often mix parent payments, adult learners, levels, teachers, books, placement tests, certificate fees and make-up promises at one desk. Keep each control separate so money, attendance, teacher work and owed classes stay explainable.
| Area | Record to keep | Why it matters | Acceptance check |
|---|---|---|---|
| Student profile | Student, parent or adult learner, language, level, batch, teacher, permitted follow-up, duplicate check and balance. | Front desk needs the right learner without putting private learning or payment notes on receipts. | A student can be found and billed without exposing sensitive details. |
| Course or level | Language, level, course track, batch rule, teacher, placement boundary and pricing boundary. | Language schools need more structure than one generic tuition item. | Course sales can be grouped by language and level without free-text item names. |
| Placement test | Test date, language, level recommendation, fee state, staff owner and result boundary. | Placement decisions affect the class promise and should not live only in chat. | Paid, free and deferred placement tests are reportable. |
| Enrolment fee | Registration item, start date, language, level, batch, teacher, amount, payment state and staff owner. | Joining money should not be hidden inside the first course bill. | Enrolment is searchable separately from course packages. |
| Monthly or term fee | Plan, validity dates, included classes, teacher or batch rule, payment state and due date. | Parents and adult learners ask whether a course is active, expired, partial or unpaid. | Front desk can answer current course status quickly. |
| Course package | Package size, sale date, expiry, eligible language, used classes, remaining classes and transfer rule. | A package is owed value until classes are consumed or expire by rule. | Each attendance redemption links to the original package sale. |
| Attendance | Class date, language, level, batch, teacher, room, attended or no-show state and package deduction. | Attendance is not the same as payment proof. | A class reduces only the accepted package or course balance. |
| Make-up class | Missed class reason, allowed or denied state, expiry, eligible batch, teacher, room and approver. | Make-up promises leak value when they live only in messages. | Every make-up has a remaining value and expiry trail. |
| Teacher assignment | Teacher, course, trial, package, exam preparation, conversation session and delivered state. | Teacher responsibility should not require editing payment records. | Owner can review delivered work by teacher. |
| Batch or room capacity | Batch, room, teacher slot, student count and over-capacity rule. | A paid course creates a schedule promise. | Over-capacity cases are flagged before another promise is made. |
| Certificate or exam fee | Certificate name, exam, level, due date, eligibility, approval, payment state and refund rule. | Certificate money should not disappear inside monthly tuition. | Eligible, paid, partial, failed and refunded states reconcile. |
| Books and materials | SKU, item type, language, level, quantity, price, tax group, stock movement and exchange rule. | Books and workbooks are inventory, not course revenue. | Stock changes separately from service income. |
| Payment proof | Cash, card, wallet, bank transfer, manual proof, failed attempt, refund and balance due. | Class permission or certificate eligibility is not collected money. | Tender totals and unpaid balances reconcile before close. |
| Privacy boundary | Parent consent, adult learner contact, learning notes, result notes, reminders and export permissions. | Education and child data should not become ordinary receipt text. | Receipts and exports do not expose private learner details. |
| Owner review | New students, renewals, dues, package balances, missed classes, make-ups, teacher activity, certificate balances, refunds and stock exceptions. | Small schools leak revenue when review depends on notebooks and messages. | Owner sees money, attendance, teacher work and remaining value together. |
Practical workflow
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 class or owing a balance. Keep attendance state and payment proof visible but separate.
Certificate fees are separate promises
When a school accepts a certificate, proficiency exam or level-test fee, it creates a promise around eligibility, date, capacity, materials and refund rules. The fee should not disappear inside a generic course item.
Children and adult learners need different boundaries
Parent contact, guardian consent, adult learner contact, learning notes, exam results and payment notes should be controlled records, not ordinary receipt text or broad exports.
Books and learning materials belong in stock
Textbooks, workbooks, flashcards, printed packs and stationery should not be buried inside lesson revenue. SKU, issue state, exchange rule and stock movement need their own trail.
Language school course package and certificate-fee flow
Run the same short path for enrolments, course packages, attendance, placement tests, make-ups, certificate fees, books and material charges before connecting timetable, LMS, reminder or portal tools.
Create student
Capture only the details needed for billing, parent or adult-learner contact, duplicate prevention, language, level, batch, teacher and approved follow-up.
Sell course or fee
Choose enrolment, term fee, course package, trial class, placement test, exam fee, certificate fee, book or material charge as a distinct sale line.
Record attendance and teacher
Assign language, level, batch, room, teacher, attended or 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 classes, make-up promises, teacher activity, placement-test balances, certificate fees, refunds and material-stock exceptions.
Hardware, data and payment setup
Hardware
- POS computer, laptop or tablet at reception.
- Receipt printer for enrolments, course packages, placement tests, certificate fees, books, materials and refunds.
- Barcode scanner only if books, workbooks, flashcards, stationery or labelled learning materials are sold.
- Cash drawer or counted cash box where cash is accepted.
- Optional teacher tablet, QR attendance or lesson-booking device after attendance and make-up rules are accepted.
- Off-device backup location for student, payment, course, attendance, teacher, certificate and stock records.
Software and data
- Student profiles with parent or adult-learner contact, language, level, batch, teacher, package, balance and permitted follow-up fields.
- Enrolment, monthly or term fee, course package, trial class, placement test, make-up class, exam fee, certificate fee, book, material charge and refund setup.
- Attendance, no-show, cancellation, make-up, pause, extension, teacher 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 classes, make-ups, teacher activity, placement tests, certificate balances, refunds and material stock.
- Export and restore workflow before importing real student lists.
Setup sequence
- Write school rules before entering prices: fee cycle, included classes, package expiry, make-up allowance, placement rule, teacher change rule, batch capacity, certificate fee rule, material issue rule, refund rule and renewal method.
- Create synthetic students first and test enrolment, term fee, package sale, attendance, trial class, no-show, make-up, placement test, certificate fee, book sale, manual proof, failed payment and refund.
- Separate enrolment fees, course packages, trials, make-up credits, placement tests, certificate fees, books, printed packs, optional fees and private learning notes as different records or accepted boundaries.
- Record one failed payment and one manual payment proof case so staff know the difference between class allowed, payment pending and payment verified.
- Run a week-start review for dues, expired packages, unused classes, absent students, make-up promises, certificate balances and teacher conflicts.
- Test book and material stock by selling, exchanging and returning one item while keeping course income and package balances unchanged.
- If a timetable, LMS, student portal or reminder tool is used, test duplicate attendance, over-capacity, teacher change, late cancellation, make-up expiry, certificate eligibility, failed reminder and offline fallback cases.
- Back up the test data, restore it on a clean device, and confirm students, packages, attendance, teachers, tests, payments, stock and reports survive.
- Approve a pilot only after owner, front desk, teacher, parent or adult-learner privacy, payment and support responsibilities are written down.
What each person sees
Student or parent
Receives clear proof of what was paid, what remains, course status, certificate-fee state, refund state and material purchase without private learning notes on the receipt.
Front desk
Can answer active, expired, unpaid, trial, package balance, make-up, teacher, level and certificate-balance questions without searching messages.
Teacher
Sees assigned classes, attendance, make-up or exam-preparation responsibility without changing billing or refund records.
Owner
Reviews dues, renewals, package liability, make-ups, missed classes, certificate balances, refunds, teacher activity and material stock.
Product evidence to inspect
Mistakes to avoid
Avoid these during rollout
- Treating class attendance as proof that course fees were collected.
- Selling course packages without expiry, make-up and remaining-class rules.
- Changing teachers, batches, rooms or levels without a date, approval and review trail.
- Letting placement tests, certificate fees and make-up promises live only in chat or staff memory.
- Mixing enrolment fees, course fees, certificate fees, materials, optional fees and book stock into one generic item.
- Putting private child-data, learning, guardian, result 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 timetable, LMS, student-portal or reminder tools before the front-desk workflow is accepted.
Use the blank language school POS acceptance record
The CSV keeps 24 controls blank until the exact school workflow is tested. It covers course packages, attendance, make-up classes, teacher assignment, placement tests, certificate fees, books, materials, 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-learner accounts.
Pinned sale model
Sale fields relevant to course packages, placement tests, certificate fees, materials, payments and balance testing.
Pinned item model
Item, SKU, barcode, quantity, price, tax and stock fields relevant to books, workbooks, flashcards, stationery 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 language school POS the same as school management or LMS software?
No. A language school may need timetable, learning-management, placement, certificate and student portal tools, but this guide focuses on front-desk POS controls: course fees, packages, attendance state, certificate fees, books, refunds and owner reports.
Should class attendance automatically mark course fees as paid?
No. Attendance, package redemption, teacher work, certificate eligibility and payment proof should stay separate until the exact workflow is accepted. A student may attend after a paid course, a trial, a make-up class, a manual payment proof or an approved exception.
How should certificate and exam fees be handled?
Record the exam or certificate name, level, due date, eligibility rule, capacity, approval, payment state and refund rule as its own record. Certificate-fee money should not disappear inside a generic course package.
How should children and adult learners be separated?
Keep parent or guardian contact, consent notes, learning notes and payment notes inside controlled records with local privacy review. Receipts and broad exports should not expose private student details.
What should the owner review every week?
New enrolments, overdue fees, expiring course packages, unused sessions, missed classes, make-up credits, teacher activity, placement-test balances, certificate-fee balances, refunds, failed payments and book or 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 language-school scheduling, LMS automation, parent portals, teacher payroll, recurring payments or a live language-school rollout.
Where Posnic fits
Posnic Community Edition can be evaluated for front-desk billing, student or parent records, payment labels, books, printed packs, material stock and owner reports. Keep timetable apps, LMS automation, parent portals, automatic renewals, reminder campaigns, teacher payroll, education-record/privacy review and full language-school automation outside the accepted scope until the exact workflow passes the blank record. Posnic Cloud helps only when the school needs remote dashboard access, managed backup, multi-outlet visibility or scoped custom work.