Tour Template Builder workspace
Build Tour Templates from Components.
Saved tour templates.
| Code | Name | Description | Status | Duration | Sell Price | Travel Dates | Components |
|---|
Mode: New
⋮
Template configuration — pricing & dates
Add Active components to build your tour template.
| Order | Day Offset | Example Date | Product Name | Supplier | Fare | RRP | Nett | Addon | Choice group |
|---|
Preview the template by example date and component class.
Validate the selected draft and inspect the final JSON payload.
Validation
JSON
Find & Replace Component
Swap a PPDID across tour templates and update any future departure overrides.
| Code | Name | Status | Old Nett | New Nett | Δ Nett |
|---|
Departures inherit components from their template — replacing in the template covers them. Only departures with an existing product override for the find PPDID (✓) will have data written.
| Departure Code | Template | Start Date | Status | Old Nett | New Nett | Δ Nett | Override |
|---|
Component availability
Cached availability per date for a component (Refreshed reguarly). Refresh button pulls the next 12 months (cached) .
Stored availability for the selected component across the year.
Components workspace
Manage reusable components for the current branch.
All saved components.
| Product ID | Product Name | PPDID | Fare | Travel Start | Travel End | Active Until | RRP | Nett |
|---|
Search TDMS by Product ID and load all fares.
| PPDID | Fare | Travel Start | Travel End | Active Until | RRP | Nett |
|---|
For products not in TDMS — bespoke add-ons, local extras, custom inclusions. Manual components behave like TDMS components: usable in tour templates, allocations, and visible to mapped partners.
Branch settings
Branch defaults and Rezdy integration settings.
Add or update users.
| First name | Last name | Branch admin | Active | Alerts |
|---|
Active branch identity. Code and name are managed by the Tour Widgets Admin.
Tours flow
This branch's TDMS account — used for component pricing and availability lookups.
Default margin applied to new components and templates.
Which gateway this branch's customers pay through. Test and production are separate TDMS accounts with their own enabled methods, so each is set here independently of which one the branch is currently running in. Only methods that can take an online payment are listed — a booking cannot be confirmed until the one in force is set.
Map widgets to tours
Pair a Tour Template with a Widget Style and copy the embed code. Swap either behind the same embed later — no website change.
Booking page
Branding, hero, layout, tour cards, buttons and trust signals for the branch's booking page.
Widget styles
Reusable appearance presets for embedded widgets. Pair one with a tour template on Widget Mapping.
Platform settings
Company setup and platform-level permissions live here.
Add or update the companies on the platform.
| Code | Name | Contact email | Default margin | TDMS |
|---|
Master-user have access to all branchs and platform level settings including company setup and sharing.
| First name | Last name | Default branch |
|---|
Assign additional branch access to existing users. Their default branch is shown for reference only.
| Name | Default branch | Shared branch | Branch admin | Active |
|---|
Backups run automatically each night for all active branches and are stored in R2. You can also trigger a manual backup or restore a branch to a previous snapshot.
| Branch | Date / Time (UTC) | Size |
|---|