How do I get checkout flow feedback from a client who doesn't use Figma?

Use a proxy-based review link. The client opens the URL in any browser, clicks the field or button they want to flag, and leaves a note — no Figma account, no extension. Figma prototype links require a login to leave comments. A review link removes the account gate entirely, which matters most for founders and small business clients who aren't daily design tool users.

How do I collect feedback on each step of a multi-step checkout separately?

Export each checkout screen as a separate image or page, then share each one as its own canvas in a review tool. The client annotates step 1 (cart), then step 2 (address), then step 3 (payment) without all the notes piling onto one screen. Alternatively, capture each step as a full-page screenshot and share a multi-page PDF — but a review link lets you track which step each comment belongs to, which a PDF cannot.

What should I ask a client when reviewing a checkout flow?

Task-framed prompts beat open questions: 'Walk through this as if you're placing an order. Flag anything that feels unclear or missing.' Then add two to three specifics: 'Is the guest checkout option visible enough?', 'Does the payment screen feel trustworthy?', and 'Is the order confirmation clear about what happens next?' Vague prompts ('Does this look right?') get vague answers that cost you another round.

How many rounds of feedback should I expect on a checkout flow?

One to three rounds is typical. Checkout flows tend to run longer than single-page designs because clients think about them in two modes: layout (does this look right?) and logic (does the step order make sense?). If you get layout notes in round one and logic notes in round two, that's a normal sequence. Pinning notes to the exact step keeps rounds shorter — you're fixing the tagged spot, not re-reading an email to find it.

Can I get feedback on a checkout flow before the payment integration is live?

Yes. Share the static screens or a Figma prototype for layout and copy review before you've wired up a payment gateway. The client can annotate 'Add Apple Pay here' or 'The CVV label is confusing' on the payment step without submitting a real transaction. Just tell them upfront: 'This is for design review — the form won't submit yet.' That framing prevents the call where they ask why their test card didn't work.

How do I get feedback on checkout error states and form validation?

Screenshot or screen-record each error state — mistyped postal code, expired card, required field left blank — and share them alongside the main flow. Clients rarely think to ask about error states unprompted, but they're the part that most damages trust at the actual purchase moment. Explicitly ask: 'Here's what a user sees if their card is declined. Does this feel clear and reassuring?'

drafty

How to get feedback on a checkout flow

Quick answer

To get feedback on a checkout flow, share a link your client opens in any browser and clicks directly on the step they want to flag — cart, address form, payment, confirmation — pinning a note right there. The main trap: clients describe steps by memory ('the payment bit') instead of by what's on screen. Pinned notes on the exact step cut out that translation round.

Step 1

Screenshot walkthrough — useful for pre-call alignment, not sign-off

Capture each step of the checkout flow as a full-page screenshot — cart, address form, payment, order review, confirmation. On Mac, Command+Shift+4 or GoFullPage in Chrome captures the full scroll; on Windows, Snipping Tool or the Edge screenshot shortcut handles the same job. Stitch the screens into a single PDF or Figma frame, annotate the steps by number, and share it before a walkthrough call. This works well for structuring your own thinking and setting a call agenda. It breaks down as a feedback method: a client who marks up a PDF of step 3 and emails it back has given you a note disconnected from the flow. When the design changes after round one, you are comparing their markup against a version that no longer exists. Screenshot walkthroughs also can't capture what clients actually notice in a real checkout: the back button, the error state on a mistyped postal code, the place they got confused about whether 'guest checkout' was available.

Step 2

Send a Figma prototype link with a task prompt

If the checkout flow was designed in Figma, set up a prototype with connected frames (cart → address → payment → confirmation), click Share → Prototype link, and send it with a task: 'Walk through a purchase as if you were buying the Pro plan. Let me know where anything feels unclear.' A task-framed prompt gets better feedback than 'what do you think?' because the client engages as a user, not a critic. The gap: leaving a comment in Figma requires a Figma account. If your client is a product manager at a mid-size company they probably have one. If your client is a founder or a small business owner, they hit the account-creation screen before they can type a note — and most of them call instead. The prototype link also won't show real error states, form validation, or inline field feedback unless you've wired all of it. What Figma gives you is layout and step order; it can't show the client what it feels like to type in a wrong card number.

Step 3

Screen recording with a narrated walkthrough

