Short answer: Use a multi-stop ride when you need one journey with ordered intermediate stops, a round trip when the route is intended to return, and hourly hire when time and agreed availability are more important than one destination. KiloDrive represents these as structured trip products rather than hiding instructions inside a destination note.
“Stop at the pharmacy, wait, then take me home” is not “drive me to the pharmacy.” One destination string can hide route, price and waiting obligations. Structured products show the work before acceptance.
What this means Add every required stop, return leg, waiting expectation and duration before requesting the ride. A chat message sent after acceptance should not silently change the price or the driver's obligation.
Multi-stop rides use ordered places
A KiloDrive multi-stop request carries an origin, final destination and an ordered collection of intermediate stops. Each stop has its own type and lifecycle. During the trip, the driver can mark a stop arrived and complete. A stop can be skipped only through the allowed action and reason, so the timeline does not pretend it happened.
Google Routes distinguishes stopover and pass-through waypoints and documents route optimization. KiloDrive must not silently reorder commitments; any proposed order needs review and confirmation before quote and request.
For an errand, enter pickup, pharmacy and home separately. Confirm the pin, accessible entrance and whether the driver waits or drops off.
Round trips make the return leg explicit
A round trip records the return so distance, duration and fare guidance include both legs, and the driver can assess schedule, fuel and duty time.
A round trip does not mean unlimited waiting or unlimited detours. Stops, waiting rules and changes remain bounded by the product and country settings. If plans change materially, use the supported change or cancellation workflow; do not rely on informal messages that leave the authoritative trip and receipt out of sync.
Hourly hire is based on time and a disclosed rate
An hourly ride is useful for a sequence of short visits, an event, business errands or a period when the final route may evolve within agreed limits. The driver can set an hourly hire rate, subject to the active country's rules and currency context. The estimate uses the selected duration and applicable rate; it should display the ISO currency and show what is included.
This article gives no default price. The review screen must use current driver and country configuration and show rate, duration, limits and accepted total. Extensions require a new agreement.
Hourly hire is also not a promise that the driver can perform any task. The vehicle category, service area, permitted destinations, road rules and safety obligations still apply.
One quote contract from preview to creation
Preview and creation use the same structured product, route, stops, distance, duration and service options. The server is authoritative; system quote, rider offer and driver counter-offer remain distinct.
ISO 4217 currency codes help avoid mistakes when several markets use a dollar symbol. Distance should be displayed in the user's supported kilometre or mile preference while the underlying route keeps one authoritative measure. Never derive missing distance backward from the fare.
If a route provider is unavailable, the app should say what input or service is missing rather than invent a precise route. Traffic, closures and stop duration can change the final experience, so all previews remain estimates.
During the ride
The trip timeline should agree on both devices: assigned, arrived, started, stop arrived, stop completed or skipped, and completed or cancelled. Chat can clarify a pickup entrance or short note, but state-changing actions belong in the trip controls. Active-trip location and route-change checks continue according to permission and country policy.
Drivers should never edit a detailed stop list while moving. The US National Highway Traffic Safety Administration warns about distracted driving; KiloDrive's moving-state interface should prioritize large, simple actions and spoken navigation, leaving detailed changes for a safe stop. Riders should also avoid pressuring a driver to interact with the phone while the vehicle is moving.
Receipts should identify the accepted product, fare currency and authoritative route or telemetry distance when available. Legacy journeys without reliable distance should say unavailable instead of calculating kilometres from money.
What is still uncertain
Product availability, maximum stops, waiting rules, hourly bounds, driver-configured rates, vehicle categories and fare bands can vary by country and tenant. Route-provider availability and current traffic also affect estimates. These implemented product types must be checked in the live capability policy before publication; no article should promise a fixed rate, unlimited stops, guaranteed waiting or route optimization that the rider did not approve.
Frequently asked questions
Is a stop written in chat included in the quoted multi-stop ride?
Not automatically. Required stops should be added through the structured trip flow so the route, offer and driver decision use the same information.
Does a round trip include unlimited waiting at the destination?
No. Waiting remains subject to the selected product, disclosed rules and agreed quote; a return leg is not an unlimited-time booking.
Who sets the price for an hourly ride?
The estimate uses the current eligible driver rate and country rules, while the final accepted amount must be shown explicitly in the active ISO currency.
Can KiloDrive automatically reorder my stops?
The trip preserves structured stop order; any future optimization should be shown and confirmed rather than silently changing the rider's plan.
What happens if a stop cannot be completed?
Use the supported skip or trip-change action with a reason so both clients and the timeline retain the same authoritative state.
Sources
- Waypoint types and options — Google Maps Platform.
- Optimize the order of stops on your route — Google Maps Platform.
- ISO 4217 — Currency codes — International Organization for Standardization.
- Distracted Driving — US National Highway Traffic Safety Administration.