Cosmetics manufacturers share the chemical industry's lot-genealogy and expiry concerns, but with their own wrinkle: formula versioning tied to regulatory filings (each formula version may need to match an INCI ingredient declaration on file with a regulator), and a much heavier emphasis on shelf-life-driven inventory rotation than most process manufacturers, because a lipstick that expires unsold is a total loss, not a reprocessable input.
Expiry dates have to drive picking, not just sit as a field
Acumatica's lot/serial class supports expiration dates and can enforce FEFO (first-expired-first-out) behavior at issue if the item class and warehouse picking configuration are set up for it — this is native, not custom. The mistake I see on cosmetics implementations is leaving the default lot-selection method at FIFO (first-in-first-out by receipt date) rather than FEFO, which is fine for most goods but wrong for anything with a hard expiry, because a later-received lot can have an earlier expiry than an older one if the vendor's own stock rotation was inconsistent.
Lot/Serial Class: COSM-FEFO
Lot Numbering: Automatic, per receipt
Expiration: Required (blocks issue of expired lots)
Issue Method: FEFO — First Expired, First Out
(not FIFO — receipt order is not expiry order)Formula versioning tracks the BOM, but INCI declaration is a separate document you must own
A cosmetics formula revision — swapping a preservative system, adjusting a fragrance load — is a new BOM revision with an effectivity date, same mechanism covered under chemical manufacturing. What Acumatica does not do is manage the INCI (International Nomenclature of Cosmetic Ingredients) declaration or regulatory filing that must correspond to that formula version for markets that require it. I handle this as a required attachment on the BOM revision (the filed INCI document, PDF, linked via standard Acumatica file attachment) plus a custom "regulatory status" field on the BOM header (Filed / Pending / Not Required) so production cannot release a batch against a formula whose paperwork is not confirmed — a soft workflow gate, not something the platform enforces by itself unless you build the check.
Some markets expect a signed batch production record (who ran it, what lots went in, QC sign-off) as a retrievable document, not just queryable transaction history. Acumatica's production order captures the underlying data natively; generating a formatted, signable batch record document is a Report Designer project, not a default screen. Ask this question explicitly during discovery — clients often assume it exists because the data does.
Small-batch and pilot-run costing distorts standard cost quickly
Cosmetics brands frequently run small pilot batches (50–200 units) to test a formula before a full production run, and if those pilot batches post against the same standard-cost item as full-scale runs, one-time setup and testing labor drags the standard cost around unpredictably. I usually isolate pilot/R&D runs into their own non-saleable item variant or a separate production order class so their cost variance does not bleed into the sellable SKU's standard cost.
Wrapping up
Cosmetics manufacturing on Acumatica needs FEFO issue configured deliberately (not left at FIFO default), a documented approach to linking BOM revisions to regulatory filings since that link is not native, and a plan for keeping pilot-batch costs from distorting standard costs. All three are known, addressable gaps — none of them are reasons to avoid the platform, but all three surprise clients who assume "lot tracking" alone covers cosmetics compliance.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.