Libraries and asset-lending teams usually start by bending Odoo Inventory or Rental into shape: a physical book becomes a product.product, a loan becomes a stock move or a rental order, and members become res.partner records. It works until it doesn't. Odoo core has no concept of a "copy" versus a "title", no ISBN or accession-number catalog, no due-date renewal policy, no per-day overdue fine accrual, and no reservation waitlist that automatically promotes the next member when a copy comes back. Circulation ends up in spreadsheets, reminders go out by hand, and nobody can say which of your five copies of a title is overdue and with whom.

This module is built specifically for that circulation workflow. We model a library.title (the bibliographic record: ISBN, author, category, cover) with many library.copy records beneath it, each carrying its own barcode/accession number, condition, and shelf location. A library.loan links a copy to a member with checkout_date, due_date, and return_date, while compute fields driven by @api.depends derive loan state (on-loan, overdue, returned) and days-overdue live. Fines accrue on a library.fine model computed against your configured daily rate and grace period, so the outstanding amount is always correct without a nightly rebuild. Reservations sit in a library.reservation queue with a sequence position; when a copy checks in, an automated action (base.automation) promotes the next member and notifies them.

The librarian works from a fast circulation desk view. A barcode-driven check-out and check-in flow scans the accession number, resolves the copy, validates member limits and outstanding fines, and writes the loan in one action, so a busy front desk is not clicking through forms. Access is locked down with ir.model.access.csv plus record rules, so members see only their own loans, librarians manage circulation, and managers configure policy. Overdue reminders and reservation-ready notices are ir.cron scheduled jobs that render QWeb email templates, and receipts, overdue notices, and inventory audit sheets are QWeb PDF reports. A member portal (built on Odoo's website/portal layer) lets patrons browse the catalog, place reservations, see due dates, and renew online, and everything is reachable over the XML-RPC/JSON-RPC API for kiosks, RFID gates, or self-checkout hardware.

Because this is build-to-order, ECOSIRE builds it around your exact rules rather than a generic one-size template: your loan periods, fine schedule, member categories, reservation limits, and branch structure. After a short scoping call we confirm the data model and workflow, build on your target Odoo version (17.0, 18.0, or 19.0, Community or Enterprise), and deliver installable source with tests. Typical delivery is one working week from confirmed scope. We install it, migrate your existing catalog and member data, run UAT on a staging database, and support the go-live. You own the source and the git repository at handover.