FAQ
Questions preschool teams ask us
Quick answers about Little's Orbit, onboarding, payments, and the parent app.
Is Little's Orbit built for preschools?
Yes. Little's Orbit is shaped around preschool workflows — daily care, parent communication, classroom updates, and school operations.
How does onboarding work?
We configure your school profile, classes, staff access, and modules first, then help you add children, link parents, and roll out daily workflows in stages.
Can we enable payments later?
Yes. Payment gateway support can be switched on when your school is ready with live gateway details.
Can we start without every module?
Yes. Many schools start with attendance, notices, parent access, and photos, then add daily care, payments, ledgers, and reports when the team is ready.
Can staff have different permissions?
Yes. School admins can control staff access for workflows such as kids, parents, photos, notices, attendance, payments, and messaging.
Can existing student data be imported?
Yes. The school admin flow supports CSV child import along with manual student and parent setup.
Is QR pickup optional?
Yes. QR pickup and attendance workflows can be used based on your school process and staff permissions.
Do parents need the app?
Yes. Parents use the mobile app for daily reports, notices, payments, QR pickup, and communication depending on your setup. Parent access is provided through the school, not direct public signup.
Does this website store child or attendance data?
No. This public website stores demo and contact submissions only. Live child, attendance, daily care, payment, and school operation data stay in the separate product system.
How is pricing calculated?
Pricing depends on your school size, modules, and rollout support. We don’t list public rates — book a demo and we’ll share a quote tailored to you.
Still curious? Get in touch