EulCourt bookings that stopped living in a group chat.
Dula is a court booking platform for pickleball, badminton, basketball and tennis venues in Cebu, live at taradula.com under the tagline "Find your game." A player picks a time, finds open courts nearby, pays and confirms. The venue verifies the payment proof and the booking locks.
** Some names are changed or fictional in keeping with privacy and NDA commitments.
The problem
Court bookings ran on chat messages and payment screenshots. Someone on the venue side read every message and checked it against a paper schedule, all day, every day.
The result was predictable: double bookings when two players claimed the same slot, no shows that nobody chased, and no way to tell which hours actually made money.
What we built
- Real time availability for every court
- Payment proof upload with venue side verification
- A week calendar with drag and drop bookings and per court colors
- Recurring blocks for coaching, leagues and maintenance
- Open Play sessions with capacity limits and signup counts
- Player accounts, squads and invitations
- Invoicing, venue credits and push notifications
- A venue admin with revenue and utilisation stats
- A partner API
How it works
- 1A player picks a court and a slot. The hold is immediate, so the same slot cannot be double sold.
- 2The player uploads payment proof for the booking.
- 3The venue confirms the payment, the booking locks, and the calendar updates for everyone.
- 4Exclusive sports like basketball automatically take out the courts sharing the same floor. Maintenance blocks stay on one court only.
- 5Recurring and maintenance blocks keep non bookable time off the grid: coaching hours, league nights, repairs.
- 6The stats bar turns the week into numbers: bookings split online versus walk in, court revenue, peak slot, cancellations.
What changed
Availability is true at the moment it is shown, so double bookings stopped being possible. Admin work became confirming payments instead of reading threads.
- Industry
- Sports venues and recreation
- Stack
- React, Express, SQLite, continuous replication to a second server
- Live at
- taradula.com
Your venue could run like this.
If your bookings still live in a chat thread and a paper schedule, we can build the system that replaces both.