Requirements overview
Tripfy Africa is a multi-vendor travel and tour booking marketplace connecting travelers with local tour guides across Africa. The platform manages the full journey from package discovery through payment settlement, guide verification, and post-tour review.Target users
Travelers
Browse destinations, book tour packages, pay securely, chat with guides, and leave post-tour reviews.
Guides
Create and publish tour packages, manage booking calendars, receive payouts, and respond to traveler reviews.
Admins
Approve packages, manage KYC verification, configure platform settings, and oversee financial settlements.
Platform scope
What the platform does
- Tour package creation, discovery, and booking
- Secure payment processing across 15+ gateways
- KYC identity verification for guides
- Real-time messaging between travelers and guides
- Post-tour reviews and ratings
- Commission management and guide payouts
- Multi-language and multi-currency support
- Admin-controlled content moderation and approvals
What the platform does not do
- Flight booking or airline integrations
- Hotel or accommodation reservations
- Travel insurance sales
- Visa processing services
Business goals
| Goal | Target |
|---|---|
| User acquisition | 100,000+ registered users in year one |
| Guide network | 1,000+ verified, active guides |
| Revenue model | Commission-based (10–15% per booking, tiered by guide plan) |
| Market position | Premier tour booking platform on the African continent |
Success metrics
- Booking volume and revenue growth month-over-month
- Guide satisfaction scores and retention rates
- Platform uptime and error rate
- User acquisition and repeat-booking rates
System constraints
Technical constraints
Technical constraints
- Stack: Laravel 11 (PHP 8.1+), MySQL 8.0+, Redis, Laravel Sanctum
- File storage: Local disk + AWS S3
- Browser support: Chrome, Firefox, Safari, Edge (current versions)
- Mobile support: iOS 12+, Android 8+
Business constraints
Business constraints
- Geographic focus: African continent initially
- Payment methods must cover region-appropriate options (mobile money, bank transfer, card)
- Language support: English plus at least five local languages
- All guides must comply with local tourism regulations
Operational constraints
Operational constraints
- Customer support available 24/7
- Critical issues responded to within 4 hours
- Financial records retained for 7 years
- Automated daily backups required
Dependencies
- Third-party payment gateway APIs (Stripe, Flutterwave, Razorpay, and others)
- Email and SMS service providers for transactional notifications
- Google Maps or equivalent for location services
- Translation services for multi-language content
Document structure
This requirements specification is organized into the following sections:- Functional requirements — Capabilities organized by user role
- Non-functional requirements — Performance, security, scalability, and reliability
- Business rules — Operational policies governing booking, payment, and guide conduct