Title: Yatra – Travel Booking & Tour Operator Software
Author: MantraBrain
Published: 10 gegužės, 2019
Last modified: 7 spalio, 2026
---
Ieškoti įskiepiuose
# Yatra – Travel Booking & Tour Operator Software
Autorius [MantraBrain](https://profiles.wordpress.org/mantrabrain/)
[Parsisiųsti](https://downloads.wordpress.org/plugin/yatra.3.0.17.zip)
* [Informacija](https://lt.wordpress.org/plugins/yatra/#description)
* [Atsiliepimai](https://lt.wordpress.org/plugins/yatra/#reviews)
* [Diegimas](https://lt.wordpress.org/plugins/yatra/#installation)
* [Kūrimas](https://lt.wordpress.org/plugins/yatra/#developers)
[Pagalba](https://wordpress.org/support/plugin/yatra/)
## Aprašymas
**✈️ 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)**.
#### ✈️ 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`, `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](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](https://lt.wordpress.org/plugins/yatra/mantrabrain@gmail.com?output_format=md)**—
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.
### 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.
## Ekrano nuotraukos
[⌊Trip pages that sell themselves — gallery, duration, season and a sticky "Book
Now" price button on any theme⌉⌊Trip pages that sell themselves — gallery, duration,
season and a sticky "Book Now" price button on any theme⌉[
Trip pages that sell themselves — gallery, duration, season and a sticky „Book Now”
price button on any theme
[⌊Book in a few taps, no redirects — live departure availability, traveller count
and enquiry, all inline⌉⌊Book in a few taps, no redirects — live departure availability,
traveller count and enquiry, all inline⌉[
Book in a few taps, no redirects — live departure availability, traveller count
and enquiry, all inline
[⌊Your whole operation at a glance — bookings, revenue and upcoming departures the
moment you log in⌉⌊Your whole operation at a glance — bookings, revenue and upcoming
departures the moment you log in⌉[
Your whole operation at a glance — bookings, revenue and upcoming departures the
moment you log in
[⌊Every trip in one organised list — search, filter by status, and see pricing,
type and availability instantly⌉⌊Every trip in one organised list — search, filter
by status, and see pricing, type and availability instantly⌉[
Every trip in one organised list — search, filter by status, and see pricing, type
and availability instantly
[⌊Build a complete trip in one place — basics, pricing, itinerary, media and SEO,
guided step by step⌉⌊Build a complete trip in one place — basics, pricing, itinerary,
media and SEO, guided step by step⌉[
Build a complete trip in one place — basics, pricing, itinerary, media and SEO,
guided step by step
[⌊Never lose track of a reservation — filter by traveller, payment state and status
across every departure⌉⌊Never lose track of a reservation — filter by traveller,
payment state and status across every departure⌉[
Never lose track of a reservation — filter by traveller, payment state and status
across every departure
[⌊Full booking detail, one-click invoice — payment summary, traveller records and
a downloadable invoice⌉⌊Full booking detail, one-click invoice — payment summary,
traveller records and a downloadable invoice⌉[
Full booking detail, one-click invoice — payment summary, traveller records and
a downloadable invoice
[⌊Every transaction accounted for — Stripe, PayPal, bank transfer and manual payments
in one ledger⌉⌊Every transaction accounted for — Stripe, PayPal, bank transfer and
manual payments in one ledger⌉[
Every transaction accounted for — Stripe, PayPal, bank transfer and manual payments
in one ledger
[⌊Run offers without spreadsheets — coupon codes with usage limits, expiry dates
and live status⌉⌊Run offers without spreadsheets — coupon codes with usage limits,
expiry dates and live status⌉[
Run offers without spreadsheets — coupon codes with usage limits, expiry dates and
live status
## Blokai
Šis įskiepis suteikia 4 blokus.
* Trip categories Display trip category cards with trip counts and pricing (same
layout as destinations).
* Destination Display destination listings with customizable options
* Trip Display trip listings with customizable options
* Activity Display activity listings with customizable options
## Diegimas
🛠️ **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)).
## DUK
### 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/)**.
## Atsiliepimai
### [Great plugin, responsive support and active development](https://wordpress.org/support/topic/great-plugin-responsive-support-and-active-development/)
[vistatours](https://profiles.wordpress.org/vistatours/) 2 rugsėjo, 2026
No tool or software is perfect from the very beginning, and Yatra is no exception.
But for me, what really matters is how a developer responds when issues, bugs or
suggestions come up. During my time using Yatra, I have reported several bugs and
shared feedback about things that could be improved. The team has always responded
quickly, taken my reports seriously and worked on solutions in a very timely manner.
What I particularly appreciate is that I no longer feel like I am simply using a
finished product and reporting problems from the outside. There is a real sense
of actively working together to improve the product, and that my feedback as an
actual user is heard and valued. Yatra already provides the functionality I need
for managing tours and bookings for Vista-Tours, and seeing the plugin continue
to improve through this kind of communication gives me a lot of confidence in its
future. For me, good software is not software that never has a bug. It is software
with developers behind it who listen, react and continuously make it better. Five
stars, well deserved.
### [The best tour plugin ever](https://wordpress.org/support/topic/the-best-tour-plugin-ever/)
[basolene](https://profiles.wordpress.org/basolene/) 12 gegužės, 2026
I like the way Yatra plugin organizes the tours on the page and the way the elements
are organized on the tour card
### [Clearly the Best Travel Plugin I Tested](https://wordpress.org/support/topic/clearly-the-best-travel-plugin-i-tested/)
[Just a test](https://profiles.wordpress.org/justmikehere/) 29 balandžio, 2026
I’m very satisfied with the Yatra plugin. I tested multiple travel and booking plugins,
but Yatra clearly stood out as the best option. It offers more features than the
others and provides a solid, well-structured solution for building a travel website.
What I appreciate most is the support. Instead of slow email responses, they offer
live chat support where you can speak directly with someone in a professional and
helpful way. This makes a big difference and shows they take their users seriously.
The pricing is also very fair. Unlike other plugins that require expensive monthly
subscriptions, Yatra offers great value for money without unnecessary ongoing costs.
Overall, a high-quality plugin with excellent support. Highly recommended.
### [Support is Horrible](https://wordpress.org/support/topic/support-is-horrible/)
[jerryrveal](https://profiles.wordpress.org/jerryrveal/) 5 liepos, 2024 1 reply
I have been trying to get several features finalized and it has been 2 months now
that I have been waiting for a response. I have followed up with no reply. This
software has some major challenges in the payments area and I would caution anyone
looking at this to make sure you do a lot of testing to make sure it meets your
needs. Something as simple as a flat deposit by person is what I am looking for
and it is not available. I will be trying to get my money back.
### [Best!](https://wordpress.org/support/topic/best-1295/)
[gaenat](https://profiles.wordpress.org/gaenat/) 8 gegužės, 2024
Best plugin and amazin support!
### [Is anyone there?](https://wordpress.org/support/topic/is-anyone-there-5/)
[moiraskitchen](https://profiles.wordpress.org/moiraskitchen/) 20 gegužės, 2023
2 replies
Was unable to purchase a license after trying with 4 different cards. Was unable
to reach anyone at the company via their chat plugin despite the mention that there
are staff online. Support forum goes to a dead page. I would avoid. I cannot even
verify they are a going concern. Their competitors seem to be more responsive.
[ Perskaityti visus atsiliepimus (23) ](https://wordpress.org/support/plugin/yatra/reviews/)
## Programuotojai ir komandos nariai
“Yatra – Travel Booking & Tour Operator Software” yra atviro kodo programa. Prie
jos sukūrimo prisidėję žmonės surašyti toliau.
Autoriai
* [ MantraBrain ](https://profiles.wordpress.org/mantrabrain/)
Įskiepis “Yatra – Travel Booking & Tour Operator Software” išverstas į 1 kalbą.
Dėkojame [vertėjams](https://translate.wordpress.org/projects/wp-plugins/yatra/contributors)
už jų darbą.
[Išverskite “Yatra – Travel Booking & Tour Operator Software” į savo kalbą.](https://translate.wordpress.org/projects/wp-plugins/yatra)
### Domina programavimas?
[Peržiūrėkite kodą](https://plugins.trac.wordpress.org/browser/yatra/), naršykite
[SVN repozitorijoje](https://plugins.svn.wordpress.org/yatra/), arba užsiprenumeruokite
[kodo pakeitimų žurnalą](https://plugins.trac.wordpress.org/log/yatra/) per [RSS](https://plugins.trac.wordpress.org/log/yatra/?limit=100&mode=stop_on_copy&format=rss).
## Pakeitimų istorija
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.17 — 7 October 2026
**New**
* **Choose what happens to your data when Yatra is removed.** A new Uninstall
section in Settings, after Advanced, carries a single switch: _Delete all data on
uninstall_. It is off, so deleting the plugin leaves every trip, booking and customer
in place and reinstalling picks up where you left off. Switch it on and deleting
Yatra removes its tables, settings, scheduled tasks and user meta for good — leaving
Yatra Pro’s own settings and scheduled work alone for as long as Pro is still installed,
so removing one plugin never half-removes the other — the screen says so plainly
before you save, and Yatra Pro follows the same switch for its own data. Deactivating
never removes anything either way. * **Kids-friendly and the other age filters can
be re-tuned.** The age each band covers was fixed in the code — kids-friendly meant„
12 and under” and nothing could change it. The four bands now come from one place
and a site can set its own: `add_filter( 'yatra_age_suitability_thresholds', fn(
$t ) => $t + [ 'kids_max' => 17 ] );`. The filter chips and the trips they return
always agree, which they could previously drift apart on.
**Fixed**
* **Review request emails could go out in one large batch, long after
the trip.** The request was scheduled for a fixed number of days after a booking
was _marked completed_, which is not the same as days after the trip. The nightly
sweep that completes finished tours can work through a backlog in one run, so customers
whose trips had ended weeks or months earlier were all asked to review on the same
night. The request is now timed from the date the trip ended, and a trip that finished
longer ago than the new _Don’t ask about trips older than_ setting (14 days by default)
is never asked about at all. Requests for trips ending on the same day are spread
over an hour rather than sent in one burst, and any reminders already queued by
an earlier version for trips that are now too old are cleared on update. Both the
delay and the age limit are configurable under Settings Review, and via the `yatra_review_reminder_days`
and `yatra_review_reminder_max_age_days` filters. * **Traveller categories, attributes
and itinerary item types were never exported.** The classifications table holds
eight kinds of entry and a backup only ever contained four of them, so traveller
categories, trip attributes, itinerary item types and itinerary items were silently
missing from every export — and the trip links pointing at them could not resolve
on import either, which quietly dropped a further 157 trip-to-classification links
on the site this was tested against. All eight are now exported and restored. * **
Restoring a backup onto a new site lost everything belonging to a Pro module that
had not been switched on.** Yatra Pro creates each module’s tables when that module
is enabled, so on a fresh install the tables for Email Automation, Dynamic Pricing,
Consent Forms and Additional Services do not exist yet, and every row destined for
them was counted as a failure and discarded — 2,440 rows on the migration this was
tested against, including the entire email history, pricing history and template
set. The import now makes sure those tables exist before it writes. Whether you
switch the modules on afterwards is a separate decision from whether your data survived
the move. * **A re-import looked like it had done nothing.** The import summary
only ever showed what it brought in and what failed, never what it recognised as
already present. Importing a backup into the site it came from is supposed to bring
in nothing — every row is already there — so the screen filled with zeroes and a
red failure count, and read as a broken import. It now reports what was imported,
what was already here, and what could not be linked, and says plainly when a file
was already fully present. Rows that reference a record the file does not contain
are no longer called failures: they are listed as „not linked”, because that is
what they are — usually something deleted on the original site. Data-type names
with more than one underscore no longer render as „Email Sequence_steps”. * **Review
request emails are now off until you switch them on.** They were enabled on every
new install. A review request is the one transactional email that is not a reply
to something the customer just did, and several jurisdictions treat it as advertising
rather than service mail — in Germany the Federal Court of Justice (VI ZR 225/17)
holds that it needs prior consent, and the existing-customer exemption does not
cover it. New sites therefore start with it off, so you can turn it on once you
have decided how you collect that consent. **Sites that already have it switched
on are unchanged.** * **The Email Logs missed everything Yatra itself sent.** Only
the Pro automation and abandoned-booking modules wrote to the log, so a booking
confirmation or a review request sent by Yatra’s own templates left no record, and
operators searching for an email a customer had received found nothing. Those sends
are now logged too, marked as coming from Yatra core, with no duplicate entry for
the emails Pro already records. * **Translated admin screens stayed in English unless
a JS translation file happened to exist.** The React admin could only read translations
from a script-translation JSON file. Translations from WordPress.org ship one, but
a site translated by hand — with Loco Translate, or a .po/.mo dropped into wp-content/
languages — has only the PHP catalogue, so every label, button and message in the
admin stayed English no matter how complete the translation was. Yatra now hands
those translations to the admin itself when no JSON file is present. Sites running
in English are unaffected and carry no extra weight. * **Adding an availability
date that already existed crashed the screen.** The date is unique per trip, departure
date and time, so the second attempt was rejected by the database — and because
the rejection was never checked, the code tripped its own return type and raised
a fatal error. Operators saw „There has been a critical error on this website” and
the Availability screen went blank. It now says _„Availability date already exists
for the selected departure”_ and the screen stays usable. The same check covers
editing a date onto a slot another date already holds, which previously reported
success while quietly changing nothing. * **Importing the same file twice duplicated
everything.** Import gave every row a fresh id, so a second run doubled trips, bookings,
discounts, availability and itineraries, while anything with a unique column was
rejected outright — on one site every customer failed to import because their email
addresses were already present. Import now recognises what the site already has
and brings in only what is missing, so running it twice leaves you where the first
run finished. That covers destinations, activities, categories and difficulty levels,
which a second run used to re-add under renamed slugs, as well as service, consent-
form and pricing-rule catalogues. Sent-email history is the one exception and is
still appended, because two genuinely separate emails can look identical and skipping
them would lose records from a restore. * **Importing could leave trip and category
links pointing nowhere.** Restoring settings also restores the permalink bases,
but the rules behind the URLs were not rebuilt, so trips and categories stopped
resolving until someone re-saved Settings Permalinks. The rules are now rebuilt
on the next page load. * **„1 Trips” on activity, destination and category listings.**
Those three templates always used the plural, so a single result read as „1 Trips”—
and in a translated site, „1 Reizen”. The count now picks singular or plural, and
translators get a proper singular to fill in. * Import no longer probes Yatra Pro’s
email-template and consent tables on sites where those modules have never been enabled,
which logged a database error for every row imported.
#### 3.0.16 — 24 September 2026
**Please read if you use reCAPTCHA.** With reCAPTCHA switched on for the booking
form, checkout could not be completed on Stripe, Square or Authorize.net — the card
form showed „reCAPTCHA verification failed. Please try again.” and the payment never
went through. Lowering the score threshold did not help, because no token was being
sent at all. This release fixes that; if you turned reCAPTCHA off to take payments,
you can turn it back on.
**New**
* **Download a booking’s invoice from the dashboard.** Bookings ⋮ _Download
invoice_, and a _Download invoice_ button on the booking detail, produce a PDF for
the whole booking rather than for a single payment. Available to anyone who can
view bookings. * **Exclude a whole period from a recurring rule.** Trip Availability
Recurring Rules gains **Excluded Periods**: give a first and last day and the rule
skips everything in between, instead of adding a business vacation one day at a
time. The existing single-date exclusions are unchanged and the two can be mixed.***
Choose what goes in the sitemap.** Settings SEO _Content in the sitemap_ lets
you publish only the types you want — trips, destinations, activities, trip categories,
listing pages. Leaving a type out of the sitemap does not stop search engines indexing
it, so there is a separate, deliberately opt-in **Also add noindex to excluded types**.
It is off by default, because switching it on removes those pages from search results.***
Google Calendar controls** (with Yatra Pro). The Google Calendar screen gains _Resync
Everything_, which walks every booking in batches and repairs the calendar in one
click; an **Event reminders** editor so the 7/3/1-day reminders are no longer fixed;**
Add customers as guests**, which keeps the customer’s address off the event entirely
so Google sends them no reminders or cancellations; and **One event per departure**,
which puts every booking on the same departure into a single event with each booking’s
details in the description. The last one is off by default.
**Fixed**
* **reCAPTCHA blocked checkout.** Gateways that handle the card themselves(
Stripe here, Square and Authorize.net in Pro) submit the booking directly, so they
never attached a reCAPTCHA token and the server rejected every attempt. Each now
sends its own fresh token. The account-registration form on the booking page had
the same gap and is fixed too. * **Excluded dates were still bookable.** A date
excluded from a recurring rule disappeared from the calendar but could still be
booked by posting that date directly, because the resolver fell through to the trip’s
default availability. Excluded dates are now refused at checkout. An explicit availability
row for that date, or another rule that generates it, still opens it as before. ***
Availability times were demanded for tours that have none.** Adding or editing an
availability date on a single-day tour insisted on a start and end time even when
the tour has no time slots configured, so the date could not be saved. Times are
now required only for day tours that actually use time slots, arrival time is always
optional, and every field says whether it is required. The capacity field also stops
overwriting a value you have already typed, and its help text names the tour’s own
maximum. * **Invoices and emails named the gateway, not its title.** Payment details
showed the internal gateway id (`bank_transfer`) instead of the title your customers
see at checkout („Bank Transfer”). The payment invoice, the booking invoice, payment
emails and the booking confirmation page now all use the checkout title, falling
back to a readable version of the id for a gateway that no longer exists. * The
sitemap is rebuilt as soon as you change what it contains, instead of waiting up
to an hour for its cache to expire.
#### 3.0.15 — 15 September 2026
_With thanks to [Vista-Tours](https://vista-tours.de) for detailed testing and feedback._
**Please read before updating — three things start happening that did not before:**
***
Pre-trip reminder emails send again.** The reminder sweep was never scheduled and
had no handler, and its booking query referenced a database column that does not
exist, so no reminder has gone out. Both are fixed. Check the _Trip Reminder_ template
under Settings Emails, or set _Booking Reminder (days)_ to `0` to keep it off. ***
Unpaid bookings are cancelled automatically** after _Settings Booking Booking
Expiry (hours)_ (default 24) — that setting previously did nothing at all. Only
bookings created after you update are ever expired, so your existing pending bookings
are never cancelled retroactively. Expiring a booking now also releases its departure
seat. Set the hours to `0` to disable. * **Cancelling a booking now notifies your
integrations.** `yatra_booking_cancelled` was never fired in-app, so Google Calendar
kept cancelled bookings on the calendar and WhatsApp / webhook cancellation events
never ran. Review those templates first.
**New**
* **Day trips show hours.** A single-day tour with a duration in hours
now reads „8 hours” instead of „1 Day” everywhere — trip cards, hero, quick facts,
availability dates, checkout, the confirmation page and email, saved trips, and
the voucher / itinerary PDF. * **Configurable booking horizon.** _Settings Booking
Booking horizon (months)_ controls how far ahead customers can book (1–36, default
12); it was hard-coded to 12. * **Quick status changes for enquiries.** The Enquiries
list’s ⋮ menu gains Mark as Completed / Closed / Spam, so an enquiry can be handled
without opening it. * **Auto-Confirm Bookings becomes a three-way choice** — don’t
auto-confirm, online payments only, or all. * **Compact listing card layout** for
trip archives, shortcodes and the Trip block. * **Per-trip booking forms and per-
trip email templates (with Yatra Pro).** Settings Booking Form gains a **Conditions**
button (Pro Dynamic Form Field) so selected trips, categories or trip types can
use their own version of each form; Email Templates gains **Override templates**(
Pro Email Automation) — a trip-specific version of any booking email, sent _instead
of_ the global one. The free plugin ships the editors, a trip-aware `GET /settings/
booking-form?trip_id=` endpoint, `trip_id` in every booking email’s merge variables,
and the `yatra_booking_form_config( $config, $tripId )` filter; without Pro nothing
changes. * **Payments card on the booking detail** listing every payment recorded
against the booking (amount, method, date, reference, status).
**Fixed**
* **A manually recorded payment now counts.** _Payments Add New Payment_
defaulted to _Pending_ and offered a _Partial_ status the database does not have,
so a deposit recorded by hand never increased the booking’s paid amount, never reduced
the balance and triggered nothing. The form now defaults to **Completed**, _Partial_
is gone, and a payment that becomes Completed (recorded, edited or _Mark as Completed_)
fires `yatra_payment_completed` exactly like an online payment — payment-received
emails, Pro `payment.partial_received` / `payment.received` automations, webhooks
and WhatsApp — once per payment. * **Partial payments used the wrong email on Pro
sites.** With the Pro _Partial Payment Received_ template switched on, a deposit
still went out as the full _Payment Received_ email (`payment.received`); the chooser
only honoured the free plugin’s own toggle. It now honours the active Pro template,
so a payment that leaves a balance sends the partial template and event. * **Language
metadata followed the plugin, not the site.** Trip and listing pages printed `og:
locale="en_US"`, `hreflang="en-US"` and `inLanguage="en-US"` on every site; they
now follow the WordPress locale (`de_DE` / `de-DE` on a German site, including _Deutsch(
Sie)_). * **Empty 360° tour and video modals were injected into every page** by `
tour-viewer.js` / `video-player.js` (an empty `h3.yatra-tour-viewer-title` on the
homepage, for example). Both are now built on first use only. YouTube _Shorts_ URLs
now embed correctly. * _Resend Booking confirmation_ on a **completed** booking
sends the „Booking confirmed” email, not the pending-wording one. * Booking Form
settings are now sanitised on save (the structured sanitiser was unreachable); the
storefront date-pricing request no longer returns HTTP 500 on trips with date-specific
departures; Edit Booking no longer hits a 401 loading tax settings. * **Duration(
Hours) can now be saved.** The trip form showed the field for single-day tours but
never included it in the save request, so the value was dropped and the field reloaded
empty — the new hours display could not be used. Switching a trip back to multi-
day now clears any stored hours rather than leaving a stale value. * Departures:
_Upcoming_ no longer hides sold-out departures; capacity is a separate **Availability**
filter; the list is genuinely paginated and its search box works. * Enquiries: the
status tabs showed `0` for every count; the bulk _Mark as Completed_ action silently
did nothing; a submission containing a `subject` field returned a server error. *
The confirmation email is sent when a gateway payment auto-confirms a booking, and
_Resend Booking confirmation_ resends the right template. * Gateways honour the
Auto-Confirm setting instead of always confirming. * The „Payment not completed”
notice can now be translated.
#### 3.0.14.2 — 31 August 2026
* **Fresh installs now create the trips table correctly:** a semicolon inside a
column comment broke the `wp_yatra_trips` table creation during dbDelta, so a
brand-new install could end up without the trips table — the tour list and sample-
data import then failed. Existing sites were unaffected; updating recreates the
table automatically.
#### 3.0.14.1 — 31 August 2026
* Declared compatibility with WordPress 7.1.
#### 3.0.14 — 31 August 2026
_With thanks to [Vista-Tours](https://vista-tours.de) for extensive beta testing
and the detailed feedback behind many of the fixes in this release._
* **Resend booking and payment emails by hand:** administrators can now re-send
a booking’s confirmation, payment, cancellation, reminder and completed emails—
and the admin copies — from the booking view, after a manual change or when an
automated email failed to arrive.
* **Set a day tour’s length in hours:** a single-day trip can carry a duration
in hours (for example an 8-hour experience). The tour then shows its length in
hours, and — with Yatra Pro — Google Calendar creates a same-day timed event
of that length instead of an all-day, multi-day one.
* **Dashboard capacity and occupancy match the Departures page:** the dashboard
now reads capacity from your Availability configuration, exactly like Departures,
so the two no longer disagree. Legacy „unlimited” capacity markers left on old
departures are normalised, and a fully-booked upcoming tour stays visible on
the dashboard instead of dropping out of the list.
* **Star rating on the booking confirmation shows the right colour:** the rating
stars rendered all grey on the confirmation page because a stylesheet was not
loaded there; the correct colours are now applied.
* **Cancelling a gateway payment returns to a working page:** cancelling PayPal(
or any gateway) under a custom booking page led to a 404. Cancel and failure
now land on the booking-confirmation page with a clear „payment not completed”
notice.
* **Offline gateways are never auto-completed:** Bank Transfer and Pay Later bookings
could be marked paid automatically; they now stay pending until you confirm the
payment by hand.
* **Correct decimal separator in payment amounts:** amounts formatted wrongly on
some European browsers; currency now formats consistently from your store settings.
Invoices also use the booking reference as the invoice number.
* **Completed (past) departures stay visible** in the tour list and the Past tab,
independent of when the daily maintenance runs; **bulk-deleting departures**
works from the all-tours view; and a new optional **date filter** in trip search
and listings lets visitors find tours available on or after a chosen date.
* **Changing a booking’s tour moves its departure with it,** releasing the seat
from the old departure and reserving it on the new one.
* **Global „Always BCC” address can be saved:** the field under Settings Email
accepted an address but never stored it. It now saves, and accepts several comma-
separated addresses.
* **The email template list opens on the Active view,** so disabled or unused templates
stay decluttered out of sight; the All and Inactive tabs remain available to
review or re-enable them.
#### 3.0.13 — 21 July 2026
* **Star ratings now match the number shown:** a 4.9 average drew four-and-a-half
stars beside the printed „4.9”. Ratings round to the nearest half star everywhere—
trip pages, the reviews block, listing cards and the booking confirmation all
draw the same rating identically.
* **Dashboard occupancy is no longer stuck at 0%:** the dashboard ignored the capacity
figures the departures list actually returns, so every tour showed 0% occupied
and available seats could read as a negative number, while the individual trip
page calculated it correctly from the same departures.
* **Departures honour the seats set on a time slot:** a private tour whose vehicle
holds 9 passengers but sells a single booking unit per departure still showed
9 available. Capacity defined on a time slot is now used everywhere it applies,
and where a date has several departure times each one uses its own seat count
instead of the day’s total.
* **Sold-out dates no longer accept bookings:** a date marked sold out could still
be booked, because the seat check looked past the sold-out record and fell back
to the tour’s overall capacity. Sold-out dates are now refused at checkout, or
offered as a waitlist where the waitlist is enabled.
* **Choose how sold-out dates appear:** a new _Show sold-out dates_ option under
Settings Booking. Leave it on to keep them on the calendar marked „Sold out”(
needed for the waitlist), or turn it off to hide them entirely, the way blocked
dates are hidden. Existing sites are unchanged.
* **Dates marked unavailable are hidden and unbookable:** an unavailable date stayed
visible and could still be booked, unlike blocked, closed and cancelled dates.
* **Manual payments recorded the wrong currency:** a payment added by hand was
saved as USD regardless of the store currency, so a euro shop saw dollar amounts
sitting beside correctly-formatted euro ones. Existing payment records are left
as they are; new ones follow the store currency.
* **Payment methods are labelled consistently:** the Payments list printed whatever
each record happened to store, so gateway payments showed „paypal” while hand-
entered ones showed „PayPal” or „Credit Card”. Every row now shows the gateway’s
proper name.
* **Changing the number of participants is saved:** editing the traveller count
on an existing booking had no effect — the booking was saved with the original
count, because the number was read from the traveller list rather than the field.
Changing it now adds or removes traveller entries to match.
* **Confirming a booking from the edit screen sends the confirmation email:** moving
a booking to Confirmed from the booking editor saved the status but sent nothing
and triggered no automation, while doing the same from the status action worked.
Both routes now behave identically — and cancelling from the editor releases
the seats, which it previously did not.
* **Backend bookings reduce availability on tours with several departures a day:**
a booking added from the admin never said _which_ departure it was for, so on
a tour running more than one departure a day it reserved no seats and the frontend
still showed the date as free. The booking screen now asks for the departure
time whenever the chosen date runs more than one, and the seats come off that
departure.
* **Invoices and vouchers show the complete business address:** only the street
line was printed, so the town, postcode and country were missing from every document.
All the address fields you have filled in are now included.
* **The dashboard no longer goes blank:** a payment with no date threw an error
that took the whole dashboard down with it. Dates that are missing or unreadable
now simply render as „-” anywhere in the admin.
* **Choosing a trigger event when creating an email template:** the template panel
showed the event as a read-only badge with nothing to change it, directly beneath
text asking you to pick one. It is now a working dropdown listing every available
event.
#### 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 ”_, _„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 `