Workshop Wednesday: Two Batches, Same Recipe, Totally Different Chocolate, How to Diagnose the Drift
Author: Cocoa Craft
Try the Chocolate Lab to save recipe versions and keep process notes close to the chocolate they describe.
You roast the same beans, weigh the same ingredients, and run the same recipe. Then Batch Two tastes sharper, feels thicker, or refuses to flow quite like Batch One. The recipe didn’t change, or so the notebook claims.
In craft chocolate QC, “same recipe” is a starting point, not proof that the process was the same. Beans change. Equipment warms up differently. A few grams can matter. And “I ran the melanger for about the usual amount of time” is not a measurement system, even if it has served faithfully for years.
The practical goal isn’t to eliminate every variation. It’s to find the point where the batches began to diverge, then test one likely cause at a time.
First, confirm the difference
Before adjusting the recipe, make sure you’re comparing like with like. Taste both batches at the same temperature and, if possible, in the same format. Check that they were tempered, moulded, and stored under similar conditions. A difference in cooling or crystallization can change snap, gloss, and mouthfeel without any change to the formulation.
Write down what is different. Be specific: “Batch Two is thicker at the same working temperature” is more useful than “Batch Two is off.” Separate sensory observations into categories such as flavor, texture, aroma, flow, and appearance. That gives you clues about where to look next.
Diagnose your process in the Chocolate Lab: save recipe versions, compare formulation changes, and keep process context and tasting notes connected.
Diagnose the drift, step by step
1. Check the beans before blaming the recipe
Start with the lot. Did both batches use beans from the same bag or shipment? Were they stored in the same place, for the same length of time, and protected from humidity and temperature swings?
Cocoa beans can take up moisture from their environment. Changes in bean moisture can affect roasting and how the nibs behave in the grinder. If one batch used beans that had been stored in a more humid area, note that before deciding the roast profile is the culprit.
Record the lot, storage conditions, and any checks you routinely use for incoming beans. If you measure moisture, sample consistently and use the same method each time. A single reading from one handful may not represent the whole lot.
2. Compare the roast as a curve, not a setpoint
A roast temperature on its own tells only part of the story. The starting temperature, bean mass, tray depth, airflow, probe position, agitation, and recovery after loading can all change how heat moves through the beans.
For each roast, record the charge weight, preheat condition, temperature over time, roast duration, and any changes in airflow or turning. Use the same thermometer placement and loading pattern where possible. If the roast differs in aroma, color, or how easily the shells separate, note that too.
If you’re investigating a difference, don’t change roast time, temperature, and bean mass all at once. Hold the other conditions steady and test one adjustment on a small batch. A roast profile that works for one bean lot may need tuning for another, but a controlled test will tell you more than an across-the-board time extension.
3. Verify the weights and recipe basis
Check the actual ingredient weights, not just the intended percentages. Make sure your recipe uses a consistent basis, such as percentages of total batch weight, and that you’re using that basis for every run.
Confirm the scale is on a stable surface and reads zero before weighing. Weigh ingredients separately, especially when a recipe includes cocoa butter, sugar, milk powder, or small additions such as lecithin. For a dark milk chocolate recipe, a modest weighing error in a smaller ingredient can shift sweetness, milk character, or flow enough to notice.
Also compare ingredient lots. Sugar or milk powder from a different source can behave differently, even when the recipe weight is identical. Record substitutions rather than quietly treating them as “the same thing.”
4. Check melanger load and the way ingredients went in
A stone grinder for chocolate is part of the process, not just a timer with rollers. Batch size, ingredient addition order, bowl temperature, and how quickly ingredients are introduced can affect circulation and refining.
Record the batch mass and the order and timing of additions. Note whether the mass circulated steadily or appeared to pack down, and whether the machine ran warmer or cooler than usual. A larger load, a slower-liquefying mass, or an ingredient added too quickly can change how the batch moves through the grinder.
Don’t treat refining time as the endpoint by itself. Two batches can spend the same number of hours in the melanger and finish with different textures. If you use a particle-size check, use the same method and sampling routine each time. Otherwise, record a consistent set of observations: flow at a defined temperature, mouthfeel, and any visible signs that the mass is struggling to circulate.
5. Check the finish, too
If the chocolate tastes similar but looks or snaps differently, review tempering and moulding before changing the formulation. Record working temperature, cooling conditions, mould temperature if monitored, and any differences in room conditions or storage.
When comparing two batches, use the same tempering method and a consistent tasting setup. Otherwise, a process difference at the finish can disguise what happened earlier.
Give the records a home
A paper notebook can be excellent. It can also become three notebooks, two loose labels, and one crucial roast note written on the back of a cocoa-butter bag.
That’s the gap recipe tracking needs to close: the formula alone doesn’t explain the batch. You need the version you made, the process conditions you used, and what you observed afterward. All connected well enough to compare later.
In Cocoa Craft’s Chocolate Lab, you can build and refine recipes, compare versions, and keep process and tasting notes with the work. Use the saved recipe as your reference, then follow the same batch checklist each time you make it. For teams that need structured production runs and operational controls, Maker Workshop is the production layer.
Save your next batch in Chocolate Lab and make the next comparison easier to trust. The tools are built around a practical idea: Built by chocolate makers, for chocolate makers.
Make the next test useful
When you find a likely cause, write down the evidence and choose one factor to test. Keep the recipe, bean lot, and other process settings steady if you can. Then compare the new batch using the same tasting and texture checks.
| What changed? | First places to investigate |
|---|---|
| Flavor changed, texture is similar | Bean lot, storage, roast curve, or ingredient lot |
| Texture changed, flavor is similar | Ingredient weights, moisture, load, or refining conditions |
| Flow changed during grinding | Batch mass, ingredient addition, temperature, or circulation |
| Snap or gloss changed | Tempering, moulding, cooling, or storage conditions |
This is how better home chocolate making and professional production meet: observe carefully, record consistently, and resist changing five things to fix one problem. Over time, those records help craft chocolate makers turn a good result into a repeatable one, and help a small team spend less time guessing at the next batch.
Get free, unlimited access to the full Cocoa Craft software suite in exchange for monthly feedback. Join the beta at cocoa-craft.com!
Improve batch repeatability. Create a free Cocoa Craft account and start keeping your recipes, process notes, and tasting observations together. Whether you’re building your first bean to bar chocolate recipe or refining artisan chocolate for production, the next batch is easier to diagnose when the last one left a clear record.