Skip to main content

Do not submit customer reviews

:::warning Customer review submission is blocked Do not open Review customer, select Send Review, or retry a previous customer review. Current evidence does not establish a reliable saved result for every affected order or guarantee that the write is restricted to the intended business scope. :::

This boundary applies whether Review customer appears in an order list or in order details. The visible action, review window, loading state, success message, error, or disappearance of the action does not provide enough evidence to proceed safely.

Before you start​

  • Do not use Review customer as an operational procedure.
  • Do not test the action with a real order or customer.
  • Do not open the review window to inspect its inputs. The write path is not admitted for documentation use.
  • If you need to report the visible state, use the minimum information required by your administrator or support process. Do not copy customer comments or other unnecessary customer details.

Record the visible state safely​

  1. Stay on the order list or order details. Do not select Review customer.
  2. Refresh the order once and wait for the current read to finish.
  3. Record whether Review customer is visible, whether you are viewing one order or a represented group, and whether the screen shows a loading, success, duplicate, or error message from an earlier attempt.
  4. Record the business and order reference through your organization's approved support process. Include no more customer information than that process requires.
  5. Escalate to the administrator responsible for the project or to Ordering support. State that you did not open, submit, or retry the review.

If the review window is already open​

  • If no review was submitted, close the window without selecting Send Review.
  • If a request is loading, do not submit again. Wait for the visible request state to settle, then refresh the order once.
  • If the window closed, a success message appeared, an error appeared, or the action disappeared, treat the saved result as unknown. Do not retry.
  • For a represented group, do not infer that every order has the same result. Record the visible state for each affected order without submitting another review.
  • Escalate the unknown result to the project administrator or Ordering support.

Why submission remains blocked​

  • The available source does not establish the required business-ownership guarantee for this review write.
  • A represented group can issue separate writes while losing reliable per-order failure information.
  • The review window can close before a grouped request settles.
  • A loading label, closed window, message, local list change, or missing action is not a saved-review guarantee.
  • The relationship between the documented source and the deployed app and API is not established.

These are safety boundaries, not instructions for working around the product. Do not attempt a single-order submission as a substitute for the blocked grouped flow.

When operational steps can return​

The customer-review procedure can be restored only after both conditions are met:

  1. Accepted API evidence establishes an exact business-owner and order-ownership restriction for the review write, or a corrected pinned API and authorization tests enforce it.
  2. The client provides reliable per-order result handling without early closure or false group success, or an authorized synthetic W4 receipt proves the complete partial/error matrix and safe recovery.

After those conditions pass, the source/API trace, public procedure, runtime disposition, and independent safety review must all be repeated before anyone uses Send Review from this guidance.

Availability and limits​

  • Review customer can appear for some past-order states when returned order data includes a customer and no existing review. Visibility is not authorization or freshness proof.
  • The list can represent more than one order while the detail view represents one selected order. Neither surface is admitted for submission.
  • The list can hide the action when order actions are disabled by connectivity. Order details does not use the same visible connection gate.
  • Comments, ratings, duplicates, and error behavior remain private evidence only while the write is blocked.
  • Source evidence does not prove deployed behavior, realtime freshness, provider behavior, saved-result integrity, or business ownership enforcement.

:::note Visual status Visual guidance is deferred pending an authorized synthetic capture program and independent visual QA. :::