A hardware-supplier perspective on kiosk formats, identification modules, enclosure design and the information a library project must confirm before a purchase order is issued.
A library self-service terminal is a hardware platform. It provides a touchscreen, a computing host, identification modules, a receipt printer and an enclosure that places those components at the right height and angle for a borrower. What it does not do, on its own, is process a loan against a library management system.
That distinction matters at the procurement stage, because public library tenders routinely bundle three separate deliverables into one document: the physical kiosk, the self-service application, and the integration with the library’s ILS through SIP2 or NCIP. A hardware supplier should be able to quote clearly on the first deliverable while stating what it needs from the second and third.
| Role | Responsibility | Not included by default |
|---|---|---|
| Hardware supplier | Kiosk hardware, optional modules, enclosure structure and appearance customization, agreed driver or interface documentation, sample testing against customer-supplied tags and cards | Borrow/return application, patron account logic, ILS protocol implementation, library system configuration |
| Customer or software partner | Self-service application, SIP2/NCIP integration, patron data handling, business logic | Hardware selection and physical adaptation |
| Jointly confirmed | Operating system and driver matching, identification module test conditions, interface definitions, prototype acceptance scope | — |
SIP2 is the long-standing protocol used by third-party self-service devices to communicate with an ILS; NCIP is a later alternative. The software implementation and licensing of either protocol typically sit with the customer or integrator. The hardware supplier’s role is to provide a platform on which that software can run, and to confirm the ports, power and driver conditions the software requires.
For a library borrow return kiosk project, this boundary also affects what a quotation should contain. A hardware quote that says “supports SIP2” without naming the software party responsible for the protocol layer creates ambiguity later. A clearer formulation is: the kiosk supports the operating system and interface conditions required by the customer’s SIP2 client software, and the hardware supplier will confirm those conditions against the actual BOM.
The starting question is not “which model do you have,” but “what space and workflow does the kiosk need to fit into.” Public libraries, branch libraries, community reading rooms and university libraries produce different answers to that question, and the hardware format should follow.
| Installation context | Format direction | Hardware parameters to confirm first |
|---|---|---|
| Existing service desk, community reading room, space-constrained branch | Desktop self-service terminal | Counter depth and load capacity; cable exit direction; screen angle for mixed seated/standing use; cut-outs for card or scanner modules |
| Main hall of a public library, dedicated self-service zone | Freestanding or floor-standing kiosk | Base fixing method (floor anchor or weighted base); body depth and circulation clearance; service door orientation; screen centre height |
| Site that needs physical book return and immediate holding | Integrated return terminal with a bin | Return slot dimensions and height; bin capacity matched to daily return volume; full-bin detection method; whether the bin is integrated with the kiosk body or separate |
| System integrator batch deployment or branded project | Standard platform with structural customization | Whether cut-out drawings and module layout can be adjusted; panel removability; packaging consistency across units |
For a public reading room self service device, the desktop format is usually the only realistic option: the room may not have floor space for a freestanding unit, and the service point may be shared with a staff desk. The hardware question then becomes how much of the module stack can fit into a shallow counter profile without forcing the reader to lean over the unit.
Outdoor or 24-hour unstaffed formats should only be presented if the supplier actually manufactures a model engineered for that environment. An indoor terminal placed near an entrance is not the same product as a weather-rated, vandal-resistant outdoor return unit, and procurement documents should not conflate the two.
This section is organized by the modules that a library project actually has to specify. For each module, the useful pattern is: what the hardware supplier can offer, and what the customer or integrator must provide before that offer can be confirmed.
Available ranges typically sit between roughly 15 and 27 inches diagonal, with 21.5-inch and 24-inch panels common in public-library self-service units. Capacitive touch is the default interaction method; projected capacitive panels at 1920×1080 are widely specified in tender documents for this product category. The parameters that change the choice are less about “bigger is better” and more about the installation: a desktop unit facing a seated user needs a different screen tilt from a floor-standing kiosk used by a standing borrower; a unit placed near a window may need an anti-glare or brightness option that an interior kiosk does not.
The customer should confirm: minimum resolution and touch-point requirements of the self-service interface; ambient light conditions at the installation position; whether the screen needs to be frequently cleaned or removed for service.
Industrial PC platforms are the normal base for a library kiosk. Memory and storage are usually specified in the range of 4–8 GB RAM and 128–256 GB SSD depending on the application footprint, but the correct starting point is the software vendor’s runtime requirements, not a generic “high-spec” assumption. Operating system options should be stated as actual supported versions—for example, a Windows IoT Enterprise LTSC build or a Linux distribution—rather than a blanket claim of compatibility with every OS.
The customer should confirm: the OS version and architecture the self-service application requires; any pinned driver versions; whether future software updates need headroom in CPU or storage. The hardware supplier should not write “compatible with all Windows / Android / Linux software” without a tested configuration behind it.
This is the module where procurement specifications most often collide with hardware reality. A public library may still hold a barcode-only collection, or it may be mid-migration, or it may run a hybrid collection where some items carry RFID and others remain barcode-only. Real tender documents for self-service terminals explicitly require that the barcode scanner and the RFID reader can work in the same transaction, so a hybrid configuration is not a theoretical option—it is a documented requirement in public procurement.
| Identification configuration | Hardware selection focus | Customer must provide |
|---|---|---|
| Barcode scanner | Scan window position and angle; depth of field; ability to read both paper barcodes and codes displayed on phone screens | Barcode symbology (1D/2D); whether credentials are paper, screen-based or both; typical scanning distance |
| RFID reader and antenna | Reader module and antenna layout; reading zone relative to the book placement surface; anti-collision performance across multiple items | Existing tag standard (for example ISO 15693 or ISO 18000-3 for HF); tag samples; expected number of items per transaction; whether tag programming or rewriting is required |
| Barcode + RFID hybrid | Physical layout so the two modules do not obstruct each other; interface support for concurrent operation | Whether the collection is mixed; whether barcode and RFID are used alternately within the same transaction; sample items of each type |
HF 13.56 MHz is the dominant RFID frequency in library self-service, and tender specifications commonly require support for ISO 15693 and ISO 18000-3 tags alongside barcode scanning. Some projects also introduce UHF for specific workflows, but the hardware configuration should follow the tag population actually present in the library, not a generic “multi-frequency” claim.
Do not write “supports all tags” or “zero miss-reads for multiple books.” Write that the module configuration will be confirmed against the customer’s tag samples and the software’s read requirements.
Book identification and patron identification are separate hardware functions and should be specified separately. Available modules include barcode scanning for patron cards, QR code scanning, and contactless card readers for the card technology the library actually issues—HF RFID, NFC or ISO 14443 A/B, depending on the project.
The customer should provide: card type and technology standard; a sample card; the data fields the software needs to read; whether the patron reader can share a scan window with the book scanner or requires its own cut-out. Biometric or passport-reading modules should not appear as default options unless the supplier has an actual module and a target project requires it.
An 80 mm thermal printer with auto-cutter is the common configuration for a library self-service terminal. Paper roll capacity, the paper-change procedure and the low-paper or fault signal are all hardware details that affect daily operation. The customer should confirm the expected receipt length and how often staff will need to change rolls; whether a duplicate receipt is required; and which host interface and power budget the printer uses.
Other peripherals—speaker or audio output, status indicators, additional USB ports—should be listed only if they are actually available on the platform and serve a defined purpose in the workflow.
For an integrator, the interface count and power budget are often more important than the screen size. A useful specification for a library self-service kiosk hardware project should state:
Customization is a hardware capability, and it should be described in terms that a project can verify. A useful division is appearance, structure and serviceability.
Colour, logo application, panel layout and graphic areas can be customized, but the work should start from an approved structure drawing rather than a reference image. The supplier should state the available finish range and the point at which a colour or logo change becomes a structural change rather than a surface change.
Typical adjustable items include desktop versus floor-standing format, screen tilt and mounting height, the book placement surface and its anti-slip treatment, cut-out positions for card readers, scanners and printers, service-door locks, and the base fixing method—floor anchors, weighted base or adjustable feet. For a project with a fixed counter height or a narrow installation slot, these dimensions need to be confirmed on a drawing before production.
Paper roll changes should not require tools. Module replacement should be possible through a single service door where the design allows. Cable connections inside the kiosk should be pluggable so that a printer or reader swap does not become a rewiring job. These are not marketing points; they are the hardware details that determine downtime.
Accessibility should be handled as a dimension-confirmation item, not a blanket standard claim. The supplier can confirm that screen height and reach distances will be checked against the project’s accessibility requirements, but should not write “compliant with all accessibility standards” unless the specific standard has been tested.
The following cases are drawn from public announcements by libraries, local governments and suppliers. They are useful because they show the hardware configuration that a real project ended up with, not a hypothetical specification sheet.
The library introduced the selfCheck 3000 at three locations, including the children’s department, funded in part by a USD 35,000 donation from Friends of the Library. The kiosks use RFID to identify books, allow up to six items to be placed on the scanner pad at once, and guide the borrower through library-card scanning and touchscreen prompts. A plexiglass RFID gateway at the entrance tracks items leaving the building and alerts staff to items not properly checked out. The library also planned a handheld RFID wand for shelf and collection scanning.[reference:0]
For a hardware specification, the relevant details are the multi-item RFID reading surface, the separate patron-card scan step, the touchscreen workflow and the integration of the kiosk with an entrance RFID gate rather than a standalone security system.
A USD 41,702 LSTA grant allowed the library to purchase 42,000 rectangular RFID tags and 4,000 circular tags for a collection of roughly 40,000 items, three RFID desktop pads for staff, two new self-checkout stations, and three RFID-enabled gates. Installation and assistance were provided by Envisionware.[reference:1]
This case illustrates a common sequencing pattern in US public-library projects: the tag purchase, staff pads, patron self-checkout stations and security gates are procured as one RFID infrastructure package, with the self-checkout station count derived from the number of service points rather than from a single-terminal purchase.
The library replaced an earlier self-checkout kiosk that it describes as “just a computer with a barcode scanner.” Only about 1% of transactions went through that kiosk. After converting a collection of more than 75,000 items to RFID and introducing RFID-based self-check kiosks alongside an automated materials handling system, the self-check kiosks averaged 76% of transactions.[reference:2]
The hardware lesson is not simply “RFID is better.” The earlier barcode kiosk required item-by-item scanning, which made it slower than the staff desk for many borrowers. The RFID kiosk changed the physical interaction—multiple items on a pad—and that change, combined with the AMH system on the return side, is what moved the transaction share.
Bibliotheca supplied Self-check 500 and Self-check 1000 units, RFID gates, remoteLockers and digital communication screens. The products were installed around Easter 2024. The university’s digital support services manager reported that the technology integrated into the library system without technical issues and that the equipment was dependable.[reference:3]
For a university project, the hardware mix included both smaller and larger self-check formats, which is typical when a library has multiple sites with different floor space and traffic levels.
RFID was introduced at the Life Sciences Branch Library in Kulmbach in November 2023. Self-checkout was then launched in the central library and in the NW I, NW II and GEO branch libraries in July 2025. The borrower places a library card on the RFID-marked area, then places media one by one on an illuminated glass surface; a green highlight in the on-screen list confirms the transaction, and a receipt is sent by email. An audible signal at the gate reminds borrowers who leave before the RFID label has been deactivated. The library also planned an intelligent return shelf that automatically checks media back in.[reference:4]
The Bayreuth case shows a phased, multi-branch rollout: one branch first, then the central library and three subject libraries, with the return-side hardware added as a later step. The illuminated placement surface and the visual/audible confirmation loop are hardware-adjacent design choices that affect first-time user success.
Inspire, which manages around 70 active libraries, ran a tender for self-service kiosks across 50 locations to replace outdated kiosks and RFID circulation pads. The project required a supplier able to meet procurement standards and provide reliable units across a large, distributed estate.[reference:5]
For a framework or multi-site tender, the hardware requirement shifts from a single kiosk specification to repeatable BOM control, consistent module configuration, and packaging and delivery arrangements that work across many buildings with different access conditions.
These cases are included as configuration and deployment examples. They do not imply that the hardware supplier in this article provided the equipment in every case, nor do they constitute an endorsement by the libraries named.
Hardware integration is not a one-way specification. The kiosk supplier needs a defined set of inputs from the application provider before it can confirm that a configuration will work. The table below is the working checklist for that exchange.
| Customer or integrator provides | Hardware supplier confirms or provides |
|---|---|
| Operating system version and application runtime requirements | Host configuration, available OS images and driver versions |
| How the software calls each module (USB HID, serial command set, SDK) | Interface type on the selected module and the technical documentation available within the agreed scope |
| RFID tag samples or tag specification | Test arrangement on the target reader module and feedback on read performance |
| Patron card technology and sample card | Reader module compatibility confirmation |
| Peripheral list and power draw | Port count, power headroom and internal layout feasibility |
| Installation dimensions and fixing conditions | Enclosure outline, base solution and approval drawings |
| SIP2/NCIP integration responsibility | Hardware does not implement the protocol; confirmation that the network and host environment meet the software’s runtime requirements |
The SIP2/NCIP line is the one that prevents the most common misunderstanding in a library borrow return kiosk procurement. The hardware supplier is not the party that maps borrower records, configures the ILS port or licenses the protocol client. What the hardware supplier can do is confirm that the kiosk’s operating system, network interface and peripheral environment allow the customer’s SIP2 or NCIP client software to run, and that the identification modules return data in a form that the software can consume.
The following checklist is structured so that a library, integrator or procurement officer can copy it into an RFQ or an internal approval note. Each unchecked line is a question that will otherwise return as an email during the quotation process.
A missing line in this checklist does not stop a quotation, but it changes the quotation from a fixed configuration into a range. For a project with a fixed budget or a public tender deadline, the difference matters.
Yes. This is the standard supply model for system integrators and library software vendors. The hardware scope covers the terminal, selected modules, enclosure and agreed driver or interface documentation; the self-service application and ILS integration remain with the customer or software partner.
The hardware platform can be configured to the operating system and driver conditions your software requires, but this must be confirmed against a prototype or a tested configuration. A hardware supplier should not promise that any application will run on any configuration without a validation step.
Yes, if samples or specifications are provided. Tag samples and patron card samples are tested on the target reader module, and the result is fed back as a configuration confirmation. The final module choice should be based on that test rather than on a generic compatibility claim.
The available sheet metal type and thickness, surface finish and colour range should be stated per platform. Cold-rolled steel is common for indoor kiosks; stainless steel or outdoor-rated finishes apply only where the product is actually designed for that environment. Material choice affects weight, base design and lead time, so it should be confirmed together with the installation conditions.
Quantity, kiosk format, identification module combination, operating system requirement, installation context and delivery location. With those six inputs, a supplier can quote a defined configuration; without them, the quotation can only be expressed as a range.
Send the installation context, identification module requirements, software runtime conditions and target quantity. We will respond with a hardware configuration direction and a quotation basis.
CEO | Interactive Display & Collaboration Solution Expert
I am the founder of Qtenboard, bringing over 17 years of hands-on expertise to the touch display industry. Drawing on the global management perspective gained through my EMBA studies at ShenZhen University, I lead my team in optimizing every stage of our operations—from product definition to high-efficiency supply chain management—ensuring our manufacturing capabilities remain at the forefront of the industry.
As the leader of Qtenboard, I specialize in providing tailored OEM/ODM solutions for interactive whiteboards, LCD video walls, digital signage, and industrial-grade touch terminals. Backed by our 330,000 m² modern industrial park in Shenzhen, we maintain full-lifecycle control over industrial design, precision manufacturing, and rigorous performance testing.
With nearly two decades of project experience, Qtenboard’s display solutions are now deployed in over 120 countries and regions, earned the trust of more than 15,000 enterprise customers worldwide. If you are seeking a responsive partner with a deep manufacturing foundation for your customized touch display projects, my team and I are ready to support your vision with professional excellence.