✈️ Yatra is the WordPress travel booking plugin built for tour operators, activity providers, travel agencies and adventure businesses that need real trip inventory — not a generic shop. The free version is a full booking office: trips, availability, checkout, customer records, transactional emails and a customer account area. Yatra Pro unlocks premium payment gateways plus a suite of 20 Pro modules you switch on as your business grows — from Channel Manager (Viator + GetYourGuide) to AI Assistant, White Label and WhatsApp Notifications.

Official site: 🌐 wpyatra.com · 📖 docs.wpyatra.com · 💳 Pricing · ✨ All features · 🎯 Live demo · 💬 Support forum

🎬 See Yatra in action

🎥 Watch Yatra in 60 seconds on YouTube — the complete tour booking system, from building a trip to getting paid. More tutorials on the MantraBrain YouTube channel.

✈️ Why tour operators pick Yatra

• 🗺️ Travel-first data model — Departures, capacity, traveler types and itineraries match how tours are actually sold, not how an e-commerce shop sells products.
• 🧭 One admin workspace — Modern Yatra dashboard inside wp-admin; less tab-hopping than bolting travel onto a generic commerce stack.
• ⚖️ Honest Free vs Pro — Core booking, CRM-style records, reviews and PayPal / Pay Later are in the free plugin. Card gateways and advanced modules are in Pro — no surprise paywalls on basics.
• 🔒 Your site, your data — Bookings and customer data stay in your WordPress database; payments go through the gateways you configure. No proxy, no markup, no per-booking fee.
• ⭐ 700+ active installs · ★ 4.6 / 5 on WordPress.org — Active development since 2018, weekly updates.

🎁 What you get in the free Yatra plugin

Trips and catalog (free)

• Trips & Itineraries — unlimited trips with rich descriptions, gallery, difficulty, duration, meeting points, included / excluded lists, day-by-day itinerary builder, per-trip FAQs and custom attributes
• Departures & Availability — scheduled departures, capacity, recurring availability rules
• Customer Accounts — booking history, payments, profile, and document access (invoices, vouchers, itineraries)
• Reviews & Ratings — moderation and trip-level display
• Sales Reports — admin reports for bookings, revenue, and trends
• Discounts & Coupons — sale and regular pricing, traveler-based pricing, coupon engine
• Enquiries Inbox — capture pre-booking questions per trip
• PDF Documents — generated invoices, vouchers, traveler itineraries
• Transactional Emails — booking confirmation, payment receipt, cancellation, reminder

Free payment gateways

• PayPal — cards, PayPal balance, Pay-in-4
• Pay Later — book now, confirm or pay offline (ideal for bank transfer, cash on arrival, invoice workflows)

Front-end + extensibility

• Templates for trip listings, single trip, booking flow, checkout, and account
• 4 Gutenberg blocks + 8 shortcodes to place trips, search, login and account on any page
• Compatible with most well-coded block themes, classic themes and major page builders
• PHP 7.4 or newer, structured codebase, hooks and filters, template overrides
• REST-oriented flows for booking and account experiences

💎 Yatra Pro — 20 modules across 3 tiers

Compare plans and buy Yatra Pro — three plans (Starter · Growth · Scale), each available yearly or lifetime.

Starter — $99/yr (sale, regular $149) · 1 site license · everything below included

• Dynamic Pricing — seasonality, demand, early bird, last-minute, inventory rules
• Flexible Payments — deposits and partial payments
• Scheduled Payments — instalment plans
• Advanced Discount — group-style discounts alongside coupons
• Additional Services — sell extras with the trip
• Email Automation — multi-step sequences, audience filters, per-send delivery logs
• Abandoned Booking Recovery — recover incomplete bookings
• Mailchimp Integration — sync travelers + bookings to lists
• Facebook Pixel — server-side + browser events
• Google Analytics 4 Enhanced — booking funnel + revenue events
• Google Calendar sync — departures and bookings into Google Calendar
• Custom Landing Pages — per-trip conversion-focused landing pages
• Dynamic Form Field — drag-and-drop custom booking questions
• Trip Consent — digital waivers and signatures
• Premium payment gateways: Stripe · Razorpay · Mollie · Paystack · Square · Authorize.Net · Bank Transfer

Growth — $149/yr (sale, regular $199) · 1 site license · everything in Starter, plus

• AI Assistant — generate itineraries, draft descriptions, suggest replies (bring your own OpenAI or Anthropic key)
• WhatsApp Notifications — booking confirmations, payment receipts and departure reminders over WhatsApp (Meta Cloud API)

Scale — from $349/yr (sale) · 1-site $349/yr (regular $449) or 15-site $599/yr (regular $749) · everything in Growth, plus

