How OEM beer contracts work: a guide for brands launching private-label beer

Private-label beer has never been easier to launch at a surface level: find a brewery, agree on a style, put your name on the can. The hard part is making sure that what arrives in your market, six months and a container of beer later, is actually what you agreed to. That gap — between a handshake on a style and a legally enforceable contract that protects you when something goes wrong — is where most brand owners underestimate the complexity of OEM brewing relationships.

This guide works through each element of a proper OEM beer contract: what it covers, why each clause matters, and what the most common failure modes look like. It is written for brand owners who are serious about building a private-label beer rather than just placing a one-time order.

What the OEM contract actually governs

A well-structured OEM beer contract is not a purchase order. It is a technical and commercial agreement that touches almost every dimension of the product. The recipe clause covers the grain bill, hop schedule, yeast strain, and target parameters — original gravity, final gravity, attenuation. The quality specification section defines acceptable ranges for ABV, IBU, color in EBC, turbidity, and microbiological limits including total viable count, coliforms, yeast and mold count, and — for packaged beer — total package oxygen (TPO). The packaging specification covers can or bottle size, label artwork files, closure type, and any secondary packaging such as a case design or gift box.

On the commercial side, the contract governs production volumes and minimums (MOQ per run and any annual volume commitment), pricing structure (per case, per hectoliter, or per unit), lead times from purchase order to production completion, payment terms, and quality rejection rights — including who bears the cost of off-spec product. Confidentiality provisions close the document, typically requiring the brewery not to share your recipe, artwork, or commercial terms with third parties.

The most important thing to understand about the recipe clause is its IP status. Recipes and formulas are the commercial heart of your brand, and their ownership should be stated explicitly in the contract rather than left implied. A recipe you bring to the brewery is your intellectual property and should be designated as such in writing. A recipe co-developed during the OEM engagement is a negotiation, and the terms of that negotiation — territorial exclusivity, the brewery's right to produce for other markets, transfer rights if you change supplier — need to be settled before a single pilot batch is brewed.

Recipe development phase: what to expect

Most OEM relationships begin not with a signed contract but with a recipe development phase, and most brand owners underestimate how long this takes and what it actually involves. A typical development cycle runs six to twelve weeks. If you are bringing a complete recipe specification — grain bill with exact percentages, hop varieties and additions by weight and timing, yeast strain, water chemistry targets, target OG/FG/ABV/IBU — the brewery's technical team will scale it to production and brew one or two pilot batches, typically 100 to 500 liters, to verify the recipe performs as written. If you are starting from a flavor brief rather than a recipe, add several weeks: the brewery needs to translate your description into a working formulation before pilot brewing begins.

Expect two to four rounds of sample revision before you sign off on a production-standard recipe. Each round involves the brewery adjusting the formulation based on your feedback, brewing another pilot, and shipping samples for your evaluation. This is not inefficiency — it is the normal engineering process of dialing in a recipe at small scale before committing it to a full production run. The things that shift between rounds are usually subtle: hop character at the drinking temperature rather than cellar temperature, mouthfeel once the beer has conditioned, color under retail lighting versus brewery lighting.

Development fees, if the brewery charges them, cover the ingredient and labor cost of pilot brews. The amount varies widely — from nothing at a brewery that absorbs pilot cost as a cost of customer acquisition, to a few thousand dollars at a facility with expensive specialty ingredients or a formal R&D team. A common arrangement is for the development fee to be deducted from the invoice for your first production run, effectively treating it as a deposit against the production relationship. Clarify this before you begin development, because discovering mid-process that pilot costs are non-refundable if you don't proceed to production changes the commercial logic of the relationship.

Quality specifications and rejection rights

The quality specification section is the most consequential part of the OEM contract for protecting your brand, and it is the section most commonly written too loosely. A robust quality spec defines the acceptable range for each measurable parameter: ABV (a typical tolerance is ±0.3%), IBU (±5 is standard), color in EBC (±3 covers normal batch variation without allowing a clearly different-looking beer), and turbidity where relevant. For microbiological safety, the spec should state the testing method and acceptable limits for total viable count, coliforms, and yeast and mold count.

