Velora Shuttle

Context and business problem

Enquiries for private transfers from Prague arrive from abroad in several languages, and a prospective customer needs to see a real price before deciding whether to make contact at all. Velora Shuttle was built to answer both: a multilingual site from day one, and a pricing engine that shows a fixed price before contact instead of a quote-only flow.

Constraints

• Enquiries come from customers who do not read Czech, so the site had to run in six locales from the outset rather than launch English-only and add languages later.
• A fixed, shown-before-contact price meant building a pricing engine around a distance-band formula, not a static price list or a quote-on-request flow.
• Stripe checkout was scoped but not built for the initial release, so bookings are still request-based rather than paid online at the point of enquiry.

Product and technical decisions

• Show a fixed price before contact, rather than requiring an enquiry first to find out the cost.
• Require no account to get a quote.
• Build the site in six locales (CS, DE, EN, UK, RU, PL) from day one, because enquiries come from abroad.
• Reprice the distance-band formula in August 2026 and add a trip calculator using Google Places and Routes in September 2026, ahead of a planned Stripe checkout.

What was built

• A Next.js site on Vercel, published in six locales.
• A request-based booking flow.
• An operator admin dashboard.
• A pricing engine built around a distance-band formula.
• A trip calculator using Google Places and Routes, added September 2026.
• A Google Ads search campaign, running since August 2026, and a Meta pixel, installed September 2026.

Current status

Live, with a Google Ads search campaign running since August 2026 and a Meta pixel installed in September 2026. Stripe checkout is planned but not yet live.

Who performed the work

Performed by

Yurii Korotun (founder)

Delivery period

2026-05 – present