Development roadmap
PHPTRAVELS roadmap: what we are building next
Where the travel booking platform is heading: the milestones already delivered, the features in development, the work planned for future releases and the requests customers ask for most.
- Completed milestones
- In development
- Planned features
- Customer requests
Short answer
The PHPTRAVELS roadmap in five parts
The roadmap sorts platform work by status, from delivered to requested. Shipped versions and their dates live in the changelog; this page shows the direction of travel across six development focus areas.
- Shipped releases, dated, are listed in the changelog
- Completed: payments, mobile apps and API, search, languages
- In development: AI booking assistant and analytics dashboard
- Planned: blockchain, AR and VR, sustainability, supplier network
- Requested: reporting, multi-vendor marketplace, social, loyalty
- Focus area
- Integrations
- Feature
- Multi-vendor marketplace
- Roadmap status
- Planned
- Your use case
- Let local suppliers list their own tours
Focus areas
Six areas the roadmap is organised around
Every roadmap item belongs to one of these platform areas, so you can see where development effort is going.
- Multi-currency and payment gatewaysStripe and PayPal, regional gateways, automatic currency conversion
- AI-powered booking assistantNatural language requests, personalised suggestions, price monitoring
- Advanced supplier networkDirect API integrations, real-time inventory sync, supplier analytics
Core platform
The booking and management features every agency relies on, from search to checkout and the admin panel.
Mobile experience
Native iOS and Android apps, responsive design and push notifications for travellers on the move.
AI and analytics
Smarter search, personalised recommendations, a booking assistant and data insights for administrators.
Integrations
Third-party services and supplier APIs that bring more inventory and payment options into the platform.
Security
Platform security and compliance work, including payment security across every checkout.
User experience
Interface design and usability improvements for customers, agents and administrators.
How the roadmap works
From feature request to release
Each idea moves through the same stages, and the status you see on the roadmap tells you where it stands.
Request
Customers and the team submit ideas. Popular requests are collected and evaluated for future releases.
Quarterly review
The roadmap is reviewed every quarter: progress is assessed, feedback gathered and priorities adjusted.
Research phase
Promising ideas such as social media integration are researched for demand and technical feasibility.
Planned
Accepted features join the plan for a future release, grouped under one of the six focus areas.
In development
The feature is built and tested. Scope can still change if testing or feedback calls for it.
Released
Finished work ships in a versioned release and is recorded, with its date, in the changelog.
In development
Three features being built now
The items the old roadmap lists as in development and testing, including the most requested addition.
AI-powered booking assistant
Natural language processing, personalised travel suggestions, automated price monitoring and a chatbot.
Advanced analytics dashboard
Real-time booking analytics, revenue tracking, customer behaviour insights and automated reports.
Advanced reporting system
The most requested feature from customers, in development alongside the analytics dashboard.
Planned
Features planned for future releases
Work that is accepted onto the roadmap but not yet in development. Scope and order can change.
Blockchain and NFT support
Cryptocurrency payments, NFT loyalty programmes, smart contracts and decentralised identity checks.
AR and VR travel experiences
Virtual property tours, 360-degree room views, AR destination guides and VR travel previews.
Sustainability and carbon tracking
A carbon footprint calculator, offset marketplace, sustainable stay badges and impact reports.
Advanced supplier network
A global supplier marketplace with direct APIs, real-time inventory sync and contract management.
Multi-vendor marketplace
A frequently requested feature that lets several vendors sell through one booking platform.
Loyalty programme enhancement
Requested improvements to loyalty features, planned alongside the marketplace work.
Roadmap and ownership
Waiting for a roadmap vs owning the code
With a hosted SaaS platform you typically depend on the vendor's roadmap. With PHPTRAVELS you can also build what you need now.
| Question | Typical hosted SaaS | PHPTRAVELS |
|---|---|---|
| You need a feature today | Typical hosted SaaSUsually wait until the vendor ships it | PHPTRAVELSBuild it on the included source code, or order custom development |
| Feature requests | Typical hosted SaaSVaries by vendor, check their process | PHPTRAVELSSend a request; popular ones are evaluated for future releases |
| When updates reach you | Typical hosted SaaSTypically applied by the vendor for everyone | PHPTRAVELSSelf-hosted, so you choose when to update |
| Roadmap visibility | Typical hosted SaaSVaries; some vendors publish none | PHPTRAVELSPublic roadmap plus a dated changelog |
| Source code | Typical hosted SaaSTypically not available | PHPTRAVELSIncluded under a commercial licence |
Who reads the roadmap
Three reasons to check the roadmap
Teams evaluating PHPTRAVELS
See where the platform is heading before you commit to it for your agency or OTA.
Existing customers
Plan upgrades around features in development and decide what to wait for or build now.
Developers
Avoid duplicating work: check whether a customisation you plan is already on the roadmap.
Roadmap policy
How we treat roadmap commitments
Reviewed every quarter
Progress, customer feedback and priorities are reassessed each quarter and the roadmap is updated.
Estimates, not promises
Timelines are best projections from current resources and can shift with technical complexity.
Clear priorities
Demand, business impact, feasibility, market trends and long-term platform vision decide the order.
Changes communicated
Features can be modified or postponed; significant changes are always shared with customers.
FAQ
PHPTRAVELS roadmap questions
What customers and buyers ask about planned features and timelines.
Talk to salesCompleted milestones such as multi-currency payments, mobile apps and multi-language support; an AI booking assistant and analytics dashboard in development; and planned work including blockchain, AR and VR, carbon tracking and a wider supplier network.
It is reviewed and updated every quarter. Progress is assessed, customer feedback is gathered and priorities are adjusted to market needs and technical feasibility.
Yes. Email your request with the feature and your use case. Popular requests are evaluated for inclusion in future releases.
No. They are best projections based on current resources and priorities and may shift because of technical complexity or changing requirements.
Planned features may be changed or postponed based on feedback, technical challenges or market conditions. Significant changes are communicated to customers.
The roadmap shows what is planned or in progress. The changelog records what has shipped, with each version's release date and notes.
Keep exploring