Routes, stops, and trips
Model the actual operating network behind every departure.
- Routes, legs, stops, and timings
- Recurring and dated departures
- Vehicle assignment, substitutions, and cancellation state
Boni Bus OS
Controlled pilotBus inventory, bookings, agents, and operations in one system.
Boni Bus OS connects routes, trips, vehicles, seat inventory, fares, holds, bookings, agents, manifests, channels, and AI-assisted exception work for bus operators and travel platforms.
For: Private intercity bus operators, fleets, branches, counters, agent networks, travel platforms, corporate transport teams, and distribution partners.
What the product connects
One operating record across the workflow
Trip and seat truth
Keep routes, stops, departures, vehicle or capacity assignments, holds, bookings, and sellability attached to the same trip record.
Operator work
Connect fare, counter, agent, manifest, passenger, cancellation, disruption, and settlement work to the reservation lifecycle.
Channel control
Make direct, agent, Bino, partner, and approved external distribution visible without creating separate inventory truth in every channel.
How it works
Run each departure from schedule to settlement.
Boni Bus OS keeps the operator-specific workflow clear while a shared reservation ledger handles availability, holds, confirmation, release, and audit consistently.
- 01
Set up the network
Define operator, branches, counters, routes, stops, boarding points, dropping points, vehicles, seat layouts, and responsible staff.
- 02
Create trips and fares
Generate departures, assign vehicles or capacity, publish seat inventory, apply fare rules, and define channel or agent controls.
- 03
Sell without conflicts
Create time-bounded holds, revalidate the requested trip inventory, and confirm a booking once the approved commercial state is complete.
- 04
Operate the departure
Prepare passenger and crew manifests, boarding state, no-shows, substitutions, changes, and disruption communication.
- 05
Manage channels and agents
Review quotas, credit, commissions, booking sources, sync failures, and channel-specific exceptions.
- 06
Reconcile the trip
Separate ticket, payment, cash or UPI collection, refund, agent statement, channel settlement, GST evidence, and trip-level exceptions.
Product scope
What the product covers.
Bus-specific routes, trips, holds, bookings, channels, fare, agent, seat-map, manifest, and AI-operations views.
Time-bound trip availability with available, held, booked, safety-buffer, and available-to-sell capacity.
Idempotent holds and confirmation so retrying a request does not create duplicate bookings.
Route, stop, branch, counter, agent, direct, partner, and distribution context for controlled implementations.
Channel health and operational signals for scarce capacity, stale sync, failed distribution, and next actions.
Connections to Bino travel journeys, Bow Chat passenger communication, and Boni payment, task, reporting, and accounting modules.
API access for approved route, trip, availability, fare, hold, booking, and event workflows.
Organisation and workspace context to keep operator data and actions scoped to the responsible business.
A shared reservation foundation without forcing hotel terminology or screens into bus operations.
Operating areas
A bus system has to connect schedule, sellability, sales channels, the departure, and the money.
Seats and fares
Control what can be sold, for which journey, at which price, and through which channel.
- Seat or berth maps and trip capacity
- Holds, bookings, blocks, and safety buffers
- Fare rules, overrides, quotas, and channel controls
Counters and agents
Preserve the commercial role of operator branches and sales partners while maintaining central visibility.
- Agent and counter identity
- Quota, credit, commission, and collection state
- Booking, cancellation, and override permissions
Manifest and departure
Turn confirmed tickets into an actionable operating record for the crew and boarding team.
- Passenger and crew manifest
- Boarding, no-show, pickup, and service state
- Bus swap, delay, cancellation, and communication workflows
Distribution
Use one inventory record across operator-owned and partner sales routes.
- Direct, agent, Bino, and API channels
- Mapping, sync, lag, retry, and exception visibility
- Controlled expansion to approved external channels
Settlement and reporting
Connect what was sold and operated to what was collected, refunded, owed, and reconciled.
- Ticket, payment, refund, and cancellation evidence
- Agent statement and channel settlement context
- Occupancy, yield, route or trip performance, and exceptions
AI inside the operation
AI should prepare work, explain risk, and improve decisions—not invent operational truth.
Route and fare-sheet intake
Turn approved route sheets, schedules, fare tables, seat charts, policy files, or operator messages into draft records with evidence and confidence.
An operator reviews the draft before publication.
Sellability review
Flag conflicting capacity, stale trip state, dead holds, weak channel health, or a schedule that needs operator attention.
AI cannot confirm a seat or alter final inventory outside the booking policy.
Fare and occupancy insight
Prepare recommendations from pickup, remaining capacity, timing, historic patterns, and commercial constraints.
Fare changes remain deterministic, policy-controlled, and auditable.
Passenger assistance
Draft answers about the actual ticket, pickup, timing, change, cancellation, or refund state and route unusual cases to staff.
The assistant must not invent trip, seat, or refund facts.
Trip and money exceptions
Summarize uncollected agent balances, unmatched payments, refund gaps, weak trips, and failed channels for operator review.
Money-moving actions require explicit approval.
Owner brief
Give management a concise view of weak routes, capacity risks, channel failures, agent exceptions, and the actions that matter today.
Every conclusion should link back to the operating record.
Implementation paths
Start where the operating gap is real.
Operator workflow pilot
Start with one route, branch, schedule, direct channel, agent network, manifest, or reporting problem and name what the incumbent system still owns.
Controlled inventory lane
Use Boni as the source of truth for an agreed vehicle pool, trip family, partner allocation, or direct booking workflow.
Partner API access
Expose approved route, trip, fare, availability, hold, and booking operations to a platform without exposing the full operator workspace.
Start with a defined operating scope.
Each rollout names the workflow, participants, source records, owner, success measures, and the parts that remain in existing systems.
Production depth is scoped
The live V0 foundation is suitable for controlled pilots. Seat-level leg sharing, advanced fare engines, full GDS connectors, crew apps, and mature financial ledgers require the contracted implementation shape.
One inventory authority
The implementation must state which system owns each route, trip, seat or capacity, fare, hold, and booking and how conflicts or stale sync are resolved.
AI does not operate silently
Fare, booking, trip cancellation, refund, settlement, passenger-impacting, and channel-impacting actions follow explicit policy and audit.
Distribution is not guaranteed demand
Bino and partner channels can extend sellability, but connection does not guarantee bookings, acceptance, reach, or revenue.
Connected products
Use it alone, or connect the next part of the operation.
Bus Inventory API
Add approved routes, trips, availability, fares, holds, bookings, and events to a travel product or partner workflow.
Explore the Bus APIBino Travel
Connect ready inventory to customer-facing bus and broader travel discovery and booking journeys.
Explore Bino travelBow Chat
Keep passenger questions, reminders, changes, disruption notices, calls, and escalations attached to the trip and booking context.
Explore Bow ChatQuestions
Common questions
Is Boni Bus OS a complete bus GDS?
The current V0 provides a working reservation foundation and bus-specific operator views. A controlled pilot defines the routes, trips, seat or capacity model, fare rules, sales channels, payment boundaries, and production depth it needs. It should not be presented as universal parity with every mature bus GDS.
Can agents and counters use the same inventory?
That is the intended operating model. Agent, counter, direct, Bino, partner, and approved external channels should draw from the same authoritative trip inventory, with their own quotas, credit, permissions, commissions, and audit rules where implemented.
How does AI help a bus operator?
AI can prepare routes and fare sheets from approved files, flag weak trips or stale channels, summarize occupancy and exception patterns, assist passenger replies, and surface reconciliation mismatches. It does not silently change fares, confirm seats, refund money, or cancel trips.
Can a travel platform integrate by API?
Yes, through an approved Bus Inventory API scope for routes, trips, availability, fares, holds, bookings, and lifecycle events. Commercial access, source-of-truth rules, support ownership, and channel constraints are agreed for each implementation.
Start with one bounded workflow