Commissioned Research
Top 10 Best Library Software of 2026

GITNUXSOFTWARE REVIEW

Education & Learning

Top 10 Best Library Software of 2026

Editorial roundup comparing library software options like Koha, for libraries evaluating features, workflows, and setup needs.

21 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

Search agents gather the source set and the review record, including transcriptions of video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

Library software runs circulation, metadata, and patron workflows with an ILS data model that has to match local cataloging rules and access policies. This comparison helps operators weigh fit across integrations, automation settings, and governance controls like RBAC and audit logs for day-to-day throughput.

Koha is the best pick for multi-branch libraries that want full ILS control because circulation and hold policies can be set per branch with fine-grained fulfillment notices, while Surpass suits teams that need repeatable, configuration-driven metadata and collection workflows with staff review stages.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

Koha

Circulation and holds policies per branch with fine-grained control over fulfillment behavior and notices.

Best for: Fits when multi-branch libraries need full ILS control with extensibility for local workflows.

2

Librarika

Editor pick

Single interface for catalog records, circulation actions, and online patron access for requests

Best for: Fits when a library needs catalog access plus circulation controls without heavy systems integration.

3

Surpass

Editor pick

Configuration-driven processing workflows that route records through review and publication stages with consistent rules.

Best for: Fits when teams need governed, repeatable metadata and collection workflows across multiple staff groups.

Comparison Table

1
KohaBest overall
SMB
9.2/10
Overall
2
8.7/10
Overall
3
vertical specialist
8.6/10
Overall
4
vertical specialist
8.5/10
Overall
5
8.2/10
Overall
6
vertical specialist
7.8/10
Overall
7
7.6/10
Overall
8
enterprise
7.3/10
Overall
9
enterprise
6.8/10
Overall
10
6.6/10
Overall
#1

Koha

SMB

Open-source integrated library system maintained by a global community.

9.2/10
Overall
Features9.2/10
Ease of Use9.1/10
Value9.3/10
Standout feature

Circulation and holds policies per branch with fine-grained control over fulfillment behavior and notices.

Koha covers core ILS workflows including acquisitions, serials management, catalog maintenance, and circulation with configurable rules per branch. Staff work is organized around item records, bibliographic records, and patron profiles, with granular permissions for staff roles. Public access is delivered through an OPAC that can be themed and extended through Koha’s customization mechanisms.

A tradeoff is administrative overhead because Koha configuration depth can require ongoing governance for new branches, rule changes, and integration endpoints. Koha fits best when libraries need control over workflows and data handling across multiple locations, including migrations from other ILS setups.

Pros
  • +Full-featured ILS workflow coverage across cataloging, circulation, holds, and serials
  • +MARC21 cataloging and authority workflows aligned to common library data practices
  • +Branch and circulation rules configurable for multi-location service models
  • +Plugin and customization options support site-specific workflows and integrations
Cons
  • –Configuration complexity increases with deeper circulation and fulfillment policy changes
  • –User experience depends heavily on local configuration and staff training
  • –Some integration patterns require custom development and maintenance work
  • –Upgrade paths demand careful testing for local customizations and plugins
Use scenarios
  • Multi-branch library operations

    Branch-specific circulation policy management

    Fewer policy exceptions

  • Cataloging department managers

    Authority-driven MARC record workflows

    More consistent cataloging

Show 2 more scenarios
  • Systems librarians

    Extend interfaces for local systems

    Lower integration friction

    Koha extensibility supports integration points for authentication, interoperability, and workflow-specific automation.

  • Interlibrary loan staff

    Patron and item fulfillment tracking

    Clearer request handling

    Koha’s circulation structures help coordinate requests, item status, and fulfillment steps through shared records.

Best for: Fits when multi-branch libraries need full ILS control with extensibility for local workflows.

#2

Librarika

SMB

Librarika is a cloud-based library management system for small libraries, schools, and organizations.

8.7/10
Overall
Features8.7/10
Ease of Use8.7/10
Value8.7/10
Standout feature

Single interface for catalog records, circulation actions, and online patron access for requests

Librarika is a library services and catalog management solution built around book and media records, patron lists, and day-to-day circulation. It supports online catalog access with collection organization features that fit small to mid-size libraries and community archives.