• Channel Manager — sell on Viator + GetYourGuide from one WordPress dashboard. Signed webhooks, anti-overbooking locks, real-time inventory sync.
• White Label — rebrand the admin, emails, PDFs and frontend. Full agency theming.
• Team & Access — granular roles + capability-based access for multi-staff agencies. 8 built-in roles, custom role builder, magic-link invitations, time-windowed access for contractors, scope filtering (per-destination / per-trip), append-only audit log. Defense-in-depth: every action gated on the server, UI mirrors via cap-aware controls.
• Webhooks — outbound HTTP delivery on booking / payment / customer events. HMAC-signed payloads, retry queue with exponential backoff, dead-letter queue, certificate pinning. Wire Yatra into Zapier, Make, n8n, or your own internal systems.

Lifetime plans also available: Starter $499 · Growth $699 · Scale $1,299 (1 site) / $1,999 (15 sites) — pay once, own it forever.

See full plan comparison and pricing →

🥊 How Yatra compares

Considering Yatra against a SaaS booking platform or another WordPress travel plugin? We’ve written honest, side-by-side comparisons against each major alternative:

• 🔄 Yatra vs Rezdy — Sell on Viator + GetYourGuide without the $99–$499 / month Rezdy SaaS bill. Lifetime license · GPL · your data, your gateway.
• 🔄 Yatra vs Bokun — Skip the per-OTA-booking fee Bokun charges (typically 2.5% per booking). Independent open-source alternative to Tripadvisor-owned Bokun.
• 🔄 Yatra vs WP Travel Engine — Same WordPress philosophy, modern architecture, broader Pro modules. Custom database tables for performance vs. WP Travel Engine’s custom post types.

Each page covers the feature matrix, pricing math, migration steps and FAQ — written without overpromising. Read the verdict, then try Yatra Pro free before you commit.

🌐 Native integrations

Yatra ships with bring-your-own-credential integrations — no proxy, no markup, no per-event fees. Full directory: All integrations on wpyatra.com.

• Payments: PayPal · Pay Later · Stripe · Razorpay · Mollie · Paystack · Square · Authorize.Net · Bank Transfer
• OTAs: Viator · GetYourGuide · Other OTAs (by request)
• Email & Messaging: Mailchimp · WhatsApp Cloud API
• Analytics & Marketing: Google Analytics 4 · Meta / Facebook Pixel
• Calendars & Scheduling: Google Calendar
• AI Providers: OpenAI · Anthropic Claude
• WordPress Ecosystem: Gutenberg blocks (4 native) · Elementor (via Shortcode) · WooCommerce (coexistence) · Loco Translate

🔍 Built-in travel SEO

Yatra is built to rank — your trips, destinations and activities are search-engine ready out of the box, with no extra SEO plugin required:

• 🧱 Schema.org structured data — automatic structured markup for trips and listing pages so search engines can surface rich results for your tours.
• 🏷️ Meta titles, descriptions & Open Graph / Twitter cards — per-trip and per-archive, with {name}-style tokens, for clean search snippets and shareable social previews.
• 🗺️ XML sitemap — Yatra publishes one sitemap of every trip, destination, activity and category at /yatra-sitemap.xml, advertised in robots.txt and integrated automatically with WordPress core, Yoast, Rank Math and All in One SEO sitemaps. (Yatra stores content in fast custom tables, so this is what keeps it fully discoverable.)
• 🔗 Clean, keyword-friendly permalinks — /trip/…, /destination/…, /activity/… URL bases you control under Settings.
• 🌍 Translation-ready interface — every label, button and email is translatable with standard .po/.mo files via Loco Translate, WPML String Translation or Polylang string translation.

🧩 Blocks and shortcodes

Use the block editor or classic shortcodes to drop catalog widgets, search and account UI into any page.

Blocks (search the inserter for “Yatra” or the block name):

• Trip — block name yatra/tour (trip grid; the registered name stays yatra/tour for backward compatibility, but the inserter title and UI now read Trip). Trip Settings (layout, Featured Priority — restrict to Featured, New, or Limited Time picked on the trip form’s Categorization → Featured Priority) and Filters: each taxonomy (destinations, activities, trip categories, difficulty / fitness level) supports Listing scope — either All published (no ID filter saved) or Only selected, with search plus checkboxes to pick numeric classification IDs.
• Activity — yatra/activity: same taxonomy picker pattern (All published vs search + IDs) in the sidebar; matches [yatra_activity] ID rules.
• Destination — yatra/destination: same pattern; matches [yatra_destination] ID rules.
• Trip categories — yatra/trip-category (same card layout as destinations; links use your trip category base from Settings).

Shortcodes (all accept string values as in the plugin defaults — use yes / no or 0 / 1 where noted):

