Case Study
Dual-Tier Tour Operations & Storefront SystemActive Platform

Wishey Tour Platform

Architected a dual-tier platform featuring a public customer storefront and an authenticated back-office operations platform.

IndustryTravel & Pilgrimage Management
CategoryEnterprise
Platform StatusActive Platform
Live DestinationVisit Site
Wishey Tour Platform application interface and architecture preview

Context & Purpose

Pilgrimage and specialty tour operators face unique logistical demands: detailed multi-day sacred itineraries, passenger manifest tracking, group room allocations, and customer support across WhatsApp and email. Wishey Technologies engineered a dual-tier architecture separating the public customer storefront from the administrative operations engine.

Primary Challenge

Coordinating complex pilgrimage itineraries, customer reservations, and internal tour operations.

Scope & Delivered Capabilities

  • Customer-facing tour catalog with detailed day-by-day pilgrimage itineraries
  • Dynamic booking inquiry capture and package variation selectors
  • Authenticated back-office operations platform for booking tracking and passenger manifests
  • Secure document storage for passenger travel permits and identification

Engineering Decisions & Architecture

01

Separated the architecture into two dedicated tiers: WordPress consumer storefront (`sacred-journeys.wisheytech.com`) for content agility, and Next.js 16 operations platform (`tour.wisheytech.com`) for mission-critical operations

02

Selected Prisma ORM with PostgreSQL on the operations platform to maintain relational data integrity across bookings, itineraries, and passenger manifests

03

Configured Clerk enterprise authentication protecting administrative operations routes behind authenticated sign-in barriers

04

Utilized AWS S3 with presigned request URLs for secure document upload and storage

Verified Implementation Details

  • Operations platform intentionally protects administrative routes behind Clerk authentication (unauthenticated visitors receive an authenticated protection redirect)
  • Public demonstration access is routed to the customer-facing storefront (`sacred-journeys.wisheytech.com`)
  • PostgreSQL schema designed with relational constraints ensuring booking records map cleanly to specific tour departures

Operational Boundaries & Scope

  • The operations portal (`tour.wisheytech.com`) is an authenticated internal workspace and is not available for anonymous public browsing. Operational workflows are actively maintained in private repository `wisheytech/wishey-tour-platform`.