Les détails du produit sont affichés en anglais. Traductions à venir.
Faits en bref
- Prix
- $399.00 USD
- Versions Odoo
- 17, 18, 19
- Temps d'installation
- 30 minutes
- Licence
- Perpétuel unique
- Langues
- 11 langues
Achat unique
Travel Visa & Immigration Services
A build-to-order Odoo case-management ERP for visa consultancies, immigration agents and document-processing firms. ECOSIRE builds, installs and supports it around your applicant pipeline, document checklists, deadline reminders and per-case invoicing.
$399.00USD
Aucun paiement maintenant. Ceci envoie une demande de devis à notre équipe — nous vous recontacterons par e-mail avec les tarifs et les prochaines étapes.
Fonctionnalités clés
Custom `visa.case` model with a Selection-driven state machine (Enquiry → Documents Pending → Ready to Submit → Submitted → Decision → Delivered) enforced via automated actions, not free-text status
Per-service document checklist as a One2many of required-document lines, with a `@api.depends` computed completeness flag that blocks the Ready-to-Submit transition until every mandatory item is collected
Configurable service catalog model for visa types, attestation, ticketing and renewals — each with default document set, standard service fee and expected government-fee lines
Kanban pipeline view grouped by stage plus a calendar view surfacing biometrics appointments, submission dates and deadlines
Scheduled/automated actions computing days-to-deadline and firing renewal and expiry reminders to the chatter and the assigned agent
Computed passport/visa expiry tracking with configurable lead-time reminders (e.g. 90/60/30 days) per applicant
Per-case invoicing into Odoo Accounting with your service fee and the government-fee passthrough posted as separate invoice lines for clean margin reporting
`ir.model.access.csv` group permissions plus `ir.rule` record rules so agents/branches see only their own caseload — appropriate for handling passport and personal data
QWeb PDF reports: case summary sheet, document-received acknowledgement and fee receipt, branded to your firm
Applicant records built on `res.partner` with family-group linking (dependants under a primary applicant) and document attachment history
XML-RPC/JSON-RPC endpoints so an external website, portal or booking form can create cases and read status without direct DB access
Document versioning via Odoo attachments/chatter so re-submitted or corrected documents keep an auditable history against the case
Assignment and workload fields (owner agent, branch, priority) with filters and grouped list views for desk-level and manager-level dashboards
Built and tested against your target Odoo edition and version (17.0 / 18.0 / 19.0), with Community-vs-Enterprise trade-offs called out before build
À propos de ce produit
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.
Pourquoi choisir Travel Visa & Immigration Services
Custom `visa.case` model with a Selection-driven state machine (Enquiry → Documents Pending → Ready to Submit → Submitted → Decision → Delivered) enforced via automated actions, not free-text status
Per-service document checklist as a One2many of required-document lines, with a `@api.depends` computed completeness flag that blocks the Ready-to-Submit transition until every mandatory item is collected
Configurable service catalog model for visa types, attestation, ticketing and renewals — each with default document set, standard service fee and expected government-fee lines
Kanban pipeline view grouped by stage plus a calendar view surfacing biometrics appointments, submission dates and deadlines
Scheduled/automated actions computing days-to-deadline and firing renewal and expiry reminders to the chatter and the assigned agent
Computed passport/visa expiry tracking with configurable lead-time reminders (e.g. 90/60/30 days) per applicant
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 2-4 weeks from confirmed scope, not an instant download.
Ce que vous obtenez
- Installable Odoo addon source code, built and tested against your chosen version (17.0, 18.0 or 19.0) and edition (Community or Enterprise)
- Installation and configuration on your server or Odoo.sh, including service catalog, document checklists and pipeline stages set up to your workflow
- Technical documentation: model/field reference, security groups and record rules, automated-action schedule and API endpoints
- End-user guide plus a live training session for agents and managers
- UAT on a staging database with a documented rollback plan before touching production
- Post-go-live support window for defect fixes and configuration adjustments
- Git repository handover with full commit history and branching for your future maintenance
Pour qui c'est
Visa consultancy owner
Runs a multi-agent desk processing student, work and visit visas. Needs a single system where every case, document and deadline is visible, so nothing slips and the firm can prove diligence if a client disputes a rejection.
Immigration case agent
Handles dozens of active applications at once. Needs a checklist that flags exactly what each applicant is still missing, automatic deadline reminders, and one-click generation of the document acknowledgement and fee receipt.
Document-attestation / PRO firm
Processes attestation, translation and government-liaison tasks with heavy government-fee passthrough. Needs service and government fees kept distinct on invoices and clean reporting on true service margin per case.
Operations / finance manager
Owns cash and compliance across branches. Needs record-rule isolation per branch, per-case invoicing into Odoo Accounting, and a manager view of pipeline health, outstanding fees and upcoming renewals.
Aperçu de l'installation
Télécharger depuis ECOSIRE
Achetez la licence sur ecosire.com et téléchargez le module ZIP Travel Visa & Immigration Services depuis le tableau de bord de votre compte.
Télécharger sur Odoo
Extrayez le ZIP dans votre dossier de modules complémentaires personnalisés Odoo sur le serveur (ou téléchargez-le via Applications > Installer à partir du fichier sur Odoo.sh / runbot).
Installer le module
Activez le mode développeur, ouvrez les applications, cliquez sur Mettre à jour la liste des applications, recherchez Travel Visa & Immigration Services et appuyez sur Installer.
Configurer les paramètres
Ouvrez le nouveau menu, collez votre clé de licence ECOSIRE, connectez toutes les informations d'identification externes (Shopify, Amazon, Stripe, etc.) et enregistrez.
Vérifier et mettre en ligne
Exécutez le test de connexion intégré, synchronisez vos 10 premiers enregistrements et planifiez le cron récurrent. Contactez le support si quelque chose échoue.
Comment Travel Visa & Immigration Services se compare
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Odoo natif |
|---|---|---|---|---|
| Visa case model & pipeline | Purpose-built `visa.case` model with a visa-specific state machine and stage kanban | Possible, but you design and debug the whole model from zero | Generic project/CRM stages repurposed; rarely a true case object | |
| Document checklist enforcement | Per-service required-document lines that block submission until complete | Buildable if you specify and test the compute/constraint logic | Usually a static attachment list with no completeness gating | |
| Deadline & renewal reminders | Automated actions computing days-to-deadline, notifying the assigned agent | Requires you to write and schedule the cron/automation yourself | Basic activity reminders, rarely visa-expiry aware | |
| Government-fee passthrough | Service fee and government fee as separate invoice lines for clean margin | Achievable with accounting configuration you design and validate | Typically one flat fee line; passthrough not separated | |
| Data isolation (branch/agent) | Record rules scope caseloads to owning agent or branch by default | You must define and test every `ir.rule` correctly | Often global visibility or coarse group access only | |
| Reports & receipts | Branded QWeb case summary, document acknowledgement and fee receipt | Design and build each QWeb template yourself | Generic templates, limited visa-specific layouts | |
| Fit to your workflow | Built from your actual services, documents and pipeline during scoping | Fully bespoke but on your time and QA budget | You adapt your process to the module's assumptions | |
| Ownership & support | Source + git handover, post-go-live support window, version-aware builds | Depends entirely on who you hired and their handover | Vendor-locked; support tied to their release cycle |
Foire aux questions sur Travel Visa & Immigration Services
+How long does delivery take?
This is a build-to-order module, not an instant download. Typical delivery is 2-4 weeks from confirmed scope — the timeline is set once we agree your case pipeline, document checklists, service catalog and reports in writing during scoping. Larger multi-branch or portal-integrated builds may run longer, and we tell you the estimate before you commit.
+Which Odoo versions and editions do you support?
We build against Odoo 17.0, 18.0 and 19.0, on Community or Enterprise. We confirm your exact version and edition during scoping and flag any place where the design differs — for example where Enterprise accounting or automation features change the approach versus Community.
+How do you keep one agency's or branch's cases private from another?
Security is enforced at the ORM layer with `ir.model.access.csv` for group-level CRUD and `ir.rule` record rules that scope visibility to the owning agent or branch. Because you are handling passports and personal data, this isolation is part of the core build, not an add-on.
+Can we separate government fees from our own service fees on invoices?
Yes. Per-case invoicing posts into Odoo Accounting with your service fee and the government-fee passthrough as distinct invoice lines. That keeps client invoices transparent and lets finance report true service margin without the passthrough distorting revenue.
+Can it connect to our website or a client portal?
Yes. The module is reachable over Odoo's XML-RPC/JSON-RPC API, so an external website form, booking page or customer portal can create cases and read status. We scope the exact endpoints and payloads as part of the build if integration is in your requirements.
+What happens after go-live — do we get updates and support?
Every build includes a post-go-live support window for defect fixes and configuration adjustments, plus full git repository handover so your team (or ours, on a maintenance arrangement) can maintain and extend it. Version upgrades — for example moving a 17.0 build to 18.0 or 19.0 — are quoted separately since they involve real migration work.
+Do we own the code?
Yes. You receive the installable source and the git repository with full history at handover, so you are never locked in to us for future changes.
Modules associés
Demander un devis
Travel Visa & Immigration Services
A build-to-order Odoo case-management ERP for visa consultancies, immigration agents and document-processing firms. ECOSIRE builds, installs and supports it around your applicant pipeline, document checklists, deadline reminders and per-case invoicing.
- Custom `visa.case` model with a Selection-driven state machine (Enquiry → Documents Pending → Ready to Submit → Submitted → Decision → Delivered) enforced via automated actions, not free-text status
- Per-service document checklist as a One2many of required-document lines, with a `@api.depends` computed completeness flag that blocks the Ready-to-Submit transition until every mandatory item is collected
- Configurable service catalog model for visa types, attestation, ticketing and renewals — each with default document set, standard service fee and expected government-fee lines
- Kanban pipeline view grouped by stage plus a calendar view surfacing biometrics appointments, submission dates and deadlines