Review the orders summary

For supported projects, Orders Summary can appear above a filtered standard Orders result. It calculates counts and a displayed Tip (Cash) amount from the order rows currently loaded into the Driver App.

This table is a local display summary. It is not an earnings statement, payout report, settlement, tax record, cash reconciliation, or current financial balance.

Availability

The summary appears only when all of these conditions apply:

• the project enables the summary feature;
• at least one search filter is active; and
• the selected tab is a standard order tab, not logistics requests.

The active filters can include supported date, order-number, external-ID, or city criteria. The summary changes as filters, loaded pages, grouped rows, order data, language, or currency formatting change.

State and result matrix

Area or state	What it displays	Safe interpretation
Expanded header	Orders Summary, Driver, and active filter details	Context for the currently loaded filtered result
Completed row	Count of loaded orders whose status is in the configured success set	Local status classification, not completed-payment settlement
Tip (Cash)	Sum from each successful order's cash value when present, otherwise numeric pay_data	Field-based local calculation, not verified Driver tip or earnings
Cancelled row	Count of loaded orders in the fixed failed set; current source uses only status [12]	Delivery-failed classification, not every Cancelled-tab order
Loaded: X of Y	Flattened loaded-member count and API-reported filtered total	Pages loaded versus reported total, not reconciliation completeness
Load more orders	Later filtered pages are available	Summary is incomplete until desired pages finish loading
Collapsed summary	Success count, failed count, and formatted tip total	Same local values in compact form
Loading	Summary/list can recalculate while a page loads	Wait before comparing values
Empty filtered result	Counts can be zero or summary absent with no rows	No matching loaded data, not zero earnings
Grouped orders	Group entries are flattened into individual members	Members count separately when their data shape is recognized
Malformed order/status	Unrecognized or mismatched values can be ignored	No data-quality guarantee
Malformed amount	Some values coerce to zero; negatives and non-finite values can pass the helper	Treat unusual output as invalid and report it

How the local calculation works

The reviewed source performs these display steps:

1. Flatten plain order rows and recognized grouped entries into member orders.
2. Compare each member's status using exact values against success and failed status lists.
3. Count successful and failed members.
4. For successful members only, use cash when it is present and not empty; otherwise convert pay_data to a number.
5. Add those values and format the total with the app's current number, currency, position, and optional exchange-rate configuration.

Numeric strings can be converted. Invalid numeric values can become zero, while negative or non-finite values are not reliably rejected by the summary helper. Do not use the table when the source data is malformed or spans an unsupported currency context.

Platform, permission, and lifecycle behavior

Collapsing or expanding the summary is local UI state and requests no additional device permission. Loading filtered orders, additional pages, language data, or currency configuration has separate network and provider boundaries.

The same formula runs on iOS and Android source, but formatting, available screen width, locale text, and malformed-number rendering can differ. No platform-equivalence or accessibility certification is implied.

Effects and boundaries

Orders Summary does not initiate a payment, payout, cash collection, adjustment, refund, transfer, or settlement. It only derives display values from the loaded filtered order data.

Order status, payment events, tips, refunds, cancellations, cash handling, provider balances, fees, taxes, and payroll are owned by separate systems and can settle independently. Use an approved financial or operational report for reconciliation.

Troubleshooting

• If the summary is missing, confirm that the project supports it, a filter is active, and you are not viewing logistics requests.
• If Loaded is lower than the reported total, use Load more orders before comparing counts—but still do not treat the table as financial reconciliation.
• If the Cancelled count differs from the Cancelled tab, remember that the summary's failed set is narrower than all cancelled statuses.
• If a tip total is negative, non-finite, or inconsistent with the cards, stop using the summary and report the affected filter/data shape.
• If currency formatting looks wrong, verify the app's currency configuration and compare with an approved financial report.

Related guides: Find deliveries · Filter and prioritize deliveries · Delivery history · Cash orders