How avishekkarn/venue-platform works
This is a QR-enabled hospitality platform for venue guests and staff. A guest scans a place QR code to resolve the venue and table, room, or counter, then can browse the menu, place and track orders, and request services; staff and kitchen users manage fulfillment, while administrators configure venue operations. The graph emphasizes these domain stages and the shared domain-to-storage layer. Several screens and API families are present in the tree but were not sampled, so their links are omitted rather than inferred.
Main entry points: orders/route.ts Guest orders API · dashboard/route.ts Dashboard metrics · client.ts PostgreSQL client · requests/route.ts Staff requests API
Components 24
Guest experience
- QR resolution
app/(guest)/qr/[token]/route.ts - Menu browsing
app/(guest)/menu/page.tsx - Cart and checkout
app/(guest)/cart/page.tsx - Guest orders API
app/api/guest/orders/route.ts - Order tracking
app/(guest)/order/[id]/track/page.tsx - Guest services
app/(guest)/services/page.tsx
Staff operations
- Staff requests API
app/api/staff/requests/route.ts - Staff console
app/staff/page.tsx - Kitchen console
app/kitchen/page.tsx
Venue administration
- Admin console
app/admin/(shell)/page.tsx - Order management
app/api/admin/orders/route.ts - Dashboard metrics
app/api/admin/dashboard/route.ts
Domain services
- Guest session
src/domain/guest/guest-session.service.ts - Order creation
src/domain/orders/create-order.ts - Order model
src/domain/orders/order.repository.ts - Service requests
src/domain/requests/request.repository.ts - Role access
src/domain/auth/can-access.ts
Infrastructure
- Order storage
src/infrastructure/db/repositories/order.repo.ts - Request storage
src/infrastructure/db/repositories/request.repo.ts - Room data
src/infrastructure/db/repositories/room.repo.ts - Table data
src/infrastructure/db/repositories/table.repo.ts - Venue data
src/infrastructure/db/repositories/organization.repo.ts - PostgreSQL client
src/infrastructure/db/client.ts
Other components
- Guest
Connections 28
- Guest → QR resolution: scans code
app/(guest)/qr/[token]/route.ts - QR resolution → Guest session: resolves session
app/(guest)/qr/[token]/route.ts - Guest → Menu browsing: browses menu
- Guest → Cart and checkout: builds order
- Cart and checkout → Guest orders API: submits order
- Guest orders API → Order creation: creates order
app/api/guest/orders/route.ts - Guest orders API → Order model: uses order port
app/api/guest/orders/route.ts - Guest orders API → Order storage: creates repository
app/api/guest/orders/route.ts - Guest orders API → Guest session: validates session
app/api/guest/orders/route.ts - Guest → Order tracking: tracks order
- Guest → Guest services: requests service
- Staff console → Staff requests API: manages requests
- Staff requests API → Service requests: uses request port
app/api/staff/requests/route.ts - Staff requests API → Request storage: creates repository
app/api/staff/requests/route.ts - Staff console → Kitchen console: fulfills orders
- Admin console → Order management: manages orders
app/admin/(shell)/page.tsx - Order management → Role access: checks access
app/api/admin/orders/route.ts - Order management → Order model: uses order port
app/api/admin/orders/route.ts - Admin console → Dashboard metrics: views metrics
app/admin/(shell)/page.tsx - Dashboard metrics → Role access: checks access
app/api/admin/dashboard/route.ts - Dashboard metrics → Room data: reads rooms
app/api/admin/dashboard/route.ts - Dashboard metrics → Table data: reads tables
app/api/admin/dashboard/route.ts - Dashboard metrics → Venue data: reads venue
app/api/admin/dashboard/route.ts - Order storage → PostgreSQL client: queries database
- Request storage → PostgreSQL client: queries database
- Room data → PostgreSQL client: queries database
src/infrastructure/db/repositories/room.repo.ts - Table data → PostgreSQL client: queries database
src/infrastructure/db/repositories/table.repo.ts - Venue data → PostgreSQL client: queries database
src/infrastructure/db/repositories/organization.repo.ts