Comparison
WickAndWax vs Craftybase
Craftybase suits a maker who wants materials inventory and cost of goods across a whole handmade catalog, while WickAndWax suits a maker whose sharpest risk is proving which pour went into which shipped order.
Comparison
Soapmaker Software is for the maker refining recipes and lye math before the pour, while WickAndWax is for the maker who has to prove what happened after it.
Soapmaker Software sits at the formulation end of the bench: recipes, lye calculations, batch resizing, the arithmetic you do before anything melts. WickAndWax starts where that ends, at the pour itself, and follows the batch through cure, release testing, label print, lot code and the customer order. A soaper still developing a bar wants a formulation workbench. A studio being asked for lot codes, cure records and compliant panels wants the traceability side. Plenty of makers run a recipe tool alongside WickAndWax and never feel the two competing.
| What you are deciding | WickAndWax | Soapmaker Software |
|---|---|---|
| Center of gravity | The batch you actually poured and where its units went | The recipe you intend to pour and the math behind it |
| Soap and candle coverage | Cold process, hot process, melt and pour, candles, melts and lotion bars in one place | Rooted in soap making practice and its formulation needs |
| Lot codes | Assigned at the batch and carried onto labels, cases and packing slips | Sits outside the formulation problem the tool is designed around |
| Cure tracking | Cure start, ready date, rack tag and a release check before packing | Cure is a property of the recipe rather than a queue you work from |
| Label panels | Generates the candle warning panel and the cosmetic panel from batch data | Approach is recipe and ingredient focused, not print output |
| Order link | Every shipped order points back to the batch that filled it | Selling and shipping sit outside the tool scope |
| Who it suits | A studio selling steadily and answering to buyers and customers | A maker building and refining formulas, including hobby scale work |
The right hand side describes where Soapmaker Software sits as a category and whose workflow it assumes. Software shifts month to month, so read their own pages before you commit. WickAndWax is published by MLJ, SASU and this page is written by Jimenez Julien.
A formulation tool answers a design question: at this superfat, with these oils, what does the lye come to and how will the bar behave. That question is answered once per recipe and revisited when you change something. It is careful, mathematical work and a dedicated tool is a reasonable place to do it.
A batch record answers a history question: on the fourteenth, using oil lot 22841 and fragrance lot A9, you made sixty bars, held them twenty eight days and shipped forty two of them to these orders. That question comes up every single pour, and the answer has to survive months so it can be produced when someone asks.
Wholesale accounts tend to ask three things: a lot code on the case, a correct panel on the unit and a lead time you can hold. None of those come out of a recipe. They come out of a record of the specific batch, which is why studios that start selling into shops usually add a production system rather than a better calculator.
The same applies when a customer writes in. The useful reply names the batch, says what was in it, says when it was made and says whether anything else from that pour is still out there. Getting there in two minutes rather than two evenings is the difference between a service reply and a weekend lost to detective work.
The clean split is straightforward. Design the formula wherever you like, then record the approved version in WickAndWax as the formula the batch was poured to, with its fragrance load and vessel size. From then on the batch record references that version, so a change to the load in March does not quietly rewrite what you poured in January.
Studios that work this way stop hunting for which version of a recipe made a particular bar. If you later reformulate, the old batches still point at the old version, which matters when a customer compares a bar they bought last year with one they bought last week.
It holds the formula you approved, including oil weights, lye amount, water and superfat, and it scales a batch up or down from that. It is a record of the formula rather than a design workbench. Makers developing new recipes usually keep a dedicated formulation tool for that stage.
Yes, and many soapers do. Treat the formulation tool as where a recipe is designed and WickAndWax as where the approved version is locked and poured against. Give each version a number so the batch record points at something specific rather than a name.
Very much so. Candle makers face the same split between a fragrance load worksheet and a record of the actual pour. Wax type, fragrance percentage, pour temperature, cure days and wick size all belong on the batch, and the warning panel is generated from it.
Comparison
Craftybase suits a maker who wants materials inventory and cost of goods across a whole handmade catalog, while WickAndWax suits a maker whose sharpest risk is proving which pour went into which shipped order.
Comparison
Airtable suits a maker who enjoys building systems and has an unusual process, while WickAndWax suits a maker who wants pour, cure, label and ship handled today.
A head to head can only compare the general shape of two products, not the way a soap loaf, a wax melt run and forty eight tins move through your particular week. Pick a pour you finished recently, bring the supplier lots and the cure dates, and we will walk it through the record in front of you. You will know by the end of the call which column of this table your studio actually lives in.