Before any menu I've built goes live, I run it through one test. Can every cocktail survive losing one ingredient and still ship as a sellable drink?
This isn't about allergies, though that's part of it. It's about operational fragility. A cocktail that can't be made without a specific elderflower liqueur is a cocktail that goes off-menu the moment that SKU is out of stock, delayed by the distributor, or discontinued by the brand. And it will happen. Supply chains are imperfect, distributor relationships change, and brands get acquired and reformulated. It always happens at the worst moment.
A fragile menu requires everything to go right in order to work. An operational menu builds in optionality.
For each cocktail on the menu, identify the one ingredient that's hardest to replace. Usually it's the liqueur, the amaro, the house-made component, or the one obscure modifier you special-ordered from a single importer.
Now ask: if that ingredient disappeared tomorrow, what's the one-ingredient swap that saves the drink?
If the answer is "there is no swap," the cocktail is fragile. You have three options:
The swap test also catches allergy fragility. If a cocktail can only be made one way and the main ingredient is a common allergen, the server is in a difficult position the moment a guest asks for a modification.
This takes about 20 minutes to run across a 12-cocktail menu. Do it before you print anything.
The swap test also protects your staff. When a server knows there is a backup option for a key ingredient, they can answer allergy and substitution questions with confidence instead of going back to the bar to ask. That confidence is part of the guest experience too.