How to Build a Multi-Experience Package With One Link

What is a package and how is it different from an itinerary?

An itinerary is a day-by-day travel plan: experiences, places and times, with a public link you can share with the traveler and edit whenever plans change, keeping the same link. A package, on the other hand, is the sellable version of that plan: several experiences bundled together, with a per-experience breakdown and a single payment link.

The practical difference is this: the itinerary is for planning and showing; the package is for charging. In Terra, Skyline's AI booking engine, you first build the itinerary with the traveler (or generate it by chat) and, once it's ready, you turn it into a package with one click. The traveler sees exactly what they're paying for, experience by experience, but only has to make one payment.

Picture an agency in Cartagena putting together a three-day plan for a couple: a walking tour of the historic center, a catamaran trip to the Rosario Islands, and a Caribbean cooking class. Instead of sending three separate payment links and chasing three confirmations, the agency builds an itinerary, reviews it with the couple, and converts it into a single package with a single link.

How do you build an itinerary before turning it into a package?

Terra builds day-by-day itineraries tailored to each traveler, with a public shareable link. This is useful even before you think about selling anything: it's the tool for sorting out ideas with the client.

Step 1: create the itinerary

You can build the itinerary from the Terra dashboard or by asking an AI assistant connected via MCP (Claude, ChatGPT or Gemini), since the MCP exposes tools to create and update itineraries directly from chat. You define, day by day, which experiences go in, in what order and at what time.

Step 2: share and adjust

The itinerary has a public link. You send it to the traveler, they review it, request a change (drop an activity, move a time slot), and you edit it while keeping the same link. There's nothing to resend: the traveler always sees the latest version at the same address.

Step 3: decide what gets sold

Not every itinerary becomes a package. Sometimes the itinerary is just a reference guide for a traveler who already booked each piece separately. The move to a package happens when you want to charge for the whole plan at once.

How do you turn an itinerary into a package with a single payment link?

Once the itinerary is approved, you convert it into a package: several experiences bundled with a per-experience breakdown and a single payment link. The traveler doesn't need to understand the internal mechanics of your operation; they just see a total and pay once.

What the package keeps from the original itinerary

The package keeps the itinerary's experience structure, but adds a commercial layer on top: a price for each experience, a total, and the payment link. It's the same logic as quickpay (a booking with a payment link from a single chat line), but for several experiences combined instead of one.

What the operator sees when building it

When building the package, you define which experiences go in and in what quantity. The system builds the breakdown automatically: each line shows the experience and its value, adding up to a total. This matters because prices are computed server-side from the catalog, not by the AI or by the operator by hand, so there's no risk of a quote going stale or a value being made up.

What exactly does the customer see at checkout?

The customer receives a single link. When they open it, they find the per-experience breakdown (what each activity includes and its price) and the package total. They don't get three or four different links, and they don't have to add anything up themselves.

Terra has its own checkout for online payments, with a 30% deposit option and the balance paid later. This means the customer can confirm their spot with a fraction of the total value and complete the payment later, without the operator having to manually chase the rest. The deposit confirms the booking; the balance stays pending until the date you set.

If the operator doesn't yet use online payments, the booking is confirmed via WhatsApp with the same link, so the "one link for the whole package" flow works the same way, with or without digital payment.

Back to the Cartagena example: the couple opens the package link and sees three lines (walking tour, catamaran, cooking class) with their individual price and a total. They decide to pay the 30% deposit to secure the spot and leave the balance to pay before traveling. The agency didn't have to put together three quotes or send three payment links.

How do you edit a package after it's sold?

Plans change: a traveler asks to add an experience, change a date, or drop an activity after already paying the deposit. This is where the link between itinerary and package becomes useful: you can go back to the itinerary, edit it (the link doesn't change), and adjust the package accordingly.

Common editing scenarios

• Adding an experience: it gets added to the breakdown and the package total updates.
• Changing a date: the underlying itinerary is adjusted without touching the link the traveler already has saved.
• Removing an activity: the breakdown reflects the change and the pending balance is recalculated.

In every case, the customer keeps the same link. There's no need to generate a new package or ask them to pay again from scratch. This cuts the typical friction of spreadsheets or traditional booking engines, where every change means manually redoing the quote and resending everything by email.

What to do if the package has already been paid in full

If the package is already fully paid and the traveler asks for a change that raises the value, the operator handles the additional charge through their own flow (a new payment link just for the difference, for example). Terra doesn't force a single path here: the logic of server-computed prices still applies, so the new value always comes from the real catalog, not from an error-prone manual calculation.

Table: itinerary vs. package in Terra

Why this matters for day-to-day operations

An operator who builds custom tours (several days, several combined experiences) usually ends up with several loose quotes per customer: one link for the day tour, another for the transfer, another for dinner. That multiplies follow-up work and raises the odds that something is left unpaid or unconfirmed.

Turning the itinerary into a single package with a single link fixes that problem at the root: the customer has one thing to pay and one thing to review. The operator has one status to monitor (paid, deposit, pending) instead of several scattered ones.

This connects directly to how Terra organizes the whole operation on a single calendar: bookings, guides, departures, travelers and payments in one place. A well-built package isn't just a convenience for the customer; it's order for the operator. If you want to understand how this connects to operating Terra by chat from an AI assistant, AI Booking Engine for Tour Operators: Full Guide covers that full flow with MCP.

What to do now

If you already have an itinerary built for a client with more than one experience, convert it into a package before sending several separate links: check the breakdown, confirm the total, and decide whether to activate the 30% deposit or confirm via WhatsApp instead.