Library Management Systems (ILS): the complete guide

What a library management system actually does

A library management system — usually shortened to ILS, for Integrated Library System — is the software that runs the day-to-day operations of a library or lending collection. Before these systems existed, that meant a card catalogue for finding items, a ledger or index card tray for tracking who had what out on loan, and a separate paper trail for ordering new stock. An ILS replaces all of that with one connected database and a set of tools built around it.

The word "integrated" is doing real work in that name. It doesn't just catalogue items — it also tracks who is allowed to borrow them, what's currently on loan, what's overdue, what's been ordered but not yet arrived, and what the collection as a whole looks like. Because all of that lives in one system, a change in one place (a book gets returned) is reflected everywhere else instantly (it shows as available in the public catalogue, the borrower's fine clock stops, and it's ready to be issued again).

For a deeper, definition-first look at this, see what an ILS actually is.

The core modules, explained

Almost every ILS, regardless of vendor, is built around the same handful of modules. They vary in how sophisticated each one is, but the shape is consistent:

• Cataloguing. Creating and maintaining records for everything in the collection — title, creator, subject, format, location, and often much more detailed metadata for specialist collections.
• Circulation. Checking items in and out, managing loan periods and renewals, calculating fines or fees, and placing and fulfilling holds.
• OPAC (public catalogue). The public-facing search interface that lets members or patrons look up what's available, without needing staff access to the back office. Covered in full in what is an OPAC?
• Acquisitions. Ordering new items, tracking budgets, and receiving stock in — more relevant to libraries with a formal purchasing workflow than to small or informal collections.
• Patron / member management. Records for everyone allowed to borrow, their loan history, contact details, and any restrictions or permissions tied to their account or membership type.
• Reporting. Statistics on circulation, collection usage, overdue items, and inventory — used both for day-to-day management and for justifying budgets to whoever funds the library.

Some systems bolt on more specialised modules — serials management for journals and periodicals, interlibrary loan, self-service kiosks, or event and room booking for community-facing public libraries. Not every library needs every module, which is part of why ILS products range from lightweight tools built for a single school library to enterprise platforms built for multi-branch public library authorities.

Who actually uses an ILS

The term is broad by design, because the same underlying pattern — catalogue plus circulation plus a public search front end — shows up across very different kinds of organisation:

• Public libraries, where the collection is broad, membership is open to the community, and self-service (holds, renewals, a branded portal) matters a lot.
• School and college libraries, often smaller in scale but with specific needs around reading levels, curriculum tagging, and integration with the wider institution.
• Special libraries, such as law firm libraries, corporate knowledge centres, or research institutions, where the collection is narrower but the metadata needs are often deeper.
• Archives, museums and galleries, which frequently use adjacent "collection management" software that shares the same DNA as an ILS but is tuned for unique, often irreplaceable items rather than multiple lendable copies — more on that distinction in the archives guide.

ILS, "library software" and "catalogue software" — sorting out the terms

In casual conversation, "library software," "library management system" and "ILS" are usually used interchangeably, and that's fine — they mean the same thing. Where it gets confusing is the difference between a full ILS and simpler "catalogue software" or "catalogue database" tools, which only handle the cataloguing piece and skip circulation, patrons and acquisitions entirely. That distinction matters more than the naming, because it determines whether a tool can actually run your lending operation or just describe what's on your shelves. It's covered in detail in ILS vs simple catalogue software.

Cloud-based vs on-premise: where the software actually runs

Once you're looking at real products, the next fork in the road is deployment. A cloud-based (SaaS) ILS runs on the vendor's servers and is accessed through a browser, with the vendor handling hosting, backups and updates. An on-premise system runs on hardware the library owns or rents, with the library's own IT staff (or contractor) responsible for keeping it running. Neither is universally "better" — the right answer depends on the size of the organisation, the sophistication of its in-house IT, and how much control it needs over where its data physically sits. The full trade-offs are set out in cloud vs on-premise library systems.

Standards you'll hear mentioned alongside an ILS

Because libraries have been sharing catalogue data with each other for decades, a handful of technical standards show up repeatedly in ILS product sheets and RFPs. MARC21 is the long-standing format for encoding bibliographic records, so systems can exchange full catalogue records without retyping them. Z39.50 (and its newer web-friendly successor, SRU) is a protocol that lets one system search another's catalogue remotely, which is how union catalogues and interlibrary loan searching work. You don't need to understand these deeply to choose an ILS, but if your library exchanges data with other institutions, ask whether a system supports them. They're covered in depth in our cataloguing and metadata standards guide, coming soon.

Choosing a system, and what it costs

Budget is usually the first practical constraint, and it's shaped heavily by the deployment model above, the number of branches or sites, the size of the collection, and which modules you actually need switched on. There's a full breakdown of pricing models and typical ranges in how much does library management software cost?, and a broader buyer's checklist — covering the whole decision, not just price — is coming soon in our guide to choosing and switching software.

It's worth resisting the urge to choose on price alone. A cheaper system that can't handle your loan rules, doesn't export data cleanly if you ever need to leave, or has thin support when something breaks on a Monday morning tends to cost more in staff time than it saves in licence fees. The most reliable evaluation method is still a live trial with your own sample data and your own edge cases — a shared collection with an odd loan period, a member type with unusual permissions — rather than a generic vendor demo.

Signs your current setup needs a change

If you already run some kind of system, a few recurring symptoms are worth watching for: staff keeping "workarounds" in spreadsheets alongside the official system, patrons regularly asking for features (holds, renewals, mobile-friendly search) that simply aren't available, or a vendor that's slow to respond, rarely ships updates, or is winding the product down. Any of these is a reasonable trigger to start evaluating alternatives, even if switching feels disruptive in the short term.

Frequently asked questions