Review available feedback options
Ordering.co Customer App can offer feedback for some eligible orders. An option can appear on a past-order card, in Order Details, or as an in-app prompt after the customer returns to the platform. Its availability depends on the order, business, products, fulfillment, current account, configuration, and whether feedback has already been recorded.
A missing feedback option does not identify the reason it is unavailable. The order can be ineligible, already reviewed, unavailable to the current account, outside the supported stage, or affected by configuration.
Start an available review
When an eligible order is presented, the customer can see a prompt that names the business and offers a rating. Select the visible rating, then choose Go to review when that action is shown.
The next stage can offer a rating scale, suggested feedback choices, an optional comment field, and Continue or Skip. Complete only the choices the current stage presents.
If the order includes eligible products, the customer can be offered a product-feedback stage after the business stage.
Completing or skipping one stage does not guarantee that another stage is available, submitted, or published.
Understand available feedback stages
| Stage | Intended subject | Availability boundary |
|---|---|---|
| Business feedback | The business that fulfilled the order. | It needs an eligible authorized order and a matching business relationship. |
| Product feedback | Eligible products from that order. | It can be absent or skipped when product feedback is unavailable or already recorded. |
| Driver feedback | A driver associated with an eligible delivery. | It does not apply to every fulfillment type or order. |
The feedback flow does not establish a professional or service-provider review procedure. Do not treat business or driver feedback as a contract for another type of provider.
Separate the visible form from the final result
| What you see | What it means | What it does not prove |
|---|---|---|
| Feedback action | The app presents a possible entry for the current order. | Eligibility at submission time, duplicate prevention, or public visibility. |
| Feedback form | Controls are available for one stage. | That the displayed choice will be the value finally accepted. |
| Loading or a local confirmation | The app started or locally completed a request. | Durable processing, moderation, or public visibility. |
| A submitted state | A feedback request was accepted for processing. | That it is public, enabled, moderated, or immediately visible. |
| A public customer surface returns feedback | A feedback record was returned for display. | That it is moderated, minimal, authorized, or consistent with every other public surface. |
| Already reviewed | The app or returned order identifies prior feedback. | That another request cannot race, duplicate, or partly settle. |
A selected score can be displayed differently from a value later handled by a controller when the feedback path is inconsistent. Do not use visual selection alone as proof of the final result.
Moderation, privacy, and operational use
Feedback submission and public presentation are separate states. Any public presentation should follow the current moderation and enablement rules and expose only the minimum customer-safe fields.
This guide does not promise:
- 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 presented; or
- whether an edit or deletion updates every public surface.
Operators can use feedback available through their authorized operational flow to understand customer experience, but they should not promise immediate publication, anonymity, permanence, or a particular moderation outcome.
Feedback can include free text, ratings, order context, business or product references, and customer or driver relationships. Keep it inside the authorized flow. Optional measurement must not receive a full comment, private order context, or unnecessary identity data, and measurement delivery is separate from feedback processing.
Grouped, duplicate, edit, and delete boundaries
A grouped order can include more than one business, product set, or driver stage. Each target can finish, fail, or remain pending independently. One success message does not establish that every target was accepted.
The app can show a prior-review state before it shows or sends feedback, but that client-side check does not prevent concurrent or repeated requests. Reliable duplicate protection requires an authoritative rule for the current customer, order, subject, and feedback type.
Customer App does not establish a supported customer procedure for editing or deleting submitted feedback. Do not promise those actions or attempt to recreate them through another app, link, or request.
Troubleshoot safely
A feedback option does not appear
Check only the current past-order or Order Details surface. Do not change device or promotional-notification settings, or test another order reference, to make a prompt appear.
The app says the order was already reviewed
Treat the current feedback state as authoritative until Ordering.co confirms otherwise. Do not submit again to replace or duplicate it.
One feedback stage appears but another does not
Treat only the current stage as available. The absence of another stage is not an error by itself.
Loading or a confirmation does not settle
Keep the outcome pending or unknown. Do not repeat the submission, reopen the prompt, or change account or project context to force a result.
A grouped review partly succeeds
Treat each business, product, and driver target separately. Do not infer that the whole group settled.
Submitted feedback is not public
Submission and public presentation are separate. Do not resubmit, add more private detail, or infer moderation status from a missing public result.
Accessibility and safe feedback state
An accessible feedback experience needs a named subject and stage, accessible rating values and selected state, a comment label and error relationship, clear required and optional rules, announced loading, error, and success states, deterministic focus, large-text layout, and a return that does not resubmit. Grouped feedback must identify which target finished and which remains pending.
Do not share comments, ratings, screenshots, order references, customer or driver details, or moderation information in unapproved channels when asking for help.
Related guides: Understand order details and status · View active and past orders · Account settings · Push-notification boundaries · Platform and accessibility considerations