IT Warranty & Support Contract Manager

This is a build-to-order module, so it is built specifically for your Odoo instance rather than downloaded. Typical delivery is 2 to 4 weeks from confirmed scope. The exact timeline depends on how many vendors and contract types you track, whether multi-company coverage is required, and how deep the Maintenance and procurement integrations go — we confirm dates in your fixed quote after the scoping call.

Pricing starts from $199 as an indicative from-price for a single-company base scope. After a short scoping call we confirm your asset model, vendor list, reminder policy and any integrations, then give you a fixed quote before any code is written. Drivers that increase scope include multi-company coverage, migrating a large backlog of existing contracts, deeper Odoo Maintenance or procurement integration, and localized renewal-quotation formats.

Every engagement includes a post-go-live support window for bug fixes and questions after deployment, plus full git repository handover so your team owns the source. You get the technical docs, a user guide and a training session. Beyond the included window we offer ongoing support and version-upgrade retainers — for example when you move from Odoo 17 to 18 or 19 — which we can quote alongside the build.

No — it builds on it. The module is designed to sit on top of your `it_asset_management_cmdb` asset register and link contracts to the assets you already track, rather than duplicating them. Coverage status, days-to-expiry and total-cost-of-ownership roll up onto your existing asset records. If your CMDB uses a custom model, we map to it during scoping.

It works on both. The core contract register, reminder engine, coverage-gap reporting, renewal quotations via Sales, and the API are all built on standard Odoo framework features that exist in Community. Where you run Enterprise we can use Enterprise-only widgets and the Maintenance bridge; where you run Community we build equivalent Community-safe views so you get the same functional outcome.

A scheduled server action (`ir.cron`) runs daily and evaluates each contract's remaining days to expiry. At the 90, 30 and 7-day thresholds it creates a `mail.activity` assigned to the responsible owner and sends a QWeb-templated email. The lead-time thresholds and the responsible user are configurable, so you can align reminders with your renewal and budgeting cadence rather than a fixed rule.

Yes. Every contract and its computed coverage state, days-to-expiry and linked assets are exposed over Odoo's standard XML-RPC and JSON-RPC API. A procurement portal, BI dashboard or external CMDB can query live warranty and AMC status through authenticated API calls without any direct SQL access, respecting the same record rules that govern in-app visibility.