Circulation and inventory workflows cover checkouts, returns, and holds in a single operating space for staff and patrons. Record handling focuses on practical metadata entry for MARC-style workflows without requiring a full institutional integration stack.

Pros
  • +Circulation and item inventory stay in one working interface
  • +Online catalog pages support patron self-service for search and requests
  • +Bulk import and export options reduce manual record upkeep
  • +Clear patron lists and lending history simplify staff lookups
Cons
  • –Limited integration coverage for enterprise discovery and authentication stacks
  • –Automation depth is thin for cross-system workflows beyond catalog updates
  • –Advanced metadata interoperability options are less flexible than ILS incumbents
  • –Role governance and audit visibility are basic compared with larger platforms
Use scenarios
  • Church and community volunteers

    Manage borrower categories and holds

    Lower overhead for lending

  • School librarians and educators

    Provide student lending visibility

    Simpler campus circulation

Show 2 more scenarios
  • Small library staff

    Process renewals and due dates

    Consistent loan tracking

    Staff handle checkouts, returns, renewals, and holds using item and member records.

  • Public library patrons

    Search collections with availability

    Faster item discovery

    Patrons access a searchable online catalog that reflects item availability without staff assistance.

Best for: Fits when a library needs catalog access plus circulation controls without heavy systems integration.

#3

Surpass

vertical specialist

Library automation system for schools and small public libraries.

8.6/10
Overall
Features8.6/10
Ease of Use8.6/10
Value8.6/10
Standout feature

Configuration-driven processing workflows that route records through review and publication stages with consistent rules.

Surpass is built for institutions that run repeatable collection maintenance, including batch record updates, controlled vocabularies, and structured metadata editing. The system’s workflow orientation supports staff review stages before records become visible in patron-facing services. Integration is designed to fit library ecosystems that exchange bibliographic records and availability details across multiple systems. It is best when collection operations require consistent processing rules rather than ad hoc cataloging.

A tradeoff appears in governance-heavy environments where strong workflow discipline is needed to keep ingest and edit rules consistent across teams. Surpass fits institutions that centralize metadata work and need auditable handoffs between ingest, quality checks, and publication steps. It is less suitable for libraries that require highly bespoke cataloging logic on a per-record basis without a standardized workflow.

Pros
  • +Workflow-driven collection maintenance with staff review stages
  • +Batch-friendly metadata editing for repeatable catalog operations
  • +Governed processing rules reduce drift across teams
  • +Integration orientation supports record exchange across library services
Cons
  • –Workflow discipline is required for consistent cross-team operations
  • –Highly bespoke per-record logic takes longer than standardized pipelines
  • –Admin configuration can be time-consuming for multi-branch teams
  • –Advanced automation depends on clear operational ownership
Use scenarios
  • Technical services teams

    Standardize batch record maintenance workflows

    Fewer metadata inconsistencies

  • Digital collections operators

    Coordinate enrichment and access readiness

    More consistent discovery visibility

Show 2 more scenarios
  • Consortia collection coordinators

    Manage centralized rules across branches

    Lower cross-site drift

    Enforces shared processing behavior while supporting branch-specific operational handoffs.

  • Systems librarians

    Integrate catalog content with external services

    Fewer manual reconciliation steps

    Supports institution workflows where records must stay synchronized across connected systems.

Best for: Fits when teams need governed, repeatable metadata and collection workflows across multiple staff groups.

#4

ResourceMate

vertical specialist

Library cataloging software for churches, schools, and special collections.

8.5/10
Overall
Features8.5/10
Ease of Use8.5/10
Value8.5/10
Standout feature

Trigger driven staff task routing tied to resource and collection workflow state transitions.

ResourceMate is a library workflow and operations layer focused on managing physical and digital resources as organized collections with configurable handling processes. Core capabilities include collection records, circulation related workflows, and task automation that routes work to staff roles based on defined triggers.

Pros
  • +Configurable workflow steps with trigger based task routing
  • +API driven integration points for resource and user related events
  • +Collection centric organization that reduces manual cross referencing
  • +Operational auditability through staff actions and workflow state history
Cons
  • –Limited coverage for full cataloging interoperability expectations
  • –Requires governance discipline to keep workflow rules consistent
  • –Automation depth depends on how externally sourced data is mapped
  • –Migration from MARC centric workflows can require custom bridging
