Skip to main content

New Discovery: TripCache Packages

Written by Product Management

TripCache packages are the "Package Deal" results travellers see on the Holidays tab (see New Discovery: Holidays) — pre-priced hotel+flight combinations that show up instantly, instead of making the traveller wait on a live search. If there's no cached match for what they searched, or they searched for more than one room (TripCache only prices single rooms), they're taken to the live Hotel + Flight result instead and never notice the difference.

What you can configure

Two places in Cockpit, both under Settings → Distribution Channels → [your channel]:

  • On the Discovery tab: "Show TripCache packages in holidays" — turns Package Deal results on or off for your site. This is the only everyday on/off switch you need.

  • On the Integrations tab, under TripCache: a single TripCache API Key field. Nezasa provisions and gives you this key — without it, no TripCache flights or packages are served for your channel at all, regardless of the toggle above.

What Nezasa configures on your behalf

Which hotels actually get cached — the airports covered, the star/review-score range, how far ahead offers are cached, which stay lengths and traveller combinations — is scope that Nezasa sets up and tunes for your TripCache tenant. It isn't something you configure yourself in Cockpit. If you want the scope changed (a new airport added, a different star range, more stay-length options), raise it with Nezasa support rather than looking for it in your settings — it isn't there.

Troubleshooting "no packages are showing up"

  1. Is "Show TripCache packages in holidays" actually on, and is a TripCache API Key filled in on the Integrations tab? Both are needed.

  2. If both are set and you still see zero Package Deal results: the search you're testing with may simply be outside what's currently cached for your channel (wrong airport, an uncommon stay length, a date too far out, more than one room). Try a well-known route, a round number of nights (7 is common), and a single room first.

  3. Still nothing after that: contact Nezasa support to confirm your TripCache scope and that the cache import has actually run recently for your channel — it runs on its own schedule, not on demand.

Did this answer your question?