The Role of Spice Tolerance in Menu Personalisation

If you had to pick one preference signal to start with, spice tolerance is a strong candidate. It's specific enough to be genuinely useful, simple enough for a guest to state in one tap, and it maps directly onto a real, common source of ordering anxiety: nobody wants to order something that turns out far hotter, or far blander, than they expected.

Why spice tolerance is such a clean signal

Unlike broader taste preferences that can be vague or hard to articulate, spice tolerance is close to a single, measurable variable. A guest generally knows their own tolerance well, mild, medium, hot, and that self-knowledge tends to be more reliable than, say, trying to describe an abstract flavour preference. It's also a preference that stays fairly stable over time for most people, which makes it a durable signal rather than something that needs constant re-checking.

How this plays out at the table

• A guest who flags a low spice tolerance can be steered away from a dish that would genuinely be an unpleasant surprise for them
• A guest who loves heat can see spicier options surfaced higher, rather than having to hunt through descriptions guessing at intensity
• Consistent spice labelling across the whole menu, not just guesswork from a description, reduces genuine mismatch between expectation and what arrives
• New dishes can be positioned toward the right spice-tolerance audience from day one, rather than guessed at broadly

This isn't purely about guest satisfaction either, it has a real operational benefit. A dish returned or complained about because it was unexpectedly too spicy is a cost to the kitchen and the server's time, on top of a bad guest experience. Getting spice expectations right upfront reduces that friction meaningfully, and it's one of the easier preferences to get consistently right, compared with vaguer taste categories.

Where spice intersects with allergen safety

Spice tolerance is a preference, not a safety issue, and it's worth keeping that distinction clear even though the two get tagged in similar places on a menu. A guest who dislikes spice has an unpleasant experience if a dish is hotter than expected. A guest with an allergy has a genuinely dangerous one if an allergen isn't flagged. Both deserve careful tagging, but they're not the same category of risk, and a good system treats allergen flagging with more rigor than spice preference, even while managing both.

Why spice tolerance also helps with the AI dish explainer

When a guest asks the menu's built-in explainer whether a dish is spicy, having an accurate, consistently tagged spice level already on file means the answer is precise rather than a vague description written once and never revisited. A guest who asks how hot something actually is gets a direct, reliable answer instead of having to interpret a chili icon that might mean something different from one dish's description to the next. That consistency compounds: once spice tagging is accurate across the whole menu, every feature that touches spice, sorting, flagging, and the explainer answering a direct question, gets more reliable at the same time.

Getting the initial tagging right during setup

Spice tolerance is one of the easiest signals to tag accurately during onboarding, since it doesn't require subjective judgement calls the way something like adventurousness might. A kitchen already knows roughly how hot each dish runs relative to the others on the menu, and translating that into a consistent scale across the whole menu takes a single pass through the dish list rather than an extended project. Getting this right early matters more than it might seem, since spice is one of the first preference signals guests interact with, and an inconsistently tagged menu undermines confidence in personalisation broadly, not just in the spice dimension specifically.

TasteGraph captures spice tolerance as one of its core preference signals during onboarding, and separately flags allergen conflicts before a guest can order them, keeping the preference side and the safety side distinct while making both easy for a restaurant to tag accurately from the start.