Use scenarios
  • Church and nonprofit librarians

    Run lending and inventory administration

    Easier daily operations

  • School and special libraries

    Handle holds and due date workflows

    More consistent transactions

Show 2 more scenarios
  • Small library inventory teams

    Validate shelf holdings with scans

    Find missing items

    Teams scan items in batches and compare results with recorded holdings in the catalog.

  • Periodicals and serials staff

    Track issues and holdings history

    Clear issue visibility

    Staff connect recurring publication issues to catalog holdings and circulation records.

Best for: Fits when library teams need workflow automation around curated collections and controlled staff operations.

#5

Insignia Library System

SMB

Insignia Library System is an integrated platform for public, school, academic, and special libraries.

8.2/10
Overall
Features8.2/10
Ease of Use8.3/10
Value8.1/10
Standout feature

Staff-facing circulation and holds screen design keeps item status, request queue, and patron account changes in one operational flow.

Insignia Library System manages circulation, holds, patron accounts, and day-to-day library workflows through an integrated library services setup. It also supports bibliographic searching and record handling that ties catalog data to item status for accurate availability.

Pros
  • +Circulation and holds workflows cover common staff and patron operations
  • +Configurable lending and item status rules support multiple policy models
  • +Catalog browsing ties record-level metadata to item availability states
  • +Operational tooling reduces manual steps during routine daily processing
Cons
  • –Integration depth varies by workflow and can require external service coordination
  • –Advanced metadata interchange needs careful setup to match local practices
  • –Workflow automation is narrower than products focused on heavy API first extensions
  • –Governance controls for multi-library structures require deliberate configuration
Use scenarios
  • Library administrators

    Maintain borrower records and holds

    Current account view

  • Cataloging teams

    Import and exchange bibliographic data

    Less manual re-entry

Show 2 more scenarios
  • School collection operations

    Track item location and barcode status

    Better item availability

    Staff manage item-level holdings, inventory status, and location details for circulation readiness.

  • Metadata cleanup managers

    Apply batch edits to large catalogs

    Faster metadata corrections

    Teams correct and standardize many bibliographic entries using batch editing and field-level updates.

Best for: Fits when a library needs a single ILS workflow for circulation and holds with practical staff operations.

#6

Libby

vertical specialist

Digital content lending platform connecting libraries with ebooks and audiobooks.

7.8/10
Overall
Features7.8/10
Ease of Use7.7/10
Value7.9/10
Standout feature

OverDrive loan and hold orchestration surfaces accurate availability and queue status inside the Libby app.

Libby provides a patron-facing catalog experience that supports browsing, wishlists, holds, and notifications tied to item-level availability from the publisher and license rules. Borrowing and reading are designed around the OverDrive loan flow, including download and stream options for supported formats. Libraries integrate by connecting patron accounts and configuring access through OverDrive’s ecosystem, then pushing catalog content and availability into Libby for end-user use.

Pros
  • +Patron-friendly borrowing flow with holds, notifications, and timed returns
  • +Consistent mobile and web reading experience for e-books and e-audiobooks
  • +Real-time availability reflects license and waitlist status
  • +Library account authentication supports multi-library and card-based access
Cons
  • –Limited admin-side workflow customization compared with full ILS tooling
  • –Format and device support depends on OverDrive media capabilities
  • –Advanced reporting and analytics require alignment with OverDrive reporting
Use scenarios
  • Patrons and circulation teams

    Manage holds for e-books and audio

    Faster pickup and fewer missed loans

  • Library digital services staff

    Deliver licensed e-content to patrons

    Consistent access across branches

Show 1 more scenario
  • Branch managers

    Support patrons with multiple library cards

    Reduced access friction

    Patrons authenticate through a library account and borrow from the correct collections.

Best for: Fits when a library prioritizes mobile-first e-book and audiobook borrowing with reliable hold handling.

#7

Soutron Library Management System

vertical specialist

Soutron provides library and information management software for specialist and corporate collections.

7.6/10
Overall
Features7.6/10
Ease of Use7.6/10
Value7.6/10
Standout feature

Configurable circulation policy rules that drive loans, renewals, and holds behavior across staff workflows.

Soutron Library Management System targets institutions that need an end-to-end workflow for circulation, cataloging, and patron services without separate tooling for each step. It supports standard bibliographic handling with MARC records, item holdings, and authority-oriented workflows for consistent access points.