• [yatra_trip] — Trip listing. Alias: [yatra_tour]. Filters: destination, activity, category accept comma-separated classification IDs. Optional: order, featured_priority (featured / new / limited), per_page, difficulty, price_min, price_max, duration_min, duration_max, search, columns, show_pagination, title, card_layout. Pagination: trip_page. Examples: [yatra_trip], [yatra_trip destination="44" activity="12"], [yatra_trip featured_priority="new" per_page="6"], [yatra_trip card_layout="compact_all"].
• [yatra_activity] — Activity listing cards.
• [yatra_destination] — Destination showcase.
• [yatra_trip_category] — Trip category cards.
• [yatra_search] — Advanced trip search form. Per-field visibility attributes — keyword, destination, activities, duration, budget — each yes / no. Omit one to inherit its Settings → Search & Listing toggle; pass a value to force it on/off for that placement. Example: [yatra_search budget="no" duration="no"]. (The built-in listing page sets these automatically from your settings.)
• [yatra_login] — Customer login form.
• [yatra_my_account] — Account dashboard for logged-in users.
• [yatra_discount_and_deals] — Discounted trips.

Empty-term filtering (hide_empty): [yatra_destination], [yatra_activity] and [yatra_trip_category] accept hide_empty="yes" to skip taxonomy terms that have zero published trips. Opt-in (default no).

Card layout (card_layout): [yatra_trip] / [yatra_tour] and [yatra_discount_and_deals] accept card_layout to set how the trip cards look for that one listing, overriding the site-wide Settings → Design → Listing Card Layout default. Values: inherit (default — follow the site setting), standard (full card), compact_mobile (compact horizontal cards on phones only, unchanged on desktop), compact_all (compact everywhere). The compact card shows image, title, price and a View Details button. Each listing is independent, so different listings on the same page can use different layouts. Example: [yatra_trip per_page="6" card_layout="compact_all"]. The Trip block offers the same choice under Trip Settings → Card layout.

Note: If you’re migrating from an older build, [yatra_cart], [yatra_checkout] and [yatra_mini_cart] are no longer registered — checkout and the booking flow now use Yatra’s own front-end routes and templates. See docs.wpyatra.com for full shortcode reference, URLs and page setup.

🎨 Compatible WordPress travel themes

Yatra works with most well-coded block themes, classic themes and major page builders. Recommended themes (optional — Yatra works with any theme):

• 🧳 Resa — the official Yatra travel theme — Lighthouse-fast, mobile-first, Gutenberg + WooCommerce ready, free on the WordPress.org theme directory. Trip card grid, departure widgets, traveler-account dashboard all pre-styled for Yatra.
• 🧱 Blocksy — modern block theme
• ⚡ Kadence — fast, flexible theme

🔗 Quick links

• 🏠 wpyatra.com — official site
• 💳 Pricing — Starter · Growth · Scale · Lifetime plans
• ✨ All features — full Free + Pro capability list
• 🌐 Integrations — every native partner
• 🥊 Yatra vs alternatives — head-to-head comparisons
• 🎨 WordPress travel theme (Resa) — recommended pairing
• 📖 Documentation — installation, blocks, shortcodes, operations
• 🎯 Live demo — see Yatra on a real WordPress demo
• 🆘 Support / contact — help and commercial support routing

💙 Join the community

• ⭐ Rate Yatra five stars — helps other tour operators find the plugin
• 💬 Facebook community — connect with other Yatra users
• 📧 Email support — direct email for product questions
• 🐛 GitHub — issues & contributions — bug reports and pull requests

🚀 Try Yatra risk-free

• 🧪 Try the free Yatra plugin in WordPress Playground — spin up a temporary WordPress site with the free Yatra plugin pre-installed. No local setup, no signup, no credit card.
• 🎁 Try Yatra Pro free — full Pro trial environment with every module enabled. No credit card required.
• 💰 14-day refund on every paid Yatra Pro plan — see the pricing page for the refund window terms.

Additional Information

Privacy

Booking and customer data are stored in your WordPress database. Payment processing is performed by the gateways you enable; review each provider’s privacy and PCI documentation. Yatra does not ship customer data to an external SaaS.

Credits

Yatra is developed by MantraBrain. Third-party libraries include components such as React (admin UI), Vite, TanStack Query, and others as shipped in the plugin package.

Contributing

Issues and contributions: GitHub — Yatra

If Yatra helps your business, a ⭐ five-star review on WordPress.org and considering 💎 Yatra Pro when you need paid features both help sustain development. Thank you for using Yatra.

🛠️ Quick setup

1. Install and activate Yatra from this screen or upload the ZIP under Plugins → Add New → Upload.
2. Complete the setup wizard (currency, basics, permalinks as prompted).
3. Add destinations and activities, then create your first trip under Yatra → Trips.
4. Configure PayPal and/or Pay Later under Yatra payment settings (free). Add Yatra Pro when you need card gateways or Pro modules.
5. Place the booking experience on your site using Yatra templates, blocks, or shortcodes (see 🧩 Blocks and shortcodes in the description above and docs.wpyatra.com).

1. 

   Trip pages that sell themselves — gallery, duration, season and a sticky “Book Now” price button on any theme

