Sofia & Oliver — booking direct Pick the tour, see what pairs, add the cruiseJourney check flags the gap, suggests the railOne payment plan for the whole trip + Add shore excursion · same order, same rules
The selling & order platform for multi-day travel
Keep the system you run today. Journeys sells your tours, cruises, rail and air as one order, in every channel. Journeys Orders handles everything after payment.
The composite architecture
Pick your supply mix — that is the only choice. Every order lands in Journeys Orders and writes back to the systems you keep.
Your system, our supply system and third parties. One basket, one order.
One spine for every order, whatever the supply mix above.
If a source times out, the basket waits or declines — it never oversells. Card data goes straight to the payment provider, never through us.
The modules at work
Three modules, one record. Change it anywhere, it changes everywhere.
Booking engines stop at checkout
Pick your world. Each order below takes one real change after payment — the kind that costs someone a week today.
The Journeys family
One platform, four modules: Storefronts, Res Console, Distribution, Orders. Start with the modules you need — Orders is always there, keeping your systems in step.
One selling and order platform, four modules. Every module below touched ORD-48213.
The platformGave Sofia & Oliver the direct booking: pick the tour, pair the cruise, one payment plan.
ModuleTook the call, loaded the order, moved the departure date across every source system.
ModuleGave the advisor their portal and set the commission per agreement — then clawed it back on the cancellation. API and partner channels live here.
ModuleEvery sale landed here. Dates moved, pieces cancelled at the right fee, documents reissued — and everything written back to the systems you keep.
Module · always onRan the journey check across every module — spotted the 2-day gap, suggested the rail. We call it connection intelligence.
Across the modulesKeeps selling on tour: guest app, tour director app, upsells — as order lines, not spreadsheets.
Pairs with JourneysEdge Studio · across everything
Edge Studio is the control layer across the whole platform. Every rule, screen and connector you’ve seen is shaped the same way: describe the change, AI drafts it, your named people approve it.
“Let guests pair the cruise with any tour that ends within 4 days — it’s 2 today.”
Journeys Rules: gap tolerance 2 → 4 days.
17 new pairings become possible · every deposit and cancellation rule still holdsReviewed and approved by your head of product.
One click · versioned · revertibleEnforced in every channel — guest, advisor, console, API.
6 minutes end to endSame trail every time: you describe it, AI drafts it, a named person approves it, the platform keeps every booking rule intact. Nothing ships unreviewed.
The agentic team
Three agents come with the platform. Talking to them costs nothing. When you want the work done, that’s the product — and a named person signs off every time.
Your platform expert
Ask anything about your own setup — answers in minutes, checked against your live environment.
Kai executes the change: planned, verified, and signed off by a named person.
Your supplier partner
Advice on your suppliers — Runa reads a contract and tells you what’s in it: rates, seasons, policies, gaps.
Contracts become live rates, supplier quotes become cost lines — extracted, human-reviewed, loaded.
Your intelligence analyst
Talk to your data in plain language — inventory gaps, pricing anomalies, payment status.
Standing intelligence: digests, watchlists and reports your team actually reads.
Where you start
You can take the value and still say no at every step. That is the design.
Keep Kaptio as your core. Add Journeys as your guest, advisor and call-centre channels.
The shortest path — you’re already connected.
Your system feeds the supply. Every sale lands in Journeys Orders and writes straight back to your system, so finance and operations carry on unchanged.
This is what your booking-engine budget was supposed to buy.
White-label the selling layer over your suppliers. Partners book and modify from one order, with commissions tracked per agreement.
Your inventory, everyone’s storefront.
The proven process
Not slides. A proof built on your real systems, judged by your own people.
AI agents draft each connector; our engineers review and certify. Your system goes first.
Real products and prices through the new adapters — marked live where they are.
What combines, what it costs, what deposit applies — configured, not hard-coded.
Guest books. Advisor extends. Your agent moves the date. One change you ask for mid-demo ships before the end.
The engine behind Journeys Orders has run tour and cruise bookings for a decade on Kaptio’s Salesforce platform.
With an expedition cruise line, ahead of public launch.
The first partners are being picked now — they shape the product. We say this plainly because you would find out anyway.
Everything in the proof is shaped through Edge Studio: AI drafts, people review, the platform enforces the booking rules.
Day 1 starts with a list, not a contract
Three weeks later you’re walking a working proof on your own systems.