A build-to-order Odoo module that turns your catalog into a full lending system: barcode check-in/out, due dates and renewals, overdue fines, reservation waitlists, and a member self-service portal. ECOSIRE scopes, builds, installs, and supports it on Odoo 17, 18, or 19. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $299.00 USD; request a quote for a scoped proposal.

A build-to-order Odoo module that turns your catalog into a full lending system: barcode check-in/out, due dates and renewals, overdue fines, reservation waitlists, and a member self-service portal. ECOSIRE scopes, builds, installs, and supports it on Odoo 17, 18, or 19.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
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.
`library.title` / `library.copy` split so multiple physical copies share one bibliographic record with per-copy barcode, condition, and shelf location
ISBN and accession-number catalog with author, category, publisher, and cover image fields, searchable from a fast circulation desk view
Barcode-driven check-out and check-in that scans the accession number, resolves the copy, and writes the `library.loan` in a single action
`@api.depends` computed loan state (on-loan / overdue / returned) and live days-overdue, no nightly recompute required
Configurable loan periods and renewal policy with a renewal cap and a block on renewing reserved or overdue items
Per-day overdue fine accrual on a `library.fine` model against a configurable daily rate, grace period, and maximum-fine ceiling
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 2 to 4 weeks 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.
Runs a physical or academic library on Odoo and needs a real circulation system: titles versus copies, due dates, fines, and reservations, rather than a rental order bent to fit. Wants staff working from a barcode desk, not spreadsheets.
Lends laptops, tools, AV kit, or lab equipment across teams and wants one Odoo-native system to track who has what, when it's due, and what's overdue, with a self-service portal so employees can reserve gear themselves.
Owns an existing Odoo deployment and needs a maintainable lending module that respects Odoo conventions: proper models, `ir.model.access.csv` and record rules, QWeb reports, and clean upgrades across 17/18/19, with source and git handover.
Checks items in and out all day and needs a fast, forgiving scan-driven workflow that enforces member limits and outstanding fines automatically, plus printable receipts and overdue notices.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 Library & Asset Lending Management for Odoo 模块 ZIP。
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中(或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传)。
激活开发者模式,打开应用程序,单击更新应用程序列表,搜索 Library & Asset Lending Management for Odoo,然后按安装。
打开新菜单,粘贴您的 ECOSIRE 许可证密钥,连接任何外部凭据(Shopify、Amazon、Stripe 等),然后保存。
运行内置连接测试,同步前 10 条记录,并安排定期 cron。如果出现任何问题,请联系支持人员。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Fit to your circulation rules | Built to your exact loan periods, fines, and member policies | Fully bespoke but you specify and manage every detail | Fixed feature set; you adapt to its assumptions | |
| Title vs copy modeling | Proper `library.title` / `library.copy` split with per-copy barcode | Possible, depends on your developer's design | Varies; many treat each copy as a flat product | |
| Overdue fines & reminders | Accruing `library.fine` + `ir.cron` reminders, configurable | Build it yourself, ongoing maintenance is yours | Often present but on the module's fixed schedule | |
| Reservations & waitlist | Queue with auto-promotion of next member on return | Buildable with your own effort and testing | Sometimes; behavior not tailored to your queue rules | |
| Member portal & barcode desk | Self-service portal + scan-driven check-in/out delivered | Depends on scope you fund | Portal quality and barcode UX vary widely | |
| Delivery model | 2-4 weeks from confirmed scope, installed & UAT'd | Timeline depends on hiring and managing a developer | Instant download but generic; you integrate it | |
| Source & ownership | Full source + git repo handover, you own it | You own it if contracted that way | Licensed module; limited to no source control | |
| Support & upgrades | Post-go-live window + optional 17-to-19 upgrade path | Only if you retain the developer | Vendor support quality and upgrade cadence vary |
No. This is a build-to-order module. ECOSIRE builds it around your specific catalog, loan policies, fine schedule, and member structure, then installs and supports it. There is no instant download; you get source code tailored to your rules and Odoo version.
Typical delivery is 2 to 4 weeks from confirmed scope. After a short scoping call we lock the data model and workflow, build on your target Odoo version, run UAT on staging, then deploy. Timeline depends on data-migration volume and how many custom policies (branches, member categories, fine rules) you need.
Every build includes a post-go-live support window for defect fixes and configuration tweaks. Because you receive the full source and git repository, you or any Odoo partner can maintain it afterward. We also offer ongoing support and version-upgrade engagements (for example moving from Odoo 17 to 18 or 19) as a separate arrangement.
We build for Odoo 17.0, 18.0, or 19.0, on either Community or Enterprise. The core lending model (titles, copies, loans, fines, reservations, portal) runs on Community; where relevant we note any Enterprise-only integration points during scoping so nothing depends on a feature you don't license.
Yes. The circulation desk is barcode-driven: scan the accession number to check items in or out. Members get an Odoo portal to browse the catalog, place reservations, see due dates, and renew online. The same data is exposed over XML-RPC/JSON-RPC for kiosks, RFID gates, or self-checkout hardware.
Yes. The copy/loan/reservation model is generic. Many teams use it to lend laptops, tools, AV gear, or lab equipment. Each asset is a copy with its own barcode, condition, and location, with the same due-date, reminder, reservation, and (optional) fine logic applied.
Migration is part of the engagement. We map your existing catalog and member records into the `library.title` / `library.copy` and member model and validate the import on a staging database during UAT, so you go live with your real data, not an empty system.
A build-to-order Odoo module that turns your catalog into a full lending system: barcode check-in/out, due dates and renewals, overdue fines, reservation waitlists, and a member self-service portal. ECOSIRE scopes, builds, installs, and supports it on Odoo 17, 18, or 19.