Beyond the parameter ranges, the spec should define the Certificate of Analysis format — what it contains, in what units, signed by whom — who performs the testing (brewery lab, third-party lab, or both), and the turnaround time for sharing CoA results before release. Some brand owners require third-party verification for the first run of a new recipe or whenever a batch is flagged as borderline. That right should be in the contract, including who pays for third-party testing.

The rejection clause is where the contract either protects you or leaves you exposed. It should state your right to reject any batch that falls outside specification, define the window in which rejection can be exercised, and — most critically — allocate the cost of rejected product. Does the brewery replace it at no charge? Do you share the loss? Is there a formula based on degree of deviation from spec? Without explicit cost allocation, a dispute over an off-spec batch becomes a negotiation under pressure, which is exactly the wrong moment to be negotiating. Get it settled in writing before you order anything.

Pricing structures and what drives cost

OEM beer pricing is typically quoted per case or per hectoliter, with the per-case figure easier to map to your retail economics. The number on the quote sheet, however, is the output of several underlying cost drivers, and understanding those drivers is what lets you manage cost intelligently over time rather than simply accepting or rejecting a quote.

Grain cost varies significantly with recipe complexity. A standard two-malt lager grist is considerably cheaper per unit than a multi-grain bill with specialty malts, because specialty malt is priced higher per kilogram and a complex grain schedule takes more mash time. Hop cost can be the biggest single variable: a dry-hopped IPA with late additions of premium hop varieties will cost meaningfully more per hectoliter than a standard lager, sometimes double. Packaging material is another lever — off-the-shelf can graphics cost far less than a custom printed can with specialty finishes, and tooling and setup charges for a new can design are usually amortized across the first production run.

Production volume is the most powerful driver of per-unit cost. Lower minimum order quantities mean shorter production runs, which means more changeover time as a percentage of total production time, which means higher cost per unit. This is not the brewery being difficult; it is the arithmetic of batch manufacturing. Alcohol tax handling adds complexity in some markets where the brewery is responsible for excise tax at the point of production rather than at import — clarify who carries this liability explicitly, because the answer affects both pricing and cash flow timing. Always request a line-item cost breakdown from any brewery you are seriously considering: a supplier who will not show you the cost structure is a supplier who does not want you to have the information you need to evaluate them fairly.

What brand owners most commonly get wrong

Three failure patterns appear repeatedly across OEM beer relationships, and all three are avoidable with the right contract structure and due diligence upfront.

The first is under-specifying the recipe. A one-page flavor brief — "light, crisp, slightly hoppy, golden" — does not constrain the brewery enough to produce consistent beer. What it produces is a beer that satisfies the brief on the first pilot, which is brewed by an attentive technical team who know the customer is evaluating them. What it does not produce is a specification detailed enough to catch drift on the fifth production run, when water chemistry has shifted seasonally, the yeast strain is on a different generation count, or the hop variety in the brief has been substituted with something the brewery had in stock. A proper recipe spec runs to several pages and covers every controllable parameter. If your brewery says a detailed spec is unnecessary, that is a reason to be cautious, not reassured.

The second recurring mistake is skipping the in-person brewery visit before committing to a contract. A brewery audit reveals quality culture in ways that a certification document or a set of photos cannot. You can see whether the cellaring temperatures are actually being controlled, whether the lab is used daily or exists mainly to show customers, whether the staff treat cleaning and sanitation as a routine or as something they perform when someone is watching. A brewery that operates well when no one is visiting is a brewery worth committing to. A certification on the wall does not tell you which kind you are looking at.

The third failure mode is accepting the first full production run without a contractual right to pre-shipment sample review. By the time a forty-foot container of beer has been sealed, loaded, shipped across an ocean, cleared customs, and arrived at your warehouse, you have a problem that costs real money to resolve if the quality is off. A pre-shipment sampling clause gives you a defined window — typically after production is complete and before the container is sealed — to receive samples, evaluate them against the CoA, and approve release. Build this in as a contractual right, not a favor the brewery is doing you. Some breweries will push back on it as unnecessary friction; that response tells you something about how they expect to handle quality disputes.