Destination and inventory content, governed from import to booking site

Bulk-load hotel, resort, tour and destination data from internal systems, curate, translate and enrich it through governed workflows, and publish it to search and booking applications in each locale you serve.

Request a demo Talk to sales
Seaview ResortProperty
Imported from
Property system, last night’s bulk load
Translations
en, de, es in sync; fr behind
Workflow
Approved
Published to
Search index and booking site, 06:15
Example property: where it came from, its translations and where it went live. Illustrative data.

What travel teams need

The same destination and property content has to reach several sites and booking applications, in many languages.

Catalog size
Destinations, properties and offers add up to more than anyone can update by hand.
Content from elsewhere
Much of it lives in other systems and arrives in repeated imports that must combine with your own.
Language drift
Each market needs its own locale, and translations fall behind when the source changes.
Constant change
Property details and promotions can’t wait for the next big release.
Hotelplan
The Hotelplan booking site, built on Gitana, with flight, hotel and cruise search
The Hotelplan booking site, built on Gitana, with flight, hotel and cruise search.

How Gitana moves a catalog from import to booking

Gitana handles large catalogs in many languages and publishes updates to your sites and booking applications.

  • Catalog-wide search

    Full-text search and structured queries run across the catalog, so editors can find and update any item.

  • Repeatable bulk import

    Map and transform content as it is imported, and bulk-load it in one transactional operation.

  • Translations in sync

    Generate translations into each locale that stay in sync with the master content and move through approval together. Access policies can limit each market’s editors to their own locale.

  • Safe, incremental updates

    Work in branches and publish incrementally, on demand or on a schedule.

Publish to booking siteChanged items only
  1. propertySeaview Resort · amenities changed
  2. propertyHarbor Lodge · description changed in es
  3. offerWinter escape · new, with its image
  4. destinationLisbon · guide updated
Example incremental publish: only what changed goes out, with related items such as an offer’s image. Illustrative data.
Editor of Spanish TranslationsAccess policy
{
  "title": "Editor of Spanish Translations",
  "statements": [{
    "action": "grant",
    "roles": ["editor"],
    "conditions": [{
      "type": "locale",
      "config": { "locale": "es" }
    }]
  }]
}
Example policy that grants the editor role over one locale, so each market’s editors work only on their own translations.

Workflow & automation Publishing & delivery Import and transfer guide

See how Gitana fits your content

In a demo, a solutions engineer walks you through Gitana around your use case. The same call covers architecture, security, deployment and procurement questions. In a guided evaluation, you work on your own content with one of our engineers on Gitana Cloud.

Request a demo Request a guided evaluation