A catalogue that knows who has the book
Issue and return against the actual student and staff records the rest of the platform uses, under a circulation policy that belongs to the school rather than to whoever happens to be on the counter today.
The issue register and the librarian’s memory
A paper register answers “who has this book” only if you read every page, and it answers “how many books does this child already have out” not at all. The loan period, the fine rate and the borrowing cap tend to exist as a rule one person remembers. Here the register is queryable, the borrower is a student record, and the policy is a document.
A hand-written issue and return register
A date card in the pocket at the back of each book
A loan period and fine rate nobody has written down
A separate accession list kept for stock-taking
Library, screen by screen
Each of these is a screen or a service in the module rather than a heading on a roadmap.
Catalogue with copies and a shelf
Title, author, ISBN, publisher, edition, year, language, category, price, shelf location, and how many copies of the title the library holds.
Issue against a real borrower
The borrower is chosen from the student or teacher record, and the form refuses a loan that would take that borrower past the cap for their type.
Policy in one document per school
Loan days, fine per day, grace days, the cap for students and the cap for staff, and how many times one loan may be renewed — where zero disables renewal outright.
Fines derived, waivable, on record
The fine follows from the due date and the policy, returns zero inside the grace period, and a waiver records both the reason and who granted it. A school that charges nothing never sees a phantom amount.
Overdue is computed, not stored
A stored status stays “issued” until something writes to the document, so overdue is recomputed from the due date every time a loan is read. The dashboard count, the report and the student’s own screen therefore agree.
Renewals, returns, lost copies
A renewal pushes the due date out and is counted against the cap. A return records who took it back and the condition it came back in. A lost copy leaves circulation with the replacement charge taken from the title’s price.
The same row, read from somewhere else
The point of an ERP is not that it has a lot of modules. It is that a fee concession, an attendance shortfall and a report card are all reading one record. These are the places Library touches.
Students
The borrower is the student record, so an outstanding book is attached to a person the fee desk, the class register and the report card already know about.
Fees
“Library” is one of the fee types, so a library charge can be raised as a fee head against the student rather than collected off the books.
Reports
Library inventory is a built-in report definition with its own filters, exportable to Excel or PDF.
What Library does not do
Stated here rather than discovered in week three. If something you need is on this list, ask before you buy — it is a better conversation than the one after.
There is no barcode scanner integration in this build. ISBN and shelf location are fields you type; the counter is keyboard-driven, not scanner-driven.
The catalogue counts copies of a title rather than tracking an accession number per physical copy, so “the third copy is the damaged one” is a remark on the loan rather than a record on the book.
A fine can be collected or waived at the counter and is recorded on the loan. It is not posted into the fee ledger for you — a charge you want on the ledger has to be raised as a fee head.
Set your institution up on Elevate
Start on the free plan for up to 250 students. Paid plans begin at ₹1499 per month, billed to the institution.