Until recently, these extras were often missing from OTA bookings. Customers could buy a tour, but not the upsell. Or worse, they’d request it through a separate form or in person, leaving you with gaps in your manifest and revenue tracking.
Now, that’s changing. Thanks to new capabilities, operators can now offer and process add-ons over the API, so even OTA bookings can include your upsells.
This is a big win for accuracy, revenue, and customer experience.
Why it matters:
- Upsells aren’t just nice extras; they’re part of your revenue strategy
- Better data: All add-ons appear in your system, no manual work
- Happier guests: They get what they booked, with no surprises
- Less chaos on the day: Your team knows exactly who ordered lunch
The techy part (but make it quick): Palisis now supports add-ons over API connections. That means you can send and receive upsell information across platforms, including OTAs, so that everything syncs cleanly with the booking.
If your reseller supports it, your add-ons are included automatically. If they don’t yet, it’s a great time to ask them why not.
Visit our support article for a step-by-step guide on getting started
Dinner with the dev team
Imagine this: you’re a tour operator at dinner with our product team. You start explaining how frustrating it is when Sharon adds a child seat or champagne upgrade and it never shows up in your system.
Our dev nods. Then says:
“We’ve enabled structured payload support for API-connected third-party modifiers.”
You blink.
Luckily, there’s a translator at the table. She leans in and says:
“What he means is: when someone books your tour and adds an extra, it’ll now show up properly in your system.”
You nod. The wine arrives. You keep going.
You: “Sometimes the guest says they added something, but it’s not in our manifest. Then my team looks bad.”
Dev: “There’s no upstream visibility because modifier metadata wasn’t passed.”
Translator: “We fixed that. Now your team gets the full picture.”
You: “And can we track what extras are selling best?”
Dev: “The analytics pipeline is aware of transactional granularity.”
Translator: “Yes.”
By dessert, you’re relaxed. Sharon gets her champagne. Your team gets fewer headaches. The dev finishes his tiramisu and quietly releases three more microfeatures.
Need help figuring it out? Reach out to us for tailored assistance on getting started with add-ons over API