Inventory, procurement, library, labs, and files
Vendor master, purchase orders with goods receipt, inventory movements, library circulation, laboratory equipment, and a school file drive: the back office layer storekeepers, librarians, and admin teams need. Behind every classroom is a chain of supplies, books, equipment, and documents. Schoolyi tracks vendors and purchase orders through goods receipt, manages stock movements, runs library lending with fines and reservations, and gives teams a shared file drive with controlled sharing - so operational assets stay accountable.
Outcomes
Practical results schools report after rolling out this area on the shared calendar and roster.
Purchase and inventory records tie back to vendors and approvals
Librarians run circulation without a separate siloed system
Lab and classroom assets stay registered and findable
Shared files reduce email attachments and lost documents
Product truth
Good school software copy should answer who owns the work, what the handoff produces, and which parts still depend on deployment decisions.
This page describes the supported workflow boundary. Confirm configuration, integrations, data, and policy requirements in a representative pilot before committing to production.
Deep dive
Use these details to turn a product page into an implementation conversation.
Behind every classroom is a chain of supplies, books, equipment, and documents. Schoolyi tracks vendors and purchase orders through goods receipt, manages stock movements, runs library lending with fines and reservations, and gives teams a shared file drive with controlled sharing - so operational assets stay accountable.
Vendor master, purchase orders with goods receipt, inventory movements, library circulation, laboratory equipment, and a school file drive: the back office layer storekeepers, librarians, and admin teams need. Because Library & back office shares roster and calendar data, teams stop reconciling exports between spreadsheets and the parent portal.
Evidence layer
Read the supporting product and implementation material before making a capability claim.
Everything included in this module, from daily workflows to exports your team relies on.
Role-scoped workspaces so each team sees only the tasks they own.
Focused pages for evaluators comparing specific library & back office workflows during an SMS rollout.
Workflow
A typical path from setup through daily use on Schoolyi.
Part of the Library & back office workflow on Schoolyi, connected to roster, calendar, and role permissions.
PO lifecycle, GRN, cancel reversals
Part of the Library & back office workflow on Schoolyi, connected to roster, calendar, and role permissions.
Part of the Library & back office workflow on Schoolyi, connected to roster, calendar, and role permissions.
Deep dive
Long-form context for evaluators comparing modules during an SMS rollout.
Behind every classroom is a chain of supplies, books, equipment, and documents. Schoolyi tracks vendors and purchase orders through goods receipt, manages stock movements, runs library lending with fines and reservations, and gives teams a shared file drive with controlled sharing - so operational assets stay accountable.
Vendor master, purchase orders with goods receipt, inventory movements, library circulation, laboratory equipment, and a school file drive: the back office layer storekeepers, librarians, and admin teams need. Because Library & back office shares roster and calendar data, teams stop reconciling exports between spreadsheets and the parent portal.
These areas work closely with library & back office and share the same calendar, roster, and role model.
Straightforward answers for visitors evaluating the product.
Storekeepers, Librarians, Admin office run daily workflows in this module while leadership reviews dashboards and exports when needed.
Assign a workflow owner and test it with a representative staff account before the busy part of the term. Verify that approvals, coverage details, and sensitive fields remain within the intended role.
Dates, working days, and class structure flow from the shared calendar so downstream modules do not maintain parallel date lists.
Set the academic calendar before enabling dependent workflows, then test one holiday and one working-day exception against the resulting attendance or exam view. Keep the school’s local policy as the authority for edge cases.
Schools often launch admissions, roster, and fees first, then add this module when the foundation data is stable.
Choose the next phase only after the team has reconciled one complete operating cycle. Record the data, role, calendar, and support dependencies before widening access.
Role-scoped workspaces show only the tasks each team needs. Most schools run a short coordinator session plus self-serve docs.
Assign a workflow owner and test it with a representative staff account before the busy part of the term. Verify that approvals, coverage details, and sensitive fields remain within the intended role.
We'll show how this module fits your school's workflows and which teams benefit first.
Already using Schoolyi? Sign in