2. 

   Book in a few taps, no redirects — live departure availability, traveller count and enquiry, all inline

3. 

   Your whole operation at a glance — bookings, revenue and upcoming departures the moment you log in

4. 

   Every trip in one organised list — search, filter by status, and see pricing, type and availability instantly

5. 

   Build a complete trip in one place — basics, pricing, itinerary, media and SEO, guided step by step

6. 

   Never lose track of a reservation — filter by traveller, payment state and status across every departure

7. 

   Full booking detail, one-click invoice — payment summary, traveller records and a downloadable invoice

8. 

   Every transaction accounted for — Stripe, PayPal, bank transfer and manual payments in one ledger

9. 

   Run offers without spreadsheets — coupon codes with usage limits, expiry dates and live status

What is the best WordPress travel booking plugin for tour operators?

Yatra is the WordPress travel booking plugin built around the operational reality of selling tours — scheduled departures, capacity, traveler categories, OTA distribution, dynamic pricing and deposit handling. The free plugin covers the entire booking lifecycle (trips, availability, customer accounts, reviews, reports, PDFs, transactional emails, PayPal + Pay Later); Yatra Pro adds 20 modules across Starter, Growth and Scale tiers. Read the head-to-head comparison vs WP Travel Engine or vs Rezdy SaaS.

Is Yatra free?

Yes. The plugin on WordPress.org is free and includes the core booking stack for many tour operators. Yatra Pro is a paid upgrade for premium gateways and 20 Pro modules.

Do I need code skills to use Yatra?

No for day-to-day operation. Developers can override templates and use hooks for custom workflows.

Which payments are free vs Pro?

Free: PayPal and Pay Later. Pro: Stripe, Razorpay, Mollie, Paystack, Square, Authorize.Net, bank transfer (as supported for your account and region).

Can I take bookings without charging a card immediately?

Yes. Use Pay Later for offline confirmation, invoices, or pay-on-arrival flows.

Can I distribute my tours on Viator, GetYourGuide and other OTAs?

Yes — the Channel Manager module (Scale tier) connects Yatra directly to Viator and GetYourGuide via their official APIs. Signed webhooks pull bookings back in real time; anti-overbooking locks prevent two channels selling the same seat. Other OTAs (Klook, TripAdvisor Experiences, Booking.com Experiences, Airbnb Experiences) are available by request.

Does Yatra work with WooCommerce?

Yes. Yatra runs alongside WooCommerce on the same WordPress site — Yatra stores trips in its own custom tables while WooCommerce uses WordPress orders. Both coexist without data conflicts. Many operators use Yatra for tours and WooCommerce for merchandise or gift cards.

Does Yatra support multilingual and multi-currency travel sites?

Interface — yes. Yatra is fully translation-ready: every label, button and email translates via standard POT / .po / .mo files using Loco Translate, WPML String Translation or Polylang string translation. RTL stylesheets ship in the Resa travel theme.

Trip content — important to know. Yatra stores trips and destinations in its own fast custom tables (not WordPress posts), so WPML and Polylang — which translate posts and taxonomies — cannot translate the trip content itself. For a fully multilingual catalogue today, run one site per language (WordPress Multisite, a subsite per language). Native per-language content translation is on our roadmap.

Currency. Set your default currency in Yatra → Settings (site-level).

Does Yatra work with my theme?

It works with most modern WordPress themes. Yatra ships front-end templates; your theme controls global layout and typography. For the smoothest pairing, see Resa — the dedicated Yatra travel theme by MantraBrain, free on WordPress.org.

Are invoices and vouchers only in Pro?

Travelers can access invoices, vouchers and itineraries from the account area on the free plugin when your site is configured for it. Pro expands payment choices and business modules — it does not remove core documents by default.

How do saved trips / wishlist work?

Saved trips appear when Yatra Pro is active and wishlist is enabled in Yatra settings.

Is Yatra GDPR-friendly?

Use WordPress privacy tools together with Yatra: export or delete user-related data as required by your policy. Bookings and customer data live in your own WordPress database — Yatra does not ship data to an external SaaS. Payment data is handled by your chosen gateways under their terms.

Where is documentation?

See docs.wpyatra.com and wpyatra.com for features, Pro and updates.

Where are shortcodes and blocks documented?

See 🧩 Blocks and shortcodes in the description above. Full walkthroughs (pages, permalinks, checkout URLs) are in the documentation.

Does Yatra provide cart or checkout shortcodes?

No. Checkout and the booking flow run on Yatra’s own front-end routes and templates — drop them on any page via the plugin’s pretty permalinks (see the Permalink settings). Catalog, search, login and account still have shortcodes and blocks as listed in the description.

What does Yatra Pro cost?

Pricing starts at $99/yr (Starter, sale) and goes up to $599/yr (Scale 15-site, sale). Lifetime plans available from $499 one-time. Every Pro tier includes a 14-day refund window. See the full pricing breakdown.

