Every book on a library shelf began as an order somewhere. Before a patron can borrow it, that title had to be selected, ordered from a vendor, paid for, received, and added to the catalogue. This behind-the-scenes work is called acquisition, and for decades it was managed entirely on paper with order registers, ledgers, and accession books. Today, the acquisition function lives inside the Integrated Library System (ILS) as a dedicated module that connects ordering, budgeting, and cataloguing into one continuous workflow. Let us look at how the acquisition subsystem works, what it must be able to do, and why automating it has become standard practice in modern libraries.

Table of Contents

What the acquisition subsystem does in an ILS

An Integrated Library System is a single software platform that brings together the core functions of a library, such as cataloguing, circulation, serials control, the OPAC, and acquisitions. These functions are organised as separate but interconnected modules that share one database, so information entered in one place is instantly available everywhere else. The acquisitions module is the module responsible for ordering, receiving, and invoicing materials.

The key advantage of keeping acquisition inside the ILS is integration. When a librarian places an order in the acquisition module, a brief bibliographic record can already be created. When the item arrives, that same record flows into cataloguing instead of being typed again. The budget is updated automatically as money is committed and spent. This connection between ordering, finance, and the catalogue is what separates a true acquisition subsystem from a standalone purchasing spreadsheet.

Functional requirements for automated acquisition

For an acquisition subsystem to be useful, it has to handle several distinct tasks reliably. These functional requirements are common across most systems, whether open-source or commercial.

Order tracking

The system must record every order from the moment it is placed until the material arrives. This includes the title, quantity, expected cost, the vendor it was ordered from, and the current status of the order. Staff can check at any time which orders are still pending, which have been partly received, and which are complete. In Koha, for example, partial receipts are supported, so some items in an order can be marked received while others remain on order.

Fund accounting

Libraries usually work with a fixed budget allocated for purchasing materials, often split across departments or subject areas. The acquisition module tracks how much of each fund has been committed and how much actually spent. A central aim of fund accounting in an automated system is to give accurate information about funds committed and money still available, along with management reports whenever they are needed. As orders are placed, the system reserves the estimated amount; when the invoice is paid, it records the real cost. This prevents overspending and keeps the budget transparent.

Vendor management

Most libraries deal with several suppliers for books, journals, and other materials. The system stores details for each vendor, including contact information and ordering terms. In Koha, at least one vendor must be entered before any order can be placed, which reflects how central the vendor record is to the whole process. Storing vendor data centrally also makes it easy to compare suppliers and review which ones deliver on time.

Duplicate checking

Before ordering, the system should check whether the title is already in the collection. An automated acquisition system provides a search interface to verify whether a requested book is already held, with searching possible by title, author, publisher, or ISBN. If the item already exists, it is flagged as a duplicate and is not ordered again unless extra copies are genuinely needed. This single check saves money that would otherwise be wasted on unwanted copies.

The workflow of automated acquisition

The acquisition process follows a logical sequence of steps. An automated system guides the work from one stage to the next, carrying the same record forward instead of creating it fresh each time.

Selection and suggestion

The process begins with deciding what to buy. Suggestions may come from faculty, students, or library staff. Many Indian library packages build this into the workflow directly. One detailed account of acquisition in the SOUL software describes six steps for mechanising acquisition: vendor management, budgeting, suggestion, ordering, accession, and payment. At this stage the duplicate check is run so that the library does not order something it already owns.

Ordering

Once a title is approved, an order is created. In Koha the workflow uses a “basket” into which titles are added, much like an online shopping cart, before the order is finalised and sent to the vendor. When the price entered exceeds the money available in a fund, the system shows a confirmation warning, allowing staff to order beyond the fund only if they consciously choose to. This is a good example of how automation guards the budget without blocking legitimate decisions.

Receiving

When the shipment arrives, staff record the items as received. This is the point where the order meets reality. In Koha, the actual cost field is usually left blank until receiving, when it is confirmed against the vendor’s packing slip or invoice. The basket must be closed before its items can be received, and receiving is tied to the vendor’s invoice number, which links the physical arrival to the financial record.

Accessioning and cataloguing

The final step turns the received item into a shelf-ready library resource. An accession number is assigned, the bibliographic record is completed, and the item passes into the catalogue. Because the brief record was already created during ordering, the cataloguer builds on existing data rather than starting over. The item then becomes searchable in the OPAC and available for circulation, completing the journey from suggestion to shelf.

Advantages of automating acquisition

The shift from paper registers to an acquisition subsystem brings clear, practical gains.

Less manual effort and fewer errors

Data is entered once and reused at every later stage, so staff are not re-typing the same title details into separate order books, ledgers, and accession registers. A study of automated acquisition in major Indian academic libraries found that the system avoids re-entering data for ordering and relieves staff from the prolonged manual process, letting them deliver requested titles to users more quickly.

Better financial control

Automated fund accounting gives an up-to-date picture of the budget at any moment. The same study noted that in the LibSys software, the module maintains an up-to-date fund account for separate plans and provides precise budget analysis at any point in time. This makes audits simpler and spending decisions more informed.

Improved tracking and reporting

Because every order, receipt, and payment is logged, the library can produce reports on demand: outstanding orders, spending by department, vendor performance, and collection growth. Reporting tools that draw on data from all modules let a library generate reports on acquisitions, circulation, and collection growth to support budget reviews and collection development. This turns routine record-keeping into evidence for better decisions.

