User Flow Diagram for e-commerce store review and rating

Acting as a world-class UX strategist consultant, you provide strategic guidance to coaches and consultants in the product design space.

Map a complete user flow for the **review and rating** process in a e-commerce store.

**Target users:** accountants
**Design style:** brutalist
**Goal:** generate leads

## Flow Overview
- Entry points: where do users begin this flow? (list all possible entry points)
- Happy path: describe the ideal step-by-step completion in one paragraph
- Success criteria: what does a completed flow look like for the user?

## Detailed Flow Steps
For each step in the flow, document:

**Step [N]: [Step Name]**
- Screen/state the user sees
- User action required (tap, type, swipe, select)
- System response (what happens after the action)
- Data captured or displayed
- Transition to next step (animation, navigation type)

Map a minimum of 8-12 steps for the full review and rating flow.

## Decision Points
- Identify every branching point in the flow
- Document the condition and both paths (yes/no, option A/B)
- Specify default selections and their rationale

## Error & Edge Cases
- Form validation errors: inline messages for each potential failure
- Network failure: offline state handling
- Permission denied: graceful degradation path
- Session timeout: recovery flow
- Back navigation: what happens when users go backward at each step

## Alternative Paths
- Shortcut paths for returning users
- Guest vs. authenticated user flow differences
- Power user keyboard shortcuts or gestures
- Accessibility alternative paths (voice control, switch access)

## Flow Metrics
- Expected completion time for accountants
- Drop-off risk points and mitigation strategies
- Funnel conversion benchmarks for review and rating in similar products
- Recommended analytics events to track at each step

## Handoff Notes
- Annotate the flow with developer implementation notes
- Specify API calls needed at each transition
- List required loading and processing states

Present as numbered steps. Each step should have: a clear action title, detailed instructions, expected outcome, and common pitfalls to avoid.