Design · November 4, 2026 · 2 min read
Writing interaction notes for product-option selectors
A row of attractive option buttons does not explain how a product selection works.
By Polo Themes

A row of attractive option buttons does not explain how a product selection works. Interaction notes should define the relationship between choices, availability, images and the final item added to the cart. Start with the catalog rules before drawing more states.
List the decisions and dependencies
Identify each option the shopper controls and whether choices depend on one another. Color and size may form combinations with different availability. A selected finish may change the image. Write those relationships using actual example variants, not only abstract labels.
Distinguish unavailable combinations from temporarily loading information. They need different feedback. Do not let a disabled-looking button become the entire explanation for why a customer cannot choose something.
Define selection and change behavior
Record whether an option is preselected, what happens when the shopper changes it and which information must update. Include the visible product identity, price if applicable, availability message and cart payload. The design should not imply a change that the implementation does not make.
For a hypothetical bag with two sizes and three colors, show a combination that exists and one that does not. Explain whether changing color preserves the selected size or requires another choice. The correct behavior depends on the catalog and implementation; document the chosen rule explicitly.
Explain incomplete selections
If the customer must choose an option before proceeding, write the guidance and error placement. Preserve valid selections when correcting an incomplete one. Avoid forcing the shopper to start again because one required choice was missing.
Check how the control communicates its selected state without relying only on color. Include visible labels and ask the implementation team to verify keyboard and assistive-technology behavior in the working component. A design annotation is a requirement, not proof of accessibility.
Finish with an order-identity check
Write a scenario that starts with a selection change and ends with the cart. The item, variant and quantity in the cart must match what the page led the shopper to expect. Repeat with another combination and an unavailable state.
These notes make the handoff testable. They also help identify whether a proposed interaction needs a capability the current theme or commerce setup does not provide.
Continue with A design decision log for ecommerce projects.
