POS operations guide
After-school activity centre package and attendance POS workflow
An after-school activity centre sells supervised time, skills, clubs, workshops, camps, activity kits, pickup promises and parent payment proof before it sells ordinary products. The POS workflow has to keep enrolments, monthly plans, session packages, attendance, make-up sessions, instructor assignment, camps, event fees, materials, refunds and owner reports clear enough for the front desk, instructors and parents.
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, tutoring, dance-school, music-school and campus guide patterns.
Stable release: v1.6.1, source commit 567a176. No complete after-school centre deployment, timetable, attendance app, parent portal, pickup authorization system, recurring mandate, instructor payroll, live student migration, child-data/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
Child, parent and student records exist
Pinned source evidence contains customer identity, address, balance and payment-term fields that can be evaluated for child, parent, guardian or adult-student accounts. It does not prove consent management, pickup authorization, learning notes or attendance history.
Package, camp and payment records exist
Sale records can hold enrolment fees, monthly plans, session packages, trial classes, camp fees, event fees, activity kits, tenders and balances for synthetic tests. They do not prove automatic renewal, timetable management or payment settlement.
Material and kit stock evidence exists
Item and stock-history paths can be inspected for art kits, robotics kits, books, uniforms, snacks, craft materials and learning supplies. Attendance, pickup, make-up credits and child-safety checks still need their own accepted process.
Supervision and pickup remain operational controls
Instructor availability, batch capacity, guardian pickup rules, emergency contacts, incident notes, reminders and local privacy requirements must be accepted against the exact after-school centre workflow before automation is trusted.
After-school centre POS controls before rollout
After-school centres often mix parent payments, weekday batches, weekend workshops, camps, instructors, pickup notes, materials and make-up promises at one desk. Keep each control separate so money, attendance, supervision and owed sessions stay explainable.
| Area | Record to keep | Why it matters | Acceptance check |
|---|---|---|---|
| Child or student profile | Child, parent or guardian, age group, activity, batch, instructor, permitted follow-up, pickup note, duplicate check and balance. | Front desk needs the right child without putting private guardian or learning notes on receipts. | A child can be found and billed without exposing sensitive details. |
| Activity setup | Activity name, level, age range, weekday or weekend rule, instructor, room and pricing boundary. | Activity centres need more structure than one generic tuition item. | Sales can be grouped by activity without free-text item names. |
| Enrolment fee | Registration item, start date, activity, batch, instructor, amount, payment state and staff owner. | Joining money should not be hidden inside the first monthly fee. | Enrolment is searchable separately from recurring or package fees. |
| Monthly activity plan | Plan, month, validity dates, included sessions, activity, batch rule, payment state and due date. | Parents ask whether a child is active, expired, partial, paused or unpaid. | Front desk can answer current plan status quickly. |
| Session package | Package size, sale date, expiry, eligible activity, used sessions, remaining sessions and transfer rule. | A package is owed value until sessions are consumed or expire by rule. | Each attendance redemption links to the original package sale. |
| Attendance | Session date, activity, batch, instructor, room, attended/no-show state and package deduction. | Attendance is not the same as payment proof. | A session reduces only the accepted package or plan balance. |
| Make-up session | Missed session reason, allowed or denied state, expiry, eligible activity, instructor, room and approver. | Make-up promises leak value when they live only in messages. | Every make-up has a remaining value and expiry trail. |
| Instructor assignment | Instructor, activity, trial, package, workshop, camp, delivered state and substitute rule. | Instructor responsibility should not require editing payment records. | Owner can review delivered work by instructor. |
| Pickup or guardian note | Authorized pickup names, timing note, exception, emergency contact boundary and privacy owner. | Child handoff information is sensitive and should not become ordinary receipt text. | Receipts and exports do not expose private pickup notes. |
| Workshop camp or event | Camp date, capacity, deposit, balance, cancellation rule, material rule and attendance. | Short programmes fail when deposits and capacity are handled outside the billing trail. | Booked, attended, cancelled, refunded and no-show states reconcile. |
| Trial class | Trial date, activity, batch, instructor, free or paid state and conversion follow-up. | Trials are a sales funnel and capacity risk. | Trial children do not become paid students without payment proof. |
| Materials and kits | SKU, item type, quantity, price, tax group, stock movement and exchange rule. | Art kits, robotics kits, uniforms, books and craft material are inventory, not activity revenue. | Stock changes separately from service income. |
| Optional fees | Transport, snack, extended care, holiday class, printing or extra session fee with approval boundary. | Optional charges create parent disputes when hidden inside monthly fees. | Each optional fee is searchable and reversible by rule. |
| Payment proof | Cash, card, wallet, bank transfer, manual proof, failed attempt, refund and balance due. | Attendance permission or pickup state is not collected money. | Tender totals and unpaid balances reconcile before close. |
| Owner review | New students, renewals, dues, package balances, missed sessions, make-ups, instructor activity, camp balances, refunds and stock exceptions. | Small centres leak revenue when review depends on notebooks and messages. | Owner sees money, attendance, supervision, stock and remaining value together. |
Practical workflow
Attendance is not payment proof
A child may attend after a paid plan, a package, a trial, a make-up session, a manual parent payment proof or an approved exception. Keep attendance state and payment proof visible but separate.
Pickup and guardian notes need privacy boundaries
After-school centres often keep emergency contacts, pickup names and exception notes. Those details should be controlled records, not receipt text, public exports or broad staff notes.
Camps and workshops create short-term promises
Holiday camps, weekend workshops and event days combine capacity, deposits, attendance, materials, cancellation rules and refunds. Treat each promise as a record instead of hiding it inside one generic activity item.
Activity kits belong in stock
Art materials, robotics kits, uniforms, books, snacks and craft packs should not be buried inside service revenue. SKU, issue state, exchange rule and stock movement need their own trail.
After-school activity package and parent-payment flow
Run the same short path for enrolments, monthly plans, session packages, trials, make-ups, camps, material kits and optional fees before connecting attendance apps, parent portals or reminder systems.
Create student
Capture only the details needed for billing, parent or guardian contact, duplicate prevention, activity, age group, batch, instructor, pickup boundary and approved follow-up.
Sell plan or package
Choose enrolment, monthly plan, session package, trial class, camp, workshop, material kit, snack, transport or optional service as a distinct sale line.
Record attendance
Assign activity, batch, room, instructor, 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, absent children, make-up promises, instructor activity, pickup exceptions, camp balances, refunds and material-stock exceptions.
Hardware, data and payment setup
Hardware
- POS computer, laptop or tablet at reception.
- Receipt printer for enrolments, monthly plans, packages, trial classes, camps, kits, optional fees and refunds.
- Barcode scanner only if kits, books, uniforms, snacks or labelled materials are sold.
- Cash drawer or counted cash box where cash is accepted.
- Optional instructor tablet, QR attendance or parent pickup device after attendance, pickup and make-up rules are accepted.
- Off-device backup location for student, parent, payment, package, attendance, pickup, camp and stock records.
Software and data
- Student profiles with parent or guardian contact, activity, batch, instructor, age group, package, balance and permitted follow-up fields.
- Enrolment, monthly plan, session package, trial class, make-up session, camp, workshop, material kit, optional fee and refund setup.
- Attendance, no-show, cancellation, make-up, pause, extension, instructor change, batch change, pickup exception and package-redemption controls.
- Payment modes and failed-payment follow-up without storing card data in POS.
- Reports for dues, package balances, missed sessions, make-ups, instructor activity, pickup exceptions, camp balances, refunds and material stock.
- Export and restore workflow before importing real student or parent lists.
Setup sequence
- Write centre rules before entering prices: fee cycle, included sessions, package expiry, make-up allowance, age group, pickup boundary, instructor change rule, batch capacity, camp fee rule, material issue rule, refund rule and renewal method.
- Create synthetic students first and test enrolment, monthly plan, package sale, attendance, trial class, no-show, make-up, camp fee, kit sale, manual proof, failed payment and refund.
- Separate enrolment fees, monthly plans, packages, trials, make-up credits, camp fees, kits, optional fees and private pickup notes as different records or accepted boundaries.
- Record one failed payment and one manual payment proof case so staff know the difference between attendance allowed, payment pending and payment verified.
- Run a week-start review for dues, expired packages, unused sessions, absent children, make-up promises, camp balances and instructor conflicts.
- Test kit and material stock by selling, exchanging and returning one item while keeping activity income and package balances unchanged.
- If an attendance app, parent portal or reminder tool is used, test duplicate attendance, over-capacity, instructor change, late cancellation, pickup exception, 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, instructors, pickup notes, camps, payments, stock and reports survive.
- Approve a pilot only after owner, front desk, instructor, parent/privacy, payment and support responsibilities are written down.
What each person sees
Parent
Receives clear proof of what was paid, what remains, attendance or camp status, refund state and material purchase without private pickup or child notes on the receipt.
Front desk
Can answer active, expired, unpaid, trial, package balance, make-up, instructor, pickup and camp-balance questions without searching messages.
Instructor
Sees assigned sessions, attendance, make-up or camp responsibility without changing billing or refund records.
Owner
Reviews dues, renewals, package liability, make-ups, missed sessions, pickup exceptions, camp balances, refunds, instructor activity and material stock.
Product evidence to inspect
Mistakes to avoid
Avoid these during rollout
- Treating attendance as proof that a parent payment was collected.
- Selling packages without expiry, make-up and remaining-session rules.
- Changing instructors, batches or pickup notes without a date, approval and review trail.
- Letting camp deposits, kit fees, pickup exceptions and make-up promises live only in chat or staff memory.
- Mixing enrolment fees, monthly plans, event fees, optional fees and material stock into one generic item.
- Putting private child-data, guardian, pickup, health or payment notes on receipts, exported billing files or broad owner reports.
- Importing real student and parent lists before a disposable restore and export test passes.
- Buying attendance, parent-portal or reminder tools before the front-desk workflow is accepted.
Use the blank after-school activity centre POS acceptance record
The CSV keeps 24 controls blank until the exact centre workflow is tested. It covers activity packages, attendance, make-up sessions, instructor assignment, parent payments, pickup notes, camps, material stock, 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 guardian accounts.
Pinned sale model
Sale fields relevant to activity packages, camps, materials, payments and balance testing.
Pinned item model
Item, SKU, barcode, quantity, price, tax and stock fields relevant to kits, books, snacks, uniforms 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 after-school activity centre POS the same as school management software?
No. Activity centres may need attendance apps, parent portals, pickup authorization and learning notes, but this guide focuses on front-desk POS controls: fees, packages, attendance state, payment proof, materials, refunds and owner reports.
Should attendance automatically mark fees as paid?
No. Attendance, package redemption, instructor work, pickup state and payment proof should stay separate until the exact workflow is accepted. A child may attend after a paid plan, a trial, a make-up session, a manual payment proof or an approved exception.
How should pickup and guardian notes be handled?
Keep pickup names, emergency contacts and exceptions inside controlled records with local privacy review. They should not print on ordinary receipts or broad billing exports.
How should make-up sessions be handled?
Record the missed session reason, allowed or denied state, expiry, eligible activity, instructor, room and approver. A make-up session is owed value until it is used, expires or is cancelled by rule.
What should the owner review every week?
New students, overdue fees, expiring packages, unused sessions, missed sessions, make-up credits, pickup exceptions, instructor activity, camp 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 attendance automation, parent portals, pickup authorization, instructor payroll, recurring payments or a live after-school centre rollout.
Where Posnic fits
Posnic Community Edition can be evaluated for front-desk billing, student or parent records, payment labels, activity kits, material stock and owner reports. Keep attendance apps, parent portals, pickup authorization, automatic renewals, reminder campaigns, instructor payroll, child-data/privacy review and full after-school 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.