Tracking Your Candle Batches Without Overcomplicating It
Most people start candle making with a notebook, a dozen sticky notes, and eventually zero idea what they did last month. I've been doing this for years, and the method that actually works is a spreadsheet I built and have been refining for a long time. It's not fancy. It's not an app. It's just a flat table with columns that matter and columns that don't, and I use it as my Minimalist Candle Making Tracker every single batch. A Minimalist Candle Making Tracker is simply a structured record of every batch you pour. Not every candle you make — the batch. Because one batch might yield twelve containers, and the variables are the same across all of them. The wax, the fragrance oil percentage, the pour temperature, the wick, the ambient temperature when it cured. Those are your real variables. Everything else is noise. The core columns I use are: date, wax type and supplier, wax weight, fragrance oil type, fragrance load percentage, total fragrance weight, wick type and size, melt pool temp (if measured), pour temp, cure duration, container type, and a results field for sinkholes, tunneling, scent throw scores, and any defects. That's it. Ten columns. Maybe twelve if you're splitting scent tests.
How I Actually Use It Day to Day
I keep it in Google Sheets because I can access it from my phone while pouring. The moment I weigh wax, I log the batch ID and wax weight. When I add fragrance, I record the FO and the load. Wick gets logged with the container SKU so I can search later. After the candle cures, I score the scent throw on a 1-5 scale and note any visual defects. The whole entry takes about thirty seconds if I'm already at the workspace. The real value comes in retrospective. I once had a batch of 16oz jars from a specific soy blend that looked perfect but had almost no cold throw. Three months later, I searched my tracker for that wax lot number and found I'd used a 7% fragrance load when this particular wax and FO combination actually needed 9%. The tracker showed me the exact batch, the FO cost per unit, and the supplier lot. I adjusted the load on the next order and stopped wasting fragrance oil. That kind of correction is impossible without a flat record.
The Columns That Most People Skip (And Why They Regret It)
Wax supplier lot number. This matters more than you think. Different manufacturing lots of the same wax brand can have slightly different melt points and opacity levels. I learned this after a batch of 12oz votives came out cloudy when my previous three batches of the same wax were crystal clear. The lot numbers were different. My tracker flagged it immediately when I sorted by lot. Two minutes of looking back saved me from repeating the mistake. Ambient temperature and humidity at curing time. Not the pour temperature — the room conditions while the candle sat curing. Temperature swings during curing affect shrinkage and top surface texture. I started logging this after a friend pointed out that my winter batches had significantly fewer sinkholes than my summer ones. I was blaming the wax. It was the curing environment. My tracker shows a consistent 2-3 degree drop in ambient temp between November and March, and the sinkhole rate drops by about forty percent in those months. That's actionable data. Fragrance oil cost per batch. This is the column nobody logs until they're trying to price their candles and have no idea what their fragrance cost actually is per unit. I calculate it once per batch and it feeds directly into my per-unit cost sheet. The difference between guessing and knowing is usually five to twelve cents per candle, which adds up fast.
Get the Full Details
Edge Case: When the Tracker Breaks Down
My tracker doesn't handle blending fragrances well. I had a phase where I was testing two-fragrance combos at different ratios, and the single FO column became useless. I ended up with entries that read "FO-A 60% / FO-B 40%" in a field designed for one answer, and later searching became unreliable. I fixed it by adding a secondary fragrance column and a ratio field. If you plan on doing custom blends, build that into the sheet before you need it. I waited too long and spent a week reformatting old entries. Another limitation: the tracker assumes you're pouring one container size per batch. If you're running a production day with 4oz, 8oz, and 16oz containers using the same wax and fragrance formula, the data gets muddled. I solved this by adding a container size field and treating each size as its own row, even if the wax and fragrance variables are identical. It inflates the row count but keeps the data searchable.
Advanced Nuance: Scent Throw Is Not a Single Number
Your results field should separate cold throw and hot throw. I used to just write "good throw" and realized six months later I had no way to distinguish between the two. Cold throw is the fragrance strength when the candle is unlit. Hot throw is what you get burning. They're influenced by completely different factors — cold throw is mostly FO affinity to the wax at room temperature, while hot throw depends on wick performance, melt pool diameter, and burn time. Logging them separately lets you diagnose problems. If your hot throw consistently scores lower than cold throw, you likely have a wick sizing issue or a melt pool that's too narrow. If cold throw is weak but hot throw is decent, your fragrance is binding properly to the wax but burning off efficiently. Those are two different problems requiring two different fixes. A Minimalist Candle Making Tracker won't predict problems before they happen. It won't tell you the optimal fragrance load for a new wax you've never used. It won't replace testing. What it does is build a historical record fast enough that you actually keep using it, and that record becomes predictive over time. After fifty-plus batches, my sheet starts showing patterns — which FO-wax combinations consistently underperform, which wick types fail at specific container diameters, which curing windows produce the cleanest tops. The patterns only appear if you log consistently. If you want something that automates wick selection or generates pricing, you'll need a more complex system. But those systems usually require a learning curve and regular data entry discipline that most makers drop after a few weeks. The spreadsheet approach works because the friction is near zero. Thirty seconds per batch. That's it.