3.1.0 — 1 November 2026

Fixed
* Refunds were deducted twice, leaving a negative amount paid. Recording a refund wrote the refund as its own entry and marked the original payment refunded, so the same money came off the booking twice over: a 1,000 payment with a 150 refund stored the amount paid as −150 instead of 850, reported more outstanding than the trip costs, and reset the payment status to Pending — indistinguishable from a booking that had never paid. A refund is now a single entry of its own and the original payment keeps its own record, so what you received, what you sent back and what that leaves are each counted once; the booking screen reports all three. A fully refunded booking now reads Refunded rather than Pending, including where you marked a payment refunded by hand. Because the original payment is no longer closed off, a second partial refund against the same payment is possible where it previously was not, and a new check refuses any refund that would send back more than the booking ever received. Bookings whose stored figures are already wrong are recalculated once, automatically, on the first admin page you open after updating; bookings with no refunds are not touched. Each booking’s previous figures are copied to a backup table (yatra_refund_totals_repair_backup_v1) before they change; if a copy cannot be made, that booking is left alone and retried later.
* Every booking was counted twice on the customer’s record. A customer with two bookings was shown as having four — in My Account and on the Customers screen alike. The booking count, total spent and traveller totals stored against a customer were added up by hand, and one checkout added to them twice, because both the checkout and the booking service create-or-update the customer record. Nothing ever subtracted either, so cancelling or deleting a booking left the count where it was, and a customer an operator added by hand started life showing one booking they had never made. These figures are now worked out from the bookings themselves whenever a booking is created, changed, cancelled or deleted, so they cannot drift again. Counts already stored wrong are repaired once, automatically, on the first admin page you open after updating. Before rebuilding, the current figures are copied to a backup table (yatra_customers_stats_backup_v1); if that copy cannot be made, the rebuild waits an hour and tries again.
* Cancelled trips were counted as upcoming. “Upcoming Trips” in My Account looked only at the travel date, so a trip the customer had cancelled kept being counted and listed as upcoming. A cancelled or refunded booking is no longer upcoming, and the Dashboard and Bookings pages now agree about a trip departing today — one used to count it and the other not.
* The payment section of the booking form could not be translated. On a translated site the booking form came out in the site’s language right up to the payment methods, which stayed in English — the one part of the checkout a customer cannot miss. Yatra had written each gateway’s name and description into your saved settings in English when it was installed, and several of those seeded texts did not match the gateway’s own wording, so the checkout mistook them for labels you had typed yourself and used them in place of the translatable ones. Yatra now recognises its own old defaults and lets them translate, without touching your saved settings: a name or description you genuinely customised is still shown exactly as you wrote it, and new installs no longer store these labels at all. The date-format hint in empty date fields (“YYYY-MM-DD”) is translatable too, so it can follow your locale’s convention.
* The confirmation page promised travel documents that were never sent. Under What’s Next, Yatra told every customer they would receive “a detailed itinerary and preparation guide within 24-48 hours” — nothing sends one, so customers waited for an email that was not coming and then asked where it was. The pay-later confirmation email said the same. Both now point to where the booking really lives: its details, trip itinerary and any balance due are in My Account, linked using your configured account address. A customer who booked as a guest is told how to reach it instead — create an account with the email address they booked with and the booking appears there — and if your site does not allow registration they are simply asked to keep their confirmation email, rather than being sent to a login page that holds nothing for them.
* Booking statuses were missing from the My Account bookings list. Every booking in the list showed a “Pending” badge whatever its real status, the Completed filter found nothing and the Pending filter only matched on payment, because the list did not carry the booking’s status at all (the booking detail page did, which is why the two disagreed). The list now carries it, so badges, filters and counts all read the real status.
* Late bookings never got the trip reminder. The daily reminder went only to bookings travelling exactly the configured number of days out, so a booking made or confirmed inside that window — booked one day before a three-day reminder, say — never received one, and neither did a booking whose reminder day WP-Cron missed. Every eligible booking travelling between today and the reminder day now gets its reminder on the next daily run, once, and a late reminder states the real number of days left instead of the configured number. Resend email → Trip reminder on a booking now sends exactly the same email as the automatic one, including the outstanding-balance block, and reports an error instead of “sent” when the Trip reminder email is switched off.
* The archive pages’ structured data described an empty list. The trip archive and the destination, activity and trip-category listings printed CollectionPage JSON-LD with a hardcoded empty ItemList ("numberOfItems": 0) even when the page showed cards. The list now holds the cards actually shown — each with its URL, name and position — following filters, sorting and pagination (page 2 continues from position 11), and a page with no results leaves the list out instead of printing it empty. SEO titles, meta descriptions, canonical URLs, robots directives, prev/next links and sitemaps are unchanged. New filter yatra_seo_collection_page_schema to change or remove the list.
* The Payments method filter offered the wrong choices. All Methods always listed Credit Card, PayPal, Bank Transfer and Cash, whatever was set up, so most gateways named in the table could not be chosen — on a site using Stripe and Bank Transfer, Stripe could not be filtered at all, and “Bank Transfer” missed bank transfers taken at checkout. The filter now lists the payment methods you have enabled plus any method that already has payments recorded, with the same names the table shows, so a gateway you switched off stays filterable for its past payments. The two spellings of one method (a checkout “bank_transfer” and a hand-entered “Bank Transfer”) appear once and filter together in every language, and the table now shows a hand-entered method under the same translated name as the gateway.
* The enquiry page could stop with a fatal error on older setups. On PHP 7.4/8.0 with WordPress 6.0–6.4, reading a trip’s enquiry settings called a PHP 8.1 function WordPress only provides from 6.5. It now works on every supported PHP and WordPress version.
* Trip listings made a request back to your own site for every card. To decide whether to show the “Group Discounts” badge, each trip card on a listing page called the site’s REST API over HTTP while the page was being built — up to a dozen extra requests per page, and on hosts that block such loopback requests each one waited for a timeout, making listings very slow. The badge information is now read directly, with the same result and no extra requests.
* The trip listing price filter always showed “$”. The price range under Filters was redrawn by the page script with a hard-coded dollar sign, so a store in euros or pounds showed “$9 – $8,999” as soon as the page finished loading or the slider moved. It now uses your currency, symbol position, decimals and separators — exactly as prices are printed elsewhere.
* Parts of the admin stayed English on sites translated with a WordPress.org language pack. Screens that load separately from the main admin script — the Trip Consent form editor among them — never received their translations, because WordPress only loads the translation file for the main script. Those screens now get their translations whichever way the site is translated, and plural forms follow the language’s own rules. A few labels in the admin header (the Pro version, the license status badge and the dark-mode button) and the Trip Consent field-type tooltips were not translatable at all; they are now.
* A recurring departure’s booking cutoff was only enforced by the calendar. Booking Cutoff (hours before) and the “bookings open N days ahead” limit on a recurring departure correctly removed those dates from the trip calendar, but the booking itself was not checked: a date inside the cutoff matched no departure, was treated as an open-dated trip and the booking went through — from an old link, a page left open, or a request made directly. Such a booking is now refused (“Booking cutoff has passed for this departure.”, or “This departure is not open for booking.” before bookings open). Tip: the cutoff is set in hours, so 20 days is 480.
* Admin calendars always started the week on Sunday. The availability calendar and the admin date pickers ignored Settings → General → Week Starts On, which the frontend calendars already honoured. They now start on the configured day, and their weekday names are translatable.
* The Google Calendar settings showed a “Sync Departures” switch that did nothing. Nothing ever created an event from it. Departures reach the calendar through One event per departure, which is built from bookings, so the switch is removed and the Sync Bookings description explains this. The setting stays stored, so nothing saved is lost.

