Protecting your recipe in a contract brewing deal

What you can and cannot protect

A beer recipe is a list of ingredients and a process. Brewing techniques are widely known, so a recipe is hard to register as intellectual property in any useful way. What you can protect is your brand, through a trademark on the name and label. You can also protect your confidential know-how, through contracts.

In India that protection rests mostly on contract terms and confidentiality obligations rather than on a registration you file somewhere. That is why the agreement with your host matters more than any certificate. Have a lawyer draft or review it. This guide covers what to ask for, not legal advice.

The clauses that matter

• Ownership. The contract should say the recipe, process notes and specifications belong to you, now and after the deal ends.
• Confidentiality. The host and its staff may use your recipe only to brew your beer. They must not share it.
• No copying. The host agrees not to brew a substantially similar beer for itself or another client for a set period.
• Return or destruction. When the deal ends, recipe documents, yeast and any special ingredients come back to you or are destroyed, in writing.

A non-compete on style is hard to enforce if it is too broad. Nobody can stop a brewery making a lager. Keep the clause about your specific beer, its specification and its distinctive ingredients.

Own the yeast, not just the paperwork

If your beer depends on a particular yeast strain, the strain is often worth more than the grist. Buy it in your name from the yeast supplier, keep a backup with the lab or a second supplier and agree in writing how many generations the host may repitch it, for example up to eight. Agree too that slurry is dumped at the end of your run.

Do the same with any unusual ingredient: a hop blend, a spice mix or a fruit purée. If you supply it pre-weighed for each brew, the host knows how much goes in without needing to know exactly what is inside. Our guide to contract brewing in India explains how supply arrangements usually work.

Practical controls on the brew day

Share the brew sheet the host needs to make the beer, not your whole development history. Trial notes, failed versions and the reasons you made each change are yours. Keep them in your own files.

Attend the first two or three brews. You will see how your recipe is translated to the host's kit. The brewers will also see that you know the beer. Ask for a copy of each batch record. It protects you if quality drifts. It also shows that the host treats your beer as yours.

When protection is really about quality

Most recipe disputes are not about theft. They are about drift. The host swaps a malt because your usual one is out of stock, or changes a hop schedule to save time. Six months later your beer tastes different and nobody wrote down why.

Write your specification with numbers: original gravity, final gravity, ABV, colour in EBC, bitterness in IBU, pH and carbonation, each with a tolerance. Require written approval for any ingredient substitution. That protects the recipe in the way that matters most to drinkers.

Think about the exit on day one

One day you may move to another host or to your own brewery. Plan for it now. The contract should let you take the recipe, specification and yeast with you without a fee. It should also oblige the host to help with a short handover if you ask.

Founders who skip this often find the host has quietly become the only place the beer can be made exactly right. Thinking through contracts, supply and exit together is a core part of running a brand you do not yet brew yourself.

Keep a reference sample and a record

Keep a few packs from every batch in cold storage for at least the beer's shelf life. If a dispute comes up over whether the host changed something, a reference sample tasted side by side with the new batch settles it faster than any argument over paperwork.

Keep your own dated record too: the recipe version, the specification and every change you approved, with the date and the reason. If you ever need to show that a beer is yours, a clear history of how it was developed is far stronger evidence than a recipe sheet that appeared the week the deal went sour.

Your first step

Make a one page list of everything that makes your beer yours: the recipe, the yeast, any special ingredients, the specification and the brand. Next to each item, write who holds it today. Anything held only by the host is the first thing to fix in your contract.

Common questions

Can I patent a beer recipe?

In practice, almost never. Recipes are usually protected through contracts and confidentiality, while the brand name and label are protected through trademarks.

Should I give the host my full recipe?

Give the host what it needs to brew the beer to specification. Keep development notes and trial history in your own files.

Who should own the yeast strain in a contract deal?

You should, ideally bought in your name with a backup held elsewhere and clear rules on how the host repitches and disposes of it.