What is an ILS (Integrated Library System)?

The definition, unpacked

"Integrated" refers to the fact that everything a library needs to operate lives in one system rather than several disconnected tools. Before ILS software existed, a library might have used a card catalogue to describe its holdings, a manual ledger to track loans, and a separate paper-based process for ordering new items. An ILS merges all of that into a single database, so that checking an item back in automatically updates its availability in the public catalogue, closes out the borrower's loan record, and stops any overdue fine clock — all from one action.

The modules that make up an ILS

Almost every ILS on the market, regardless of vendor or price point, is built from the same core set of modules:

• Cataloguing — creating a record for each item with details like title, creator, format, subject and location, so it can be found and identified.
• Circulation — the check-in/check-out process, loan periods, renewals, holds, and any fines or fees.
• Patron or member management — records for everyone entitled to borrow, along with their loan history and any account restrictions.
• OPAC — the Online Public Access Catalogue, the public-facing search screen patrons use themselves. See what is an OPAC? for a full breakdown.
• Acquisitions — ordering and receiving new items, often tied to a budget, though smaller or informal collections may not use this module at all.
• Reporting — usage statistics, overdue lists, and inventory reports for day-to-day management.

Not every ILS implements every module with the same depth. A system built for a small school library might have a lightweight acquisitions module (or none at all), while an enterprise public library platform might add serials management, interlibrary loan, and multi-branch transfer on top of the basics.

Why a spreadsheet or plain database isn't an ILS

It's entirely possible to track a small collection in a spreadsheet: one row per item, a column for who has it. This works for a while, but it breaks down for reasons that have nothing to do with the size of the collection and everything to do with what it can't do: it can't calculate a fine automatically, can't stop a member borrowing once they hit a limit, can't tell you at a glance what's overdue across hundreds of items, and can't give the public a search screen of their own without staff manually managing it. An ILS is built specifically to handle those workflows, not just to store data about them. For a closer look at exactly where that line sits, see ILS vs simple catalogue software.

Who needs one

Any organisation that lends items to more than a handful of people benefits from an ILS — public libraries, school and college libraries, corporate and law firm libraries, and special collections that circulate material rather than just archiving it. Organisations that hold unique, non-circulating items (archives, museums) more often use a related but distinct category of "collection management" software, covered in our archive & special collections guide (coming soon).

What ties these very different organisations together isn't the size of the collection but the presence of lending as an activity that needs tracking. A one-room community library with a few hundred books and a corporate legal team sharing reference volumes across an office both need the same basic mechanics — they just need very different amounts of polish, capacity and reporting wrapped around them.

Where it runs: cloud or on-premise

An ILS can be delivered as a cloud-hosted (SaaS) service accessed through a browser, or installed on servers the library owns and manages itself. This is a separate decision from which modules you need, and it has a big effect on cost and IT overhead — see cloud vs on-premise library systems for the full comparison.