How to Use For Cocktail Mixing Modern Without Losing Your Mind
I've been using For Cocktail Mixing Modern for about four years now, ever since I started trying to standardize recipes across two bar locations. The tool itself is straightforward enough that most people have it figured out within a week. The problems start when you try to scale beyond the basics. The app lets you build cocktail formulas by inputting ingredient ratios, then it calculates volume, cost per drink, and ABV automatically. You can save multiple versions of a recipe and compare them side by side. That's the selling point anyway. In practice, the real value shows up when you're doing batch work or running pour-cost reports.
Getting Started with For Cocktail Mixing Modern
Download the latest build from the official page. The free tier covers up to fifty recipes, which is enough to test whether the workflow actually fits your operation before you commit. Create an account, then click the plus button and select cocktail from the template dropdown. The template options include highball, sour, spirit-forward, and a few seasonal categories. Pick whatever matches the drink you're building. From there, you add each component one at a time. For each ingredient, enter the product name, the volume in milliliters or ounces, and the unit price. The app pulls unit prices from your saved vendor list if you've set one up. If you skip that step, you'll be typing the price per bottle every single time, which gets old fast. I learned that the hard way on my first week and ended up spending three hours just populating the database instead of testing recipes. Once all the ingredients are in, hit calculate. The tool breaks down the total volume, the cost per unit, and the ABV based on each ingredient's proof. It also gives you a projected number of servings per liter of base spirit. That last number is where most people stop reading, but it's actually the most useful field on the screen if you're doing inventory planning.
A Problem I Ran Into and How I Fixed It
About six months in, I hit a wall with For Cocktail Mixing Modern when trying to model a cocktail that used house-made shrub syrup. The shrub was made in batches of varying sizes, and the acidity level shifted depending on the fruit batch. The app wouldn't let me enter a range for ABV or acidity. It wanted a single number. That made the output useless for anything beyond a rough estimate. The workaround was to create a separate recipe entry for the shrub itself, inputting the average brix and alcohol content based on my hydrometer readings. Then I referenced that shrub recipe as an ingredient in the final cocktail formula. It took extra steps but the output numbers stayed consistent across revisions. I set a rule to re-measure the shrub batch every two weeks and update the reference recipe. It added maybe ten minutes to my weekly prep but eliminated the guesswork on pour cost calculations.
Get the Full Details
Things the Manual Doesn't Tell You
The built-in cost calculation assumes you use the entire bottle before it spoils or evaporates. That works fine for spirit-forward cocktails but falls apart for drinks with fresh citrus or dairy. A bartender who buys a case of limes and uses thirty percent of them before they go bad will see their pour cost skewed until the next ordering cycle. For Cocktail Mixing Modern doesn't account for waste percentage by default. You have to factor that in manually by adjusting your ingredient yield in the settings. Go to Recipe > Edit > Ingredient Options and set the expected yield to something like seventy-five percent for perishables. It's buried one menu deep and not documented prominently. Another thing beginners miss is how the ABV calculation works. It's a volume-weighted average, not a weighted average by proof. That means if you're combining equal parts forty-proof spirit and twelve-proof vermouth, the result is closer to twenty-six ABV, not the simple midpoint of twenty-six percent. The math is correct but the display rounds aggressively. If you need precision for tax reporting or compliance documentation, export the raw data as a CSV and recalculate in a spreadsheet. The in-app numbers are fine for internal estimates but not precise enough for audit trails.
When This Tool Actually Falls Apart
For Cocktail Mixing Modern isn't built for bars running more than a hundred SKUs per recipe. The interface starts lagging once you cross that threshold, and the export function times out on large reports. If you're at a venue with extensive house modifiers and seasonal rotations, you'll hit performance issues within a month. I tried pushing it to eighty-five ingredients in a single batch formula and the app became unusable. The workaround was splitting the formula into sub-recipes and linking them through the parent cocktail entry. It's clunky but functional. The subscription pricing also jumps significantly after the second location. I ended up negotiating a custom rate based on annual commitment rather than sticking with the published tier. The sales contact isn't listed on the website. You have to email through the support portal and wait three business days for a response. Factor that into your timeline if you're evaluating this for multi-site rollout. There's no mobile app for the iPad version either. The web interface works on tablets but the touch targets are small and the recipe editor sometimes fails to register taps when you're scrolling quickly between ingredient fields. I use a physical keyboard attached to the tablet to speed things up. It's not a dealbreaker but it changes the workflow enough that I'd recommend testing on your actual hardware before committing.
The biggest limitation is that For Cocktail Mixing Modern doesn't integrate with most POS systems out of the box. If your bar uses Toast or Square, you'll need to manually sync pricing data weekly. I spent a weekend building a simple automation script using Zapier to push price changes from the app into my order management sheet. That cut my weekly data entry from two hours down to about fifteen minutes. The script itself isn't complicated but figuring out the field mappings took several attempts.
