Title: Yatra &#8211; Travel Booking &amp; Tour Operator Software
Author: MantraBrain
Published: <strong>10 ພຶດສະພາ 2019</strong>
Last modified: 21 ກໍລະກົດ 2026

---

ຄົ້ນຫາປລັກອິນ

![](https://ps.w.org/yatra/assets/banner-772x250.png?rev=3505714)

![](https://ps.w.org/yatra/assets/icon-128x128.png?rev=3505701)

# Yatra – Travel Booking & Tour Operator Software

 ໂດຍ [MantraBrain](https://profiles.wordpress.org/mantrabrain/)

[ດາວໂຫຼດ](https://downloads.wordpress.org/plugin/yatra.3.0.13.zip)

 * [ລາຍລອຽດ](https://lo.wordpress.org/plugins/yatra/#description)
 * [ການຣີວິວ](https://lo.wordpress.org/plugins/yatra/#reviews)
 *  [ການຕິດຕັ້ງ](https://lo.wordpress.org/plugins/yatra/#installation)
 * [ການພັດທະນາ](https://lo.wordpress.org/plugins/yatra/#developers)

 [ການຊ່ວຍເຫຼືອ](https://wordpress.org/support/plugin/yatra/)

## ຄຳອະທິບາຍ

**✈️ Yatra** ແມ່ນ **ປລັກອິນຈອງການທ່ອງທ່ຽວ WordPress** ທີ່ສ້າງຂຶ້ນສຳລັບ **ຜູ້ປະກອບ
ການທົວ, ຜູ້ໃຫ້ບໍລິການກິດຈະກຳ, ບໍລິສັດທ່ອງທ່ຽວ ແລະ ທຸລະກິດການຜະຈົນໄພ** ທີ່ຕ້ອງການ
ລະບົບຈັດການທົວແທ້ໆ — ບໍ່ແມ່ນຮ້ານຄ້າທົ່ວໄປ. ເວີຊັນຟຣີແມ່ນລະບົບຈັດການການຈອງທີ່ຄົບຖ້ວນ:
ທົວ, ວັນທີຫວ່າງ, ການຊຳລະເງິນ, ຂໍ້ມູນລູກຄ້າ, ອີເມວແຈ້ງເຕືອນ ແລະ ພື້ນທີ່ບັນຊີລູກຄ້າ.**
[Yatra Pro](https://wpyatra.com/pricing/)** ຈະປົດລັອກ [ຊ່ອງທາງການຊຳລະເງິນລະດັບພຣີມຽມ](https://wpyatra.com/pricing/)
ພ້ອມກັບ [20 ໂມດູນ Pro](https://wpyatra.com/features/) ທີ່ທ່ານສາມາດເປີດໃຊ້ໄດ້ຕາມການ
ເຕີບໂຕຂອງທຸລະກິດ — ຕັ້ງແຕ່ [Channel Manager (Viator + GetYourGuide)](https://wpyatra.com/features/channel-manager/)
ໄປຈົນເຖິງ [AI Assistant](https://wpyatra.com/features/ai-assistant/), [White Label](https://wpyatra.com/features/white-label/)
ແລະ [ການແຈ້ງເຕືອນຜ່ານ WhatsApp](https://wpyatra.com/features/whatsapp/).

**ເວັບໄຊທາງການ:** 🌐 [wpyatra.com](https://wpyatra.com/) · 📖 [docs.wpyatra.com](https://docs.wpyatra.com)·
💳 [ລາຄາ](https://wpyatra.com/pricing/) · ✨ [ຄຸນສົມບັດທັງໝົດ](https://wpyatra.com/features/)·
🎯 [ເວັບໄຊຕົວຢ່າງ](https://demo.wpyatra.com/) · 💬 [ຟໍຣຳຊ່ວຍເຫຼືອ](https://wordpress.org/support/plugin/yatra/)

#### 🎬 ເບິ່ງການເຮັດວຽກຂອງ Yatra

🎥 ເບິ່ງວິດີໂອແນະນຳ Yatra ໃນ YouTube — ທົວ, ການຈອງ, ການຊຳລະເງິນ ແລະ ບັນຊີຜູ້ໃຊ້ໃນ
ເວລາບໍ່ຮອດຫ້ານາທີ. ເບິ່ງບົດຮຽນເພີ່ມເຕີມໄດ້ທີ່ **[ຊ່ອງ YouTube ຂອງ MantraBrain](https://www.youtube.com/@MantraBrain)**.

#### ✈️ ເປັນຫຍັງຜູ້ປະກອບການທົວຈຶ່ງເລືອກ Yatra

 * 🗺️ **ຮູບແບບຂໍ້ມູນເພື່ອການທ່ອງທ່ຽວໂດຍສະເພາະ** — ວັນອອກເດີນທາງ, ຈຳນວນທີ່ຮອງຮັບ,
   ປະເພດນັກທ່ອງທ່ຽວ ແລະ ກຳນົດການ ຖືກອອກແບບມາໃຫ້ກົງກັບການຂາຍທົວແທ້ໆ, ບໍ່ແມ່ນການຂາຍ
   ສິນຄ້າແບບອີຄອມເມີຊທົ່ວໄປ.
 * 🧭 **ພື້ນທີ່ຈັດການດຽວ** — ແຜງຄວບຄຸມ Yatra ທີ່ທັນສະໄໝພາຍໃນ wp-admin; ບໍ່ຕ້ອງປ່ຽນ
   ແທັບໄປມາຄືກັບລະບົບອີຄອມເມີຊທົ່ວໄປ.
 * ⚖️ **ຄວາມແຕກຕ່າງລະຫວ່າງ Free ກັບ [Pro](https://wpyatra.com/pricing/)** — ລະບົບ
   ການຈອງຫຼັກ, ບັນທຶກຂໍ້ມູນລູກຄ້າ, ການຣີວິວ ແລະ PayPal / ຈ່າຍທີຫຼັງ ແມ່ນມີໃຫ້ໃນປ
   ລັກອິນເວີຊັນຟຣີ. ສ່ວນຊ່ອງທາງບັດເຄຣດິດ ແລະ ໂມດູນຂັ້ນສູງແມ່ນຢູ່ໃນ [Pro](https://wpyatra.com/pricing/)—
   ບໍ່ມີການເກັບເງິນເພີ່ມສຳລັບຟັງຊັນພື້ນຖານ.
 * 🔒 **ເວັບໄຊຂອງທ່ານ, ຂໍ້ມູນຂອງທ່ານ** — ຂໍ້ມູນການຈອງ ແລະ ລູກຄ້າຈະຢູ່ໃນຖານຂໍ້ມູນ
   WordPress ຂອງທ່ານ; ການຊຳລະເງິນຈະຜ່ານຊ່ອງທາງທີ່ທ່ານຕັ້ງຄ່າເອງ. ບໍ່ມີພຣັອກຊີ, ບໍ່ມີ
   ການບວກລາຄາ, ບໍ່ມີຄ່າທຳນຽມຕໍ່ການຈອງ.
 * ⭐ **ມີການຕິດຕັ້ງ 700+ ຄັ້ງ · ຄະແນນ ★ 4.6 / 5 ໃນ WordPress.org** — ມີການພັດທະນາ
   ຢ່າງຕໍ່ເນື່ອງຕັ້ງແຕ່ປີ 2018, ອັບເດດທຸກອາທິດ.

#### 🎁 ສິ່ງທີ່ທ່ານຈະໄດ້ຮັບໃນປລັກອິນ Yatra ເວີຊັນຟຣີ

**Trips and catalog (free)**

 * [ທົວ & ກຳນົດການ](https://wpyatra.com/features/trips/) — ສ້າງທົວໄດ້ບໍ່ຈຳກັດ ພ້ອມ
   ຄຳອະທິບາຍລະອຽດ, ຄັງຮູບພາບ, ລະດັບຄວາມຍາກ, ໄລຍະເວລາ, ຈຸດນັດພົບ, ລາຍການທີ່ລວມ/ບໍ່
   ລວມ, ລະບົບສ້າງກຳນົດການແຕ່ລະວັນ, FAQ ແຕ່ລະທົວ ແລະ ຄຸນລັກສະນະອື່ນໆ
 * [ວັນອອກເດີນທາງ & ວັນທີຫວ່າງ](https://wpyatra.com/features/departures/) — ກຳນົດ
   ເວລາອອກເດີນທາງ, ຈຳນວນທີ່ຮອງຮັບ, ກົດເກນວັນທີຫວ່າງແບບຊ້ຳ
 * [ບັນຊີລູກຄ້າ](https://wpyatra.com/features/customer-accounts/) — ປະຫວັດການຈອງ,
   ການຊຳລະເງິນ, ໂປຣໄຟລ໌ ແລະ ການເຂົ້າເຖິງເອກະສານ (ໃບແຈ້ງໜີ້, ວາວເຊີ, ກຳນົດການ)
 * [ການຣີວິວ & ໃຫ້ຄະແນນ](https://wpyatra.com/features/reviews/) — ການກວດສອບ ແລະ 
   ການສະແດງຜົນໃນແຕ່ລະທົວ
 * [ລາຍງານການຂາຍ](https://wpyatra.com/features/reports/) — ລາຍງານສຳລັບຜູ້ດູແລລະບົບ
   ກ່ຽວກັບການຈອງ, ລາຍໄດ້ ແລະ ແນວໂນ້ມ
 * [ສ່ວນຫຼຸດ & ຄູປອງ](https://wpyatra.com/features/discounts/) — ລາຄາປົກກະຕິ ແລະ
   ລາຄາຫຼຸດ, ລາຄາຕາມປະເພດນັກທ່ອງທ່ຽວ, ລະບົບຄູປອງ
 * [ກ່ອງຂໍ້ຄວາມສອບຖາມ](https://wpyatra.com/features/enquiries/) — ຮັບຄຳຖາມກ່ອນການ
   ຈອງສຳລັບແຕ່ລະທົວ
 * [ເອກະສານ PDF](https://wpyatra.com/features/pdfs/) — ສ້າງໃບແຈ້ງໜີ້, ບັດກຳນົດສິດ(
   Voucher), ກຳນົດການເດີນທາງ
 * [ອີເມວແຈ້ງເຕືອນອັດຕະໂນມັດ](https://wpyatra.com/features/transactional-emails/)—
   ຢືນຢັນການຈອງ, ໃບຮັບເງິນ, ການຍົກເລີກ, ການແຈ້ງເຕືອນ

**ຊ່ອງທາງການຊຳລະເງິນແບບຟຣີ**

 * [PayPal](https://wpyatra.com/features/paypal/) — ບັດ, ຍອດເງິນ PayPal, ລະບົບຜ່ອນ
   ຊຳລະ
 * [ຈ່າຍທີຫຼັງ (Pay Later)](https://wpyatra.com/features/pay-later/) — ຈອງກ່ອນ, 
   ຢືນຢັນ ຫຼື ຈ່າຍແບບອອບໄລນ໌ (ເໝາະສຳລັບການໂອນເງິນ, ຈ່າຍເມື່ອໄປຮອດ, ຫຼື ລະບົບໃບແຈ້ງ
   ໜີ້)

**ໜ້າເວັບ + ການຂະຫຍາຍຄວາມສາມາດ**

 * ເທັມເພຼດສຳລັບລາຍການທົວ, ໜ້າທົວດ່ຽວ, ຂັ້ນຕອນການຈອງ, ການຊຳລະເງິນ ແລະ ບັນຊີ
 * **4 Gutenberg blocks** + **8 shortcodes** to place trips, search, login and account
   on any page
 * ເຂົ້າກັນໄດ້ກັບທີມແບບບລັອກ, ທີມແບບຄລາສສິກ ແລະ ເຄື່ອງມືສ້າງໜ້າເວັບຫຼັກໆເກືອບທັງໝົດ
 * PHP 7.4 ຫຼື ໃໝ່ກວ່າ, ໂຄງສ້າງໂຄ້ດທີ່ເປັນລະບົບ, ມີ hooks ແລະ filters, ຮອງຮັບການ
   template overrides
 * ຂັ້ນຕອນການຈອງ ແລະ ບັນຊີຜູ້ໃຊ້ທີ່ຮອງຮັບ REST

#### 💎 Yatra Pro — 20 ໂມດູນ ໃນ 3 ລະດັບ

**[ປຽບທຽບແພັກເກັດ ແລະ ຊື້ Yatra Pro](https://wpyatra.com/pricing/)** — ມີສາມແພັກ
ເກັດ (Starter · Growth · Scale), ແຕ່ລະອັນມີໃຫ້ເລືອກແບບລາຍປີ ຫຼື ຕະຫຼອດຊີວິດ.

**Starter — $99/ປີ (ລາຄາຫຼຸດ, ປົກກະຕິ $149)** · ໃບອະນຸຍາດ 1 ເວັບໄຊ · ລວມທຸກຢ່າງທີ່
ລະບຸໄວ້ລຸ່ມນີ້

 * [ລາຄາແບບໄດນາມິກ](https://wpyatra.com/features/dynamic-pricing/) — ປັບລາຄາຕາມລະດູການ,
   ຄວາມຕ້ອງການ, ການຈອງລ່ວງໜ້າ, ຫຼື ນາທີສຸດທ້າຍ
 * [ການຊຳລະເງິນແບບຍືດຫຍຸ່ນ](https://wpyatra.com/features/flexible-payments/) — ເງິນ
   ມັດຈຳ ແລະ ການຊຳລະບາງສ່ວນ
 * [ກຳນົດເວລາຊຳລະເງິນ](https://wpyatra.com/features/scheduled-payments/) — ແຜນການ
   ຜ່ອນຊຳລະ
 * [ສ່ວນຫຼຸດຂັ້ນສູງ](https://wpyatra.com/features/advanced-discount/) — ສ່ວນຫຼຸດ
   ແບບກຸ່ມຮ່ວມກັບຄູປອງ
 * [ບໍລິການເສີມ](https://wpyatra.com/features/additional-services/) — ຂາຍບໍລິການ
   ເພີ່ມເຕີມໄປພ້ອມກັບທົວ
 * [ລະບົບອີເມວອັດຕະໂນມັດ](https://wpyatra.com/features/email-automation/) — ສົ່ງ
   ອີເມວແບບເປັນລຳດັບ, ກອງກຸ່ມເປົ້າໝາຍ, ບັນທຶກການສົ່ງ
 * [ກູ້ຄືນການຈອງທີ່ຄ້າງຄາ](https://wpyatra.com/features/abandoned-booking-recovery/)—
   ຕິດຕາມການຈອງທີ່ບໍ່ສຳເລັດ
 * [ເຊື່ອມຕໍ່ Mailchimp](https://wpyatra.com/features/mailchimp/) — ຊິງຄ໌ຂໍ້ມູນນັກ
   ທ່ອງທ່ຽວ ແລະ ການຈອງເຂົ້າໃນລາຍຊື່ເມວ
 * [Facebook Pixel](https://wpyatra.com/features/facebook-pixel/) — ຕິດຕາມເຫດການ
   ທັງຝັ່ງເຊີເວີ ແລະ ບຣາວເຊີ
 * [Google Analytics 4 ແບບລະອຽດ](https://wpyatra.com/features/google-analytics/)—
   ຕິດຕາມຂັ້ນຕອນການຈອງ ແລະ ລາຍໄດ້
 * [ຊິງຄ໌ກັບ Google Calendar](https://wpyatra.com/features/google-calendar/) — ເອົາ
   ວັນອອກເດີນທາງ ແລະ ການຈອງເຂົ້າໃນ Google Calendar
 * [ໜ້າ Landing Page ແບບກຳນົດເອງ](https://wpyatra.com/features/custom-landing-pages/)—
   ສ້າງໜ້າຂາຍສະເພາະແຕ່ລະທົວເພື່ອເພີ່ມຍອດຂາຍ
 * [ຊ່ອງຂໍ້ມູນແບບໄດນາມິກ](https://wpyatra.com/features/dynamic-form-field/) — ລາກ
   ແລະວາງເພື່ອສ້າງຄຳຖາມການຈອງແບບກຳນົດເອງ
 * [ການຍິນຍອມທົວ](https://wpyatra.com/features/trip-consent/) — ເອກະສານສະລະສິດ ແລະ
   ລາຍເຊັນດິຈິຕອນ
 * **ຊ່ອງທາງການຊຳລະເງິນລະດັບພຣີມຽມ**: Stripe · Razorpay · Mollie · Paystack · Square·
   Authorize.Net · ການໂອນເງິນຜ່ານທະນາຄານ

**Growth — $149/ປີ (ລາຄາຫຼຸດ, ປົກກະຕິ $199)** · ໃບອະນຸຍາດ 1 ເວັບໄຊ · ລວມທຸກຢ່າງໃນ
Starter, ບວກກັບ

 * [AI Assistant](https://wpyatra.com/features/ai-assistant/) — ສ້າງກຳນົດການເດີນທາງ,
   ຮ່າງຄຳອະທິບາຍ, ແນະນຳຄຳຕອບ (ໃຊ້ຄີ OpenAI ຫຼື Anthropic ຂອງທ່ານເອງ)
 * [ການແຈ້ງເຕືອນ WhatsApp](https://wpyatra.com/features/whatsapp/) — ຢືນຢັນການຈອງ,
   ໃບຮັບເງິນ ແລະ ແຈ້ງເຕືອນການອອກເດີນທາງຜ່ານ WhatsApp (Meta Cloud API)

**Scale — ເລີ່ມຕົ້ນ $349/ປີ (ລາຄາຫຼຸດ)** · 1 ເວັບໄຊ $349/ປີ (ລາຄາປົກກະຕິ $449) ຫຼື
15 ເວັບໄຊ $599/ປີ (ລາຄາປົກກະຕິ $749) · ລວມທຸກຢ່າງໃນ Growth, ບວກກັບ

 * [Channel Manager](https://wpyatra.com/features/channel-manager/) — ຂາຍໃນ Viator
   + GetYourGuide ຈາກແຜງຄວບຄຸມ WordPress ດຽວ. ມີລະບົບ Webhooks, ປ້ອງກັນການຈອງເກີນ
   ແລະ ຊິງຄ໌ຂໍ້ມູນຈຳນວນທີ່ຫວ່າງແບບທັນທີ.
 * [White Label](https://wpyatra.com/features/white-label/) — ປ່ຽນແບຣນໃນໜ້າຈັດການ,
   ອີເມວ, PDF ແລະ ໜ້າເວັບ. ປັບແຕ່ງຮູບແບບໃຫ້ເປັນຂອງບໍລິສັດທ່ານເອງ.
 * [ທີມ & ການເຂົ້າເຖິງ](https://wpyatra.com/features/team-access/) — ກຳນົດບົດບາດ
   ແລະ ສິດການເຂົ້າເຖິງແບບລະອຽດສຳລັບບໍລິສັດທີ່ມີພະນັກງານຫຼາຍຄົນ. ມີ 8 ບົດບາດມາກັບ
   ລະບົບ, ສ້າງບົດບາດເອງໄດ້, ສົ່ງຄຳເຊີນຜ່ານລິ້ງ, ກຳນົດເວລາເຂົ້າເຖິງສຳລັບຜູ້ຮັບເໝົາ,
   ກອງຂອບເຂດການເຂົ້າເຖິງ (ຕາມຈຸດໝາຍປາຍທາງ / ຕາມທົວ) ແລະ ບັນທຶກປະຫວັດການເຮັດວຽກ.
 * [Webhooks](https://wpyatra.com/features/webhooks/) — ສົ່ງຂໍ້ມູນ HTTP ອອກເມື່ອ
   ມີເຫດການການຈອງ / ການຊຳລະເງິນ / ລູກຄ້າ. ຮອງຮັບ HMAC-signed payloads, ລະບົບລໍຖ້າ
   ສົ່ງໃໝ່, dead-letter queue. ເຊື່ອມຕໍ່ Yatra ເຂົ້າກັບ Zapier, Make, n8n ຫຼື ລະບົບ
   ພາຍໃນຂອງທ່ານເອງ.

**ແພັກເກັດຕະຫຼອດຊີວິດ** ກໍມີໃຫ້ບໍລິການເຊັ່ນກັນ: Starter $499 · Growth $699 · Scale
$1,299 (1 ເວັບໄຊ) / $1,999 (15 ເວັບໄຊ) — ຈ່າຍຄັ້ງດຽວ, ເປັນເຈົ້າຂອງຕະຫຼອດໄປ.

[ເບິ່ງການປຽບທຽບແພັກເກັດ ແລະ ລາຄາທັງໝົດ ](https://wpyatra.com/pricing/)

#### 🥊 ການປຽບທຽບ Yatra

ກຳລັງປຽບທຽບ Yatra ກັບແພລດຟອມການຈອງແບບ SaaS ຫຼື ປລັກອິນທ່ອງທ່ຽວ WordPress ອື່ນໆຢູ່
ບໍ? ພວກເຮົາໄດ້ຂຽນການປຽບທຽບແບບກົງໄປກົງມາລະຫວ່າງແຕ່ລະທາງເລືອກຫຼັກໄວ້ໃຫ້ແລ້ວ:

 * 🔄 **[Yatra ປຽບທຽບກັບ Rezdy](https://wpyatra.com/yatra-vs-rezdy/)** — ຂາຍໃນ Viator
   + GetYourGuide ໂດຍບໍ່ຕ້ອງຈ່າຍຄ່າ SaaS ຂອງ Rezdy ທີ່ລາຄາ $99–$499 ຕໍ່ເດືອນ. ໃບ
   ອະນຸຍາດຕະຫຼອດຊີວິດ · GPL · ຂໍ້ມູນຂອງທ່ານເອງ, ຊ່ອງທາງການຊຳລະເງິນຂອງທ່ານເອງ.
 * 🔄 **[Yatra ປຽບທຽບກັບ Bokun](https://wpyatra.com/yatra-vs-bokun/)** — ຂ້າມຄ່າ
   ທຳນຽມຕໍ່ການຈອງ OTA ທີ່ Bokun ເກັບ (ປົກກະຕິ 2.5% ຕໍ່ການຈອງ). ເປັນທາງເລືອກ open-
   source ທີ່ເປັນອິດສະຫຼະຈາກ Bokun ທີ່ເປັນຂອງ Tripadvisor.
 * 🔄 **[Yatra ປຽບທຽບກັບ WP Travel Engine](https://wpyatra.com/yatra-vs-wp-travel-engine/)**—
   ປັດຊະຍາ WordPress ດຽວກັນ, ໂຄງສ້າງທີ່ທັນສະໄໝ, ໂມດູນ Pro ທີ່ກວ້າງຂວາງກວ່າ. ໃຊ້ຕາຕະລາງ
   ຖານຂໍ້ມູນແບບກຳນົດເອງເພື່ອປະສິດທິພາບ ສູງກວ່າການໃຊ້ custom post types ຂອງ WP Travel
   Engine.

ແຕ່ລະໜ້າຈະກວມເອົາລາຍລະອຽດຄຸນສົມບັດ, ການຄິດໄລ່ລາຄາ, ຂັ້ນຕອນການຍ້າຍຂໍ້ມູນ ແລະ FAQ —
ຂຽນຕາມຄວາມເປັນຈິງ. ອ່ານລາຍລະອຽດແລ້ວ [ທົດລອງໃຊ້ Yatra Pro ຟຣີ](https://try.wpyatra.com/try-yatra-pro/)
ກ່ອນທີ່ທ່ານຈະຕັດສິນໃຈ.

#### 🌐 ການເຊື່ອມຕໍ່ພາຍໃນ

Yatra ມາພ້ອມກັບການເຊື່ອມຕໍ່ແບບໃຊ້ຂໍ້ມູນສ່ວນຕົວຂອງທ່ານເອງ — ບໍ່ມີພຣັອກຊີ, ບໍ່ມີການ
ບວກລາຄາເພີ່ມ, ບໍ່ມີຄ່າທຳນຽມຕໍ່ລາຍການ. ລາຍການທັງໝົດ: **[ການເຊື່ອມຕໍ່ທັງໝົດໃນ wpyatra.com](https://wpyatra.com/integrations/)**.

 * **ການຊຳລະເງິນ**: PayPal · ຈ່າຍທີຫຼັງ · Stripe · Razorpay · Mollie · Paystack ·
   Square · Authorize.Net · ການໂອນເງິນຜ່ານທະນາຄານ
 * **OTAs**: Viator · GetYourGuide · OTA ອື່ນໆ (ຕາມການຮ້ອງຂໍ)
 * **ອີເມວ & ຂໍ້ຄວາມ**: Mailchimp · WhatsApp Cloud API
 * **ການວິເຄາະ & ການຕະຫຼາດ**: Google Analytics 4 · Meta / Facebook Pixel
 * **ປະຕິທິນ & ການວາງແຜນ**: Google Calendar
 * **ຜູ້ໃຫ້ບໍລິການ AI**: OpenAI · Anthropic Claude
 * **ລະບົບນິເວດ WordPress**: ບລັອກ Gutenberg (4 ອັນ), Elementor (ຜ່ານຊອດໂຄ້ດ), WooCommerce(
   ໃຊ້ຮ່ວມກັນ), 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.

#### 🧩 ບລັອກ ແລະ ຊອດໂຄ້ດ

ໃຊ້ **ຕົວແກ້ໄຂບລັອກ** ຫຼື **ຊອດໂຄ້ດແບບຄລາສສິກ** ເພື່ອວາງວິດເຈັດລາຍການ, ການຄົ້ນຫາ
ແລະ UI ບັນຊີລູກຄ້າໃນໜ້າໃດກໍໄດ້.

**ບລັອກ (Blocks)** (ຄົ້ນຫາໃນຊ່ອງຄົ້ນຫາບລັອກດ້ວຍຄຳວ່າ “Yatra” ຫຼື ຊື່ບລັອກ):

 * **ທົວ (Trip)** — ຊື່ບລັອກ `yatra/tour` (ຕາຕະລາງທົວ; ຊື່ທີ່ລົງທະບຽນຍັງຄົງເປັນ `
   yatra/tour` ເພື່ອຄວາມເຂົ້າກັນໄດ້ກັບເວີຊັນເກົ່າ, ແຕ່ຊື່ໃນລະບົບ ແລະ UI ໃນປັດຈຸບັນ
   ຈະສະແດງເປັນ **Trip**). **ການຕັ້ງຄ່າທົວ** (ຮູບແບບ, **Featured Priority** — ຈຳກັດ
   ສະເພາະ _Featured_, _New_, ຫຼື _Limited Time_ ທີ່ເລືອກໃນແບບຟອມທົວ **ໝວດໝູ່  Featured
   Priority**) ແລະ **ຕົວຢັ້ງຢືນ (Filters)**: ແຕ່ລະໝວດໝູ່ (ຈຸດໝາຍປາຍທາງ, ກິດຈະກຳ,
   ໝວດໝູ່ທົວ, ລະດັບຄວາມຍາກ) ຮອງຮັບ **ຂອບເຂດລາຍການ** — ບໍ່ວ່າຈະເປັນ **ເຜີຍແຜ່ທັງໝົດ**(
   ບໍ່ມີການບັນທຶກ ID ຕົວຢັ້ງຢືນ) ຫຼື **ສະເພາະທີ່ເລືອກ**, ໂດຍມີ **ຊ່ອງຄົ້ນຫາພ້ອມກັບ
   ກ່ອງເລືອກ** ເພື່ອເລືອກ ID ຂອງໝວດໝູ່.
 * **ກິດຈະກຳ (Activity)** — `yatra/activity`: ຮູບແບບການເລືອກໝວດໝູ່ດຽວກັນ (ເຜີຍແຜ່
   ທັງໝົດ ຫຼື ຄົ້ນຫາ + ID) ໃນແຖບຂ້າງ; ຕົງກັບກົດເກນ ID ຂອງ **`[yatra_activity]`**.
 * **ຈຸດໝາຍປາຍທາງ (Destination)** — `yatra/destination`: ຮູບແບບດຽວກັນ; ຕົງກັບກົດເກນ
   ID ຂອງ **`[yatra_destination]`**.
 * **ໝວດໝູ່ທົວ (Trip categories)** — `yatra/trip-category` (ຮູບແບບບັດດຽວກັນກັບຈຸດໝາຍປາຍທາງ;
   ລິ້ງຈະໃຊ້ຖານໝວດໝູ່ທົວຈາກການຕັ້ງຄ່າ).

**ຊອດໂຄ້ດ (Shortcodes)** (ທັງໝົດຮອງຮັບຄ່າຕາມຄ່າເລີ່ມຕົ້ນຂອງປລັກອິນ — ໃຊ້ `yes` /`
no` ຫຼື `0` / `1` ຕາມທີ່ລະບຸ):

 * **`[yatra_trip]`** — ລາຍການທົວ. ຊື່ອື່ນ: **`[yatra_tour]`**. ຕົວຢັ້ງຢືນ (Filters):`
   destination`, `activity`, `category` ຮອງຮັບ ID ທີ່ຂັ້ນດ້ວຍຈຸດ. ຕົວເລືອກເສີມ: `
   order`, `featured_priority` (`featured` / `new` / `limited`), `per_page`, `difficulty`,`
   price_min`, `price_max`, `duration_min`, `duration_max`, `search`, `columns`,`
   show_pagination`, `title`. ການແບ່ງໜ້າ: `trip_page`. ຕົວຢ່າງ: `[yatra_trip]`, `[
   yatra_trip destination="44" activity="12"]`, `[yatra_trip featured_priority="
   new" per_page="6"]`.
 * **`[yatra_activity]`** — ບັດສະແດງລາຍການກິດຈະກຳ.
 * **`[yatra_destination]`** — ສະແດງຈຸດໝາຍປາຍທາງ.
 * **`[yatra_trip_category]`** — ບັດສະແດງໝວດໝູ່ທົວ.
 * **`[yatra_search]`** — ແບບຟອມຄົ້ນຫາທົວແບບລະອຽດ. ຄຸນລັກສະນະການສະແດງຜົນແຕ່ລະຊ່ອງ—`
   keyword`, `destination`, `activities`, `duration`, `budget` — ແຕ່ລະອັນກຳນົດເປັນ`
   yes` / `no`. ຖ້າຂ້າມອັນໃດໄປ ມັນຈະໃຊ້ຄ່າຕາມ **ການຕັ້ງຄ່າ  ການຄົ້ນຫາ & ລາຍການ**;
   ສົ່ງຄ່າເຂົ້າໄປເພື່ອບັງຄັບ ປິດ/ເປີດ ໃນຕຳແໜ່ງນັ້ນ. ຕົວຢ່າງ: `[yatra_search budget
   ="no" duration="no"]`. (ໜ້າລາຍການທີ່ມາກັບລະບົບຈະຕັ້ງຄ່າເຫຼົ່ານີ້ໃຫ້ໂດຍອັດຕະໂນ
   ມັດຕາມການຕັ້ງຄ່າຂອງທ່ານ.)
 * **`[yatra_login]`** — ແບບຟອມເຂົ້າສູ່ລະບົບຂອງລູກຄ້າ.
 * **`[yatra_my_account]`** — ແຜງຄວບຄຸມບັນຊີສຳລັບຜູ້ໃຊ້ທີ່ເຂົ້າສູ່ລະບົບແລ້ວ.
 * **`[yatra_discount_and_deals]`** — ສະແດງທົວທີ່ມີສ່ວນຫຼຸດ.

**ການກອງລາຍການທີ່ວ່າງ (`hide_empty`):** `[yatra_destination]`, `[yatra_activity]`
ແລະ `[yatra_trip_category]` ສາມາດໃຊ້ `hide_empty="yes"` ເພື່ອຂ້າມລາຍການທີ່ບໍ່ມີທົວ
ເຜີຍແຜ່. (ຄ່າເລີ່ມຕົ້ນແມ່ນ `no`).

**ໝາຍເຫດ:** ຖ້າທ່ານກຳລັງຍ້າຍມາຈາກເວີຊັນເກົ່າ, `[yatra_cart]`, `[yatra_checkout]`
ແລະ `[yatra_mini_cart]` ຈະບໍ່ໄດ້ຖືກລົງທະບຽນນຳໃຊ້ແລ້ວ — ການຊຳລະເງິນ ແລະ ຂັ້ນຕອນການ
ຈອງໃນປັດຈຸບັນແມ່ນໃຊ້ເສັ້ນທາງ ແລະ ເທັມເພຼດໜ້າເວັບຂອງ Yatra ເອງ. ເບິ່ງ **[docs.wpyatra.com](https://docs.wpyatra.com)**
ສຳລັບການອ້າງອີງຊອດໂຄ້ດທັງໝົດ, URL ແລະ ການຕັ້ງຄ່າໜ້າເວັບ.

#### 🎨 ທີມທ່ອງທ່ຽວ WordPress ທີ່ເຂົ້າກັນໄດ້

Yatra ເຮັດວຽກໄດ້ກັບທີມແບບບລັອກ, ທີມແບບຄລາສສິກ ແລະ ເຄື່ອງມືສ້າງໜ້າເວັບສ່ວນໃຫຍ່. **
ທີມທີ່ແນະນຳ** (ທາງເລືອກ — Yatra ສາມາດໃຊ້ໄດ້ກັບທຸກທີມ):

 * 🧳 **[Resa — ທີມທ່ອງທ່ຽວທາງການຂອງ Yatra](https://wpyatra.com/best-wordpress-travel-theme/)**—
   ໂຫຼດໄວ, ເນັ້ນການສະແດງຜົນໃນມືຖື, ຮອງຮັບ Gutenberg + WooCommerce, ຟຣີໃນ WordPress.
   org. ມີຮູບແບບຕາຕະລາງທົວ, ວິດເຈັດວັນອອກເດີນທາງ ແລະ ແຜງຄວບຄຸມບັນຊີຜູ້ໃຊ້ທີ່ອອກແບບ
   ມາເພື່ອ Yatra ໂດຍສະເພາະ.
 * 🧱 **[Blocksy](https://wordpress.org/themes/blocksy/?ref=yatrapluginorg)** — 
   ທີມແບບບລັອກທີ່ທັນສະໄໝ
 * ⚡ **[Kadence](https://wordpress.org/themes/kadence/?ref=yatrapluginorg)** — 
   ທີມທີ່ໄວ ແລະ ຍືດຫຍຸ່ນ

#### 🔗 ລິ້ງດ່ວນ

 * 🏠 **[wpyatra.com](https://wpyatra.com/)** — ເວັບໄຊທາງການ
 * 💳 **[ລາຄາ](https://wpyatra.com/pricing/)** — ແພັກເກັດ Starter · Growth · Scale·
   ຕະຫຼອດຊີວິດ
 * ✨ **[ຄຸນສົມບັດທັງໝົດ](https://wpyatra.com/features/)** — ລາຍການຄວາມສາມາດທັງໝົດ
   ຂອງ Free + Pro
 * 🌐 **[ການເຊື່ອມຕໍ່](https://wpyatra.com/integrations/)** — ພັນທະມິດທີ່ເຊື່ອມຕໍ່
   ໂດຍກົງທັງໝົດ
 * 🥊 **[Yatra ປຽບທຽບກັບທາງເລືອກອື່ນ](https://wpyatra.com/yatra-vs-rezdy/)** — ການປຽບທຽບ
   ແບບລະອຽດ
 * 🎨 **[WordPress travel theme (Resa)](https://wpyatra.com/best-wordpress-travel-theme/)**—
   ທີມທີ່ແນະນຳໃຫ້ໃຊ້ຮ່ວມກັນ
 * 📖 **[ເອກະສານແນະນຳ](https://docs.wpyatra.com/)** — ການຕິດຕັ້ງ, ບລັອກ, ຊອດໂຄ້ດ,
   ການເຮັດວຽກ
 * 🎯 **[ເວັບໄຊຕົວຢ່າງ](https://demo.wpyatra.com/)** — ເບິ່ງການເຮັດວຽກຂອງ Yatra 
   ໃນເວັບໄຊ WordPress ຕົວຢ່າງ
 * 🆘 **[ຊ່ວຍເຫຼືອ / ຕິດຕໍ່](https://mantrabrain.com/contact)** — ຊ່ອງທາງການຊ່ວຍເຫຼືອ
   ແລະ ການຊ່ວຍເຫຼືອທາງທຸລະກິດ

#### 💙 ເຂົ້າຮ່ວມຊຸມຊົນ

 * ⭐ **[ໃຫ້ຄະແນນ Yatra 5 ດາວ](https://wordpress.org/support/plugin/yatra/reviews/?filter=5)**—
   ຊ່ວຍໃຫ້ຜູ້ປະກອບການທົວຄົນອື່ນໆຄົ້ນຫາປລັກອິນເຫັນ
 * 💬 **[ຊຸມຊົນ Facebook](https://www.facebook.com/groups/yatrawordpressplugin)**—
   ເຊື່ອມຕໍ່ກັບຜູ້ໃຊ້ Yatra ຄົນອື່ນໆ
 * 📧 **[ອີເມວຊ່ວຍເຫຼືອ](https://lo.wordpress.org/plugins/yatra/mantrabrain@gmail.com?output_format=md)**—
   ສົ່ງອີເມວໂດຍກົງສຳລັບຄຳຖາມກ່ຽວກັບຜະລິດຕະພັນ
 * 🐛 **[GitHub — ແຈ້ງບັນຫາ & ການມີສ່ວນຮ່ວມ](https://github.com/MantraBrain/yatra)**—
   ລາຍງານບັກ ແລະ ສົ່ງ pull requests

#### 🚀 ທົດລອງໃຊ້ Yatra ໂດຍບໍ່ມີຄວາມສ່ຽງ

 * 🧪 **[ທົດລອງໃຊ້ປລັກອິນ Yatra ຟຣີໃນ WordPress Playground](https://try.new/plugins/yatra)**—
   ສ້າງເວັບໄຊ WordPress ຊົ່ວຄາວທີ່ຕິດຕັ້ງປລັກອິນ Yatra ໄວ້ໃຫ້ແລ້ວ. ບໍ່ຕ້ອງຕິດຕັ້ງ
   ໃນເຄື່ອງ, ບໍ່ຕ້ອງສະໝັກສະມາຊິກ, ບໍ່ຕ້ອງໃຊ້ບັດເຄຣດິດ.
 * 🎁 **[ທົດລອງໃຊ້ Yatra Pro ຟຣີ](https://try.wpyatra.com/try-yatra-pro/)** — ລະບົບ
   ທົດລອງ Pro ແບບເຕັມຮູບແບບທີ່ເປີດໃຊ້ທຸກໂມດູນ. ບໍ່ຕ້ອງໃຊ້ບັດເຄຣດິດ.
 * 💰 **ຄືນເງິນພາຍໃນ 14 ວັນ** ສຳລັບທຸກແພັກເກັດ Yatra Pro ທີ່ຊຳລະເງິນ — ເບິ່ງເງື່ອນໄຂ
   ການຄືນເງິນໄດ້ທີ່ [ໜ້າລາຄາ](https://wpyatra.com/pricing/).

### ຂໍ້ມູນເພີ່ມເຕີມ

#### ຄວາມເປັນສ່ວນຕົວ

ຂໍ້ມູນການຈອງ ແລະ ຂໍ້ມູນລູກຄ້າຈະຖືກເກັບໄວ້ໃນຖານຂໍ້ມູນ WordPress ຂອງທ່ານ. ການປະມວນ
ຜົນການຊຳລະເງິນແມ່ນດຳເນີນການໂດຍຜູ້ໃຫ້ບໍລິການທີ່ທ່ານເປີດໃຊ້; ກະລຸນາກວດສອບເອກະສານຄວາມເປັນ
ສ່ວນຕົວ ແລະ PCI ຂອງແຕ່ລະຜູ້ໃຫ້ບໍລິການ. Yatra ຈະບໍ່ສົ່ງຂໍ້ມູນລູກຄ້າໄປຫາ SaaS ພາຍນອກ.

#### ເຄຣດິດ

Yatra ພັດທະນາໂດຍ **MantraBrain**. ມີການໃຊ້ໄລບຣາຣີພາຍນອກ ເຊັ່ນ React (admin UI), 
Vite, TanStack Query ແລະ ອື່ນໆ ທີ່ມາພ້ອມກັບແພັກເກັດປລັກອິນ.

#### ການມີສ່ວນຮ່ວມ

ແຈ້ງບັນຫາ ແລະ ການມີສ່ວນຮ່ວມ: [GitHub — Yatra](https://github.com/MantraBrain/yatra)

ຖ້າ Yatra ຊ່ວຍທຸລະກິດຂອງທ່ານໄດ້, ການໃຫ້ ⭐ **ຣີວິວ 5 ດາວ** ໃນ WordPress.org ແລະ 
ການພິຈາລະນາໃຊ້ **💎 [Yatra Pro](https://wpyatra.com/pricing/)** ເມື່ອທ່ານຕ້ອງການ
ຄຸນສົມບັດເພີ່ມເຕີມ ຈະຊ່ວຍສະໜັບສະໜູນການພັດທະນາຕໍ່ໄປ. ຂອບໃຈທີ່ໃຊ້ Yatra.

## ພາບໜ້າຈໍ

[⌊ແຜງຄວບຄຸມ Yatra ໃນ WordPress — ການຈອງ, ລາຍໄດ້ ແລະ ການເຂົ້າເຖິງວຽກປະຈຳວັນຢ່າງວ່ອງໄວ⌉⌊
ແຜງຄວບຄຸມ Yatra ໃນ WordPress — ການຈອງ, ລາຍໄດ້ ແລະ ການເຂົ້າເຖິງວຽກປະຈຳວັນຢ່າງວ່ອງໄວ⌉[

ແຜງຄວບຄຸມ Yatra ໃນ WordPress — ການຈອງ, ລາຍໄດ້ ແລະ ການເຂົ້າເຖິງວຽກປະຈຳວັນຢ່າງວ່ອງໄວ

[⌊ຂັ້ນຕອນການຈອງທົວ — ຮູບພາບຫຼັກ, ກຳນົດການ ແລະ ຂັ້ນຕອນການຈອງ⌉⌊ຂັ້ນຕອນການຈອງທົວ — 
ຮູບພາບຫຼັກ, ກຳນົດການ ແລະ ຂັ້ນຕອນການຈອງ⌉[

ຂັ້ນຕອນການຈອງທົວ — ຮູບພາບຫຼັກ, ກຳນົດການ ແລະ ຂັ້ນຕອນການຈອງ

[⌊ບັນຊີຜູ້ເດີນທາງ — ການຈອງ, ການຊຳລະເງິນ ແລະ ເອກະສານ⌉⌊ບັນຊີຜູ້ເດີນທາງ — ການຈອງ, ການ
ຊຳລະເງິນ ແລະ ເອກະສານ⌉[

ບັນຊີຜູ້ເດີນທາງ — ການຈອງ, ການຊຳລະເງິນ ແລະ ເອກະສານ

## ບລັອກ

ປລັກອິນນີ້ມີ 4 ບລັອກ.

 *   Destination Display destination listings with customizable options
 *   Trip categories Display trip category cards with trip counts and pricing (same
   layout as destinations).
 *   Activity Display activity listings with customizable options
 *   Trip Display trip listings with customizable options

## ການຕິດຕັ້ງ

🛠️ **ການຕັ້ງຄ່າດ່ວນ**

 1. ຕິດຕັ້ງ ແລະ ເປີດໃຊ້ **Yatra** ຈາກໜ້ານີ້ ຫຼື ອັບໂຫຼດໄຟລ໌ ZIP ພາຍໃຕ້ ປລັກອິນ  ເພີ່ມ
    ໃໝ່  ອັບໂຫຼດ.
 2. ຕັ້ງຄ່າຜ່ານຕົວຊ່ວຍ (ສະກຸນເງິນ, ຂໍ້ມູນພື້ນຖານ, permalinks ຕາມທີ່ລະບົບແນະນຳ).
 3. ເພີ່ມຈຸດໝາຍປາຍທາງ ແລະ ກິດຈະກຳ, ຈາກນັ້ນສ້າງທົວທຳອິດຂອງທ່ານພາຍໃຕ້ **Yatra  ທົວ (Trips)**.
 4. ຕັ້ງຄ່າ **PayPal** ແລະ/ຫຼື **ຈ່າຍທີຫຼັງ (Pay Later)** ພາຍໃຕ້ການຕັ້ງຄ່າການຊຳລະເງິນ
    ຂອງ Yatra (ຟຣີ). ເພີ່ມ **[Yatra Pro](https://wpyatra.com/pricing/)** ເມື່ອທ່ານຕ້ອງການ
    ຊ່ອງທາງບັດເຄຣດິດ ຫຼື [ໂມດູນ Pro](https://wpyatra.com/features/).
 5. ວາງລະບົບການຈອງໃນເວັບໄຊຂອງທ່ານໂດຍໃຊ້ເທັມເພຼດ, **ບລັອກ**, ຫຼື **ຊອດໂຄ້ດ** ຂອງ Yatra(
    ເບິ່ງ **🧩 ບລັອກ ແລະ ຊອດໂຄ້ດ** ໃນລາຍລະອຽດຂ້າງເທິງ ແລະ [docs.wpyatra.com](https://docs.wpyatra.com)).

## ຄຳຖາມທີ່ພົບເລື້ອຍ

### ປລັກອິນຈອງການທ່ອງທ່ຽວ WordPress ທີ່ດີທີ່ສຸດສຳລັບຜູ້ປະກອບການທົວແມ່ນຫຍັງ?

Yatra ແມ່ນ **ປລັກອິນຈອງການທ່ອງທ່ຽວ WordPress** ທີ່ສ້າງຂຶ້ນຕາມຄວາມເປັນຈິງຂອງການຂາຍ
ທົວ — ການກຳນົດເວລາອອກເດີນທາງ, ຈຳນວນທີ່ຮອງຮັບ, ປະເພດນັກທ່ອງທ່ຽວ, ການແຈກຢາຍຜ່ານ OTA,
ລາຄາແບບປ່ຽນແປງ ແລະ ການຈັດການເງິນມັດຈຳ. ປລັກອິນເວີຊັນຟຣີກວມເອົາຂັ້ນຕອນການຈອງທັງໝົດ(
ທົວ, ວັນທີຫວ່າງ, ບັນຊີລູກຄ້າ, ການຣີວິວ, ລາຍງານ, ໄຟລ໌ PDF, ອີເມວແຈ້ງເຕືອນ, PayPal
+ ຈ່າຍທີຫຼັງ); [Yatra Pro](https://wpyatra.com/pricing/) ເພີ່ມອີກ 20 ໂມດູນໃນລະດັບ
Starter, Growth ແລະ Scale. ອ່ານ [ການປຽບທຽບກັບ WP Travel Engine](https://wpyatra.com/yatra-vs-wp-travel-engine/)
ຫຼື [ກັບ Rezdy SaaS](https://wpyatra.com/yatra-vs-rezdy/).

### Yatra ຟຣີບໍ່?

ແມ່ນແລ້ວ. ປລັກອິນໃນ WordPress.org ແມ່ນຟຣີ ແລະ ລວມມີລະບົບການຈອງຫຼັກສຳລັບຜູ້ປະກອບການ
ທົວ. **[Yatra Pro](https://wpyatra.com/pricing/)** ແມ່ນເວີຊັນອັບເກຣດທີ່ຕ້ອງຊຳລະເງິນ
ສຳລັບ [ຊ່ອງທາງການຊຳລະເງິນລະດັບພຣີມຽມ](https://wpyatra.com/pricing/) ແລະ [20 ໂມດູນ Pro](https://wpyatra.com/features/).

### ຂ້ອຍຕ້ອງມີທັກສະການຂຽນໂຄ້ດເພື່ອໃຊ້ Yatra ບໍ່?

ບໍ່ຈຳເປັນສຳລັບການເຮັດວຽກທົ່ວໄປ. ນັກພັດທະນາສາມາດປັບແຕ່ງເທັມເພຼດ ແລະ ໃຊ້ hooks ສຳລັບ
ຂັ້ນຕອນການເຮັດວຽກແບບກຳນົດເອງ.

### ການຊຳລະເງິນແບບໃດທີ່ຟຣີ ແລະ ແບບໃດທີ່ເປັນ Pro?

**ຟຣີ:** [PayPal](https://wpyatra.com/features/paypal/) ແລະ [ຈ່າຍທີຫຼັງ (Pay Later)](https://wpyatra.com/features/pay-later/).**
[Pro](https://wpyatra.com/pricing/):** Stripe, Razorpay, Mollie, Paystack, Square,
Authorize.Net, ການໂອນເງິນຜ່ານທະນາຄານ (ຕາມການຮອງຮັບໃນບັນຊີ ແລະ ພາກພື້ນຂອງທ່ານ).

### ຂ້ອຍສາມາດຮັບການຈອງໂດຍບໍ່ຕ້ອງຕັດບັດທັນທີໄດ້ບໍ່?

ແມ່ນແລ້ວ. ໃຊ້ **ຈ່າຍທີຫຼັງ (Pay Later)** ສຳລັບການຢືນຢັນແບບອອບໄລນ໌, ໃບແຈ້ງໜີ້, ຫຼື
ການຈ່າຍເມື່ອໄປຮອດ.

### ຂ້ອຍສາມາດກະຈາຍທົວຂອງຂ້ອຍໄປຍັງ Viator, GetYourGuide ແລະ OTA ອື່ນໆໄດ້ບໍ່?

ແມ່ນແລ້ວ — ໂມດູນ [Channel Manager](https://wpyatra.com/features/channel-manager/)(
ລະດັບ Scale) ເຊື່ອມຕໍ່ Yatra ໂດຍກົງຫາ **Viator** ແລະ **GetYourGuide** ຜ່ານ API ທາງການ.
ລະບົບ Webhooks ຈະດຶງຂໍ້ມູນການຈອງກັບມາແບບທັນທີ; ລະບົບປ້ອງກັນການຈອງເກີນ (anti-overbooking)
ຈະປ້ອງກັນບໍ່ໃຫ້ສອງຊ່ອງທາງຂາຍບ່ອນນັ່ງດຽວກັນ. ສ່ວນ OTA ອື່ນໆ (Klook, TripAdvisor Experiences,
Booking.com Experiences, Airbnb Experiences) ສາມາດຂໍເພີ່ມໄດ້ຕາມຕ້ອງການ.

### Yatra ເຮັດວຽກຮ່ວມກັບ WooCommerce ໄດ້ບໍ່?

ແມ່ນແລ້ວ. Yatra ເຮັດວຽກຮ່ວມກັບ WooCommerce ໃນເວັບໄຊ WordPress ດຽວກັນໄດ້ — Yatra 
ເກັບຂໍ້ມູນທົວໄວ້ໃນຕາຕະລາງຂອງຕົນເອງ ໃນຂະນະທີ່ WooCommerce ໃຊ້ລະບົບຄຳສັ່ງຊື້ຂອງ WordPress.
ທັງສອງສາມາດຢູ່ຮ່ວມກັນໄດ້ໂດຍບໍ່ມີຂໍ້ຂັດແຍ່ງຂອງຂໍ້ມູນ. ຜູ້ປະກອບການຫຼາຍຄົນໃຊ້ Yatra
ສຳລັບທົວ ແລະ ໃຊ້ WooCommerce ສຳລັບຂາຍສິນຄ້າ ຫຼື ບັດຂອງຂວັນ.

### Yatra ຮອງຮັບເວັບໄຊທ່ອງທ່ຽວແບບຫຼາຍພາສາ ແລະ ຫຼາຍສະກຸນເງິນບໍ່?

**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).

### Yatra ເຮັດວຽກຮ່ວມກັບທີມຂອງຂ້ອຍໄດ້ບໍ່?

ມັນເຮັດວຽກໄດ້ກັບທຸກໆທີມ (Theme) WordPress ທີ່ທັນສະໄໝ. Yatra ມາພ້ອມກັບເທັມເພຼດໜ້າ
ເວັບ; ສ່ວນທີມຂອງທ່ານຈະຄວບຄຸມໂຄງສ້າງ ແລະ ຮູບແບບຕົວອັກສອນທົ່ວໄປ. ເພື່ອການເຮັດວຽກທີ່
ເຂົ້າກັນໄດ້ດີທີ່ສຸດ, ເບິ່ງ **[Resa](https://wpyatra.com/best-wordpress-travel-theme/)**—
ທີມສຳລັບ Yatra ໂດຍສະເພາະຈາກ MantraBrain, ຟຣີໃນ WordPress.org.

### ໃບແຈ້ງໜີ້ ແລະ ວາວເຊີ ມີສະເພາະໃນ Pro ບໍ່?

ນັກທ່ອງທ່ຽວສາມາດເຂົ້າເຖິງໃບແຈ້ງໜີ້, ວາວເຊີ ແລະ ກຳນົດການເດີນທາງໄດ້ຈາກພື້ນທີ່ບັນຊີ
ໃນປລັກອິນເວີຊັນຟຣີ ຖ້າທ່ານຕັ້ງຄ່າເວັບໄຊໄວ້. [Pro](https://wpyatra.com/pricing/) 
ຈະເພີ່ມທາງເລືອກການຊຳລະເງິນ ແລະ ໂມດູນທຸລະກິດ — ແຕ່ມັນບໍ່ໄດ້ລຶບເອກະສານຫຼັກອອກ.

### ການບັນທຶກທົວ / ລາຍການທີ່ຢາກໄດ້ ເຮັດວຽກແນວໃດ?

ທົວທີ່ບັນທຶກໄວ້ຈະປາກົດຂຶ້ນເມື່ອ **[Yatra Pro](https://wpyatra.com/pricing/)** ເປີດ
ໃຊ້ງານ ແລະ ມີການເປີດໃຊ້ **ລາຍການທີ່ຢາກໄດ້ (wishlist)** ໃນການຕັ້ງຄ່າ Yatra.

### Yatra ເປັນມິດຕໍ່ GDPR ບໍ່?

ໃຊ້ເຄື່ອງມືຄວາມເປັນສ່ວນຕົວຂອງ WordPress ຮ່ວມກັບ Yatra: ສົ່ງອອກ ຫຼື ລຶບຂໍ້ມູນທີ່ກ່ຽວຂ້ອງ
ກັບຜູ້ໃຊ້ຕາມນະໂຍບາຍຂອງທ່ານ. ຂໍ້ມູນການຈອງ ແລະ ຂໍ້ມູນລູກຄ້າຈະຖືກເກັບໄວ້ໃນຖານຂໍ້ມູນ
WordPress ຂອງທ່ານເອງ — Yatra ຈະບໍ່ສົ່ງຂໍ້ມູນໄປຫາ SaaS ພາຍນອກ. ຂໍ້ມູນການຊຳລະເງິນແມ່ນ
ຖືກຈັດການໂດຍຜູ້ໃຫ້ບໍລິການຊຳລະເງິນທີ່ທ່ານເລືອກຕາມເງື່ອນໄຂຂອງພວກເຂົາ.

### ເອກະສານແນະນຳຢູ່ໃສ?

ເບິ່ງ **[docs.wpyatra.com](https://docs.wpyatra.com)** ແລະ **[wpyatra.com](https://wpyatra.com/)**
ສຳລັບຄຸນສົມບັດ, **[Pro](https://wpyatra.com/pricing/)** ແລະ ການອັບເດດ.

### ເອກະສານກ່ຽວກັບຊອດໂຄ້ດ ແລະ ບລັອກຢູ່ໃສ?

ເບິ່ງ **🧩 ບລັອກ ແລະ ຊອດໂຄ້ດ** ໃນລາຍລະອຽດຂ້າງເທິງ. ຂັ້ນຕອນການຕັ້ງຄ່າທັງໝົດ (ໜ້າເວັບ,
permalinks, URL ຊຳລະເງິນ) ແມ່ນມີຢູ່ໃນເອກະສານແນະນຳ.

### Yatra ມີຊອດໂຄ້ດສຳລັບກະຕ່າສິນຄ້າ ຫຼື ໜ້າຊຳລະເງິນບໍ່?

**ບໍ່.** ການຊຳລະເງິນ ແລະ ຂັ້ນຕອນການຈອງ ແມ່ນເຮັດວຽກຜ່ານເສັ້ນທາງ ແລະ ເທັມເພຼດໜ້າເວັບ
ຂອງ Yatra ເອງ — ທ່ານສາມາດວາງພວກມັນໄວ້ໃນໜ້າໃດກໍໄດ້ຜ່ານ permalinks ຂອງປລັກອິນ (ເບິ່ງ
ການຕັ້ງຄ່າ Permalink). ສ່ວນລາຍການສິນຄ້າ, ການຄົ້ນຫາ, ການເຂົ້າສູ່ລະບົບ ແລະ ບັນຊີ ຍັງຄົງ
ມີຊອດໂຄ້ດ ແລະ ບລັອກ ຕາມທີ່ລະບຸໄວ້ໃນລາຍລະອຽດ.

### Yatra Pro ລາຄາເທົ່າໃດ?

ລາຄາເລີ່ມຕົ້ນທີ່ **$99/ປີ** (Starter, ລາຄາຫຼຸດ) ແລະ ສູງສຸດແມ່ນ **$599/ປີ** (Scale
15 ເວັບໄຊ, ລາຄາຫຼຸດ). ແພັກເກັດຕະຫຼອດຊີວິດເລີ່ມຕົ້ນທີ່ **$499** ຈ່າຍຄັ້ງດຽວ. ທຸກລະດັບ
Pro ແມ່ນລວມການ **ຄືນເງິນພາຍໃນ 14 ວັນ**. ເບິ່ງ **[ລາຍລະອຽດລາຄາທັງໝົດ](https://wpyatra.com/pricing/)**.

## ການຣີວິວ

![](https://secure.gravatar.com/avatar/c2a377b477250d9abac9f68ffae0cd18231bc8a0775a82a9cee62fd45cf37a38?
s=60&d=retro&r=g)

### 󠀁[The best tour plugin ever](https://wordpress.org/support/topic/the-best-tour-plugin-ever/)󠁿

 [basolene](https://profiles.wordpress.org/basolene/) 12 ພຶດສະພາ 2026

I like the way Yatra plugin organizes the tours on the page and the way the elements
are organized on the tour card

![](https://secure.gravatar.com/avatar/d5c8991851c261ec89ca2821115e7ede9b85c0defac3ea49c5938def7302b8cd?
s=60&d=retro&r=g)

### 󠀁[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 ເມສາ 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.

![](https://secure.gravatar.com/avatar/76f1ba83c8f694d71641319319b52b78c76466cb46911e3551dcfb8ee916ad7c?
s=60&d=retro&r=g)

### 󠀁[Support is Horrible](https://wordpress.org/support/topic/support-is-horrible/)󠁿

 [jerryrveal](https://profiles.wordpress.org/jerryrveal/) 5 ກໍລະກົດ 2024 1 ການຕອບ
ກັບ

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.

![](https://secure.gravatar.com/avatar/66e087f7ab07f236cac1b14ea54ce9e2a7ee14fe965016aa362ddb0204df06ca?
s=60&d=retro&r=g)

### 󠀁[Best!](https://wordpress.org/support/topic/best-1295/)󠁿

 [gaenat](https://profiles.wordpress.org/gaenat/) 8 ພຶດສະພາ 2024

Best plugin and amazin support!

![](https://secure.gravatar.com/avatar/1dd5fdd8a8e9ff017aba6d3e1d8cedd5484ec87d673cd00255bac8ea2602fb3a?
s=60&d=retro&r=g)

### 󠀁[Is anyone there?](https://wordpress.org/support/topic/is-anyone-there-5/)󠁿

 [moiraskitchen](https://profiles.wordpress.org/moiraskitchen/) 20 ພຶດສະພາ 2023 
2 ການຕອບກັບ

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.

![](https://secure.gravatar.com/avatar/75f427e3acca5621693d75d6780f3f751c87a5f1b2ead1acb489f160952e94b6?
s=60&d=retro&r=g)

### 󠀁[Yatra Rocks](https://wordpress.org/support/topic/yatra-rocks/)󠁿

 [Zakaria Kalatozishvili](https://profiles.wordpress.org/logicaldata/) 15 ພຶດສະພາ
2023

Overall, I highly recommend the Yatra plugin to anyone who wants to enhance their
travel website’s functionality and provide their visitors with a top-notch booking
experience. Thank you, Yatra, for creating such a great plugin!

 [ ອ່ານການຣີວິວທັງໝົດ 22 ລາຍການ ](https://wordpress.org/support/plugin/yatra/reviews/)

## ຜູ້ຮ່ວມພັດທະນາ ແລະ ຜູ້ພັດທະນາ

“Yatra – Travel Booking & Tour Operator Software” ແມ່ນຊອຟແວໂອເພັນຊອດ (Open Source).
ບຸກຄົນຕໍ່ໄປນີ້ໄດ້ມີສ່ວນຮ່ວມໃນການພັດທະນາປລັກອິນນີ້.

ຜູ້ຮ່ວມພັດທະນາ

 *   [ MantraBrain ](https://profiles.wordpress.org/mantrabrain/)

“Yatra – Travel Booking & Tour Operator Software” ໄດ້ຖືກແປເປັນ 1 ພາສາທ້ອງຖິ່ນ. ຂໍ
ຂອບໃຈ [ທີມງານຜູ້ແປ](https://translate.wordpress.org/projects/wp-plugins/yatra/contributors)
ສຳລັບການປະກອບສ່ວນຂອງເຂົາເຈົ້າ.

[ແປ “Yatra – Travel Booking & Tour Operator Software” ເປັນພາສາຂອງເຈົ້າ.](https://translate.wordpress.org/projects/wp-plugins/yatra)

### ສົນໃຈຮ່ວມພັດທະນາບໍ່?

[ເບິ່ງລະຫັດ](https://plugins.trac.wordpress.org/browser/yatra/), ກວດເບິ່ງ [ຄັງເກັບ SVN](https://plugins.svn.wordpress.org/yatra/),
ຫຼື ຕິດຕາມ [ບັນທຶກການພັດທະນາ](https://plugins.trac.wordpress.org/log/yatra/) ຜ່ານ
[RSS](https://plugins.trac.wordpress.org/log/yatra/?limit=100&mode=stop_on_copy&format=rss).

## ບັນທຶກການປ່ຽນແປງ

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.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 <parent\_node>”_, _“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 departurereturn 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).

## ປລັກອິນເພື່ອການຄ້າ

ປລັກອິນນີ້ແມ່ນຟຣີ ແຕ່ມີການອັບເກຣດ ຫຼື ການຊ່ວຍເຫຼືອແບບເພື່ອການຄ້າເພີ່ມເຕີມ. [ເບິ່ງການຊ່ວຍເຫຼືອ](https://wpyatra.com?ref=wordpress.org)

## ຂໍ້ມູນກຳກັບ (Meta)

 *  ເວີຊັນ **3.0.13**
 *  ອັບເດດຫຼ້າສຸດເມື່ອ **2 ອາທິດ ທີ່ຜ່ານມາ** ທີ່ຜ່ານມາ
 *  ການຕິດຕັ້ງທີ່ໃຊ້ງານຢູ່ **600+**
 *  ເວີຊັນ WordPress ** 6.0 ຫຼື ສູງກວ່າ **
 *  ທົດສອບເຖິງເວີຊັນ **7.0.2**
 *  ເວີຊັນ PHP ** 7.4 ຫຼື ສູງກວ່າ **
 *  ພາສາ
 * [English (US)](https://wordpress.org/plugins/yatra/) ແລະ [Lao](https://lo.wordpress.org/plugins/yatra/).
 *  [ແປເປັນພາສາຂອງເຈົ້າ](https://translate.wordpress.org/projects/wp-plugins/yatra)
 * ແທັກ
 * [tour booking](https://lo.wordpress.org/plugins/tags/tour-booking/)[Tour Operator](https://lo.wordpress.org/plugins/tags/tour-operator/)
   [travel](https://lo.wordpress.org/plugins/tags/travel/)[travel agency](https://lo.wordpress.org/plugins/tags/travel-agency/)
   [Travel booking](https://lo.wordpress.org/plugins/tags/travel-booking/)
 *  [ມຸມມອງຂັ້ນສູງ](https://lo.wordpress.org/plugins/yatra/advanced/)

## ການໃຫ້ຄະແນນ

 4.6 ຈາກທັງໝົດ 5 ດາວ.

 *  [  ການວິຈານ 5 ດາວ ຈຳນວນ 20 ລາຍການ     ](https://wordpress.org/support/plugin/yatra/reviews/?filter=5)
 *  [  ການວິຈານ 4 ດາວ ຈຳນວນ 0 ລາຍການ     ](https://wordpress.org/support/plugin/yatra/reviews/?filter=4)
 *  [  ການວິຈານ 3 ດາວ ຈຳນວນ 0 ລາຍການ     ](https://wordpress.org/support/plugin/yatra/reviews/?filter=3)
 *  [  ການວິຈານ 2 ດາວ ຈຳນວນ 0 ລາຍການ     ](https://wordpress.org/support/plugin/yatra/reviews/?filter=2)
 *  [  ການວິຈານ 1 ດາວ ຈຳນວນ 2 ລາຍການ     ](https://wordpress.org/support/plugin/yatra/reviews/?filter=1)

[Your review](https://wordpress.org/support/plugin/yatra/reviews/#new-post)

[ເບິ່ງ ຄຳຄິດເຫັນ ທັງໝົດ](https://wordpress.org/support/plugin/yatra/reviews/)

## ຜູ້ຮ່ວມພັດທະນາ

 *   [ MantraBrain ](https://profiles.wordpress.org/mantrabrain/)

## ການຊ່ວຍເຫຼືອ

ບັນຫາທີ່ໄດ້ຮັບການແກ້ໄຂໃນສອງເດືອນຜ່ານມາ:

     1 ຈາກ 1

 [ເບິ່ງຟໍຣັມການຊ່ວຍເຫຼືອ](https://wordpress.org/support/plugin/yatra/)