Data & reporting
Booking dashboard prototype for five locations
We built a first version of one screen for every booking across all five locations, so the owner could judge whether to take it further.
A prototype that pulls live bookings from all five of a rental operator's location accounts into one screen. The bookings view runs on live data; the overview, trend, and channel views are designed on sample data, ready for the next phase.
- Five-location bookings
- Revenue roll-up
- Top equipment
- Next-phase design
- Next.js 16
- React 19
- Recharts
- Booking system API
- TypeScript
Before
The operator's bookings ran through a third-party booking system, with a separate account for every location. To see how the business was doing, someone had to log into five dashboards and stitch the numbers together by hand. We built a prototype that pulls all five into one view, so the owner could see the idea working on real bookings before deciding how far to take it.
What made it hard
Five separate booking accounts, one per location, each with its own credentials and its own data.
The bookings view had to read from the live booking system, not a stale export.
It had to stay readable for an operator, not an analyst, with the figures that matter first.
The booking system limits how much it returns at once, so the prototype had to page through each account and cache the results.
What we built
Connected to all five location accounts in the booking system and pulled bookings, revenue, products, and customers from each.
Combined them into one bookings view: total bookings, gross and collected revenue, customers, and the top-booked equipment across the business.
Designed the overview, trend, and channel views on sample data, so the owner could judge the full product before more was built.
Paged through each account and cached the results for five minutes, and limited access to the team.
Results
All five location accounts come into a single bookings screen, instead of five separate logins stitched together by hand.
The bookings view reads straight from the booking system rather than from an exported spreadsheet.
The overview, trend, and channel views are laid out on sample data, so a next build starts from an agreed design.
Where it stands
Prototype. Access is limited to the team, and live data stays switched off until it is needed.
