A made-to-order Odoo library management module for schools, colleges and universities — catalog, member cards, barcode circulation, overdue fines and reservations, built and installed by ECOSIRE. Not an off-the-shelf download; we build it to your circulation rules. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $299.00 USD; request a quote for a scoped proposal.

A made-to-order Odoo library management module for schools, colleges and universities — catalog, member cards, barcode circulation, overdue fines and reservations, built and installed by ECOSIRE. Not an off-the-shelf download; we build it to your circulation rules.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
Institutional libraries run on rules that generic tools ignore: a title can have twelve physical copies each with its own accession number, students and staff carry different borrowing limits, fines accrue per overdue day and must reconcile against the fee ledger, and a reserved book has to jump the hold queue the moment it comes back. Odoo core gives you stock for physical items, account for money and mail for reminders — but out of the box it has no concept of a loan, a due date, an accession number, a member card, or a reservation. Librarians end up bolting circulation onto spreadsheets and manual registers while the real transactions live nowhere the institution can report on.
`library.book` catalog model with ISBN, author, publisher, category and rack/shelf location, plus category tagging for OPAC filtering
`library.copy` child records giving each physical volume a unique accession number and its own barcode/QR label
`library.member` records linked to `res.partner` with per-member-type borrowing limits and loan periods (student, staff, faculty)
Barcode/QR-scan issue and return via an OWL scan panel, enforcing due-date rules at the point of circulation
`@api.depends`-computed overdue-day fields with an `ir.cron` automated action that posts fines to `account` (Fees/Accounting), never off-book
Reservation/hold queue (`library.reservation`) with position tracking and a renewal workflow that respects hold priority
ECOSIRE builds a dedicated education-library-management module on top of base, mail, account and stock. We model the catalog as a library.book record (ISBN, author, publisher, category, rack/shelf location) with child library.copy records — one per physical volume, each carrying a unique accession number and its own barcode/QR label. A library.member model links to res.partner and enforces borrowing limits and loan periods that differ by member type (student vs staff vs faculty). Circulation runs through a library.loan model where issue and return are driven by barcode/QR scan against due-date rules; an @api.depends-computed field calculates overdue days, and a scheduled automated action (Odoo ir.cron) posts the fine to account via the Fees/Accounting flow so nothing is collected off-book. Reservations use a library.reservation hold queue with renewal logic, and lost/damaged copies trigger replacement charges through the same accounting path.
Everything is real Odoo, not a black box. Access is governed by ir.model.access.csv plus record rules so a branch librarian sees only their library's circulation while an administrator sees all of it; multi-company libraries are scoped with company_id record rules. The librarian works in list/kanban/form views with an OWL-based scan panel for fast issue/return, QWeb reports render fine notices and circulation slips, and due-date and overdue reminders go out as templated emails/SMS through mail. A website-facing OPAC-style catalog search lets students find and reserve titles from the portal, and a library dashboard surfaces circulation, overdue and inventory KPIs. Reading-history-per-member and popular-titles reporting come from the loan history, and the whole module is reachable over Odoo's XML-RPC/JSON-RPC API if you need to feed a student-information system or gate access. It targets Odoo 17.0, 18.0 and 19.0 on both Community and Enterprise (SMS and some website widgets vary by edition, which we confirm during scoping).
Because this is build-to-order, nothing ships until we agree the scope. After a short scoping call we confirm your member types, loan periods, fine schedule and any integrations, then build, test on a staging copy of your database, and hand over installable source. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $299 (indicative, single-company base scope); multi-branch/multi-company libraries, deeper accounting/localization of fines, student-information-system integration, and bulk migration of an existing catalog and member records increase the quoted scope. You get a fixed quote after the scoping call — never a surprise invoice.
Runs daily circulation for a single-campus library and needs fast barcode issue/return, automatic overdue fines and reminder emails without maintaining a manual register or spreadsheet.
Manages multiple branches and thousands of members, needs `company_id`-scoped access control, SIS integration over the JSON-RPC API, and consolidated circulation and inventory KPIs.
Owns the Odoo deployment and wants library circulation living in the same database as fees and accounting, with clean models, security rules and a git-handed-over codebase they can maintain.
Cares about collection health and usage — popular-titles reports, reading history, overdue trends and reservation demand — to justify acquisitions and measure engagement.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Education Library Management 模块 ZIP。
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中(或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传)。
激活开发者模式,打开应用程序,单击更新应用程序列表,搜索 Education Library Management,然后按安装。
打开新菜单,粘贴您的 ECOSIRE 许可证密钥,连接任何外部凭据(Shopify、Amazon、Stripe 等),然后保存。
运行内置连接测试,同步前 10 条记录,并安排定期 cron。如果出现任何问题,请联系支持人员。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Circulation model (loans, due dates, accession numbers) | Purpose-built `library.loan`, `library.copy` and accession numbering tailored to your rules | Possible but you specify and pay for every model from scratch | Generic loan model that may not match your member types or fine rules | |
| Overdue fines into accounting | Cron-computed fines posted to `account` via Fees/Accounting, on-book | Whatever you commission; integration effort is on you | Often a standalone fine field, not always reconciled to accounting | |
| Barcode / QR circulation | OWL scan panel for fast issue/return with due-date enforcement | Buildable but adds significant scope | Usually supported, UX and speed vary | |
| Reservations and renewals | Hold queue with position tracking and renewal logic respecting priority | Requires you to design the queue behavior | Basic reservations, renewal handling varies | |
| OPAC / portal search and reserve | Website catalog search and self-service reservation, configured for you | Extra build effort on top of the core module | Sometimes offered, sometimes an add-on | |
| Fit and changeability | Built to your scope; git handover so your team can maintain it | Fully custom but you own all specification risk and cost | Fixed feature set; changes mean overrides or forking | |
| Delivery and support | 2–4 weeks from confirmed scope, UAT on staging, post-go-live window | Depends entirely on your chosen developer and contract | Instant install but self-service; support depends on vendor | |
| Multi-branch access control | `company_id` record rules scope circulation per library | Must be designed and tested by whoever builds it | Multi-company support inconsistent across apps |
No. This is a build-to-order module. ECOSIRE builds it to your specific circulation rules — member types, loan periods, fine schedule and integrations — then installs and supports it. There is no instant download; you receive installable source once your version is built and tested.
Typical delivery is 2–4 weeks from confirmed scope. After the scoping call we agree the exact feature set and data model, then build, test on a staging copy of your database, and hand over. Larger multi-branch or migration-heavy projects can run longer, and we tell you that up front in the quote.
Pricing starts from $299 (indicative, single-company base scope). We hold a short scoping call to confirm your requirements, then give you a fixed written quote — no surprise invoicing. Drivers that increase scope include multi-company/multi-branch libraries, student-information-system integration, deeper fine/accounting localization, and bulk migration of an existing catalog and member list.
Every build includes a post-go-live support window for defect fixes and questions, and you receive the full git repository so your team can maintain it. We can also quote an ongoing support and version-upgrade retainer if you want us to carry it forward across Odoo releases.
We build for Odoo 17.0, 18.0 and 19.0 on both Community and Enterprise. Some capabilities — SMS reminders and certain website/portal widgets — behave differently between editions; we confirm exactly what your edition supports during scoping so there are no surprises.
Yes. The module includes an OPAC-style catalog search on the website/portal where students and staff can find titles and place reservations, which then enter the hold queue. Portal access and self-service reservation depend on your website configuration, which we set up as part of installation.
Yes. Overdue fines, lost-book and damage replacement charges are posted through Odoo `account` via the Fees/Accounting flow, so every charge is on-book and reconcilable rather than tracked in a separate register. The exact journals and fee products are configured to match your chart of accounts.
A made-to-order Odoo library management module for schools, colleges and universities — catalog, member cards, barcode circulation, overdue fines and reservations, built and installed by ECOSIRE. Not an off-the-shelf download; we build it to your circulation rules.