Ziyarat operations software for pilgrimage operators
Run Ziyarat groups to Karbala, Najaf, Kadhimiya, Samarra, Mashhad and Qom. A season arrives in days, across two visa systems. Travix Ziyarat builds the package, holds a named roster of zaireen, tracks Iraq and Iran visas for each person, groups them into departures, prints vouchers, and posts the sale to your accounts — one line per part, each with its own supplier and margin.
Accounting ends at the invoice. Operations start there.
Travix Ziyarat is the operations layer for the Atabat in Iraq — Najaf, Karbala, Kadhimiya and Samarra — and for the Mashhad and Qom legs many groups add. Group organizers answer for who they take and who comes home, so it keeps a named record of every pilgrim, every visa and every departure list. It builds the package an agent actually quotes from, follows each person through each country’s visa process, and turns sold bookings into departure groups and printable vouchers. It posts nothing to your general ledger itself: it raises the invoice Travix Finance posts, so one set of numbers stays true.
The money
Travix Finance
Invoices and receipts
Customer and vendor ledgers
Double-entry GL, P&L
Refunds, commission, tax
The movement
Travix Ziyarat
Packages and per-component pricing
Iraq, Iran and Syria visa tracking
Pilgrim rosters and passports
Departure groups and passenger manifests
Operational vouchers (ZRV), printable
Per-component vendors and margin
What Travix Ziyarat does
Eleven capabilities, all shipping today, and free on every plan.
Packages that price themselves
A package is a list of components — nights, meals, transfers, staff, visa fees — each with a rate, a quantity and a vendor. Quote for twelve pilgrims and Travix expands the whole thing line by line. The price is the sum of its parts, so nothing is apportioned and no rounding drift is possible.
Per-pilgrim build-up of rate x quantity, expanded at quote time
Sell rate and cost rate on the same line, so margin is visible before you sell
A currency per package, with the exchange rate captured on the sale
Change a rate in your masters and every future quote uses it
Re-quote at a different pax count without rebuilding the package
Two visa regimes, tracked separately
One row per pilgrim per country, not one visa field per pilgrim. Iraq and Iran progress independently, a Damascus leg is a third row rather than a migration, and no pilgrim is ever "half approved".
Iraq, Iran and Syria tracked as separate rows on the same pilgrim
Visa company, number, applied, issue and expiry dates per country
Pending, approved, rejected, expired, cancelled — or not required, for exempt nationalities
Rows derived from the package’s own destinations, so nobody chases a visa the trip does not need
Documents attached to the visa row they belong to
A named roster on every booking
The invoice says twelve pilgrims. The roster says which twelve. Each is a real pilgrim record keyed on passport, shared with the rest of Travix, and carrying every trip they have taken with you.
Pilgrims attached to the invoice, not retyped onto it
Passport-keyed records reused across trips and across products
Passports and documents held against the pilgrim, not the booking
A status per pilgrim per trip
One pilgrim cannot be added to the same booking twice
Departure groups, not a spreadsheet roster
Once the booking is sold, put the pilgrims into a named departure — a date window, a capacity, and the cities on the itinerary. Assign by Ziyarat invoice; the sell-time occupancy rides along for the hotel work that comes next.
Optional season and package template on each departure
Assign a whole booking (or selected operations) into a group
Capacity enforced on the server — overfill is a conflict, not a silent overflow
Printable and CSV passenger manifest with agency letterhead
Links back to each pilgrim’s booking console
Operational vouchers without a shirka
A Ziyarat voucher is the itinerary document your ground team carries — flights, stays and ground segments against Ziyarat destinations, numbered ZRV-YYYY-######. It never posts to the ledger; Travix Finance already owns the sale.
Draft → approved → in progress → completed or cancelled, audited every step
Prefill party and roster from a sold Ziyarat invoice
Searchable invoice picker — reference number or customer name
Print view with your agency letterhead, not a third-party brand
Approve and cancel gated separately from create and edit
Your cities and the parts every trip is made of
Start from ready cities in Iraq and Iran and the parts a Ziyarat trip is built from, then change them to match how you really work.
Najaf, Karbala, Kadhimiya, Samarra, Kufa and Balad, plus Mashhad, Qom, Tehran and Nishapur
Add your own stops, each tied to a country
Fourteen ready parts, from hotel and food to Moukeb contribution and Arbaeen walk logistics
Seasons by name and year, so Arbaeen 2026 and Arbaeen 2027 stay apart
Switch things off instead of deleting them, so old trips stay intact
Bill in one currency, pay in another
The customer price and the supplier cost each carry their own currency and their own rate, so an Iraqi hotel paid in dinar and a customer billed in dollars both come out right.
A currency and a rate on each side of every line
Rates taken at the invoice date
A foreign amount with no rate is refused, never posted at face value
Converted to your base currency before it reaches the books
Refund one part, not the whole trip
Because every part is its own line, a refund can give back only the visa or only the hotel. The rest of the booking stays as it was.
Choose the part to refund
Other parts and their suppliers are untouched
Uses the same refund steps as any travel bill
Bills your customers can read
A Ziyarat bill prints as the package and its pilgrims, not as your internal cost build-up. Your saved terms print at the bottom.
The package, the names and the total
No internal costs or margins on the customer copy
Saved notes for terms and reminders on every bill
Your agency letterhead
Who can sell, edit and approve
Permissions are separate for packages, selling, pilgrims, visas, departures and vouchers, checked on the server and not only hidden in the screen.
Selling is separate from editing package prices
Visa work can be given to a visa desk only
Voucher approval is separate from creating a voucher
Admins get every Ziyarat permission
It posts to your accounts
Selling a package raises a travel invoice in Travix Finance. Every component line carries its own vendor payable, its own revenue account and its own cost account — so Ziyarat margin is separable in the P&L instead of being one lump labelled "packages".
One invoice line per component, each with its own vendor
Revenue and cost accounts set per component type in your masters
Resolved at sell time, so a masters change reaches every future sale
Customer, vendor and general ledgers all posted by the finance module
Refunds, receipts and aging work exactly as they do for any other invoice
This is how the parts fit together from first price to last refund. It is an example, not a customer story.
1
Before the season
Set your cities and parts
Ahead of Muharram, Safar or Arbaeen, start from ready cities in Iraq and Iran, add your own stops, and list the parts every trip is made of, each with its supplier.