Several systems offer strong acquisition modules, ranging from free open-source platforms to proprietary products.

Koha

Koha is one of the most widely used open-source Integrated Library Systems in the world, and its acquisition module covers the full cycle from ordering and budget management through to receiving. Its open-source nature means it can be customised freely, which has made it especially popular here. The National Mission on Libraries under the Ministry of Culture has advocated Koha for automating public libraries, and the Kerala State Government has declared Koha as the official ILS for its public libraries. Several large library systems in the country, including the Delhi Public Library system, use Koha.

SOUL

SOUL, short for Software for University Libraries, was developed by the INFLIBNET Centre specifically for the needs of academic libraries here. SOUL 2.0 is compliant with international standards such as the MARC 21 bibliographic format and uses Unicode for multilingual records, and it includes a full acquisition module alongside cataloguing, circulation, and serials control. Because it is designed with the university and college library system in mind, it suits these institutions with minimal customisation.

Proprietary and cloud-based systems

Beyond open-source options, commercial systems remain widely used. LibSys is a long-established proprietary package well known for its acquisition and fund-accounting features. At the larger end, Alma is a cloud-based library services platform used by many big academic libraries, offering order creation, vendor management, and fund tracking with advanced analytics for data-driven collection decisions. The right choice depends on budget, library size, and how much technical support an institution can provide.

Bringing it together

The acquisition subsystem is where the library’s collection physically begins. By moving selection, ordering, fund accounting, receiving, and accessioning into one connected module, an ILS removes duplicated effort, protects the budget, and feeds clean data straight into the catalogue. For a working librarian, this means less paperwork and a clearer view of where every rupee and every order stands at any moment.

What do you think? If your library still relies partly on manual order registers, which single step in the acquisition workflow would benefit most from automation? And when choosing between a free open-source system and a paid proprietary one, what would matter more to you: the cost savings or the guaranteed technical support?

How useful was this post?

Click on a star to rate it!

Average rating 0 / 5. Vote count: 0

No votes so far! Be the first to rate this post.

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

References
  1. https://www.sciencedirect.com/topics/computer-science/integrated-library-system
  2. https://socialsci.libretexts.org/Courses/Sacramento_City_College/LIBT_300:_Introduction_to_Library_Services_(Li)/01:_Technical_Services_and_Infrastructures/1.02:_New_Page
  3. https://kohasupport.com/knowledge-base/what-are-acquisitions/
  4. https://ebooks.inflibnet.ac.in/lisp5/chapter/library-automation-acquisition/
  5. https://koha-community.org/manual/22.11/en/html/acquisitions.html
  6. https://www.researchgate.net/publication/235320633_Ranking_of_selected_library_software_packages_in_India
  7. https://koha-community.org/manual/22.05/en/html/acquisitions.html
  8. https://www.researchgate.net/publication/267265964_AUTOMATED_BOOK_ACQUISITION_SYSTEM_A_CASE_STUDY_OF_CENTRAL_LIBRARIES_OF_IIT_DELHI_IIT_KANPUR_AND_KASHMIR_UNIVERSITY
  9. https://www.soutron.com/en_us/blog/general/integrated-library-system/
  10. https://egyankosh.ac.in/bitstream/123456789/35928/5/Unit-3.pdf

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

ICT in Libraries

1 Introduction to Library Automation

  1. Evolution of Library Automation
  2. Automated Library Systems
  3. Automated Library System: Standards and Software
  4. Automated Library System: Global Recommendations
  5. Automated Library System: Development of RFP
  6. Automated Library System: Trends and Future

2 Library Automation Processes

  1. Library Workflow: System Approach
  2. Acquisition Subsystem in ILS
  3. Document Processing Subsystem in ILS
  4. Serials Control Subsystem in ILS
  5. Circulation Subsystem in ILS
  6. System Administration

3 Library Automation – Software Packages

  1. History, Evolution and Generations
  2. Categorisation of ILS
  3. Open Source Software Packages
  4. Commercial Software Packages
  5. Freeware ILS
  6. Evaluation of Software Packages

4 Library Automation – Applications of Open Source Software

  1. Open Source Movement
  2. Open Source Software: Development Path
  3. Open Source Software vs. Commercial Software
  4. Open Source Software: Philosophy, Principles and Licensing
  5. Open Source Software and Libraries
  6. Open Source Software in Libraries: System Level
  7. Open Source Software in Libraries: Domain Level
  8. Towards Open Library System

5 Introduction To Digital Library

  1. Concept
  2. Types of Digital Libraries
  3. Major Digital Library Initiatives
  4. Future Trends

6 Digitisation Process

  1. Digitisation of Print Based Documents
  2. Video Digitisation
  3. Audio Digitisation
  4. Audio/Video Compression
  5. Audio/Video Streaming
  6. File Formats and Content Creation

7 Creating Digital Libraries Using DSpace

  1. Functional Features of DSpace
  2. Installing DSpace on Windows
  3. Working with DSpace

8 Creating Digital Libraries Using GSDL

  1. Technical Features
  2. Installation of GSDL on Windows
  3. Greenstone Interfaces
  4. Collection Building in Greenstone