Parent portal Role 1
Register against a school, add each child with their enrollment ID, see the approved syllabus set, order the full set in one click, pay online and follow the courier timeline.
Preview the parent viewSchool book supply, end to end
One website where schools publish their syllabus book lists, retail branches approve and price them, and parents order the exact set their child needs — with stock, payment and delivery tracked in one place.
Start where a parent starts
A parent never browses a generic bookstore. They pick their school first, and only the syllabus list approved for that school and class appears. Try the picker below — it uses sample schools, not real client data.
No sample school matches that search. Clear the search or choose another board.
Selected school None yet — choose one above
Open the parent demoThree portals, one workflow
The system is not one admin screen with different labels. Each portal has its own scope, its own actions, and data separation enforced on the server — not hidden in the interface.
Register against a school, add each child with their enrollment ID, see the approved syllabus set, order the full set in one click, pay online and follow the courier timeline.
Preview the parent viewImport the book list from Excel or enter it manually, fix row-level errors, submit a version for approval, and track exactly what was approved, rejected or sent back for changes.
Preview the school viewOwn schools, staff, catalogue, prices and stock. Review submissions with a before/after diff, approve them, publish to parents, then pack, dispatch and reconcile orders and refunds.
Preview the branch viewThe part that is not an online shop
The approval gate is built into the data model. A school cannot publish to parents directly, and a branch cannot skip pricing or stock confirmation.
Excel template with class, subject, title, edition, publisher and quantity. Row errors are shown before anything is submitted.
Draft versionA before/after diff, comments, approve, reject or request changes. Prices and stock are confirmed at this step, not by the school.
Approval gateThe approved list appears only for that school and class. Parents add the full set or single books, pay online, and get a receipt.
Paid only on server confirmationStock is reserved at payment, then packed and dispatched with courier and AWB. Parent and school both see the tracking timeline.
Tracked deliveryBuilt for the failure cases
Most of the engineering is not the storefront. It is what happens when a payment webhook repeats, stock runs out, or the wrong branch tries to open another school's order.
Versioned lists, before/after diff, comments, and atomic publish. Unapproved or withdrawn books cannot be ordered, whatever the URL says.
Template download, validation preview, row and column errors, duplicate detection and batch history — tested at 500 and 5,000 rows.
Reserved at payment, released on failure or timeout, with low-stock flags. Concurrency is tested so two parents cannot buy the last copy.
Hosted checkout, signed webhook verification, idempotent handling and receipts. Card data never touches the application server.
Super admin, branch admin, school admin and parent. Every privileged action — approval, price, stock, refund — is written to an audit log.
Pack, dispatch, AWB and delivery status in one timeline. The school sees its students' delivery progress — not what parents spent.
Planning pack · Option B
The plan proves the school → branch → parent approval chain before payment and courier work starts. Scope is a 98-item acceptance checklist, so "done" is measurable rather than a matter of opinion.
Read the plan and TRP