Pros
  • +MARC-based cataloging with practical holdings management for real workflows
  • +Policy-driven circulation supports common loan rules, holds, and renewals
  • +Staff role controls separate day-to-day access from privileged operations
  • +Integration options for connecting external systems that track patron and item data
Cons
  • –Deep integrations can require governance to keep data exchange consistent
  • –Limited visibility into end-to-end automation chains compared with workflow-heavy suites
  • –Advanced reporting relies more on configured outputs than on ad hoc analytics
  • –Some specialized workflows may depend on add-ons or custom configuration
Use scenarios
  • Small library operations staff

    Manage loans, renewals, and holds

    Fewer manual circulation issues

  • Technical services catalogers

    Maintain MARC records and authorities

    Cleaner catalog data

Show 2 more scenarios
  • Integration and systems team

    Exchange patron and item transactions

    Reduced data duplication

    Provides integration hooks to share patron, item, and transaction data with external systems.

  • Consortium administrators

    Standardize access workflows across libraries

    More uniform patron experiences

    Enables consistent item and patron services using shared workflows and roles across participating institutions.

Best for: Fits when mid-sized libraries need a single system for circulation and catalog operations with defined staff roles.

#8

V-Smart

enterprise

V-Smart is a library management system for public libraries, schools, and cultural institutions.

7.3/10
Overall
Features7.3/10
Ease of Use7.3/10
Value7.3/10
Standout feature

API-driven workflow handoffs that connect circulation and patron actions to external services with controlled permissions.

V-Smart targets library operations with a workflow and integration approach focused on circulation, patron management, and back-office services rather than only public discovery.

Pros
  • +API-first integration for common library workflow handoffs
  • +Configurable service processes for circulation and patron actions
  • +Multi-institution operational setup for shared deployments
  • +Governed user permissions for staff access control
Cons
  • –Advanced automation may require integration work for edge cases
  • –Audit depth depends on how logging is enabled per workflow
  • –Some discovery-style use cases need separate components
  • –Data synchronization requires careful mapping across connected systems
Use scenarios
  • Circulation operations managers

    Automate lending and check workflows

    Faster service turnaround times

  • Library IT integration teams

    Connect patron identity and holds systems

    Reduced manual data reconciliation

Show 2 more scenarios
  • Back-office service coordinators

    Manage multi-institution operational settings

    Consistent cross-library operations

    Provides admin controls for institutions, permissions, and operational configurations across environments.

  • Discovery-to-service workflow owners

    Route requests to fulfillment workflows

    Fewer broken request handoffs

    Links external bibliographic services and workflows so requests move into managed lending actions.

Best for: Fits when libraries need an interoperable library services platform with automation and governed admin control.

#9

LIBSYS

enterprise

LIBSYS provides integrated library management software for academic, corporate, public, and government libraries.

6.8/10
Overall
Features6.8/10
Ease of Use6.8/10
Value6.8/10
Standout feature

Configurable lending and operational policy rules that apply directly to membership, circulation actions, and request handling.

LIBSYS is a library services platform built for day-to-day circulation, cataloging, and patron management workflows in Indian library settings. It focuses on practical operational coverage like membership records, issue and return tracking, and holds or request handling tied to local catalog operations.

Pros
  • +Covers core circulation workflows with straightforward patron tracking
  • +Supports bibliographic maintenance for ongoing catalog record hygiene
  • +Role-based staff access supports controlled library operations
  • +Library policy settings help enforce consistent lending rules
Cons
  • –Integration surface is limited compared with API-first ILS deployments
  • –Authority control depth is thin for libraries needing advanced linking
  • –Some workflows rely on manual catalog processes for exceptions
  • –Reporting breadth is narrower than full analytics suites
Use scenarios
  • Library circulation staff

    Daily issue return and renewal processing

    Fewer checkout errors

  • Cataloging librarians

    Manage bibliographic records and edits

    Cleaner catalog records

Show 2 more scenarios
  • Library administrators

    Control lending rules and permissions

    Consistent policy enforcement

    Configures library policies and staff roles to govern lending eligibility and operational access.

  • Institutional library managers

    Handle holds and requests workflows

    Faster patron request fulfillment

    Manages hold and request handling linked to catalog operations and membership records.

Best for: Fits when a library needs a workable ILS-style workflow for circulation and catalog maintenance with controlled staff roles.

