Routes, stops and legs
Routes built from ordered stops with pricing per leg, so a passenger travelling part of the route is priced and seated correctly.
Waypoint
Waypoint runs the commercial side of a coach network: routes and stops, schedules and trips, vehicle-accurate seat layouts, seat locking during checkout, per-leg pricing, agent and office sales, customer booking, refunds against a stated policy, and parcel freight moving on the same vehicles.
Built, pre-launch Multi-tenant platform modelling routes, trips, seats, agents and parcels.
40+entities
modelling routes, trips, seats, agents and parcels
Multioperator
tenancy with per-operator subscription plans
Seatlevel
inventory with locking to prevent double sale
2revenue lines
passenger tickets and parcel freight on one trip
01 / The problem
The office sells a seat. An agent in another town sells a seat. A customer books online. The conductor sells at the door. All four are selling from the same 49 seats on the same vehicle, and the only thing stopping a double sale is how fast someone updates a WhatsApp group.
Add per-leg pricing — a passenger boarding halfway pays differently and frees a seat for part of the journey — and manual inventory stops working entirely.
Waypoint makes the seat the unit of inventory, locks it the moment a sale begins, and gives every channel the same live view of what is actually available.
02 / In operation
The shape below is true to the real product. The numbers are not — these are illustrative values, never customer data.
Illustrative interface with sample data.
03 / Capabilities
10 capability areas, each built because the operation breaks without it.
Routes built from ordered stops with pricing per leg, so a passenger travelling part of the route is priced and seated correctly.
Recurring schedules generate trips, each with its own vehicle, crew and live seat inventory.
Seat layouts modelled per bus type and seat class, so the map the agent sees is the vehicle that arrives.
A seat is held the moment a booking starts and released on timeout — the mechanism that makes multi-channel selling safe.
A network of offices and agents with their own accounts, commissions and daily reconciliation.
Direct booking and payment for passengers, against the same inventory the counters use.
Changes and cancellations evaluated against a configured refund policy, with the outcome recorded rather than negotiated.
Parcels booked onto the same trips with their own types, pricing and handover tracking — a second revenue line on an asset already moving.
Drivers, conductors, vehicles and offices as managed records tied to the trips they run.
Several operators run isolated on one deployment, each on its own subscription plan.
04 / Surface area
Breadth is only an asset when the parts share a data model. Every module here reads and writes the same records — there is no export step between them.
05 / Architecture
A Laravel application with explicit seat-lock semantics, tenant scoping enforced at the data layer, and role-and-permission separation between operator staff, offices, agents and customers.
06 / Integrations
Third parties are first-class parts of the architecture, isolated behind stable internal contracts so any one of them can be replaced without touching the core.
Card and mobile money collection at counter and online, reconciled per office.
Ticket delivery and departure reminders by SMS and push.
Counter ticket and parcel label printing at offices and agents.
Passenger transport
We can walk you through the live platform, talk about how it maps onto how you work today, and be honest about where it does not fit.