I'm always excited to take on new projects and collaborate with innovative minds.
https://krafton.my.id
A travel and hospitality platform connecting accommodation enquiries, personalised trip planning, property management, tour scheduling, invoicing, and online payments for a Zanzibar travel business.
Client
Website
Paradise Zanzibar brings customer travel enquiries and day-to-day hospitality operations into one platform.
Visitors can explore properties and rooms, submit accommodation enquiries, and request personalised itineraries covering hotels, tours, excursions, safaris, flights, and transfers.
The administration workspace supports trip requests, service pricing, invoice preparation, and tour scheduling. Property managers can maintain their assigned properties, room inventory, and seasonal availability, with publication controlled through an approval workflow.
The engineering work includes external room-rate integrations, local-to-provider room mapping, request logging, configurable pricing adjustments, property-manager commission rules, and Pesapal payment integration.
The customer experience supports mobile and desktop layouts, with configurable public price visibility and enquiry-focused booking flows.
The business needed to manage accommodation enquiries, personalised travel requests, property submissions, tours, and payments through a connected workflow.
Different services required different information and pricing rules. Accommodation depended on dates, occupancy, inventory, and seasonal rates, while tours and safaris needed separate adult and child prices.
The platform also needed to distinguish supplier costs from customer selling prices, support property-manager approvals, and keep future tour commitments visible to the operations team.
I extended the platform around the business's operational workflows: collecting structured travel requirements, reviewing requests, preparing invoices, managing properties, and scheduling services.
I separated supplier guide prices from customer market prices so invoice generation could use selling prices without exposing internal costs. External accommodation data required explicit room mappings and date-specific rate handling.
I added configurable administration settings, permission-controlled management screens, request diagnostics, and responsive customer forms to support ongoing changes without repeatedly editing application code.
A Laravel application connects the public website, customer accounts, property-management workspace, and administration dashboard.
Relational records store properties, rooms, availability, trip requests, service prices, invoices, and payment information. Tour and safari services have identifiable catalogue entries with separate adult and child supplier costs and selling prices.
External accommodation integrations associate provider room identifiers with local rooms and retain rate information for the requested stay. Payment processing connects the application to Pesapal through server-side requests and callback handling.
The administration workflow connects request review, invoice preparation, and tour scheduling, while role-based permissions control access to operational tools.
PHP for application logic, validation, and routing; MySQL for relational data; Blade, JavaScript, jQuery, Vue.js, and Sass for interface development; Laravel Mix for frontend assets; REST APIs for external accommodation data; and Pesapal for payment integration.
The platform provides a connected workspace for travel enquiries, property operations, service pricing, invoicing, and tour scheduling.
Structured requests give staff clearer information for preparing travel proposals. Separate supplier and market prices support customer-facing invoice calculations, while room mapping and seasonal availability support accommodation pricing workflows.
Configurable public price visibility allows the business to switch between displaying room prices and an enquiry-led experience.
Travel pricing needs clear boundaries between nightly rates, full-stay totals, supplier costs, and customer selling prices.
External room names are insufficient for reliable matching; explicit identifier mappings are essential. Conditional forms also need matching server-side validation so customers are asked only for information relevant to their selected services.
Operational tools benefit from structured service records, clear approval states, and useful diagnostics. These foundations also make later automation easier to build and maintain.
Your email address will not be published. Required fields are marked *
