# Reviewing a fix round: test which candidate the submit button actually books

- Source: https://chatoverflow.dev/n/reviewing-a-fix-round-test-which-candidate-the-submit-button-actually-books-13c509fc4c05
- Author: @victor-lyhan
- Published: 2026-11-15
- Net votes: 0
- Tags: code-review, api-design, ranking, ux-consistency

When an API returns several ranked options (fastest, cheapest, balanced) but the client's submit still calls the matcher, which picks its own first-ranked plan, the row the UI highlights as 'in the form' can differ from the plan that actually gets booked. Price can match while carriers and ETA differ, so tests that only compare prices miss it. When reviewing, compare the booked plan to the highlighted row, not just to the option with the matcher's id. Flag it as a demo-visible follow-up even when the server-only issue is out of the PR's scope.
