Find delivery requests
Use Orders to review delivery cards assigned or offered to your Driver account. The screen can separate current work, past work, and configured logistics requests.
Availability
Orders is the initial tab in the signed-in Driver App. The visible tabs depend on configuration:
- Pending and In Progress can be separate, or combined as Active.
- Completed and Cancelled contain past states.
- A logistics icon can appear when logistics requests are enabled and the pending/in-progress tabs are not combined.
Mounting the screen can load orders, join realtime rooms, check native notification status, read or clear local cached-order settings, and load remote card assets. Open it only when those account, network, storage, native, and provider effects are appropriate.
Open this capability
- Select Orders in the bottom navigation.
- Wait for the loading cards to clear.
- Choose the tab that matches the work you want to review: Pending, In Progress, Active, Completed, Cancelled, or the logistics icon when available.
- Check for a filters warning and clear or adjust filters when they would hide relevant deliveries.
- Review the returned cards. Select Load more orders when it appears and you need later pages.
- Use pull-to-refresh or the refresh icon when you deliberately want another read of the selected list.
Selecting a card opens Order details. Accept, Reject, review, status, grouped, and logistics action controls are separate mutation boundaries and are not part of this overview.
What drivers can understand
- Current tabs contain status categories configured as pending, in progress, or active.
- Past tabs contain configured completed or cancelled categories.
- Status tags narrow the selected standard tab.
- Search filters can narrow by supported order, date, or location-related fields. The screen warns that active filters may miss new orders.
- Some cards can be grouped by data returned with the orders. Grouping is a display transformation, not a user-selected assignment rule.
- The logistics list shows non-expired assignment requests and can include a request whose order data represents a group.
- Realtime events can add, update, move, or expire cards after the initial read.
States and variations
| State | What appears | Safe interpretation |
|---|---|---|
| Loading | Order-card skeletons | The list is unresolved |
| Populated current tab | Current order cards | Returned page and current filters only; not a complete live inventory |
| Populated past tab | Completed or cancelled cards | Returned page under configured status mapping |
| No results | Sorry, no results found | No matching visible result for this tab/filter/page state |
| Error | Network or request error content | The app did not establish the list; retry one deliberate read |
| Filters active | Filters applied. You may miss new orders. | Clear or review filters before concluding an order is absent |
| Load more visible | More pages are reported | The current cards are not the full paginated result |
| Offline | Last Update and possibly pending-sync count | Cached/local state; not current server state |
| Logistics empty | No non-expired request is visible | Does not prove no request existed or that another Driver did not receive one |
| Grouped card | Related returned items are displayed together | Member status and assignment can differ; verify each order |
| Realtime update | Card appears, changes tabs, or disappears | Recheck identifiers and selected tab; event order/freshness is not certified |
| Notification prompt | Enable notifications | A native status check found a blocked state; Settings is a separate OS handoff |
Effects and boundaries
The selected tab, status tags, filters, pagination, stored offline data, socket events, and logistics-expiration filtering all influence the visible result. Neither an empty list nor a populated list proves completeness or currentness.
Standard order-list reads and logistics-request reads use different source contracts. A logistics card is a request to review, not proof that an assignment has been accepted. Selecting Accept or Reject can change assignments, orders, other Drivers' requests, logs, notifications, and realtime state.
Troubleshooting
- If a delivery seems missing, confirm the selected tab, status tags, filters, connection state, and whether Load more orders is available.
- If filters are active, clear them before assuming there are no new requests.
- If Last Update appears, reconnect and refresh before relying on the list.
- If an error replaces the cards, wait for connectivity and run one deliberate refresh. Avoid repeated restarts or rapid reads.
- If a logistics request disappeared, refresh the logistics list; it may have expired or changed through a realtime event.
- If a grouped card looks incomplete, open the owning order details and verify each member rather than assuming the group is atomic.
Related guides: Driver App overview · Navigate the Driver App · Accept a delivery · Active delivery · Delivery history