#JP-0612Confirmed
Japan Highlights · Jun 12
Templates that scale.
Departures that don't.
You do not design a trip once — you run it many times. Build the programme once, then duplicate it into every departure, each with its own dates, pax, rooming, and supplier lines.
Live previewJapan Highlights · 10 daysGroup base · 50 departures planned
Booked12
Confirmed18
Pre-dep.9
Operating6
The headline number
One template, duplicated = a season of departures that move independently from the first change onward.
What matters to a tour operator
The five things that change a season.
Tour operators have a small number of signature itineraries that run dozens of times a year. The work is in the variation: this group gets twin rooms, that one gets singles, the next has a vegetarian. Abrid models the variation, not just the template.
01
Trip templates & one-click duplication
Save a trip as a template. Duplicate it for the next departure with new dates and pax. The TripDuplicator service does a deep-copy of the entire graph — days, events, choice groups, costs, content templates. The new trip is fresh and editable.
↗
02
Library of saved days & events
Reusable building blocks. SavedDays for repeat days. SavedEvents for repeat activities. Copied on use, never linked, so old trips don't break when you edit the template.
↗
03
FIT, Group, and MICE segments on one base
The same Japan grand tour can run as a private FIT for two, a scheduled group of 16, or a corporate MICE incentive for 40. The Trip carries a segment field; the same content backbone serves all three.
↗
04
Rooming lists, generated automatically
Booking participants + room assignments → rooming list PDF, with guest names, room types, special requests. Sent to the accommodation supplier as a standard document.
↗
05
Pipeline kanban for a season of bookings
Custom columns per organization (Booked → Confirmed → Pre-departure → Operating → Departed → Closed). A season of departures moves through the kanban without anyone re-typing a thing.
↗
Operations at scale
From one trip to fifty departures.
Tour operators don't just need to design a trip — they need to run it many times, each instance with its own pax, dates, suppliers, and finance. A pipeline you define, automations that schedule the work, and documents built from the live booking keep parallel departures on one readable board.
- Per-departure pax and rooming configurations
- Confirmation status tracked per supplier line, per departure
- Travel vouchers and rooming lists generated from the live booking
- Cost variance tracking when supplier rates shift mid-season
- External reference field for back-office system propagation
Live previewJune season · 50 departuresPipeline kanban
Booked2
#JP-0605Confirmed
Japan Highlights
#JP-0612Confirmed
Japan Highlights
Confirmed3
#JP-0619Confirmed
Japan Highlights
#JP-0626Confirmed
Japan Highlights
#JP-0703Confirmed
Japan Highlights
Pre-dep.1
#JP-0522Ready
Japan Highlights
Operating2
#JP-0515Ready
Japan Highlights
#JP-0508Ready
Japan Highlights
1click
Duplicates a whole trip — days, events, costs, and supplier assignments.
03
Segments (FIT, group, MICE) from one base trip.
04
Documents generated per departure from the live booking.
00
Sold trips disturbed by a library edit — saved days are copied on use.
FAQ
Common questions.
Can I run the same trip in different languages?+
Yes. Trip titles and descriptions are multi-language, and each trip carries its own display language. The web proposal and its PDF render in that language — the one you set on the trip, not one guessed from the reader's browser.
What if a hotel raises rates mid-season?+
Update the supplier service's seasonal pricing. Future trips and quotations pick up the new rate. Existing bookings are frozen — their cost snapshots don't change unless you explicitly revise the booking item, with variance tracked.
How do I handle different rooming for different groups?+
Per-cost quantity configuration. The same accommodation event can have its room counts adjusted per booking — "this group needs 8 doubles and 4 singles" — without rebuilding the trip. The selection is stored per-booking; the template stays clean.
Can I have different trip templates per season?+
Yes. Folders organize trips and templates by season, region, or any other dimension. Pipeline status is orthogonal to folder — archived trips disappear from the kanban without losing their folder placement.
Plan a season in an afternoon.
Create an account, build one programme, and duplicate it into the departures you actually run.
No credit card required to start