Hajj and Umrah operators run a seasonal, document-heavy, high-liability business that stock ERPNext was never shaped for. A single pilgrim record has to carry passport data, visa status, Mahram linkage, a Nusuk/Tasreeh reference, room and seat assignments, and a payment plan spread over months — and hundreds of these have to move through visa cut-offs, hotel allocation windows, and flight manifests as coordinated groups. In native ERPNext you can bend a Customer, a Sales Order, and a Payment Entry to approximate some of this, but there is no pilgrim lifecycle, no group/package structure, no visa-deadline tracking, and no bus-seat or room allocation. Operators end up managing the real work in spreadsheets alongside ERPNext, which breaks the moment a group changes size or a hotel block is reassigned.

ECOSIRE builds a proper Frappe application (ecosire_hajj_umrah) that installs on your own ERPNext bench and adds the domain natively. We model the business as first-class DocTypes — Pilgrim, Pilgrim Group, Package, Visa Application, Accommodation Allocation, Transport Allocation, and Installment Plan — each with proper naming series, links back to standard ERPNext Customer, Sales Order, and Payment Entry documents, and workflow states (Draft, Documents Pending, Visa Issued, Confirmed, Travelled). The pilgrim lifecycle and the package configurator are the core; everything else — hotels, buses, flights, money — hangs off them by Link and Table fields so a change in one place propagates correctly.

Technically, the app is wired the way a maintainable Frappe app should be. Document events in hooks.py (validate, on_submit, on_update) enforce rules such as passport-expiry-versus-travel-date, group-capacity limits, and no-double-booking of a seat or room. Server scripts and whitelisted methods (frappe.whitelist()) expose operations like bulk visa-status updates and manifest generation, callable from the Frappe REST API so your existing portal or a GDS/visa-agent integration can push and pull data. Client scripts drive the in-form UX — auto-filling Mahram details, warning on visa cut-offs, recalculating an installment schedule when a package price changes. Scheduler events run the time-based work: nightly reminders for expiring passports and unpaid installments, and daily recomputation of group fill rates. Access is governed by ERPNext role profiles and permission rules so a visa officer, an accountant, and a group leader each see only what they should.

Because every deployment is scoped to how your agency actually operates — your packages, your hotels in Makkah and Madinah, your bus operators, your visa channel, your installment terms — this is a build-to-order engagement, not a marketplace download. We start with a scoping call, agree the DocTypes and workflows in writing, then build against a staging bench on Frappe/ERPNext v15 (with v16 supported). Typical delivery is one working week from confirmed scope. You receive the installable app source, run UAT on staging, and go live with a support window and the git repository in your hands.