=== Yatra - Travel Booking & Tour Operator Software ===
Contributors: MantraBrain
Tags: tour-booking, travel-booking, tour-operator, travel, travel-agency
Requires at least: 6.0
Tested up to: 7.0
Requires PHP: 7.4
Stable tag: 3.0.11
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

WordPress travel booking plugin for tour operators. Trips, departures, payments, OTAs, AI. Free + [Pro](https://wpyatra.com/pricing/) from $99/yr.

== Description ==

**✈️ 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](https://wpyatra.com/pricing/)** unlocks [premium payment gateways](https://wpyatra.com/pricing/) plus a suite of [20 Pro modules](https://wpyatra.com/features/) you switch on as your business grows — from [Channel Manager (Viator + GetYourGuide)](https://wpyatra.com/features/channel-manager/) to [AI Assistant](https://wpyatra.com/features/ai-assistant/), [White Label](https://wpyatra.com/features/white-label/) and [WhatsApp Notifications](https://wpyatra.com/features/whatsapp/).

**Official site:** 🌐 [wpyatra.com](https://wpyatra.com/) · 📖 [docs.wpyatra.com](https://docs.wpyatra.com) · 💳 [Pricing](https://wpyatra.com/pricing/) · ✨ [All features](https://wpyatra.com/features/) · 🎯 [Live demo](https://demo.wpyatra.com/) · 💬 [Support forum](https://wordpress.org/support/plugin/yatra/)

= 🎬 See Yatra in action =

🎥 Watch the Yatra walkthrough on YouTube — trips, bookings, checkout, and traveler accounts in under five minutes. More tutorials on the **[MantraBrain YouTube channel](https://www.youtube.com/@MantraBrain)**.

	[youtube https://www.youtube.com/watch?v=cHmC-x7y0TQ]

= ✈️ 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](https://wpyatra.com/pricing/)** — Core booking, CRM-style records, reviews and PayPal / Pay Later are in the free plugin. Card gateways and advanced modules are in [Pro](https://wpyatra.com/pricing/) — 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](https://wpyatra.com/features/trips/) — 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](https://wpyatra.com/features/departures/) — scheduled departures, capacity, recurring availability rules
* [Customer Accounts](https://wpyatra.com/features/customer-accounts/) — booking history, payments, profile, and document access (invoices, vouchers, itineraries)
* [Reviews & Ratings](https://wpyatra.com/features/reviews/) — moderation and trip-level display
* [Sales Reports](https://wpyatra.com/features/reports/) — admin reports for bookings, revenue, and trends
* [Discounts & Coupons](https://wpyatra.com/features/discounts/) — sale and regular pricing, traveler-based pricing, coupon engine
* [Enquiries Inbox](https://wpyatra.com/features/enquiries/) — capture pre-booking questions per trip
* [PDF Documents](https://wpyatra.com/features/pdfs/) — generated invoices, vouchers, traveler itineraries
* [Transactional Emails](https://wpyatra.com/features/transactional-emails/) — booking confirmation, payment receipt, cancellation, reminder

**Free payment gateways**

* [PayPal](https://wpyatra.com/features/paypal/) — cards, PayPal balance, Pay-in-4
* [Pay Later](https://wpyatra.com/features/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](https://wpyatra.com/pricing/)** — three plans (Starter · Growth · Scale), each available yearly or lifetime.

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

* [Dynamic Pricing](https://wpyatra.com/features/dynamic-pricing/) — seasonality, demand, early bird, last-minute, inventory rules
* [Flexible Payments](https://wpyatra.com/features/flexible-payments/) — deposits and partial payments
* [Scheduled Payments](https://wpyatra.com/features/scheduled-payments/) — instalment plans
* [Advanced Discount](https://wpyatra.com/features/advanced-discount/) — group-style discounts alongside coupons
* [Additional Services](https://wpyatra.com/features/additional-services/) — sell extras with the trip
* [Email Automation](https://wpyatra.com/features/email-automation/) — multi-step sequences, audience filters, per-send delivery logs
* [Abandoned Booking Recovery](https://wpyatra.com/features/abandoned-booking-recovery/) — recover incomplete bookings
* [Mailchimp Integration](https://wpyatra.com/features/mailchimp/) — sync travelers + bookings to lists
* [Facebook Pixel](https://wpyatra.com/features/facebook-pixel/) — server-side + browser events
* [Google Analytics 4 Enhanced](https://wpyatra.com/features/google-analytics/) — booking funnel + revenue events
* [Google Calendar sync](https://wpyatra.com/features/google-calendar/) — departures and bookings into Google Calendar
* [Custom Landing Pages](https://wpyatra.com/features/custom-landing-pages/) — per-trip conversion-focused landing pages
* [Dynamic Form Field](https://wpyatra.com/features/dynamic-form-field/) — drag-and-drop custom booking questions
* [Trip Consent](https://wpyatra.com/features/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](https://wpyatra.com/features/ai-assistant/) — generate itineraries, draft descriptions, suggest replies (bring your own OpenAI or Anthropic key)
* [WhatsApp Notifications](https://wpyatra.com/features/whatsapp/) — 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](https://wpyatra.com/features/channel-manager/) — sell on Viator + GetYourGuide from one WordPress dashboard. Signed webhooks, anti-overbooking locks, real-time inventory sync.
* [White Label](https://wpyatra.com/features/white-label/) — rebrand the admin, emails, PDFs and frontend. Full agency theming.
* [Team & Access](https://wpyatra.com/features/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](https://wpyatra.com/features/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 →](https://wpyatra.com/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](https://wpyatra.com/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](https://wpyatra.com/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](https://wpyatra.com/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](https://try.wpyatra.com/try-yatra-pro/) 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](https://wpyatra.com/integrations/)**.

* **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`. Pagination: `trip_page`. Examples: `[yatra_trip]`, `[yatra_trip destination="44" activity="12"]`, `[yatra_trip featured_priority="new" per_page="6"]`.
* **`[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`).

**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](https://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](https://wpyatra.com/best-wordpress-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](https://wordpress.org/themes/blocksy/?ref=yatrapluginorg)** — modern block theme
* ⚡ **[Kadence](https://wordpress.org/themes/kadence/?ref=yatrapluginorg)** — fast, flexible theme

= 🔗 Quick links =

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

= 💙 Join the community =

* ⭐ **[Rate Yatra five stars](https://wordpress.org/support/plugin/yatra/reviews/?filter=5)** — helps other tour operators find the plugin
* 💬 **[Facebook community](https://www.facebook.com/groups/yatrawordpressplugin)** — connect with other Yatra users
* 📧 **[Email support](mailto:mantrabrain@gmail.com)** — direct email for product questions
* 🐛 **[GitHub — issues & contributions](https://github.com/MantraBrain/yatra)** — bug reports and pull requests

= 🚀 Try Yatra risk-free =

* 🧪 **[Try the free Yatra plugin in WordPress Playground](https://try.new/plugins/yatra)** — 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](https://try.wpyatra.com/try-yatra-pro/)** — 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](https://wpyatra.com/pricing/) for the refund window terms.

== Installation ==

🛠️ **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](https://wpyatra.com/pricing/)** when you need card gateways or [Pro modules](https://wpyatra.com/features/).
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](https://docs.wpyatra.com)).

== Frequently Asked Questions ==

= 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](https://wpyatra.com/pricing/) adds 20 modules across Starter, Growth and Scale tiers. Read the [head-to-head comparison vs WP Travel Engine](https://wpyatra.com/yatra-vs-wp-travel-engine/) or [vs Rezdy SaaS](https://wpyatra.com/yatra-vs-rezdy/).

= Is Yatra free? =

Yes. The plugin on WordPress.org is free and includes the core booking stack for many tour operators. **[Yatra Pro](https://wpyatra.com/pricing/)** is a paid upgrade for [premium gateways](https://wpyatra.com/pricing/) and [20 Pro modules](https://wpyatra.com/features/).

= 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](https://wpyatra.com/features/paypal/) and [Pay Later](https://wpyatra.com/features/pay-later/). **[Pro](https://wpyatra.com/pricing/):** 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](https://wpyatra.com/features/channel-manager/) (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](https://wpyatra.com/best-wordpress-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](https://wpyatra.com/best-wordpress-travel-theme/)** — 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](https://wpyatra.com/pricing/) 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](https://wpyatra.com/pricing/)** 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](https://docs.wpyatra.com)** and **[wpyatra.com](https://wpyatra.com/)** for features, **[Pro](https://wpyatra.com/pricing/)** 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](https://wpyatra.com/pricing/)**.

== Screenshots ==

📷 **Screenshots** (as shown on WordPress.org)

1. Yatra dashboard inside WordPress — bookings, revenue and quick access to daily tasks
2. Trip Creation Process — content, pricing, media and settings in one workspace
3. Trip list & All listing page — search, filters and status at a glance
4. Trip Booking Process — hero, itinerary and book flow
5. Global Settings - Payment Gateways etc.
6. Traveler account — bookings, payments and documents

== Changelog ==

The two most recent releases are listed below. For the complete version history, see [changelog.txt](https://plugins.svn.wordpress.org/yatra/trunk/changelog.txt).

= 3.0.11 — 20 July 2026 =
* **Departures now honour your recurring availability rule:** a tour with a 9-seat vehicle but a rule allowing only **1 booking per date** showed 9 under Departures. Overlapping rules were resolved in an arbitrary order (every rule carries the same priority), so the wrong one could win and the display fell back to the tour's passenger capacity. Rule matching is now deterministic — the most recently created rule wins a tie — and rules created in the editor are read correctly everywhere.
* **Departures can be deleted again:** deletion always failed with *"Manual departures or departures with bookings cannot be deleted"*, even for an empty, auto-created departure. The check required an internal value the plugin never actually stores, so **no** departure was ever deletable. A departure can now be removed once no bookings remain — checked against the real booking records rather than a counter that can drift — and departures with bookings are still protected.
* **Dashboard occupancy is no longer 0%:** the dashboard counted only departures inside the selected date range, which excluded the upcoming departures the figure is about, while individual trip pages calculated it correctly.
* **Guest selector on sold-out dates:** the traveller selector stayed usable on a fully booked departure and allowed more guests than the tour's capacity. A sold-out date now starts at 0 with the controls disabled, and the maximum always reflects the seats actually left.
* **Bulk actions no longer report the wrong thing:** choosing departures and pressing Apply without picking an action said *"Please select departures and a bulk action first"*, pointing at the selection rather than the missing action. Each message now names the input that is actually missing (also fixed on Rules, Items, Item Types, Itinerary and Email Templates).
* **Star ratings on the booking confirmation:** half stars never appeared, so a 4.5 rating rendered as 4 solid stars next to the text "4.5". Trip pages and the confirmation page now round identically.
* **Administrators can change a customer's email address:** editable from the customer screen. If the customer can sign in, a confirmation link is sent to the new address and the change applies once confirmed (matching WordPress); customers without an account are updated immediately.
* **Invoices show full addresses:** the customer's postal address is included, and a multi-line company address keeps its line breaks instead of collapsing onto one line.
* **Invoices respect your number and currency settings:** amounts previously always printed as `$1,234.56`, ignoring the configured decimal separator, thousands separator, decimal places and symbol position. Vouchers and itineraries were corrected too.
* **Invoices reflect the payment status:** after an offline payment the invoice stayed *Payment Pending* with nothing paid and the full amount due. Marking a booking paid now settles the amounts and records the payment, so the invoice reads Paid with a zero balance.
* **Customised admin emails are used again:** when a payment arrived the customer received their customised template but the administrator still got the built-in default. Every core email type can now be overridden.
* **Bank transfer details on invoices are translatable:** they reuse the same translations as the booking confirmation page, so translating once covers both.
* **Bank details on the booking confirmation are aligned** with every other row.
* **Payment status can be changed from the bookings list:** an Actions entry for Paid, Partially Paid, Pending and Refunded — useful for bank transfers and other payments received by hand. Marking a booking paid also records it in Payments, so a later payment cannot overwrite it.
* **Always-BCC and per-template CC/BCC:** archive or monitor outgoing mail with a site-wide blind copy, plus optional CC/BCC on any individual template. Nothing is copied until you enter an address.
* **Country flags in every country selector**, including a search box, on checkout and in the admin.
* **Invoice, voucher and itinerary branding:** the White Label module can now supply a company logo and header colour for generated documents.
* **Separate "Partial Payment Received" email:** an optional template with its own wording and remaining-balance details, used only when deposits or partial payments are enabled and the template is switched on.
* Fixed several smaller issues: hidden PHP notices on the departures and customers screens, hardcoded `$` in discount labels and deposit messages, a To address with several recipients being silently mangled, team invitations bypassing SMTP settings, and an admin bundle that could never be cached by the browser.

= 3.0.10 — 15 July 2026 =
* **Tour review structured data (SEO) — fixed the Google Search Console errors:** GSC reported *"Invalid object type for field &lt;parent_node&gt;"*, *"Missing field author"* and *"Missing field itemReviewed"* on tour pages. The cause was the review Microdata — the AggregateRating was nested in a `TouristTrip` (a type Google doesn't support for review snippets), and the whole reviews section was marked as one `Review` with no author/itemReviewed. Microdata can't express this correctly here (the rating is in the hero, the reviews are a separate section, so they can't share one valid parent node), so review structured data is now emitted as **JSON-LD** — Google's recommended format — centrally for every tour page: a `Product` with the tour name, `aggregateRating`, and a `review[]` array where each review carries `author` (Person), `reviewRating`, `reviewBody`, `datePublished` and the review title. The broken Microdata was removed. Tours without reviews keep their previous schema (no incomplete-Product markup). The JSON-LD is `\u`-escaped so review text can never break out of the `<script>` block.
* **Account email address is now editable:** customers can change their account email from **My Account → Profile**. It follows WordPress's own confirmation-link flow — the address is not changed until the customer clicks a link emailed to the **new** address — with **Resend** and **Cancel** actions, a pending-change notice, and a security notice sent to the **old** address once confirmed. All four emails are editable transactional templates.
* **Sold-out departures can no longer be booked:** a sold-out date is now disabled up front instead of only failing at the final checkout step. The button reuses the exact server-side waitlist/capacity rule, so the UI matches what the server will accept; the server guard remains as defense-in-depth.
* **Deposits no longer auto-confirm when Auto-Confirm is off:** paying a deposit/partial now leaves the booking **pending** (status), matching the *Auto-Confirm Bookings* setting, across all payment-completion paths (synchronous gateways, Stripe/generic, PayPal). Deposit-paid bookings are shielded from the pending-expiry cron, so no booking is auto-cancelled after a partial payment. Overridable via the `yatra_confirm_booking_on_payment` filter.
* **reCAPTCHA v3 now works:** invisible, score-based protection is verified **server-side** on each protected form (enquiry, review, booking, registration) and fails closed; the secret key never reaches the browser; the action is validated against the form.
* **Invoice fixes:** the *"Invoice #"* field is no longer empty (derived from the payment id, matching the account page), and the pro-forma invoice shows the booking's **real** payment state — Paid / Partially Paid / Payment Pending — instead of a fixed "Payment Pending".
* **Pro-forma invoice for offline bookings:** bookings paid by Bank Transfer / Pay Later can now download an invoice (previously only card payments produced one); when a balance is due it includes the operator's payment instructions (Yatra Pro fills in the bank-transfer details).
* **Discounts respect the currency:** the *Discount Amount* and *Minimum Booking Amount* fields now show the configured currency symbol and its position.
* **Confirmation & checkout pages no longer leak another page's SEO:** the virtual booking-confirmation / checkout pages no longer inherit an unrelated WordPress page's title/meta (SEO plugins were pulling a colliding page's data).
* **Capacity & occupancy fixes:** a departure's capacity now correctly honours a recurring availability rule when the date carries a time component; the dashboard occupancy no longer reads 0% for every tour; and the Reports *Average Group Size* is computed over the right set of departures.
* **Booking confirmation stars restored:** the star rating on the confirmation page renders again (the CSS was missing), including a proper half-star for e.g. 4.5.
* **Google Calendar:** the target **Calendar ID / Name** chosen in Settings → Integration is now saved and survives a reload (it was silently dropped).
* **Translations:** the plugin's own bundled translations now load correctly from its `i18n/languages` folder (the load path was pointing at a non-existent directory), and all new strings are translatable. Regenerated the translation template (`yatra.pot`).
* Safe to update from 3.0.9 — no database changes and no migrations. Pair with **Yatra Pro 3.0.8**.

= 3.0.9 =
* **Price filter — highest trips are reachable again:** the trip-listing price filter now bounds its Min/Max on **every** price a customer can actually book. Previously the maximum only looked at the base trip price, so trips priced through a per-category (traveler-based) tier or an availability-date / recurring-rule / departure **override** could sit above the slider's top and become impossible to find. The slider can now also land exactly on the true maximum (the range step no longer stops short, e.g. capping €10,000 at €9,909). Bounds are computed only from published, non-deleted trips, so a draft/trashed override can't inflate them.
* **Travel itinerary PDF — correct arrival & departure dates:** the travel-timeline section now shows the actual booked **start** date (arrival) and **end** date (departure) instead of repeating the same date twice. Falls back to the trip duration only when no stored end date exists, matching the booking's inclusive end-date calculation.
* **Wishlist login goes to My Account:** the "Login" action in the wishlist popup (trip listing and single-trip pages) now sends guests to the configured **My Account** page (Settings → Permalink slug) instead of the raw WordPress login screen.
* **Guest checkout / authentication:** "Logged in as…" no longer appears for guests during checkout; the "Sign In" secondary action on the email-verification / verified pages is shown only when an account is actually part of the flow (registration enabled and guest checkout off); and guest email verification uses the configured, editable email template.
* **Admin fixes:** the Field ID input in the Booking Form builder no longer closes the editor after every keystroke; clearing a number in Payment Settings no longer snaps back to the previous value; the Email Template form shows a clear empty-state when no events are available.
* **Translations:** account field labels (Traveler, Date of Birth, Email, Nationality), the PayPal redirect message, the "Processing…" button state, and the traveler-count / group-discount summary text are now translatable, with the JavaScript `sprintf` shim hardened so number placeholders (`%d`/`%s`) always resolve. The customer account pages' count labels — e.g. "1 Traveler" and the saved-trip review count — now translate too (they used a JS plural form the build couldn't extract from the minified account bundle, so they stayed English; rebuilt to an extractable form). Regenerated the translation template (`yatra.pot`).
* **Build integrity:** added an asset-integrity check to the build and CI so a desynced/missing lazy-loaded admin chunk can never ship (the cause of a blank Settings page after an update).
* **Timezone-safe dates & inclusive durations:** an availability card's "Duration" is now derived from that card's own departure→return span, so it can never contradict the dates shown beside it (a Jun 25 → Jul 4 window reads **10 Days**, not 9); the availability editor's duration check counts inclusively (both endpoints); and the Travel Voucher / payment-receipt PDFs show the correct **return date** — the booking's stored end date when present (so a flexible window or a duration changed after booking is honoured), otherwise departure + duration − 1 (matching the booking's inclusive end date). Several admin displays that could show a date one day early in timezones behind UTC — the booking list & details travel date, enquiry travel date, dashboard Recent Bookings & Pending Payments, discount expiry, license expiry and the dashboard month chart — now parse date-only values as local calendar days. Normal availabilities (where the return equals departure + duration − 1) are unaffected.
* **International phone fields:** phone inputs on the booking form now show a searchable country selector with **flag + dial code** on the left and the number on the right. Pasting a full international number (e.g. `+9779806015400`) auto-detects the country (Nepal) and stores the number with its country code. All 243 dialling countries are included with crisp per-country SVG flags (lazy-loaded). The widget is on by default; the Pro dynamic form builder adds a per-field **"Show country code"** toggle. Existing saved numbers are never rewritten — a legacy national-only number renders exactly as stored. Booking details show the flag + full number.
* **Admin traveller dates follow the global date format:** the Travellers list (Travel Date) and the booking-details **Date of Birth** now use the site's configured date format instead of the browser locale, and parse date-only values as local calendar days (no off-by-one).
* **Stripe checkout & webhook setup:** when only Card is enabled, the redundant "Payment methods → Card" chooser is hidden and the card field shows on its own. The Stripe settings panel now shows the exact **Webhook Endpoint URL** for your site with a **Copy** button and a mode-aware "Open Stripe → add this endpoint" link, so the webhook is no longer guesswork.
* **Email notifications:** manually changing a booking's **payment status** to Paid/Partial (e.g. confirming an offline bank transfer) now sends the customer a Payment Confirmation and the admin a Payment Received email, and no longer logs an "Undefined array key data" warning. A guest booking that requires **email verification** now sends its booking-confirmation email once the customer verifies (it was previously dropped).
* Safe to update from 3.0.8 — no database changes and no migrations. Pair with **Yatra Pro 3.0.7**.

**Older versions:** the full history is in [changelog.txt](https://plugins.svn.wordpress.org/yatra/trunk/changelog.txt).

== Upgrade Notice ==

= 3.0.8 =
Release **3.0.8** — new XML sitemap for trips, destinations, activities and categories (integrated with WordPress core, Yoast, Rank Math and All in One SEO, advertised in robots.txt), Additional Services percentage-pricing fix, Bank Transfer / deposit fix on guest and waitlist checkout, and broader translation coverage. No database changes — safe to update from 3.0.x.

= 3.0.4 =
Release **3.0.4** — Unicode / Cyrillic slug support end-to-end, pricing single-source-of-truth (sidebar = payment-gateway amount), pricing summary cleanup, services dedupe fix, Loco script-translation fallback so React surfaces (account page, admin) pick up `.json` translations from Loco's workspace, mobile sticky-bar JS extraction, FSE template support, and CI pipeline fixes. Safe to update from 3.0.3.

= 3.0.3 =
Release **3.0.3** (`[yatra_trip_category]` shortcode, versioned upgrades, discounts, single-trip and admin polish). Safe to update from 3.0.2.x.

= 3.0.2.5 =
Maintenance release (setup wizard autosave, admin notices). Safe to update from 3.0.2.4.

= 3.0.2.4 =
Bugfix release (trip permanent-delete REST endpoint, bulk trip confirmation UX). Safe to update from 3.0.2.3.

= 3.0.2.3 =
Maintenance update (admin UX, REST license route, trip list stability in Departures/Availability). Safe to update from 3.0.2.2.

= 3.0.2.2 =
Patch release. Safe to update from 3.0.2.1.

= 3.0.2.1 =
Readme update (Pro feature links to pricing). Safe to update from 3.0.2.

= 3.0.2 =
Readme / documentation listing update only. Safe to update from 3.0.1.

= 3.0.1 =
Maintenance update (banner, WordPress.org readme/assets, and small fixes). Safe to update from 3.0.0.

= 3.0.0 =
Major release. Back up your site and database before upgrading from 2.x. Update free Yatra from WordPress.org first; then align **[Yatra Pro](https://wpyatra.com/pricing/)** with a version compatible with 3.0.

== 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](https://github.com/MantraBrain/yatra)

If Yatra helps your business, a ⭐ **five-star review** on WordPress.org and considering **💎 [Yatra Pro](https://wpyatra.com/pricing/)** when you need paid features both help sustain development. Thank you for using Yatra.