Tulips Manufacturing Execution System

The Tulips platform was built as a customization layer on ERPNext, the open source ERP from Frappe. The base system provided the records and permissions model, and the engagement added the order, manufacturing, and delivery handling the business runs on.

Order tracking replaced the paper trail. Each order is recorded once and carries its own status through the pipeline, so the state of an order is read from the system rather than reconstructed from files and phone calls.

Manufacturing execution was modeled against how the floor already works, with production stages recorded as work moves through them. Each stage entry attaches to the order it belongs to.

Exceptions sit in the same place as the work. A delay or a rejected batch is logged against the stage where it occurred, instead of being handled outside the record and lost.

Delivery tracking closed the loop between production and dispatch. Completed output is recorded against the order it fulfills, and dispatch status stays on the same record the floor and the office both work from.

Because the delivery step shares the order history, what was ordered, what was produced, and what shipped can be compared without a separate reconciliation.

Management gained a view across the company. Orders, production stages, and deliveries report into one portal, so the picture of what is happening does not depend on who is asked.

Recording every movement also made the pipeline accountable. Discrepancies and losses the paper process had absorbed without a trace now surface against a specific order, stage, and entry, which is what makes inefficiencies in the flow possible to find and act on.

The same approach applies to any manufacturer whose orders, production stages, and deliveries are tracked in separate books, whether the work starts from ERPNext or from another base system.