Flex OS

The operation

The client is a flexible-packaging manufacturer — the rolls and pouches that food, FMCG and industrial products ship in. They run three plants across India and sell to more than 1,700 customers, buying raw material from hundreds of vendors.

Flexible-packaging converting is a sequence: procure the film and inks, extrude or receive the base material, print it, laminate it, slit it to size, and dispatch. A single customer order can move through several of those stages, across more than one plant, over days or weeks.

The problem

That sequence was being tracked in spreadsheets, registers and phone calls. Each plant had its own version of the truth. Procurement didn't have a live view of what the floor actually needed; the floor didn't have a live view of what procurement had committed; dispatch found out an order was ready when someone walked over and said so.

The cost of that isn't dramatic on any single day — it's a slow tax. Material ordered late or twice. A machine idle because the next job's film hadn't landed. A customer chased for a status nobody could answer without three calls.

What we built

Flex OS is one system that follows an order from raw-material procurement through the floor to dispatch:

• Procurement — purchase orders against real demand, vendor records, receipts logged against what was ordered.
• Floor logging — each production stage recorded as it happens, so a job's real state is always current, not reconstructed at end of day.
• Inventory — raw material and work-in-progress visible across all three plants, not siloed per site.
• Dispatch — what's ready, what's committed, what's gone out.

It was built with the operators — sitting on the floor, watching how the work actually runs rather than how a process document says it should — and rolled out plant by plant.

How it runs now

Flex OS is live in production across all three plants, with fifty-plus people using it daily — procurement, plant supervisors, floor staff, dispatch. CoreHQ hosts it, monitors it, backs it up and supports it. Changes and issues go through the client's portal.

It's not a product anyone can sign up for. It's one company's system, built for how that company works.

The stack

An independent web application — Node and Postgres — deployed on infrastructure CoreHQ controls. No shared platform, no dependency on CoreHQ's other work. If the client ever wants to bring it in-house, the buy-out clause hands over the running system and its source.