ORGANICS ERP

Organics’ cosmetics manufacturing runs through sales, R&D, packaging design, purchasing, planning, plant, warehouse, QA, QC and finance, and each hand-off between them — a brief becoming a formula, a formula becoming a bill of materials, a material shortfall becoming a purchase — has to reach the next team intact and stay traceable afterwards. ORGANICS ERP is also the company’s system for IPO readiness: as it prepares to list on the stock exchange, every transaction has to show who created it, who approved it and the evidence behind it. The build had to put every department on one shared record behind a single sign-in, with each person seeing only the work their role and department allow. It also had to follow the documents the office already files, so the system fits the way the factory works rather than the other way round.

We designed the ERP around workflows rather than department silos: every console is its own app, but they all read and write the same records through shared services, so one department’s output becomes the next department’s input without re-keying.

1. 1. Consoles over shared services

   A pnpm and Turborepo monorepo holds a Next.js 16 console per department, each in Thai and English via next-intl, over NestJS services for master data, procurement, inventory and finance on Prisma and MongoDB, deployed on DigitalOcean App Platform.

2. 2. One sign-on, three layers of permission

   An auth centre signs users into every console at once. Access combines role, department and one of six tiers, with attributes such as approval limits, and the services decide authorization from the verified token, never from caller-supplied headers.

3. 3. An audit trail by default

   An audit interceptor records every create, update and delete with the actor and the old and new values. Documents carry running numbers that restart each year, and purchase orders and goods-received notes print on the forms the office actually files.

4. 4. The manufacturing chain as one flow

   A new-product (NPD) project versions the brief, the R&D formula and the packaging BOM, then hands them on as a production request. Planning adds the loss allowance, a shortfall raises a purchase request straight from the plan, and the floor cannot start a batch until every material line has been issued.

5. 5. Controls inside the workflow

   Goods receipts pass QC with lot tracking, quarantine labels and FEFO. QC testing and QA release are separate roles, and finance documents go through a segregation-of-duties guard, so the person who creates one cannot also approve or post it.

ORGANICS ERP is live in production for 500+ users. User acceptance testing runs alongside it, and fixes are promoted to production as they pass.

• Every department, one system

  Each team works in its own console behind one sign-in, seeing the work its role and department allow.

• Traceable from brief to stock

  A product’s brief, formula, BOM, production request, purchases, receipts and QC results stay linked, so any step can be traced back.

• Approvals that hold up

  Self-approval is refused by design, and every change is logged with who made it and what it changed.

• Production on materials in hand

  Shortfalls turn into purchase requests from the plan, and production starts only once every material line has been issued.