Chemical manufacturers evaluating Acumatica ask a narrower, sharper question than most verticals: not "can it make things" but "can it prove what went into this batch, six months after the fact, when a regulator or a customer's QA department asks." That is a lot genealogy question, and it is where Acumatica Manufacturing Edition's process-manufacturing support either earns its keep or falls short of what a client actually needs.
Process manufacturing is BOM plus quantity flexibility, not a separate module
Acumatica does not have a distinct "process manufacturing" module the way some ERPs do (formula management as a first-class object separate from BOM). What it has is the standard Manufacturing Edition BOM/Routing engine used in a process-like way: formula-style BOMs where component quantities are percentages or ratios of a batch size, and Production Orders that consume raw materials by weight/volume rather than discrete unit counts. This works for most batch chemical processes, but it means "formula versioning" is really BOM revision management — effectivity dates and revision numbers on the BOM header — not a dedicated formula-history object. Set client expectations there before the demo, not after.
Lot genealogy: this part is genuinely strong
Where Acumatica does deliver real value is lot tracking through the full transaction chain. Every issue, receipt, and production consumption carries the lot number, and the Where Used / Trace inquiries (built on the standard INLotSerTran history) let you walk from a finished-goods lot back to every raw-material lot consumed in it, and forward from a raw-material lot to every finished lot it touched. For a recall scenario that is the whole ballgame.
// Simplified trace: which raw material lots fed a given finished-goods lot
SELECT LotSerialNbr, InventoryID, TranType, RefNbr
FROM INTran
WHERE TranType = 'I' -- issue to production
AND RefNbr IN (
SELECT DISTINCT OrderNbr FROM AMProdItem
WHERE FinishedLotSerialNbr = @finishedLot
)Where I extend it: standard lot inquiries assume one level of consumption. For a multi-stage batch process (intermediate compound A feeds intermediate compound B feeds finished product), full genealogy needs a recursive trace across production orders, which I have built as a custom graph action that walks AMProdItem parent/child relationships and materializes the chain into a report, because the stock screens stop at one hop.
Acumatica has no built-in SDS (Safety Data Sheet) management, DOT/IATA hazmat classification fields, or REACH/GHS compliance tracking. Clients in regulated chemical manufacturing consistently need these as custom attributes on the Stock Item screen plus a document-attachment discipline for SDS PDFs, or a third-party EHS system integrated via the REST API. I have never seen a chemical manufacturer skip this requirement, so budget for it from the first estimate rather than discovering it in UAT.
Expiry dates and potency-adjusted quantities
Lot expiration is a native field (expiration date on the lot/serial class), and Acumatica will block issuing expired lots if the item class enforces it. What it will not do natively is potency-adjusted quantity — a raw material that is 92% pure this batch and 97% the next, requiring a yield-adjusted consumption quantity in the formula. That is a custom BOM quantity calculation, similar in shape to the apparel size-yield problem, just triggered by an assay result instead of a size code.
Wrapping up
Acumatica's lot genealogy and BOM revisioning cover the traceability backbone a chemical manufacturer needs, and cover it well. The gap is always the regulatory layer — SDS, hazmat classification, potency adjustment — which is customization or integration, not configuration. Scope that gap explicitly in the SOW; it is the single biggest source of change orders I have seen on chemical-manufacturing Acumatica projects.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.