Purchase history navigation
Help order history reviews preserve the shopper's place
Keep date filters, pagination, and detail navigation together when documenting how a shopper finds an earlier purchase.
- ✓Filters and page indicators diverge
- ✓Repeated purchases are hard to locate
- ✓Empty results resemble missing orders
Order-list evidence with a return path
Return-path reproduction
Preserve the filter and list position that existed before an order was opened.
Coherent empty-state criteria
Define how people leave a narrow date range without implying their purchases disappeared.
Synthetic order context
Give engineering representative history conditions without exposing customer transaction details.
Use a history with meaningful variety
Order history must help a returning customer locate a particular purchase, not merely display a list of cards. Review your product with synthetic orders spanning several months, repeated product names, mixed visible statuses, and enough entries for pagination. Capture the default list, date filter, and one expanded summary. Record the account state and expected filter rules separately. Keep real addresses, transaction identifiers, and customer names out of the media.
Follow the return path from details
Record filtering to an earlier period, opening an order from a later list page, and returning through the provided navigation. A useful issue is Back to orders resets the date filter but leaves the old page indicator. Show the selected period before opening details and the list state afterward. Avoid calling an order missing until you have ruled out a changed filter or pagination state. Status wording and navigation retention should remain separate findings.
Define a coherent list state
Capture the browser journey with Retick or upload supported screenshots and recordings. Review AI candidate issues, edit the date range and page references, reject unsupported claims about missing purchases, and annotate the inconsistent indicator. Example acceptance criteria: return navigation restores the approved filter state; the page indicator matches the displayed results; and an empty filtered list offers a clear route back to other orders. Product should explicitly decide whether returning restores the previous position or resets the entire list.
Recheck changing result counts
After implementation, manually repeat with a single matching order, no matches, and a filter that reduces the page count. Inspect long item names and a canceled-order label on a narrow screen. Verify order ownership, payment state, and fulfillment records through separate authorized commerce checks. Retick does not retrieve purchases, reconcile transactions, or verify that an order exists in a backend system. Use safe fixtures rather than relying on automatic redaction of account details.
Download the accepted findings as a file for manual handoff, or export selected issues from the individual media item to an accessible Trello board and list. Include the original filter and return action so developers can reproduce the inconsistent history state without access to a real customer's purchases.
Review an order history journey
Show the filter before details and the list after returning.