Textile Printer — Production Tracking & Nesting Engine

In printed textile manufacturing, the expensive mistake is fabric. Designs are laid out on a roll before printing, and every square metre of gap between them is money burned. The plant was doing that layout in third-party software, by eye, and tracking production status on paper.

I built the tracking system and then the layout engine underneath it. Orders flow through defined production stages with barcode-driven labelling at each step, so a roll's status is a fact rather than a phone call. The nesting engine does the placement in-house: a search layer explores candidate arrangements instead of taking the first feasible one, and writes the result directly into the printer's own binary job format — which meant reverse-engineering that format, since no documentation for it exists.

The measurable outcome is 10–13% less fabric consumed on live orders. Alongside it sit the systems that make the plant legible: a costing and scrap-rate module, dated pricing, a native Android scanner app for the shop-floor terminals, and a customer-facing pipeline that pulls design archives straight from the client's own cloud storage into the catalogue.