New
* Payment notes are now a history rather than a single field. The Notes box on a payment held one value, so recording why a refund was issued wrote over whatever was there before, and nothing recorded when a note was added or who added it. Payments → Notes now keeps a dated, attributed list: every note stays visible as new ones are added, each showing the time and the member of staff who wrote it. Anything already in the old Notes field is still shown, first in the list and marked as recorded before the history existed — nothing is migrated or overwritten, so the old field keeps working exactly as it did.
* A separate cancellation email for cancellations you make. Yatra has only ever had one customer cancellation email, so a trip you cancelled told the customer their own cancellation had been received. Yatra already records who ended a booking; it now uses that. Switch on Email While Cancelling → Cancelled by us in Settings → Emails and a cancellation you make uses its own wording, while one the customer asked for — or one the unpaid-booking expiry produces — keeps the ordinary email. Off by default, so nothing changes until you ask for it, and if that wording is switched off or left empty the ordinary cancellation email is sent instead rather than nothing at all.
* Payment due dates are now shown to customers and to you. A booking with a balance outstanding showed the amount owed but never said when it was owed — not in the customer’s account, not on the booking screen, and not on the Payments screen. All three now show the next payment due date (or Overdue since, when it has passed) with the amount, and list each instalment separately where there is more than one. On Payments it is a Next Due column you switch on from the column picker, so no existing layout changes until you ask for it. Requires Yatra Pro with Scheduled Payments switched on, since that is what defines when a balance falls due; with it off there is no due date to show and nothing changes.
* The lead traveller’s date of birth and nationality now reach the customer profile. A booking collects them from the lead traveller, but the customer record was built only from the Contact section — which on a default form has no date-of-birth or nationality field — so those two stayed empty and the customer was asked for them a second time on their profile. They are now taken from the lead traveller, along with gender. An existing profile is never overwritten: only a blank is filled, so anything the customer has set themselves is kept exactly as it is.
* New {{payment_reference}} merge tag. Payment emails could only show the gateway’s Transaction ID, which is empty for anything recorded by hand — so the line either sat blank or had to be left out. Yatra’s own payment number (PAY-000004), the one already shown on the Payments screen, the invoice and the customer’s account, is now available as Payment Reference in Available Variables. It is filled for every recorded payment, so a customer always has a number to quote.
* You can now record why a booking was cancelled, and tell the customer. The cancellation email has always been able to print a reason — {{cancellation_reason}} is a documented merge tag and the booking table has a column for it — but nothing except the unpaid-booking expiry cron ever wrote to it, so an operator cancelling a booking by hand had no way to say why and the tag arrived empty. The booking screen now offers a Cancellation Reason when you set a booking to Cancelled, and it is saved with the status change so the customer’s email carries it. Leave it blank and the email is exactly what it was before.
* Email templates that cannot send are now labelled. Two of the built-in templates are older names for templates still in use — they sit on the same event, look identical in Emails → Templates, and editing the wrong one has no effect at all. Such a template now carries a Not in use badge naming the one that handles the event instead, so the wording you edit is the wording that gets sent.
* Customers can now keep a postal code on their profile. The My Account profile asked for country, city and street address but had no postal/ZIP field, so a customer could never give a complete address — and the postal code already stored on their Yatra customer record was not shown back to them either. The field is now on the profile, saved to the same customer record the booking form and the admin Customers screen use, and read back when the page loads, so what the customer enters is what they see next time.
* Notes on excluded dates and periods. In a recurring availability rule, each excluded date or period now has an optional note — Easter break, guide on leave — so everyone managing availability can see why a date is closed, long after it was blocked. Notes are visible to your team only, never to customers, and are plain text up to 200 characters. Existing exclusions are unchanged and simply have no note.
* Booking-form answers in emails read like the booking page. Merge tags for booking-form answers — the contact_…, emergency_… and lead_traveler_… tags and {{traveler_custom_fields_html}} — printed the stored value: a dropdown’s internal value (spouse, gluten_free) or a country code (DE). They now print what the booking page shows — the option’s label (Spouse/Partner, Gluten Free, translated like on the booking form) and the country name (Germany) — and the traveller block uses each field’s own label. Free-text answers are unchanged.
* Choose a Google Calendar from a list. Once connected, Settings → Integration → Google Calendar offers the calendars the account can add events to, instead of only a Calendar ID box. Requires the matching Yatra Pro release; with an older Pro the box works as before.
* Settings for the new Google Calendar options. The Google Calendar dashboard gains Calendar time zone and Event text (your own event title and details with variables). Both need the matching Yatra Pro release and stay hidden without it.
* Resend the trip reminder from the bookings list. The row actions menu on Bookings now has Resend trip reminder, next to Resend confirmation email. It sends the same email as Resend email → Trip reminder on the booking itself. It is offered only for trips still to come, not for cancelled, refunded or completed bookings.
* New yatra_booking_inserted action. Fired as soon as a booking is stored, for every booking — including one still waiting for e-mail verification, which delays yatra_booking_created. For integrations that must act at checkout time, such as recording the visitor’s consent choice.

