Revenue This Month
—
confirmed bookings by travel date
Overview
Branch operations at a glance
Authenticated users are scoped to one company unless they are marked as master users.
Pax This Month
—
confirmed passengers travelling
Open Capacity — Next 30 Days
—
seats available across active departures
This Week
—
Revenue
—
Pax
—
Bookings
This Month
—
Revenue
—
Pax
—
Bookings
Upcoming Departures
| Date | Departure | Sold / Cap | Sell-through | Revenue Potential |
|---|---|---|---|---|
| Loading... | ||||
Operational
B
Bookings
Total
—
Confirmed
—
Processing
—
Unlinked
—
De
Departures
Active
—
Draft
—
Departing 14d
—
Total
—
To
Tour Templates
Published
—
Draft
—
Total
—
Al
Allocations
Committed %
—
Without Allocations
—
C
Components
Active
—
Expired
—
Next Season
—
Bookings
Groups
Review passengers and itinerary for a departure before submitting the group booking to TDMS.
Total Pax
—
Total Revenue
—
Total Nett
—
Profit
—
GP%
—
| # | Qty | First Name | Last Name | Phone | DOB | Title | Country |
|---|
No linked bookings found for this departure.
| Day | Date | Product | PPDID | Fare | Nett | Supplier |
|---|
No components found for this departure's template.
Active Addons
Live-bookable extras — not included in the group quote
| Day | Date | Product | Supplier | RRP |
|---|
Customer addon links
Email a branded link so each customer can pick & pay for their own addons.
| Recipient | Status | Sent | Paid | Total |
|---|
No links sent yet.
Send addon links
TDMS JSON Preview
▼ show
Bookings
Bookings
Rezdy bookings received via webhook. Link each booking to a departure to track allocation and supplier costs.
Actions ▾
Search Rezdy bookings
Fetches bookings from Rezdy and imports any that are missing or have changed. Use date range to target a specific window.
Fetch booking by order number
Retrieve a specific booking from Rezdy by its order number and import or update it.
Manual booking
Record a direct or phone booking not received via Rezdy.
| Order Ref | Guest | Code | Product | Travel Date | Pax | Status | Amount | Balance Due | Departure | Addon |
|---|
Departures
Departures
Browse and manage departure instances.
Departures are scoped to the active branch.
New departure
Start by choosing one published tour template for this departure.
Travel Dates: -
Departure dates ▶
Select departure dates
Pick one or more departure dates.
Existing departures ▶
Branch departures will appear here once the backend flow is defined.
| Tour Code | Date | Tour Name | Total Qty | Qty Booked | Qty Avail | Allocated | Components | Status | |
|---|---|---|---|---|---|---|---|---|---|
| No departures have been created yet. | |||||||||
Allocations
Allocation workspace
Set date-based allocations for components.
Select a saved component fare to manage allocations.
Pick one or more departure dates, then apply an allocation.
Set allocation
Selected fare
Year overview
All saved allocations for the selected fare across the year.
Year
Payments
Payments
Customer and supplier payment schedule.
Customer Payments
Due date = travel date − 42 days
Supplier Payments
Due date = 15th of travel month
Timeline
Slide to see cumulative totals up to any date.
Customer Total
—
Customer Outstanding
—
Supplier Nett
—
—
Reports
Reports
Operational reports.
Tours
Tour Template Builder workspace
Build Tour Templates from Components.
Tour Templates for the active branch.
Tour library
Saved tour templates.
| Code | Name | Description | Status | Duration | Sell Price | Travel Dates | Components |
|---|
Created at -
Updated at -
Tour editor
Mode: New
Status
Draft
Review
⋮
Components bundle
Add Active components to build your tour template.
| Order | Day Offset | Example Date | Product Name | Supplier | Fare | RRP | Nett | Addon |
|---|
Visual schedule
Preview the template by example date and component class.
Validation / JSON
Validate the selected draft and inspect the final JSON payload.
Validation
JSON
Tour Templates
Find & Replace Component
Swap a PPDID across tour templates and update any future departure overrides.
Search
Templates
| Code | Name | Status | Old Nett | New Nett | Δ Nett |
|---|
Future Departures
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 |
|---|
Components
Components workspace
Manage reusable components for the current branch.
Components are scoped to the active branch.
Current components
All saved components.
| Product ID | Product Name | PPDID | Fare | Travel Start | Travel End | Active Until | RRP | Nett |
|---|
Add new component
Search TDMS by Product ID and load all fares.
Search TDMS for a product in the current branch.
| PPDID | Fare | Travel Start | Travel End | Active Until | RRP | Nett |
|---|
Add manual component
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.
Settings
Branch settings
Branch defaults and Rezdy integration settings.
Branch settings are scoped to the active branch.
Branch settings unavailable
Switch branch.
Branch users
Add or update users.
| First name | Last name | Branch admin | Active |
|---|
Branch defaults
Booking margin and Rezdy integration settings for this branch.
TDMS / Website Travel
Rezdy integration
Addon portal branding
Customer-facing addon portal is hosted at the domain you configure below (set up via Cloudflare for SaaS). The logo, primary color, and support contacts appear on every customer page.
Admin
Platform settings
Company setup and platform-level permissions live here.
Master user access required.
Master user required
Only master users can access platform settings.
Companies
Add or update the companies on the platform.
| Code | Name | Contact email | Default margin | TDMS |
|---|
Master users
Master-user have access to all branchs and platform level settings including company setup and sharing.
| First name | Last name | Default branch |
|---|
Sharing
Assign additional branch access to existing users. Their default branch is shown for reference only.
| Name | Default branch | Shared branch | Branch admin | Active |
|---|
Partners
Map partner login emails to TDMS supplier IDs. Partners log in at partner.groupbooker.com.au and see bookings against their products across all branches.
| Supplier | Display name | Active |
|---|
No partner mappings yet.
Branch backups
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 |
|---|
No backups found.