Record yourself walking through the live or staging checkout — Loom, QuickTime, or OBS all work — narrating each step as you go: 'This is the cart. Here's where the user sees their summary. Now I'm clicking Continue…' Share the Loom link or upload the recording to a shared drive and ask the client to leave time-stamped comments, or watch it together on a call. This is the most effective method for remote clients who struggle to describe UI in text. They can watch the flow at their own pace, and Loom's comment-at-a-timestamp feature lets them pin reactions to specific moments. The downside is direction: a screen recording of your walkthrough is still your interpretation of the flow, not theirs. You are deciding what to highlight and what to skip. If the client's mental model of the checkout is different from yours — say, they expect to enter a discount code before seeing the order total — a recording steered by you won't surface that gap.

Step 4

Share a review link they annotate step by step

The most reliable way to collect actionable checkout feedback: give your client a link that wraps the staging checkout or each Figma-exported screen in an annotation layer. They open it in any browser — no account, no extension — and click the exact field, button, or label they want to flag. 'Guest checkout is buried' lands as a pinned note on the guest checkout button, not in an email. 'I don't trust this payment screen' lands on the payment step, not a vague paragraph about trust. Proxy-based review tools (Drafty, Markup.io, BugSmash) handle this: paste your staging URL or export the screens and share the review link. The practical edge on a multi-step checkout is that you can share each screen as a separate canvas or combine them — the client navigates step by step and pins notes as they go. Every note is in one thread, resolved inline, and the revised flow lives on the same link. One subtlety worth knowing: if your staging checkout has server-side form validation or a real payment gateway, the proxy layer will capture the design but won't let the client submit a real order. That's fine for design review — just set the expectation in your message ('this is for layout and copy feedback, not a live test').

The faster way

If you're a freelance designer waiting on client approval before handing off a checkout flow to dev, paste each step — cart, address, payment, confirmation — into Drafty and share the review link. Your client clicks 'Guest checkout' or the 'Place order' button and pins their note right there. No Figma account, no extension. When you update the screens the revised version lives on the same link, so there's no re-sending files. Stakeholders who need to weigh in — a brand lead on the payment page, an ops contact on the address form — can comment on their step without seeing the whole project.

Open a live demo

Questions

How do I get checkout flow feedback from a client who doesn't use Figma?: Use a proxy-based review link. The client opens the URL in any browser, clicks the field or button they want to flag, and leaves a note — no Figma account, no extension. Figma prototype links require a login to leave comments. A review link removes the account gate entirely, which matters most for founders and small business clients who aren't daily design tool users.
How do I collect feedback on each step of a multi-step checkout separately?: Export each checkout screen as a separate image or page, then share each one as its own canvas in a review tool. The client annotates step 1 (cart), then step 2 (address), then step 3 (payment) without all the notes piling onto one screen. Alternatively, capture each step as a full-page screenshot and share a multi-page PDF — but a review link lets you track which step each comment belongs to, which a PDF cannot.
What should I ask a client when reviewing a checkout flow?: Task-framed prompts beat open questions: 'Walk through this as if you're placing an order. Flag anything that feels unclear or missing.' Then add two to three specifics: 'Is the guest checkout option visible enough?', 'Does the payment screen feel trustworthy?', and 'Is the order confirmation clear about what happens next?' Vague prompts ('Does this look right?') get vague answers that cost you another round.
How many rounds of feedback should I expect on a checkout flow?: One to three rounds is typical. Checkout flows tend to run longer than single-page designs because clients think about them in two modes: layout (does this look right?) and logic (does the step order make sense?). If you get layout notes in round one and logic notes in round two, that's a normal sequence. Pinning notes to the exact step keeps rounds shorter — you're fixing the tagged spot, not re-reading an email to find it.
Can I get feedback on a checkout flow before the payment integration is live?: Yes. Share the static screens or a Figma prototype for layout and copy review before you've wired up a payment gateway. The client can annotate 'Add Apple Pay here' or 'The CVV label is confusing' on the payment step without submitting a real transaction. Just tell them upfront: 'This is for design review — the form won't submit yet.' That framing prevents the call where they ask why their test card didn't work.
How do I get feedback on checkout error states and form validation?: Screenshot or screen-record each error state — mistyped postal code, expired card, required field left blank — and share them alongside the main flow. Clients rarely think to ask about error states unprompted, but they're the part that most damages trust at the actual purchase moment. Explicitly ask: 'Here's what a user sees if their card is declined. Does this feel clear and reassuring?'

Keep exploring

How to get feedback on a homepage How to get feedback on a web design How to get feedback on a Figma design Website feedback tool

Stop emailing files back and forth.

Share one link. They comment on the exact spot — no account, always the current version.

Open a live demo