Understand grouped deliveries
The Orders list can display related standard orders inside one expandable group. This is a viewing aid derived from the returned order data; it is not a single order, a user-selected grouping rule, or proof of one atomic workflow.
Availability
A grouped card can appear when returned standard orders share the same group reference and remain visible under the selected tab and status filters. The card shows a group label, member count, a date taken from the displayed group data, and a control for expanding or collapsing the member list.
In the accepted Driver App composition, grouped status controls are hidden by the default offline-actions context. Do not expect Accept all, Reject all, or shared pickup/delivery actions to be available.
State and result matrix
| State | What appears | Safe interpretation |
|---|---|---|
| Collapsed standard group | Group label, count, date, and expand icon | A display container for returned members |
| Expanded standard group | One card per deduplicated member | Review every member separately |
| Members in different status tabs | A group can split, shrink, move, or disappear | Status filtering applies to individual orders, not one shared group state |
| Duplicate member data | The list removes repeated member IDs from the rendered group | Deduplication is a UI transformation, not server reconciliation |
| Group action controls absent | No shared mutation buttons | Expected in the accepted composition; do not use another flow as a workaround |
| Logistics request with a group | A request can lead to grouped logistics details or View order | A separate assignment contract, not the same as standard display grouping |
| Loading or error | Skeleton or list error from Orders | Group membership is unresolved |
| Realtime change | A member can update or move between tabs | Reopen and verify each member; event ordering is not certified |
| Offline cached list | Previously stored members can appear | Local/stale group display, not current server state |
Viewing a standard group
- Open Orders and select the relevant current or past tab.
- Find the grouped card and check its displayed member count.
- Expand the group.
- Review each member's identifier and status individually.
- Open a member only when you need its own Order details.
This reference stops before every member or group action. The group header's count and date summarize displayed data only; they do not certify shared status, schedule, assignment, settlement, or completion.
Standard groups and logistics groups
| Dimension | Standard grouped display | Grouped logistics assignment |
|---|---|---|
| Source | Returned standard orders with shared grouping data | A Driver assignment request that represents an order group |
| Purpose | Organize cards in Orders | Offer a group assignment for review |
| Visible action in this reference | Expand and inspect members | Open the logistics-request guide or grouped detail |
| Mutation availability | Hidden in the accepted Driver composition | Assignment controls belong to the logistics flow, not this reference |
| Settlement | No shared operation is performed by viewing | Assignment, member changes, and later per-order estimates can settle separately |
Do not treat one kind of group as evidence for the other.
Platform, permission, and lifecycle behavior
Expanding a standard group is local UI state and requests no new permission by itself. Opening Orders can still perform list reads, socket joins, storage work, notification checks, and remote asset loads as described in the Orders overview.
Group membership can be recomputed when a tab, filter, page, cache, or realtime event changes. iOS and Android layout can differ, but neither platform turns the display group into an atomic server operation.
Effects and boundaries
The source contains dormant routes and handlers for grouped Accept/Reject and status changes, but the accepted provider tree does not expose them. They are not current Driver journeys.
If those controls were reintroduced, the reviewed contracts still would not prove atomicity:
- a logistics group assignment can settle before separate estimate updates for each member; and
- a grouped status change can send one request per member, with independent validation and failure.
This documentation therefore makes no grouped action, rollback, all-members success, or offline replay claim.
Troubleshooting
- If a group contains fewer members than expected, check the selected tab, filters, pagination, and connection state before concluding that an order is missing.
- If members show different statuses, review them individually. Do not infer the group's state from the first card or header.
- If the group disappears after a realtime update, refresh the selected tab and search for the members separately.
- If shared mutation buttons appear in a different build, do not use this page as authorization. Verify the release and use an approved action-specific guide.
- If a group is a logistics request, use the logistics guide rather than the standard grouped-card interpretation.
Related guides: Find deliveries · Logistic requests · Navigate the Driver App · Active delivery