Simplified booking layer for Japan's confusing train system

What to build

A web app for foreign tourists that takes plain-English travel plans (dates, cities, JR Pass status) and outputs a day-by-day Japan rail itinerary with auto-matched seat reservations, transfer routing, and luggage/seat rules, delivered as printable QR/PDF tickets.

Japan's rail network is excellent but its official booking portals are notoriously hard for foreign tourists to navigate, creating an opening for a simplified English-language itinerary layer monetized per trip.

Demand

Millions of inbound tourists to Japan hit this friction every year when trying to book JR East, JR West, and regional trains in English, and the pain is visible enough to generate large organic discussion online.

• Hacker News (vinibrasil.com/japan-train)Engagement

  "Japan's trains are great. Why is booking one so hard?" reached 39 points and 90 comments on Hacker News, indicating high engagement with the booking-friction problem.

• Signal cluster (arbitrage opportunity description)Opportunity

  Opportunity text identifies unmet demand for plain-English search, auto seat reservation, JR Pass eligibility handling, transfer logic, and luggage/seat rules packaged as a day-by-day itinerary with QR/PDF tickets.

Stack

• Next.js
• OpenAI API (itinerary parsing from plain-English input)
• Navitime/Jorudan route-data scraping or unofficial APIs
• Puppeteer (automating JR booking portal flows where no API exists)
• Stripe (per-itinerary payment)
• PDF generation library (e.g. react-pdf) for ticket output

Solo + AI difficulty

The hard part is reliable automation against JR's reservation systems, which have no public API and may require scraping or browser automation that breaks when sites change; the easy part is the English itinerary UI and PDF/QR output, which AI coding tools handle well. Realistic MVP for a single rail operator and a handful of common tourist routes is 4-8 weeks; true end-to-end multi-operator coverage takes much longer.

Entry threshold

Needs scraping or partnering with existing rail booking APIs/sites (JR East, Smart EX, Eki-net) which have inconsistent English support and no public API, so the main effort is UX and data wrangling rather than infrastructure; a solo builder can get a usable MVP live in a few weeks using browser automation or unofficial APIs.

Window

6-12 months

Where to find first users

• r/JapanTravel
• r/solotravel
• Japan travel Facebook groups
• Product Hunt launch
• Partnerships with Japan-focused travel bloggers/YouTubers

Competitors

• Navitime
• Jorudan
• Klook
• JR East official booking site (Eki-net/JR-EAST Train Reservation)

Counter-signals & risks

• Existing players (JR East's own English booking site, Klook, Japan Rail Pass resellers, Navitime, Jorudan) already target this space, which could limit differentiation and willingness to pay.

• Deep integration with JR and regional rail reservation systems may require formal data-sharing or ticketing agreements, API access, or partnerships that are difficult for a third party to obtain.

• Monetizing via per-itinerary fees may face resistance if JR Pass pricing changes or official portals improve their English UX, eroding the arbitrage window.