3.0.19 — 16 October 2026

Fixed
* Pressing Book Now twice created two bookings. Nothing remembered the booking a submission had already made, so each press minted another booking, another reference and another customer email — and because the card is collected after the booking exists, an abandoned or declined payment left one behind every time. An identical resubmit now resumes the booking it already created: same reference, no second booking, no second email, and the payment step runs again so the card can be retried against it. Only an identical resubmit is absorbed — change the party, the date, the amount, the payment method, or correct a detail you had mistyped, and you get a new booking carrying the change, exactly as before. Works the same on every payment method, card or otherwise.
* “Verify your email” was sent again on every attempt. On sites that ask guests to verify their email address, each press of Book Now sent another verification link. The link from the first attempt stays valid, so one is now sent per booking every few minutes: pressing the button repeatedly sends one email, while coming back later still gets you a fresh link.
* A checkout that posted no payment method was booked as “pay on arrival”. An absent or unrecognised payment method silently fell back to Pay Later, which is an offline method: no card was taken, the booking was created and the customer was emailed. Leaving the card fields empty was the usual way to reach it. Yatra now falls back to Pay Later only on sites that actually offer it, and otherwise asks the customer to choose how they would like to pay.

New
* Choose what the customer is emailed while a card payment is still pending. A booking and its reference are created before the card is charged, because the payment gateway needs a booking to charge against — so a checkout that is abandoned at the card step, or whose card is declined, already had a confirmation email sent for it. Settings → Bookings → Email While Payment Is Pending now offers “Send the booking confirmation straight away” (what Yatra has always done, and still the default) or “Wait until the payment succeeds”. Pay-later, bank transfer and zero-balance bookings are unaffected either way: they have no payment to wait for.

