Review a customer
The Driver App can show Review customer on configured past Order details that meet local visibility checks when the order has a customer and does not already contain a customer-review object. The form collects a rating and optional comments for that order/customer relationship.
Availability
The action can appear for configured completed, rejected, cancelled, failed, or other terminal order statuses. It remains hidden when:
- the order is not in a configured past status that passes local visibility checks;
- the order has no customer identifier; or
- the order already contains a customer-review object.
The absence of a visible star or rating does not prove that another review can be submitted. A review object with a zero, empty, or otherwise non-visible qualification can still hide Review customer.
Before you start
Confirm that you are reviewing the correct customer and order. A submitted review can create a persistent relation, run review plugins, update the local order display, emit an app event, and affect later account or reporting views.
Keep the comment factual and relevant to the delivery. Do not include addresses, contact details, payment data, access instructions, credentials, medical data, or other sensitive information.
Complete the task
- Open a configured past order that shows Review customer in Order details.
- Select Review customer.
- Choose a rating from 1 to 5: Terrible, Bad, Okay, Good, or Great.
- Select any relevant quick-comment suggestions.
- Optionally add a concise comment in Comments.
- Review the rating and final combined comment. Changing the rating clears the selected quick comments, while separately typed text can remain.
- Select Send Review once and wait while the button shows Loading.
The client can allow Send Review while the rating is still 0, but the reviewed API source requires a qualification of at least 1. Choose a rating before submitting.
Verify the result
A button press proves only that the Driver App attempted a review request. A success toast, modal close, local star, or app event reflects client processing of the response; it does not prove deployed persistence, plugin completion, moderation, reporting, or visibility elsewhere.
Reopen or refresh the order and check whether Review customer remains. If the outcome is unclear, do not submit again immediately. A duplicate review for the same order/customer/reviewer type can be rejected.
States and variations
| State | What appears | Safe interpretation |
|---|---|---|
| Client-visible candidate and no review object | Review customer | Candidate action only; API relation/duplicate checks still apply |
| Review object present | Action hidden | Client considers the order already reviewed, even if no rating star is visible |
| Qualification greater than 0 | Rating star can appear in customer details | Displayed value, not proof of publication or plugin settlement |
| Modal open, rating 0 | Rating scale and Send Review | Choose 1–5 before submitting |
| Rating 1–5 | Rating-specific quick comments | Client selection only |
| Quick comments selected | Suggested text is combined into the review comment | Review final text for relevance and privacy |
| Additional comment | Optional free text | No moderation, privacy, or visibility guarantee |
| Loading | Button text becomes Loading | Wait; do not press repeatedly |
| Error | Error alert | Close the alert, verify order/rating, and avoid immediate retry |
| Success-style client state | Toast, event, modal close, or later rating display | Not deployed persistence or downstream success |
| Grouped-order review | Shared source branch is hidden in the accepted composition | No grouped-review procedure or all-members success claim |
Troubleshooting
- If Review customer is missing, verify the order status, customer, and whether any review object is already attached.
- If no rating star appears, do not assume the order is reviewable; refresh the order and check the action itself.
- If the API rejects rating 0, reopen the form and choose a rating from 1 to 5.
- If the modal reports a duplicate or relation error, do not create another review from a different order or grouped control as a workaround.
- If the submission outcome is unclear, wait and refresh the individual order before any retry.
Related guides: Order details · Delivery history · Delivery problems · Messages