Integrate External Content

Already managing content in another system? Decide which integration approach fits your setup so you only have one single point of truth for your data.

Single point of truth for all your data

You don't have to manage content in GUIBO. If you already maintain trip data elsewhere — routes in a mapping tool, hotels in a booking system, whole itineraries in a trip builder — GUIBO works with that in order to support the single point of truth concept for all your data.

In order to find your best integration setup, you need to understand on how you want to create releases in GUIBO. A release is one set of travel documents published for one booking — delivered to travelers via a Trip Link. Every booking in GUIBO results in one release.

Choose your setup: where are itineraries assembled?

There are two ways to integrate external content. The deciding question is where you are assembling your itineraries based on building blocks.

• Do you assemble itineraries in GUIBO?

• Or does your own system — a trip builder — already assemble them from building blocks?

The more individual itineraries you orchestrate in your own system, the more the second option pays off.

Option 1: Assemble itineraries in GUIBO (template-based)

You build itineraries in GUIBO with guidebook templates based on your building blocks. Each booking turns a guidebook template into a booking specific release.

Best when you have standard products for which all bookings have more or less the same itienrary with variations in accommodations only.

Option 2: Let your system deliver itineraries (on-demand)

Your trip builder sends the full itinerary per booking, and GUIBO generates the guidebook automatically — no pre-existing guidebook templates.

Best when you already orchestrate itineraries based on reusable building blocks in an existing itinerary builder.

Compare: template-based vs. on-demand

Dimension	Template-based	On-demand
Itineraries assembled in	GUIBO	Your own system
Per-booking automation	Hotels & dates automatic; itinerary changes manual	Entire itinerary automatic
Roadbook PDF	✓	✗
TourMaps	✓	✗ Possible with parent guidebook templates based on static itineraries
IT dependency	Lower	Higher
Best fit	You assemble & control itineraries in GUIBO	You already orchestrate itineraries elsewhere

Decide: which setup fits you?

If you're unsure, start with template-based. It's the lower-risk path: you keep full output, stay in control, and learn what you actually need — and you can move high-volume or fully individual itineraries to on-demand later.

Choose on-demand when you already orchestrate many itineraries based on building blocks in your own trip builder and want to avoid rebuilding them in GUIBO.

Next Steps

Your situation	Next step
Itinerary managed in GUIBO with guidebook templates	Integrate external content when using guidebook-templates to create releases from
Itinerary managed in your external system and releases are created on-demand	Integrate external content when using on-demand releases to directly create release