What B2B travel supply means, and how GTOS talks about it

GTOS is the Global Travel Operating System from Voraal, built on operating experience across 100,000+ trips. GTOS itself is the operating system for policy, approvals, the trip record, spend and duty of care. Supply — where searchable content comes from — is a related but separate question. This entry defines the term, points to the honest product conversation, and states a limit we will not blur.

Supply is not the same as the operating record

A company can have rich content and still lose the trip if policy, approvals and documents live somewhere else. Conversely, a strong operating record still needs content travellers can actually book. In GTOS, in-policy search and a specialist desk already work the record. How a given source of hotel, ground, or other content is connected is scoped during implementation, as described on hotel content and ground transport. We do not name aggregators, carriers, or chains, and we do not publish a certified connector catalogue.

Suppliers in the product sense is about the supplier dimension of the programme — who was booked, what was spent — not a claim that every source is already live.

Where Avunzo sits, and the status you should remember

Avunzo is designed to connect travel content and booking flows to your own channels and is not yet live on production; early access is available on request. For agencies thinking about white-label or broader supply, Avunzo is the relevant Voraal conversation. It must be described with that status in view. It is not a claim that a particular B2B source is already inside GTOS, and it is not a consumer marketplace.

USD is the main currency on this site. Software pricing is in USD and available on request. We do not publish content-source fees or package rates. Each company or client file remains inside its own data boundary. Access is by role. We do not claim certifications we do not hold, including any implied certification of a distribution standard.

How to use the term in a buying conversation

Ask two questions. First, do you need an operating system for the trip, the policy and the desk? That is GTOS. Second, do you need a broader B2B content or channel path? That may be an Avunzo conversation, with early access, or an implementation discussion about sources that can actually be connected today. A demo should keep those questions in separate chapters, so a live trip record is never confused with a supply product that is not yet in production.