How it's built
Working with the WordPress booking engine
WP Travel Engine provides the core trip and booking functionality. The trip content type uses the trip slug, and the customization work builds around the plugin's existing hooks and data model. This approach keeps trip management within WordPress and reduces the need to recreate booking features that the plugin already provides.
The Tourex theme controls important parts of the presentation layer. When a trip page does not render in the intended layout, both the hook callbacks and the template's parent containers are used to creat the intended layout. Hook priority determines callback order but does not independently create a two-column layout or repair an incompatible wrapper.
Flitt checkout integration
The payment work separates order creation from the embedded checkout step and from final payment confirmation. The checkout flow uses the provider's token endpoint to initialize the embedded payment interface.
The token endpoint was distinguished from a separate checkout URL endpoint, and the Create Order response was reviewed against the signature checks applied by the integration.
A successful checkout initialization alone is not sufficient evidence that the live payment flow, callbacks, and booking-status updates are all working correctly, so I completed automated and manual end-to-end verification for those stages.
Currency display without changing the charge
The currency-switcher was built to be intentionally display-only. The planned currencies were Georgian lari (GEL), US dollars (USD), euros (EUR), and British pounds (GBP), with USD retained as the booking system's base currency. Frankfurter was used as the exchange-rate source, and the switcher was placed in the Elementor header as well as a custom footer section only show on mobile.
A modal was used to explain that converted values are indicative and that the final booking is charged in the base currency. This boundary matters because changing a display preference must never silently change the amount or currency sent to the payment gateway.
SEO, FAQs, and structured data
Yoast SEO was already participating in title and metadata generation, so custom SEO code needed to work with that output.
The FAQ implementation uses ACF fields named faq_question andfaq_answer. FAQPage JSON-LD was and ontinues to be generated from the same content users can see on the page.
Product/Offer-style schema also reflected the actual tour offer, including the correct price and currency. Since WP Travel Engine can emit trip-related schema, its existing output was inspected before custom structured data wass added. The aim was consistent, non-duplicated metadata rather than simply adding more JSON-LD.
Maintainability and debugging
The implementation uses WordPress-native extension points where possible, including plugin settings, hooks, filters, custom fields, and theme templates. PHP development tooling and WordPress/WP Travel Engine stubs were also part of the local workflow to improve editor completion and catch integration issues during development.