Return requests before submission

Keep return requests tied to the chosen item and quantity

Document the item, quantity, and backward edits that shape a return request before the customer submits it.

  • ✓Summaries retain old quantities
  • ✓Policy text and actions conflict
  • ✓Confirmation implies approval

Return-flow findings with an item boundary

Latest-answer summary checks

Show whether the review step reflects a changed quantity instead of an earlier selection.

Request and approval distinguished

Keep confirmation language aligned with the actual stage of the return process.

Policy decisions assigned explicitly

Have the returns owner approve eligibility-related wording outside generated observations.

Choose a return with multiple decisions

A return request can ask which item, how many units, why it is being returned, and which next step is available. Review your product with a synthetic order containing two variants and multiple units of one item. Capture the eligibility explanation, item selection, reason fields, and review step. Write down the intended return window and available methods from your test setup. Those rules cannot be established solely by the presence of a Return button.

Record a backward edit before submission

Select two units, choose a reason, advance to the summary, and then return to change the quantity to one before revisiting the summary. An example issue is Return summary still lists two units after the shopper reduces the quantity to one. Show the edited field and the later summary in a continuous sequence. Keep the stale quantity separate from unclear policy copy or an unavailable label link. Avoid describing a completed return when only a request confirmation is visible.

Specify what the review step must preserve

Capture the browser flow with Retick or upload supported screenshots and recordings. Review AI candidate issues, edit inferred eligibility claims, reject assumptions about money movement, and annotate the inconsistent quantity. Example acceptance criteria: the summary reflects the latest selected units and reason; going back preserves unrelated answers; and the final action describes submitting a request rather than guaranteeing approval. The returns owner should confirm the intended wording and whether any method choice must be reconsidered after a quantity edit.

Follow the alternate request paths

After implementation, manually repeat with one eligible item, an ineligible item, and cancellation before final submission. Inspect long reason text and a narrow-screen summary. Verify return eligibility, request creation, shipping label behavior, and subsequent refunds through separate authorized systems and tests. Retick does not approve returns, generate customer labels, or execute commerce workflows. Use fictional order details and remove addresses before capture; there is no automatic redaction guarantee.

Download accepted findings for a manual file handoff, or export selected issues from the individual media item to an accessible Trello board and list. Include the backward edit and the product-approved request wording so developers can reproduce the summary mismatch without mistaking it for a policy change.

Review a return request summary

Capture the edited answer and the final request it should update.