---
title: Selecting an option applies it immediately… · Rubric
description: Apply the result of a selection — a radio button, a dropdown, a quantity stepper — as soon as it is made, updating totals, delivery estimates and stock…
url: https://rubric.design/ux/forms.changes-apply-without-a-button
format: agent view of this page
updated: 2026-11-16
---

[UX guides](https://rubric.design/ux/) / [Forms](https://rubric.design/ux/topic/forms) / Selecting an option applies it immediately, without a separate Apply step

# Selecting an option applies it immediately, without a separate Apply step

Usually high · How serious this usually is when it goes wrong. Not a score.

## The guideline

Apply the result of a selection — a radio button, a dropdown, a quantity stepper — as soon as it is made, updating totals, delivery estimates and stock information without a separate "Apply" click. Reserve an explicit confirm button for fields where the user is typing free text and needs to signal they are finished, such as a promo code or a gift message, where the system genuinely cannot tell completion from an in-progress keystroke.

## Common failures

- The checkout flow requires users to click an "Apply" button after making straightforward selections like changing shipping method, payment option, or quantity, rather than updating totals and options automatically as the user interacts with the form.

## Where it applies

### Pages

- Forms

### Industries

- Ecommerce

### Disciplines

- Conversion

### Devices

- Desktop web
- Mobile app
- Mobile web

## Why it matters, how to fix it, and the research behind it

Rubric's full guide adds the reasoning, the fix and the sources for this check, and checks your pages against it and the rest of the checklist, the way a visitor would meet them. Findings come back worst first.

[Use demo account](https://rubric.design/demo) · [Use it from your coding agent (MCP)](https://rubric.design/#agents)

## Related guides

- [Entered checkout data survives errors and back-navigation](https://rubric.design/ux/checkout.entered-data-persists-through-errors) · Usually high · Preserve every non-sensitive field — name, address, phone, email — across validation errors, session-level failures, and backward or forward navigation within…
- [Slow checkout actions show a status, not a frozen screen](https://rubric.design/ux/checkout.loading-state-feedback) · Usually high · Show a spinner or progress indicator within a fraction of a second of any checkout action that can take more than a couple of seconds — payment submission…
- [Inputs declare their type and autocomplete purpose](https://rubric.design/ux/forms.autofill-and-input-type) · Usually high · Set the type attribute to match the data a field collects (email, tel, number with inputmode, and so on) and add the matching autocomplete token from the HTML…
- [CTA label matches the page it leads to](https://rubric.design/ux/forms.cta-label-matches-destination) · Usually high · Word the CTA to describe exactly what the destination page is, using the same or closely matching terms — a button labelled "See Plans" leads to a page whose…
- [Required and optional fields are both marked, consistently](https://rubric.design/ux/forms.required-optional-marking) · Usually high · Mark every field's required/optional status explicitly and visibly — not only the required ones, since a form with asterisks on some fields leaves every…
