Review available feedback options
Customer App can show feedback options for some completed or otherwise eligible orders. Availability, stages, and visible results depend on the exact order, business, products, fulfillment, current account, configuration, and whether feedback was already recorded.
This guide is a pre-action state reference. It does not instruct you to enter a rating or comment, submit feedback, change notification settings, or test publication. Submission, duplicate prevention, moderation, public visibility, grouped settlement, editing, and deletion are not fully established by the current pinned implementation.
Recognize the entry points
| Entry point | What it can show | Important boundary |
|---|---|---|
| A past-order card | A feedback action when the order and project allow it. | A visible action is not proof that every feedback stage is eligible. |
| Order details | A feedback action for the current authorized order. | Opening Order details can perform separate reads and listeners; feedback remains a distinct action. |
| An automatic in-app prompt | A pending eligible order can be offered for feedback. | Notification permission is not review eligibility. Do not change device or promotional-notification settings to make the prompt appear. |
If no feedback action appears, the order can be ineligible, already reviewed, unavailable to the current account, outside the supported stage, or affected by configuration. Absence does not identify which condition applies.
Understand the feedback stages
Customer App source contains separate stages rather than one universal review:
| Stage | Intended subject | Availability boundary |
|---|---|---|
| Business feedback | The business that fulfilled the order. | Requires an eligible authorized order and a matching business relationship. |
| Product feedback | Eligible products from that order. | Can be skipped or absent when product review is unavailable or already recorded. |
| Driver feedback | The driver associated with an eligible delivery. | Does not apply to every fulfillment type or every order. |
The stages can appear in sequence. Completing or skipping one stage does not prove that the next stage is available, submitted, or published.
Professional or service-provider reviews are not established by this Customer App flow. Do not interpret driver or business feedback as a professional-review contract.
Separate visible input, submission, and publication
| State | What it means | What it does not prove |
|---|---|---|
| Feedback action visible | The app currently presents a possible feedback entry. | Eligibility at submit time, duplicate protection, or public visibility. |
| Feedback form visible | The app presents controls for one stage. | That the displayed choice will match the submitted value. |
| Local loading or confirmation | The app started or locally completed a request. | Durable Ordering settlement, moderation, or publication. |
| Submitted to Ordering | Ordering accepted a feedback request for processing. | That it is public, enabled, moderated, or immediately visible. |
| A public customer surface returns feedback | The surface received a feedback record for display. | That the record was moderated, enabled, minimal, authorized, or consistent with every other public surface. |
| Already reviewed | The app or returned order indicates a prior review. | That a second request cannot race, duplicate, or partially settle. |
Customer App can display a selected score differently from the value later sent by a controller when the current feedback path is inconsistent. Do not use the visual selection alone as proof of the submitted result.
Moderation and public visibility
Feedback can have private submission state and separate public presentation. Publication should depend on the current approved moderation and enablement rules and should expose only the minimum customer-safe fields.
The current pinned source does not establish a complete customer contract for:
- when submitted feedback becomes public;
- whether it is reviewed before publication;
- which identity details are shown or hidden;
- when a public view refreshes;
- how rejected or disabled feedback is represented; or
- whether a later edit or deletion changes every public surface.
Do not promise immediate publication, anonymity, permanence, or a specific moderation result.
Grouped and partial outcomes
A grouped order can involve more than one business, product set, or driver stage. Those targets can settle independently.
If one target succeeds and another fails or remains pending, the overall result is partial or unknown. A single success message must not be treated as proof that every business, product, or driver feedback item was accepted. Do not repeat the complete sequence to force a single visible result.
Duplicate, edit, and delete boundaries
The app can check whether an order appears reviewed before showing or submitting feedback, but a client-side check does not prevent concurrent or repeated requests. Exactly-once protection requires an authoritative server rule for the current customer, order, subject, and feedback type.
The current Customer App does not establish a supported customer procedure for editing or deleting a submitted review. Do not promise those actions or attempt to recreate them through another app, link, or request.
Privacy and optional analytics
Feedback can contain free text, ratings, order context, business or product references, and customer or driver relationships. Keep that information inside the authorized feedback flow.
Optional measurement must not receive a full comment, private order context, or unnecessary identity data. Analytics delivery is separate from feedback settlement and public moderation. A measurement event does not prove that a review was saved or published.
Do not share comments, ratings, screenshots, order references, customer or driver details, or moderation information when asking for help.
Troubleshooting
A feedback option does not appear
The order can be ineligible, already reviewed, gated by project configuration, or unavailable to the current account. Check only the current past-order or Order details surface; do not change notification permission or test another order reference.
The app reports that the order was already reviewed
Treat the existing feedback state as authoritative until Ordering confirms otherwise. Do not submit again to replace or duplicate it.
One feedback stage appears but another does not
Treat only the stage currently presented as in scope. This guide does not instruct submission; absence of another stage is not an error by itself.
Loading or confirmation does not settle
Keep the outcome pending or unknown. Do not repeat the submission, reopen the prompt, or change account/project to force a result.
A grouped review partly succeeds
Treat each business, product, and driver target separately. Preserve the visible successful and pending states; do not assume the whole group settled.
Submitted feedback is not publicly visible
Submission and publication are different states. Do not resubmit, add more private detail, or infer moderation status from a missing public result.
Editing or deletion is expected
Those actions are not an accepted Customer App procedure at this pin. Keep the request with the authorized support/product owner without sharing the review content publicly.
Accessibility and safe review state
An accepted feedback experience needs a named subject and stage, accessible rating values and selected state, comment label and error relationship, clear required/optional rules, announced loading/error/success, deterministic focus, large-text layout, and a safe return that does not resubmit. Grouped feedback must announce which target settled and which remains pending.
When this guidance needs revalidation
Repeat the feedback review after changes to order eligibility, business/product/ driver stages, automatic prompting, notification-state checks, visible rating controls, submitted payload mapping, duplicate/idempotency rules, grouped settlement, moderation/public projections, edit/delete policy, analytics, privacy/redaction, or accessibility.
Related guides: Understand order details and status · View active and past orders · Account settings · Push-notification boundaries · Platform and accessibility considerations