DenizTrip

The problem

Deniz Trip works agency-to-agency: partner travel agencies resell its organised trips, hotel allotments, and transfers. All of that used to run on phone calls, messages, and spreadsheets — checking availability, confirming a booking, and issuing the paperwork could eat a full day of back-and-forth.

The goal was one platform where a partner agency sees exactly what is available right now, books it in a few clicks, and walks away with the voucher and invoice — no manual steps on either side.

Two sides, one platform

The platform has two faces. Partner agencies get a clean portal: browse published trips, hotels, and transfer routes, check live availability and their pricing, book, and download their documents. The Deniz team gets a full back office: publish and update offers, control what each agency sees, manage bookings, and push ads and announcements into the agency dashboards.

Everything an agency sees is driven by availability. When Deniz marks a departure as full or a hotel allotment as sold out, it disappears from the agency side instantly — no double bookings, no awkward phone calls.

• Role-and-permission system on both sides, from super-admin down to read-only agency staff.
• Availability-driven catalogue: sold-out trips and hotels are hidden from agencies automatically.
• Invoices and vouchers generated automatically for every confirmed booking.
• Ads and announcements managed by Deniz and displayed inside agency accounts.

From availability check to voucher in a few clicks — with zero phone calls in between.

Under the hood

The front end is React with Tailwind CSS — two role-aware applications, one for the agency portal and one for the admin back office. Both talk to a Laravel API backed by PostgreSQL, where a permission layer guards every endpoint: what an account can list, book, edit, or export is decided server-side, never in the UI.

Google Maps and Places power the location side: hotel positions, transfer pickup points, and trip itineraries are geocoded and rendered on interactive maps.

The project was delivered at Sadeem Informatique, the software house I work at. I led the build with two teammates from the Sadeem team — owning the architecture, the data model (agencies, offers, allotments, bookings, and the documents they produce), and the booking flow end to end.

The outcome

The platform shipped in four months and runs in production today. Partner agencies book directly against live availability, paperwork that used to be manual is generated on the spot, and the Deniz team manages its whole catalogue — trips, hotels, transfers, ads — from one place.