Amela
YuTrip New Platform Launch Story
For confidentiality, company names, project names, and system images have been replaced with pseudonyms and mock-ups.

The hot-spring & tourism booking experience, Built in-house from scratch.

YuTrip is a platform handling reservations for hot-spring inns, day-trip baths, and sightseeing spots. It supports both web self-booking and phone booking channels.

Reservations, facilities, spots, tickets, users — the launch story of a new platform that satisfies all 5 axes required for tourism booking at once, built in-house from scratch in 10 months.

Loosely coupled services
5 services
Reservations / Facilities / Spots / Tickets / Users
Booking channel integration
2 channels
Web self-service + call center
Booking occupancy rate
99.9%
A processing platform that never stops, even in peak season
In-house build duration
10 months
From zero to production
YuTrip Booking
Inn with an open-air bath
Yukemuri Sanso — Tsukimi no Yado
12-min walk from the station
¥18,800Book now
Proceed to book with these dates
01
CLIENT
About the client

YuTrip, one of Japan's leading players driving tourism & lodging bookings.

YuTrip is a tourism & lodging booking operator that handles reservations for hot-spring inns, day-trip baths, and sightseeing spots all in one place. Users can book on their own, or book by phone with the help of an operator.

Connecting facilities, sightseeing areas, and tickets on a single platform, completing everything from route checking to reservation, payment, and notification. It delivers a booking experience that meets diverse travel styles.

1,200+
Registered facilities & spots
2
Booking channels (web / phone)
Nationwide
Covers hot-spring resorts & tourist areas
Booking business flow
STEP 1
Route search
Check travel time from the nearest station
STEP 2
Booking
Instantly secure vacancies from shared inventory
STEP 3
Payment
Pay securely via the payment gateway
STEP 4
Notification
Auto-send confirmations by SMS / email
02
CHALLENGE
Design challenges to solve

The four structural requirements demanded of the platform.

Business requirements tied directly to missed bookings, operational load, and drop-off. A fresh build from scratch required a design that satisfies them all at once.

Separating booking channels causes inventory to drift

If web and phone are managed separately, double bookings and vacancy mismatches occur, leading to lost opportunities.

Scattering admin screens makes operations heavier

If facilities, spots, and tickets are on separate systems, operational load grows and the frontline can no longer keep up.

Missing route info causes drop-off before booking

If the way to get there is unclear, users drop off just before booking, and inquiries also increase.

A flawed processing design stalls during peak season

If a holiday traffic surge can't be handled, bookings and notifications stall, eroding trust.

03
ARCHITECTURE
The architecture we built together

Turning the booking experience into a "never-stopping platform" across four domains.

We built in-house from scratch an architecture that separates reservations, facilities, spots, tickets, and users by role, connected through a shared inventory and OAuth authentication. Both the web and phone channels reference the same inventory.

Amela
EXECUTION
10 months
Duration
72 person-months
Total effort
Domain ①
Booking core
Challenge
Need to handle the same inventory on web and phone
Solution
Centralized with shared inventory + OAuth
Both channels reference the same booking core
Domain ②
Facility, spot & ticket management
Challenge
Need to handle multiple managed objects on one screen
Solution
Admin console separated by role
Unified operation of inventory, tourism, and tickets
Domain ③
Route, payment & notification integration
Challenge
Need to make the pre- and post-booking experience seamless
Solution
Auto-linked route search → payment → notification
Auto-send SMS / email on confirmation
Domain ④
Stable processing in peak season
Challenge
Need to stay up even under traffic spikes
Solution
Stable processing with queue + scheduler
Run notifications and batch jobs asynchronously and reliably
Frontend
Node.js
Backend
LaravelPHPMySQL
Infra
DockerNginxOAuth
04
IMPACT
The value the platform creates

YuTrip's "growth of the booking experience" accelerates.

A booking platform that prevents missed reservations

Because web and phone see the same inventory, double bookings and vacancy mismatches are prevented.

Operations can be consolidated on one screen

Facilities, tourism, and tickets can all be operated from a single admin console.

Pre-booking worries can be resolved

Travel time for the route can be checked on the spot, nudging users a step closer to booking.

Can focus during peak season

Traffic spikes are handled with stable processing, so staff can focus on serving guests.

STAKEHOLDER
Users
Travelers
Typically
Booking and route checking are separate and cumbersome
At YuTrip
Seamless from route checking to booking and payment
Business impact
Higher booking completion rate
STAKEHOLDER
Operator
Call center
Typically
Phone bookings use a separate ledger, causing inventory to drift
At YuTrip
Confirm on the spot from the same inventory as the web
Business impact
Improved reception efficiency
STAKEHOLDER
Facilities
Inns & hot springs
Typically
Inventory, pricing, and tourism info managed separately
At YuTrip
Unified operation of inventory and tickets on one screen
Business impact
Lower operating costs
STAKEHOLDER
Operations
Business division
Typically
Risk of downtime from peak-season traffic spikes
At YuTrip
Stable operation with queue + scheduler
Business impact
Ensured business continuity
05
DEMO
Three scenarios

Experience YuTrip through a live, working demo.