Island rides that know the ferry.
When a route crosses a ferry line, Webaxi splits the trip into taxi legs, uses the real timetable and keeps the whole journey on one screen.
Screenshots in this gallery: Ferry trip · 3 legs, The whole trip on one screen, Locked until the rider confirms
One booking, three legs, one ferry
A real recording from the client app: Malinska–Lubenice as one layover ride. Leg 1 to the Valbiska dock, the real Krk–Cres sailing (38 min wait · 25 min crossing), Leg 3 from Merag.
38 min wait · 25 min crossing
The wait at the dock is computed from the real ferry departure.
Ferry ticket paid separately
The taxi price covers the road legs; the ferry ticket is the passenger's own, shown on screen.
Every leg on one screen
Every leg with status, planned time and price, plus the total trip time.
The ride starts only after check-in
The scheduled origin ride opens a check-in window; chat, payments and full ride details become available once the client confirms.
Real recording, client confirms a ferry-layover ride (Malinska–Lubenice)
It finds the crossing so you don't have to
Each route is checked against the crossing lines and port areas you set. You decide whether island crossings are offered at all, and a distance rule keeps short hops with one driver.
The crossings are already listed
Valbiska–Merag, Split–Hvar. Every ferry line arrives as a crossing with the port area around it, managed per network. Jadrolinija today, other operators to follow.
It notices the route breaks at the port
Route analysis finds where the road ends and the water begins, and where the first taxi leg hands over.
Asking again is instant
Once Webaxi recognises a crossing, the ferry timetable never slows a customer down.
The real ferry timetable, matched to the arrival
Timetables arrive daily from Jadrolinija. Webaxi picks the next sailing that fits, shows the wait and the crossing separately, and times leg 2 from the ferry's arrival.
Daily schedule import
Webaxi reads Jadrolinija's timetable every day, so a schedule change never stands in the way of a price.
Wait and crossing, priced apart
“38 min wait · 25 min crossing”. The wait comes from the real departure, so customers know what the stop costs them in time.
Second leg timed to the arrival
The far-side taxi is timed from the ferry's arrival; reschedule the origin ride and the whole chain re-plans.
Each leg priced, one clear total
Each road leg is priced by your own rules. Zones, point-to-point fares, coupons. The crossing total is the sum of the legs, compared with the single-driver option. If it is not cheaper, or no far-side driver covers it, the offer is not shown.
Leg-by-leg pricing
€22 to the dock + €52 from the far dock = the total the customer sees. Your rules, worked out by the platform.
Cooperation & partner legs
The far-side leg can be served by a partner fleet under your collaboration terms. Each leg keeps its own driver and terms.
Offered only when it saves time
No saving against one driver, no car on the far side, or no valid price: the split option is simply not shown.
The customer sees one journey
In the customer app the ride shows as Leg 1 · Leg 2 · Leg 3, each with its state, planned time and price, and the ferry ticket marked separately.
One trip, with the wait shown
Every leg with its type, state, pickup and drop-off, distance, time and price. Current and planned, exactly as it runs.
Ferry ticket paid separately
The app states that the ferry ticket is paid separately by the passenger and is not included in the taxi price.
Check in, then confirm the ride
Check in before the origin ride, then “Confirm ride” opens chat, payments and full ride details.
Island routes at every size
A ferry layover is the same mechanism whether you own one car or a network of island fleets.
The ferry hand-off is scheduled for you
Detection and timetable matching need no configuration. The driver follows the planned legs.
One look shows who takes the ferry leg
The whole journey, with the wait, the crossing and the far-side pickup on one screen, so the office knows when the second car must be at Merag.
Crossings and partners per network
Crossings and schedules are organised per network, and a partner fleet can serve the far side under your collaboration terms.
Screenshots in this gallery: “Book with layover, save” in the widget
How a cross-ferry trip becomes one journey
Request the island route
The platform answers with the ferry-wait option. Ferry timetable and total trip time already known.
Leg 1: the taxi to the dock
The origin leg is a normal booking, priced by your rules, timed to land at the port before the ferry.
The ferry, on schedule
Real departure, real wait, real crossing. And the passenger buys the ferry ticket separately.
Leg 3: the driver on the far side
The far-side taxi is scheduled from the ferry's arrival, with its own driver, status and price.
Your island route, one booking
Taxi legs, ferry schedule and the whole journey in one view. For you, your drivers and your customers.


