Delivery reports
Delivery reports maps to the fixed Driver Analytics source surface. It composes authenticated report requests for delivery orders, sales, statuses, timing, satisfaction, availability, and location data; it is not evidence that any deployed session returns those panels.
The fixed route /intelligence/drivers allows level 0. The sidebar item requires Pro or Enterprise for level 0; its separate Business-owner expression can name configured Reports membership, but the route remains level 0. Route, menu, plan, and API authorization are independent gates.
Source-defined filter surface
The controller initializes today, browser timezone, and unselected driver, Business, app, driver-group, and franchise filters.
The Pro/Enterprise UI source renders Country, Brand, Driver group, Drivers, Timezone, and date controls.
The screenshot remains a controls-only reference. It contains no proof of current data, authorization, aggregation, or deployed availability.
Request and metric boundary
At the fixed source pin, the controller builds authenticated /reports/* reads using lapse and normalized timezone, with optional driver, Business, app, driver-group, and franchise parameters. Separate requests cover driver orders and sales, order statuses, top orders, satisfaction, acceptance and pickup/delivery timing, available/busy time, and order locations.
Timezone is part of request construction, so it can change the queried interval rather than only formatting labels. Filter changes can also fan out across multiple private report requests. No request was executed; GET and HEAD are not presumed safe.
Privacy and location boundary
Source-defined responses can expose driver and Business identifiers, orders, sales, operational timing, satisfaction, availability, and customer order coordinates. Maps and aggregates can therefore reveal sensitive operational or location data even when individual names are absent.
The inspected UI source does not render a CSV or other report-download control for this surface. That is a bounded source statement, not a deployed guarantee and not permission to test other report or API exports.
Maintenance boundary
Revalidate route/menu/plan gates, every report endpoint and parameter, timezone normalization, status/subfilter behavior, metric labels, and location handling on pin or control drift. Runtime interpretation requires an approved synthetic delivery fixture with no live orders, drivers, Businesses, locations, exports, or writes, plus an immutable serving receipt and independent admission.
Related guides: Business reports · Reports overview