Most teams running Odoo track their IT hardware in spreadsheets, sticky notes, and someone's inbox. Who has which laptop? When does that server's warranty expire? Which monitors are in the store room versus assigned? When a workstation fails, the support request lands in a chat message and gets lost. Odoo core gives you product.template and stock.lot for goods you sell and hr.employee for people, but it has no native concept of an internal IT asset with an owner, a warranty clock, a maintenance history, and a support queue tied to it. The Maintenance app covers factory equipment, not laptops-and-licenses IT operations, and it does not model warranty windows, RMA cycles, or a helpdesk-style ticket linked to a specific device. That gap is exactly where teams lose visibility and money.

We build a dedicated it.asset model that represents each piece of hardware — laptop, desktop, server, network switch, phone, peripheral — with fields for serial number, asset tag, purchase date, vendor, cost, warranty start/end, and current state (in_stock, assigned, in_repair, retired, disposed). Assets link to hr.employee (current holder), res.partner (vendor/supplier), and a location, so you can answer "what does this person hold" and "what is at this site" instantly. A compute field with @api.depends('warranty_end') derives days-to-expiry and a status flag, and a scheduled ir.cron automated action flags assets whose warranty lapses within a configurable window and notifies the IT owner. On top of the asset registry we build an internal support ticket model (it.support.ticket) with stages, priority, SLA target, assignment, and a threaded log via mail.thread and mail.activity.mixin, so every request is chatter-tracked with follow-ups — and each ticket can reference the affected it.asset, building a real maintenance history per device.

Technically the module ships as a proper Odoo addon: a clean __manifest__.py declaring dependencies (typically base, hr, mail, and optionally stock), models under models/ using models.Model with typed fields, access control in ir.model.access.csv plus ir.rule record rules so, for example, employees see only their own assigned assets while IT managers see everything. The UI is delivered as XML views — list, form, kanban by state, and a search view with useful filters and group-bys (by owner, by location, by warranty status) — with OWL components only where an interactive widget genuinely helps. We add QWeb PDF reports (asset register, per-employee hand-over sheet, warranty-expiry report) and expose everything over the standard XML-RPC/JSON-RPC API so procurement or an external CMDB can sync. The build targets your chosen Odoo version and edition; we note Community vs Enterprise differences up front (for instance where Enterprise studio-style fields or the mobile app change behaviour) and write the code to run cleanly on Odoo 17.0, 18.0, or 19.0.

Because this is build-to-order, nothing is downloaded and installed blindly. We start with a short scoping call to confirm your asset types, custom fields, approval and assignment workflow, ticket stages, and reporting needs, then produce a fixed quote. We develop on a staging copy of your database, run UAT with your team, and deploy to production with a rollback plan and a git repository handover. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); multi-company/multi-site rollouts, deeper localization, integration with an existing procurement or CMDB system, and migrating large volumes of historical asset data from spreadsheets increase the quoted scope.