3.0.18 — 9 October 2026

New
* Booking form fields can be pre-filled by add-ons. A new yatra_booking_form_field_prefill filter lets a value be supplied for any field by its rendered input name, covering the traveller section and operator-added fields as well as the contact details — previously only the contact section could be pre-filled, and only from an existing booking. Yatra Pro uses this to restore what a customer had typed when they return through an abandoned-booking recovery link.
* The lead traveller’s answers can now be used in emails. The booking form builder lets you mark a traveller field “lead traveller only”, but there was no merge tag to print the answer — the only way to show it was {{traveler_custom_fields_html}}, which prints every traveller’s answers to everything. Each traveller field now also has a {{lead_traveler_<field>}} tag carrying the lead traveller’s answer, listed in the Available Variables panel beside the others. Fields asked of every traveller still have no single-value tag of their own, because a booking has many travellers; the lead is the one person there is exactly one of.
* A theme can now design your trip, listing and destination pages. Yatra offers block templates for those screens so they can be edited in the Site Editor, but only an edit saved from the editor was ever used — a template file shipped by your theme appeared in the list and was then ignored on the site itself. A theme built for Yatra can now lay out those pages properly: reassurance under an itinerary, a prompt at the end of a listing, whatever it wants. Nothing changes unless your theme ships one, and an edit you have saved yourself still takes precedence over it.
* yatra_trip_reminder_due fires for each booking that reaches its trip-reminder day, whether or not the reminder email is switched on. Yatra Pro uses it to start pre-departure email sequences.

Fixed
* The link that lets a customer pay their balance was hidden from the template editor. Reminder emails can carry a secure link that opens the outstanding payment ready to pay, without the customer signing in or hunting through their account. It worked, but it was missing from the Available Variables list, so there was no way to discover it and operators linked to the account page instead. It is now listed as Pay Balance Link on the scheduled payment templates.
* Marking a booking paid could tell the customer they had paid the whole trip. The payment email announced the booking’s running total rather than the payment just taken — and when nothing had been recorded yet it fell back to the full booking price. A customer paying a deposit could be sent a receipt for the entire trip. The email now reports the amount that change actually recorded, so a deposit reads as a deposit and the balance is right.
* Marking a booking paid could leave it still owing money. When a booking already showed an amount paid that the Payments screen had no record of — an imported booking, or one taken before payments were itemised — marking it paid recorded only the balance and then set the amount paid to just that balance, losing the earlier payment. The booking read as part paid with an amount still due, and because the paid total is recalculated from the Payments screen, the next payment of any kind would undo the settlement again. The earlier payment is now written to the Payments screen as its own entry, so the two agree and the booking settles properly. The receipt still reports only the payment just taken.
* A status change no longer claims a payment arrived when none did. Re-marking an already-settled booking as paid, or moving one to partial, sent a “payment received” email for money that had not just been received. Those changes are bookkeeping, not payments, and are now silent; use Resend email on the booking to send a receipt deliberately.
* Emails no longer show an empty Transaction ID. A manually recorded payment has no transaction reference, and the row was printed anyway with nothing after the label. Any detail row whose value comes out empty is now left out.
* Destinations and activities showed a rating of 0.0 before anyone had reviewed them. The star and the score were printed whether or not there were any reviews, so a new site, or any destination nobody had reviewed yet, advertised what looked like the worst possible score. The rating now appears once there is one.
* Switching an email off in Emails → Templates did not always stop it. With Yatra Pro’s Email Automation in use, the setting that switches a transactional email on or off was skipped entirely whenever Pro held a template for the same event, so an email you had turned off kept going out. The setting is now honoured. Pro still decides which wording is used; what it no longer does is override “off”. This needs the matching Yatra Pro update to take full effect — until Pro is updated, Yatra deliberately leaves the old behaviour alone rather than switch off emails on its own, so nothing stops unexpectedly while the two are out of step.
* Review request emails linked to the wrong page. The link was built from the trip’s row number rather than the trip itself, so it pointed at whatever unrelated post happened to share that number, or at nothing at all when none did — customers received a review link that went somewhere else or could not be clicked. It now points at the trip. A request that cannot be given a working link is no longer sent.
* Customers who had already left a review were asked for another one. The check for an existing review looked for two columns that reviews do not have, so it failed every time it ran and never once prevented a reminder. It now matches on the trip together with the customer’s account or the email address on the booking.
* The “Book Now” button on a trip page ignored your primary colour. The rule that colours it was written twice, and the second one painted the button a fixed green, so it was the one element on the page that never followed the colour set in Settings. It now uses your primary colour like every other main action. If you had not changed the primary colour, the button will no longer be green — set the one you want under Primary brand color in Yatra → Settings.

The two most recent releases are listed below. For the complete version history, see changelog.txt.

The full history for older releases is kept with the source: https://github.com/mantrabrain/yatra/blob/master/readme.txt