TNS Booking Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
TNS Booking connects your WordPress website to an existing TravelNetSoft (TNS) service. Display destinations, service groups and bookable travel experiences from your configured TNS instance without manually copying the catalogue into WordPress.
A TNS account, an API endpoint and valid PublicKey/SecretKey credentials are required for catalogue, availability, booking and payment-link functionality. A TNS account is provided only after the required separate service agreements have been signed. Installing this plugin alone does not create a TNS account or supply travel products.
The plugin is distributed as one full version. There is no FREE/PRO feature split or plugin license-key activation. The external TNS service is separate and may be subject to the service operator’s commercial agreement and fees.
Features
- Destination and service-group browsing.
- A common service-list layout across destination, group and search flows.
- Search by multiple destinations and service groups, check-in date and duration.
- Checkbox dropdowns with filtering and a compact row in wide layouts.
- Dates displayed as dd.MM.yyyy; search/API values use yyyy-MM-dd.
- Service images, descriptions, itineraries, inclusions and exclusions.
- Availability and dated booking options supplied by TNS.
- Service variants, passenger choices, quantity and price breakdowns.
- A browser-based shopping cart and customer checkout form.
- Server-side recalculation of cart prices before requesting a payment link.
- Automatic Payment Success and Payment Error return pages.
- H1/H2 headings, dynamic page titles, meta descriptions and contextual image/link attributes.
WooCommerce and the TNS Explorer theme are not required. The plugin supplies its own booking/search interface and uses your active theme for the surrounding website.
External services and data use
This plugin depends on an external TNS service. Its purpose is to retrieve travel content and availability, validate booking options and request a payment URL. The API base URL is entered by the site administrator under Settings > TNS Booking; it is not a fixed analytics or advertising endpoint.
Service provider: TravelNetSoft by GOL-IT Consulting GmbH.
Website: https://travelnetsoft.com/
Privacy policy: https://travelnetsoft.com/legality/dataprotection
Terms of service: TNS service use is governed by separate agreements that must be signed before a TNS account is issued. The plugin cannot provide its connected booking functionality without that account. The signed agreements define service access, usage conditions and applicable commercial terms. Contact TravelNetSoft or the operator of the configured TNS instance through the service website to arrange onboarding and receive the agreements. These external-service agreements are separate from the GPL license covering the plugin code; no additional plugin license-key activation is required.
When information is sent:
- When a visitor opens a booking view, the website requests the relevant destinations, service groups, service details, images, itineraries, dates or prices from the configured TNS API.
- Search requests send selected country names, service-group IDs, dates and duration.
- Viewing dated options and submitting checkout send service IDs, travel dates, passenger counts, selected variants and quantities for validation and price calculation.
- Submitting checkout sends the customer’s name, address fields, city, postal code, state/region, country code, phone number, email address and optional TNS customer code, as entered in the form, together with the validated booking/cart data.
- The payment-link request includes the WordPress site’s generated Success and Error return URLs.
- Server-side SEO generation may request a service or service-group record and cache the response in WordPress for approximately five minutes.
The PublicKey, a timestamp and an authentication hash are included in authenticated API URLs. The SecretKey is stored in WordPress settings and used on the server to calculate the hash; it is not included in the plugin’s frontend configuration or sent as a plain SecretKey field. Site administrators must protect their WordPress database and API credentials.
Requests from WordPress expose the website server’s network information to the configured API infrastructure. Images supplied by the API are loaded by the visitor’s browser from the returned image URLs; these image hosts may receive the visitor’s IP address and browser/referrer information. Continuing to payment redirects the visitor to the URL returned by TNS, which may be hosted by an external payment provider. The applicable TNS instance operator, image hosts and payment provider may have additional privacy policies and terms that the website operator needs to disclose to visitors.
This plugin contains no analytics or advertising SDK, does not download executable PHP or JavaScript from the TNS service and does not collect card details in its checkout form. The TravelNetSoft website’s own analytics/cookie notices describe that website and do not mean this plugin installs those tools.
Local storage and retained data
Cart items are stored in the visitor’s browser localStorage, namespaced by website and PublicKey. The cart contains selected service information, travel dates, quantities, passenger counts, options and calculated amounts. The customer contact form fields are not written to localStorage by the plugin.
The cart remains until cleared through the cart interface, browser storage is cleared, or a successful checkout API response returns a valid payment URL. Cart removal at that stage is not proof that payment has been completed. A failed checkout request leaves the cart in place.
WordPress stores connection settings, generated return-page IDs and short-lived SEO content caches. The plugin does not create local WordPress booking/order records. Payment/booking processing and records are handled by the configured backend service.
Deactivation keeps settings and the generated return pages. The plugin does not automatically delete these on removal. Browser carts and records held by an external TNS service are separate from WordPress plugin files. Website operators should describe the actual deployment and external providers in their own privacy notice.
Source Code
All PHP, JavaScript and CSS source used by the plugin is included in this package. No build step, remote executable code or third-party JavaScript framework is required. Bundled browser scripts are in assets/.
Optional TNS CMS homepage
Compatible themes may request homepage groups and offers through this plugin.
No CMS request is made merely by activating the plugin. In TNS Explorer, explicitly
enabling the TNS homepage permits requests to your configured TNS API and loading
of TNS-hosted images. Turn that option off to stop homepage CMS requests.
CMS responses are cached for five minutes; stale responses may be used for one day
on connection failure. Refresh TNS content invalidates only this homepage cache.
The existing endpoint, PublicKey and SecretKey settings authenticate CMS requests
using the same UTC timestamp and SHA-512 contract. Credentials stay server-side.
API service/privacy/account terms are described in External services above.
Identifier rename in 1.1.17
The plugin slug, display name, API field names, DOM classes and translation domain
remain unchanged. Plugin-owned PHP classes/functions, settings names, shortcode
names, cache keys, AJAX action/nonce names, REST namespace, URL query parameters,
script/style handles and JavaScript globals now use travelnetsoft/TravelNetSoft.
This is a name-only release. No migration or compatibility aliases were added.
Existing installations must save their connection settings under the new names
and replace old shortcodes in their pages. For example, [tns_booking] becomes
[travelnetsoft_booking] and [tns_search] becomes [travelnetsoft_search].
Old saved return-page references and cart keys are not read under their old names.
Code outside the plugin calling the old names must use the new names.
Screenshots
No screenshots provided

