TRV10 - v2.x - Feature Backlog

[Rishabh-ondc]

Outlining the features planned for subsequent versions of model implementations of the Ride Hailing domain on the network below.

Updated discussion threads addressing v2.0.1 patch updates.

Feature	Description	Thread	Solution	Status	Priority
Offering categorization	Categorization of various offerings provided by providers. On-demand: -Rental (Intracity/ Outstation) -Trip (Intracity/ Outstation) Scheduled: -Rental (Intracity/ Outstation) -Trip (Intracity/ Outstation)	Discussion Thread		Drafting specs in v2.1	P0
Purple Ride	Support for disability tags for enhanced experience for riders requiring special assistance	Discussion Thread		Drafting specs in v2.1	P0
Inclusions/ Exclusions	Provider providing features/ properties for their offerings			To be initiated
End stop update	Rider being able to update the end stop of the ride after the ride. Option by seller apps/ drivers whether stop updation is serviceable. Driver side get the route updated if serviceable May even be handled using soft and hard update request			Drafting specs in v2.1	P0
Stops addition	Riders is able to add multiple stops in their journey added as intermediate stops in the fulfilment trail between start and end stops. - stops added during driver search - stops added after ride started			Drafting specs in v2.1	P0
Feature tags	specific features provided by seller app as flags Live chat ; Tip addition ; Live ride sharing ; Enhanced safety ; Driver assistance ; Direct to driver payment			Drafting specs in v2.1
Live Tracking	Tracking the driver: - during driver reaching the rider - during trip			To be initiated
Vehicle Category/ Variant	Vehicle category and variant of the ride provided as enumised list. Proposed list below: Two wheeler Auto rickshaw Cab - Hatchback - Sedan - SUV	Discussion Thread	Refer v2.0.1 enums for category variant	Done
Offerings types	Types of rides provided by the seller [Premium ; Economy ; Prime ; …]			Drafting specs in v2.1
OTP based allocation	Rider is provided an OTP which is leveraged in a queueing type use case. Rider uses the OTP/ code at the time of getting in a vehicle in the queue and then the update of the vehicle details takes place	Discussion Thread	Refer v2.0.1	Done
Cancellation reason codes	Enum list for reasons for cancellations of an order	Discussion Thread	Refer v2.0.1 Cancellation Reason Codes	Done
Rebooking Workflow	Once a driver cancels, workflow for re-initiation of transaction journey - Initiated from BPP - Initiated from BAP			To be initiated
Buyer side fare proposal	Buyer app/ buyer proposing fares for a ride journey			Drafting specs in v2.1	P0
Driver Tips	Tipping option for the rider to provide to the drivers. - During selection of service - Post ride completion			Drafting specs in v2.1	P0
Area code	Handling area code for providers/ drivers to reach the stops		Refer v2.0.1	Done
Order id agnostic status call	Creating a status request for a transaction before an order.id is created		Refer v2.0.1	Done
TLC construct update	Alignment of the way TLCs are shared among NPs as per model implementations across other domains BAP Terms BPP Terms			Drafting specs in v2.1	P0
Multi quotes	A provider providing multiple offerings / quotes to a single ride/ trip enquiry			Drafting specs in v2.1
Fulfillment Enums update	Updating enums for the fulfilment state	Discussion Thread	Refer v2.0.1	Done
Enums sync	Updating enums for the various attributes: Order state ; Fulfilment stop types ; Authorization types ; Cancellation terms ; Fare policy ; Inclusions/ Exclusions			Drafting specs in v2.1	P0