Visa and immigration agencies live or die by the state of every case file: which applicant is missing a police clearance, whose passport expires next month, which application has a biometrics appointment on Thursday, and which government fee still needs collecting before submission. Run this in Odoo core and you quickly hit the wall — there is no native "case" object with a visa-specific status pipeline, no per-document checklist that blocks submission until everything is collected, and no way to separate a pass-through government fee from your own service fee on the same invoice. Teams end up bolting the whole operation onto spreadsheets, a CRM pipeline that was never designed for compliance deadlines, and a shared drive of scanned documents nobody trusts.

We build a dedicated case-management module on top of Odoo (17.0, 18.0 or 19.0) that treats each application as a first-class record. The core is a custom models.Model (for example visa.case) with a proper state machine — a Selection field driving stages like Enquiry, Documents Pending, Ready to Submit, Submitted, Decision, Delivered — enforced through record state transitions and automated actions rather than free-text notes. Each case links to the applicant (res.partner), the chosen service from a configurable catalog (visa type, attestation, ticketing, renewal), and a One2many set of required documents. Computed fields with @api.depends roll up checklist completeness, days-to-deadline and outstanding government fees so a manager sees the true state of the desk at a glance, not a stale spreadsheet.

Technically, the build ships as a clean Odoo addon: a proper __manifest__.py declaring dependencies (typically base, mail, contacts and account), ORM models with the compute/constraint logic, backend views in XML (list, form, kanban by pipeline stage, calendar for appointments and deadlines) plus OWL widgets where the standard views fall short, and QWeb PDF reports for case summaries, document acknowledgements and fee receipts. Security is done correctly — ir.model.access.csv for group-level CRUD plus ir.rule record rules so a branch or an individual agent only sees their own caseload, which matters when you handle passports and personal data. Deadline and renewal reminders run on scheduled/automated actions that post to the Odoo chatter and notify the assigned agent. Per-case invoicing integrates with Odoo Accounting so your service fee and the government-fee passthrough post as distinct invoice lines, and everything is reachable over the XML-RPC/JSON-RPC API if you need to feed a customer portal or an external booking site.

Because it is genuinely build-to-order, nothing is generic. We start from your actual services, document lists per visa type, fee structures and the exact pipeline your agents already use, and we tell you up front where Enterprise features (like advanced accounting analytic distribution or Studio-adjacent automation) change the design versus Community. After a scoping call we confirm the model, fields, pipeline and reports in writing, build against your Odoo version, and hand over installable source plus a git repository — typical delivery is one working week from confirmed scope, not an instant download.