The Notes Field Nobody Reads

Tom yam is a hot soup. That is the dish, not a defect in it. Customers kept typing “not spicy” into the order notes anyway.

Two ordinary facts had collided. People who cannot take chilli still want that soup, and a kitchen at peak hours does not read free text. Nobody was being careless. The request was made, and it died in the gap between the two.

The fix was not a larger notes field or a warning above it. The Add to cart button was taken off the dish entirely. The only way in is a dialogue that will not close until a heat level is chosen. The order then leaves as one line: Tom Yam (10072), mild. One SKU, one line, sitting where the cook is already looking.

What changed is not the amount of information but its form. Free text invites people to shout into a void and feel they have been heard. A required choice makes the same intent structured, singular and impossible to skip. Make a meaningful choice, then order.

The trade is worth naming, because it runs both ways. The customer's path got one step longer: a dialogue stands between him and the cart where there used to be a single click. In exchange he cannot end up waiting forty minutes for a soup he is unable to eat. The kitchen gets a line instead of an essay, and stops guessing. Care in both directions, and the price of it is one click.

The pattern held: the lunch builder followed, base and side and salad as options on a single SKU, same reasoning. And it is the same discipline this site applies to machines. A declaration beats prose, because the receiver is busy and will read exactly one line. Here the receiver is a cook with six tickets up.