One platform for every event, booking and supplier
Travel Places runs its events, bookings, suppliers and tasks on an operations platform we built on the web, live since July 2026 and kept in step with the FileMaker systems the business has run on for years.
- Client
- Travel Places
- Built
- The operations platform
- For
- Agents, operations and accounts
- Live since
- July 2026
One trip, many departments, one record.
The problem. A team's trip touches every part of Travel Places: the agent who books the hotel, the operations team who sees the squad through the airport, and the accounts team who invoices it and claims the commission afterwards. For years each department kept its own view of that trip, in FileMaker layouts and spreadsheets, and passed it on.
The approach. We built one platform on the web that every department works from. An event holds its clients, bookings and suppliers; a booking carries its rooms, rates, payments and commission from confirmation to close, and moves itself on at each step. FileMaker stays in step underneath, so nothing had to stop for the switch.
Travel Places' operations platform, rebuilt with invented data: a hotel booking for a rugby squad's tour to Lisbon on its Inventory tab, with five room lines and their costs, sale rates and commission, one line opened to the travellers in its rooms, the booking's totals, and a side panel whose process steps fill in from Booking Confirmed to Booking Closed as the status in the header changes to match.
Every room, rate and traveller
Each line on a booking carries its dates, cost, sale rate and commission, with the travellers allocated room by room.
A booking that moves itself on
Two days after check-out it moves to reconciliation, then on to the commission claim and closed, with each change logged.
Profit known before the trip
Sale value, commission, profit and margin are worked out from the lines, and payments to the hotel are tracked against them.
From the event to the booking, in one place.
Screens from Travel Places' operations platform, rebuilt with invented data: the events list regrouping into a board by status, a hotel booking for a squad's tour to Lisbon with its room lines and the travellers in each room, the same booking's process filling in from confirmed to closed, and the home page where the day's check-ins, supplier payments and commission differences are ticked off one at a time.
Every event, grouped the way you work
The events list holds every trip with its client, dates and any travellers whose documents have expired. Group it by status, sales group, country or client and it becomes a board.
Each booking, line by line
A booking on the event holds its rooms with their costs, sale rates and commission, and opens to show which traveller is in which room.
From confirmed to closed on its own
After check-out the platform moves the booking to reconciliation, sends the commission claim and closes it once the hotel has paid, logging each step against the booking.
The day's work, ticked off
Home gathers what needs doing today: check-ins in the next 96 hours, supplier payments falling due and commission that came in short. Tick one off and it drops from the list.
What the platform does
Built in Next.js on Supabase, in step with FileMaker every two minutes, and live for Travel Places' team since July 2026.
- Every event with its clients, dates, bookings, suppliers and purchase orders, and a running snapshot of spend and profit
- Bookings from hotel rooms to transfers, each line with its cost, mark-up, sale rate and commission
- A booking that moves itself on: reconciled after checkout, commission claimed, payment received, closed and archived
- A home page for each person: what needs attention, check-ins in the next 96 hours, supplier payments due and their own tasks
- A calendar of every event and booking across the year, by client and by sales group
- Clients, suppliers and hotel chains in one directory, with contacts, bank details and booking history
- Tasks on events, bookings and travellers, and a morning email of what is overdue or due today
- Search across travellers, bookings and events from anywhere in the platform
Where it stands
The platform went live in July 2026 and has improved every week since: more than 1,800 changes since January, each one released to Travel Places' team when it was ready.
Requests for proposal to hotels and proposals to clients are built into the same platform, ready to switch on, which takes it from the booking back to the first enquiry.
What we used
- Next.jsThe platform itself
- SupabaseEvery record, who can see it, and the nightly jobs that move bookings on
- FileMakerThe systems the business has run on for years, kept in step every two minutes
- n8nEmail from Travel Places' own mailboxes, and alerts in Teams
- PostHogFeature flags, to release each area when it is ready
- VercelHosting, with a preview of every change