#10

Apollo

SMB

Cloud-based ILS designed specifically for small and medium public libraries.

6.6/10
Overall
Features6.6/10
Ease of Use6.5/10
Value6.7/10
Standout feature

Workflow automation tied to configurable circulation and back-office policies, reducing manual rework during ongoing operations.

Apollo from Biblionix supports library workflows through cataloging and circulation oriented modules, with configuration centered on bibliographic records and local policies. It provides APIs and integration tooling for synchronizing library data with external systems and for managing e-resources access paths.

Pros
  • +APIs for data sync with external catalog, e-resource, and analytics systems
  • +Automation for recurring catalog and circulation tasks
  • +Admin configuration focuses on library policy controls
  • +Extensibility paths for integrating adjacent library services workflows
Cons
  • –Automation coverage depends on workflow design and integration scope
  • –Fine-grained governance requires careful role configuration
  • –Some integrations may need additional build work for legacy systems
  • –Reporting depth can be limited without tailored extraction
Use scenarios
  • Public and school libraries

    Publish patron-facing search and browsing

    Smarter material selection

  • Cataloging staff

    Create and export structured records

    More maintainable data

Show 2 more scenarios
  • Circulation operators

    Process loans and item status changes

    Predictable loan handling

    Operators manage checkouts, returns, and patron transactions using staff workflows.

  • Library consortia

    Coordinate shared cataloging and holdings

    Fewer duplicate cataloging efforts

    Multiple libraries share cataloging and holdings workflows while coordinating local collection operations.

Best for: Fits when a mid-size library needs workflow automation plus an integration-first architecture for records and patron services.

Conclusion

After evaluating 10 library software, Koha stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
Koha

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Library Software

How do Libby and Koha differ for e-book and audiobook access workflows?
Libby is a patron-first e-book and audiobook borrowing interface that orchestrates holds and loan status through OverDrive loan models inside the app. Koha is an ILS library services platform that runs circulation and holds policies for physical and other cataloged items. Libraries choose Libby when e-content borrowing experience matters more than running full catalog and circulation in one system.
Which tool is better when multi-branch circulation policy needs fine-grained control?
Koha fits multi-branch needs because circulation and holds policies can be configured per branch with staff permission controls around circulation actions. LIBSYS also supports operational rules tied to local lending behavior, but its design targets Indian library settings and membership-driven workflows. Libraries that require the widest local policy variability per branch tend to standardize on Koha.
How does Surpass handle governed metadata and record processing compared with Koha?
Surpass routes bibliographic and holdings records through configuration-driven ingest and enrichment workflows with staff tasking at defined review stages. Koha focuses on MARC21 cataloging workflows, authority control, and circulation operations inside a single open source platform. Surpass is the better fit when the dominant requirement is repeatable metadata pipeline governance across staff groups.
What breaks if an institution tries to replace circulation and holds workflows with a collection automation tool?
ResourceMate and V-Smart can automate staff routing and operational tasks, but replacing the core circulation and holds engine can leave loan and request state transitions under-specified. In ResourceMate, automation is built around resource and collection workflow state transitions, so deep patron account and item-availability correctness depends on its integrated hooks. In V-Smart, API-driven workflow handoffs require external services to maintain accurate circulation outcomes.
How do Apollo and V-Smart support integrations and data synchronization in library workflows?
Apollo provides APIs and integration tooling for synchronizing library data and managing e-resource access paths alongside configured circulation and back-office policies. V-Smart targets interoperability by using API-driven workflow handoffs that connect circulation and patron actions to external services under controlled permissions. Apollo is often used when external record and e-resource syncing dominates, while V-Smart is used when end-to-end service task handoffs need stronger automation patterns.
When does an admin team prefer RBAC and operational permissions over broad configuration-only controls?
Koha includes permissions management tied to circulation, messaging, and reporting so roles can be restricted per workflow capability. LIBSYS also administers roles for librarians and staff, aligning operational permissions with local lending rules and membership handling. Soutron relies on staff roles and configurable policy rules across circulation and catalog workflows, so teams that require tight workflow-level access boundaries often evaluate Koha and LIBSYS more directly.
Where does Soutron tend to fall short compared with Koha for complex cataloging and authority workflows?
Soutron focuses on end-to-end practical operations with MARC records, item holdings, and authority-oriented workflows, so advanced authority control edge cases depend on its configurable implementation. Koha is purpose-built for MARC21 cataloging and authority control workflows that sit close to the underlying ILS data model. Libraries that treat authority control and cataloging configuration as a daily, high-variance workflow often favor Koha.
How do Librarika and Insignia differ in handling catalog access plus day-to-day circulation?
Librarika combines online catalog access with circulation actions, inventory, and holds in a single operating space for small to mid-size libraries. Insignia Library System keeps item status, request queue, and patron account changes in staff-facing circulation and holds screens that drive availability accuracy during requests. Librarika fits when a single interface matters most, while Insignia fits when transaction visibility during holds processing is a primary operational requirement.
Which tradeoff appears when a library chooses open source extensibility with Koha instead of configuration-driven workflow processing in Surpass?
Koha’s extensibility via plugins and custom code supports tailoring circulation and reporting behavior, but it can shift complexity into implementation and ongoing governance. Surpass emphasizes configuration-driven processing pipelines and staff task routing for metadata and service operations, reducing ad-hoc customization needs for ingestion and publication stages. Libraries that want low change management on metadata pipelines often prefer Surpass, while libraries that require deep local feature customization tend to prefer Koha.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Library Software

