AromaERP
A self-hosted ERP for a perfume manufacturer. It runs on their own Windows server and serves every device on the office network, with no internet connection needed.
- Sector
- Perfume manufacturing
- Status
- In development
- Runs on
- Client's own server
- Internet
- Not required
01The problem
Formulas, batch records and billing were kept in separate files, and the owner wanted production data to stay inside the building, off the internet.
- 01
Formulas in files
Formula versions were copied between sheets, so the batch floor could work from an old version without anyone noticing.
- 02
Lots used out of order
Material was picked by whatever was nearest, not by expiry, so older lots aged on the shelf.
- 03
Billing retyped
GST invoices were typed up again from batch records, which is slow and where errors creep in.
02What we built
Formula to invoice, on their own network.
The formula drives the batch, the batch drives the lot pick, and the released batch drafts its own GST invoice.
Every product has a formula with ingredient costs. Editing it creates a new version, so past batches keep the one they were made with.
Each order shows its product, batch, supervisor, material cost and status, from planned to completed.
Finished batches cannot be sold until approved here. Rejected materials are quarantined and kept out of production.
Stock by lot and rack, with expiry dates and expired lots flagged before they are used.
03How it works
One chain, no retyping.
Formula
Versioned, with every component and its share.
Batch
Planned from one formula version and a size.
Lot pick
Lots suggested in expiry order and scanned.
Quality
Tested, then released or held for retest.
Invoice
GST invoice drafted from the released batch.
04From the client
05Scope
- Modules
- Formulas, batches, FEFO lots, quality control, barcodes, GST billing
- Runs on
- The client's Windows server, reached from every device on the office network
- Internet
- Not required to run
- Status
- In development