An MES for plants that measure output in batches, not units
Manufacturing execution system software for food, beverage, supplement, cosmetics and chemical manufacturers. Work orders run from versioned recipes, operators record the lots they consume, and yield is compared with plan on every batch, so execution and traceability come from the same entries.
What an MES does on a batch floor
An ERP plans what should happen and records what it cost. An MES records what actually happened while it was happening. On a batch floor, that means lots, recipes and yield.
Work orders from versioned recipes
Each order is built from a specific recipe version with its components and expected yield. Components scale to the batch size, and the version that ran stays on the record.
Lot-level ingredient consumption
Operators record which lots went into the batch and how much of each, with units converted automatically between purchase and recipe units.
Actual against planned yield
Output is compared with the plan on every batch, so loss is attached to a lot, a line and a shift rather than surfacing at month end.
Variance approval on the floor
When consumption passes your production policy limit, the order cannot be completed until a supervisor or manager approves the exception with a recorded reason.
Quality holds that are enforced
Material on hold cannot be issued to a work order or shipped, and the release decision stays with the lot it applies to.
Genealogy as a by-product
Because consumption and output are recorded by lot, one-up/one-back genealogy and mock recalls come from the execution record itself.
MES or ERP: what each one answers
Most batch manufacturers need both. Zelviq covers the execution side, and keeps accounting where it already is.
What should we make?
Planning and demand, which sit in the ERP or planning layer.
What did we actually use?
The MES question: which lots, how much, on which line and shift.
What did we get?
Finished lots with their own codes and expiry dates, compared against plan.
Who approved the exceptions?
Variances beyond policy carry a named approval and a reason.
What did it cost?
Costs flow back to accounting through the two-way QuickBooks Online sync or the REST API.
Why batch plants choose a batch MES
Built for recipes, not assemblies
Discrete MES products assume serial numbers and assembly steps. A batch plant needs lots, expiry dates, unit conversions and yield, which is what Zelviq records.
Execution and traceability in one record
No reconciling a shop floor system against a separate traceability tool, because the genealogy is built from the same entries operators already make.
Priced for one plant, not an enterprise rollout
Published plans from $189 a month, flat per company, with a 30-day free trial and no credit card.
Frequently asked
What is a manufacturing execution system?+
An MES records production as it happens: which order ran, what went into it, what came out, and who signed off. It sits between planning (what should be made) and accounting (what it cost). In batch manufacturing the unit of record is the lot, not the serial number.
What is the difference between an MES and an ERP?+
An ERP plans and accounts: purchasing, inventory value, orders, finance. An MES captures execution on the floor: consumption, output, variance and approvals. Zelviq covers execution together with inventory and traceability, and syncs with QuickBooks Online so accounting stays where it is.
Does Zelviq connect to PLCs, SCADA or OPC-UA?+
No. There is no machine connectivity in Zelviq, so it does not collect machine data, run OEE from machine signals or control equipment. Operators enter consumption and output through the application. If automated line data capture is your requirement, an automation-focused MES is the right tool.
Is Zelviq suitable for discrete manufacturing?+
No. It is built for batch and process manufacturers in food, beverage, supplements, cosmetics and chemicals. Discrete assembly with serial numbers and routing steps is a different problem.
Can we run Zelviq as an MES alongside an existing ERP?+
Yes. Execution and lot records live in Zelviq, and the REST API and outbound webhooks push data to whatever sits upstream. There are no packaged SAP, Oracle or Dynamics connectors, so that integration is built against the API.
How long does it take to get running?+
The setup work is master data: items, units of measure, recipes and locations. Most manufacturers start with one product line inside the 30-day trial, run it alongside paper for a few batches, then switch.
See a work order run end to end
Bring one recipe and a recent batch. We will run it through Zelviq: issue the lots, record the output, and show the yield and the genealogy that come out.