We see the biggest differences in how well each system handles circulation workflows, how deep its integration breadth goes, and how much control you get over configuration and reporting. In practice, these show up as automation options, API access, and admin governance you can verify during a real demo with your sample records.

Workflow automation for day-to-day tasks

Why it matters

Workflow automation for day-to-day tasks determines whether staff spend time clicking through routine steps. It also affects turnaround for notices and status changes, especially when batches of records need updates.

How to check

Ask the demo team to set up a small batch and show how the system triggers the next steps automatically (for example, status updates and notices). Then watch whether manual overrides are logged and whether the workflow can run on a schedule.

Typical range

N/A

Integration and API surface depth

Why it matters

Integration and API surface depth matters when your library tools must exchange data reliably without custom workarounds. It also clarifies whether you can automate imports, sync, and operational reporting across systems.

How to check

Request an API walkthrough: list the main endpoints or functions they expose for core objects, and ask what can be automated. If possible, test a simple sync in the demo using a sample dataset and confirm what changes in the UI afterward.

Typical range

N/A

Import/export fidelity for bibliographic data

Why it matters

Import/export fidelity affects how much effort you’ll spend cleaning and re-mapping records. When data round-trips correctly, migrations and ongoing updates stay predictable.

How to check

Bring a sample export you trust and ask them to import it with the same field mapping. Verify that key attributes survive (titles, item/holding details, identifiers) and that the system produces an actionable error report for failures.

Typical range

N/A

Admin governance and RBAC controls

Why it matters

Admin governance and RBAC controls determine who can change policies, configurations, and record data. Strong controls reduce accidental changes and make audits more meaningful.

How to check

Ask for roles you can assign (for staff, cataloging, circulation staff, and reports). Then attempt a permission-sensitive action in the demo and confirm access is denied and recorded in an audit log.

Typical range

N/A

Reporting coverage and audit log usability

Why it matters

Reporting coverage and audit log usability affects whether you can prove what happened and monitor operational health. When logs are easy to search, staff can resolve issues faster.

How to check

Ask to view audit log entries for a specific change you trigger in the demo, then export or filter those results. Also request a few operational reports that match day-to-day needs and check whether filters reflect the objects you care about.

Typical range

N/A

Configuration flexibility for rules and policies

Why it matters

Configuration flexibility for rules and policies changes how often you need staff workarounds when policies evolve. It also shows whether the system can adapt to your local operating model without code changes.

How to check

In the demo, request a policy tweak (such as fine/fee rules, notice timing, or item rules) and see whether it can be done through configuration screens. Confirm how the system handles existing records after the change.

Typical range

N/A

Red flags

  • Automation requires manual steps for routine status changes.
  • API access is limited to read-only or lacks objects you need to sync.
  • Imports “work” but fail silently or lose important fields without clear errors.

Fit by situation

  • If we need fewer handoffs between staff during daily operations, prioritize Workflow automation for day-to-day tasks.
  • If we rely on other systems for record exchange, prioritize Integration and API surface depth.
  • If we’re migrating or regularly importing legacy records, prioritize Import/export fidelity for bibliographic data.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.