Rides
A ride is the taxi side of the transport core: a passenger, a pickup, a drop-off, a requested time. The same machinery as a shipment — resolved addresses, the tariff, the dispatcher's assignment, the driver's screen, an immutable timeline — with a different object.
Requesting a ride
Transport → Rides → New ride. The passenger (name, phone, e-mail, how many), the pickup and the
drop-off (street, postal code, municipality — the postal code resolves the place and its point
through the geo lists), the requested time (empty = now), the service and a note. A customer of the
portal may be attached; Claudia requests rides with transport_request_ride.
The fare estimate comes from the tariff: the straight-line distance between the two points is
matched against the service's rules with a distance band (Tariffs → from km / to km). No matching
rule, or an unresolved address, leaves the fare on request; the dispatcher may type an estimate by
hand. The public door /api/web/v1/transport/ride-estimate?from=&to=&service= answers the same
estimate for a form on the firm's site without creating anything. The block Ride fare estimate
(Structure → Blocks, category Transport) draws that form anywhere on the site: two postal codes in,
the distance and the fare out, with an optional Order the ride link (block settings: intro, a
fixed service, the order link). The erp showcase shows it under /kde-rozvazame.
Assigning and driving
The ride page shows the facts, the assignment form (vehicle + driver — the fleet's current driver assignments whose employee has a user account) and the allowed moves:
| From | To | Who |
|---|---|---|
| requested | assigned | the dispatcher (through Assign) |
| requested, assigned | cancelled | the dispatcher, the customer; the driver once assigned |
| assigned | en route | the dispatcher, the driver |
| assigned | requested | the dispatcher (un-assign; vehicle and driver clear) |
| en route | picked up | the dispatcher, the driver |
| picked up | done | the dispatcher, the driver |
On done the fare becomes final: the amount typed, else the estimate. The driver hears about an assignment by mail (transport_ride_assigned); the passenger with an e-mail hears when the ride is done (transport_ride_done). Both texts are editable under Mail → Templates.
The driver's screen
The app channel (/erp/rozvoz/jazdy/) lists the driver's rides of the day with the passenger, both
addresses with a Navigate link, the phone, the fare, and the moves the driver may make: On my
way, Passenger picked up, Done (with the final fare), Cancel. Only the driver's own rides are
visible; the office keeps the whole board.
The customer's rides
The portal page /moje-jazdy/ is the shipped view My rides (transport_my_rides, portal
access): a signed-in customer sees only the rides attached to their partner — the state, the time,
both places and the fare. The account page (/account/) links it next to All my shipments.
The screen
The Rides screen is the shipped view Rides (transport_rides): a kanban by status with a card
per ride — number, passenger, pickup, drop-off, time, vehicle, driver — and an Open action. A firm
may reshape it like any default view (columns, filters, a table instead of the board) and revert to
the shipped declaration at any time.