In this guide 6 sections
Formulation software serves the lab: it stores trial recipes, properties and experiments. A chemical ERP serves the plant: it schedules reactors, issues materials, records batches and ships orders. Most resin makers need both, joined by one approved recipe that passes from the lab to production.
Two tools for two different jobs
Formulation software is built for chemists. It holds trial recipes, target properties such as viscosity, gel time and glass transition temperature, and the history of what was tried. The question it answers is which mix gives the result.
A chemical ERP is built for the plant. It holds approved recipes, reactor schedules, raw material stock, batch records, quality release and customer orders. The question it answers is how to make that mix repeatedly and ship it on time.
Mixing them up causes trouble. A lab tool rarely knows about drum stock, and a plant system rarely helps a chemist compare fifty epoxy trials side by side on peel strength and open time.
- Formulation tool: trials, properties, experiments
- ERP: reactors, stock, batches, orders
- Lab owner: R&D chemist
- Plant owner: production and planning
What a resin or adhesive plant needs from each
Resin and adhesive work has features that a general tool misses. Polyester and epoxy batches run to a cooking curve with temperature holds. Acid value and hydroxyl value are checked mid-batch and the cook is extended or stopped on the result.
Adhesive makers often blend a base with a hardener at a set ratio, then ship the two parts as a kit with a stated pot life. The ERP must track both components and the kit as one sellable item.
The lab, meanwhile, needs freedom. Chemists change a catalyst level six times in an afternoon and do not want an approval workflow for each trial.
- Cook curve with holds and in-process tests
- Acid value, hydroxyl value, viscosity limits
- Kit ratios and pot life for two-part products
- Lab trials without approval overhead
Where the handover goes wrong
The riskiest moment is scale-up. A recipe leaves the lab as a page of notes in grams, with solvents in millilitres and a remark that the mixture needs stirring until clear. Production must turn that into kilograms, reactor steps and safe charging order.
Teams often retype the recipe by hand. Typing errors creep in, and the plant version slowly differs from the lab one. Nobody can say which is the approved master.
Fix this with a defined release step. The chemist marks a trial as a candidate. A process engineer converts units, adds charging order and hold times, and quality approves. Only then does the recipe exist in the plant system.
How the two connect in practice
The simplest link is a controlled export. The formulation tool produces a recipe file with ingredients, quantities and target properties, and the ERP imports it as a draft that production completes. Nobody retypes a number.
Going the other way matters too. Batch results, such as the actual viscosity at the end of the cook, should flow back to the lab. Chemists then see how a lab recipe behaves at 5,000 litres.
If the budget allows only one tool, choose by where your losses sit. Rejected batches and late orders point to the ERP. Slow product development points to the lab tool.
- Export with units, ingredients and targets
- Import as a draft needing plant steps
- Batch results returned to the lab
- One master recipe with one owner
Decide with a short set of questions
Ask who touches the recipe after the chemist. If planners, buyers and the quality lab all do, you need the ERP side. Ask how many trials a chemist runs each month and how they find an old one. A shared folder of PDFs as the only archive points to the lab side.
Ask how a customer complaint reaches the formula. A complaint about gel time should lead from the invoice to the batch, to the raw material lots and back to the trial that created the recipe.
Begin by writing your current handover on one page. Mark each retyping step in red. Those red marks are where a connection pays for itself.
Lab-to-plant handover sheet
A one-page form that travels with each recipe. Block one holds product, grade, lab owner and trial number. Block two lists ingredients with lab quantity, plant quantity and unit. Block three records charging order, temperature holds and in-process tests with limits. Block four carries signatures from chemist, process engineer and quality.
Open a blank worksheet to printQuestions owners ask
Do resin makers need formulation software?
If the lab runs many trials and compares properties, yes. A small plant with few products can keep formulations inside its ERP or a controlled sheet until trial volume grows.
Can a chemical ERP replace lab formulation software?
It can hold recipes and versions, but it seldom supports trial comparison or property modelling well. Most plants keep a lab tool for research and an ERP for production.
What is the biggest risk when moving a recipe to production?
Retyping and unit conversion. Quantities in grams or millilitres must become kilograms and charging steps, and every manual copy is a chance for the plant and lab versions to drift.
How do we keep the plant and lab recipes in step?
Name one master recipe, one owner and one release step. Changes start in the lab, pass the handover form and enter the plant system only after approval.