TermoHub
One scan on the floor, and the plant knows where the part is and which truck took it.
Shop-floor tracking of finished goods: scan at the station, build the shipment in the app, keep working with no network.
Who it is forPlants where finished goods pass through several stations and are then loaded onto trucks against route sheets.
Discuss a projectThe task
Finished goods moved between stations and left the plant on paper lists and word of mouth. The company's accounting system saw a shift's output late, and whether a part had actually passed its station — or ended up on the right truck — could only be reconstructed after the fact. A shop floor is also where mobile coverage dies, so anything we built had to keep working offline.
Solution
We built a worker's mobile app, a gate console and a manager's panel on top of our own Strapi and PostgreSQL server that syncs employees and barcodes with the plant's accounting system. Product scans and shipment operations go through an on-device queue: every operation carries a stable idempotency key, so a retry after the network returns is discarded server-side, and an operation the server refuses is shown to the person instead of being swallowed. Permissions follow responsibility rather than job titles — a trip can only be changed by someone assigned to the station it belongs to. Socket.IO carries live state, and notifications reach the phone as push.
Outcome
Paper loading sheets gave way to a shipment record in the app: containers, loose items, the vehicle and the route sheet sit in one entry with its full status history. A scan at the station answers immediately whether it was accepted, and a part that turns up at the wrong station is recorded as a conflict with a stated reason instead of an argument on the floor. The system reached a working prototype, deployed on a server and wired into the plant's accounting system.
Capabilities
- 01Barcode scanning of finished goods at a station, answered by the plant's accounting system: the scan is either accepted or comes back with the reason it was refused.
- 02Shipment trips with containers and loose items, an assigned vehicle and route sheet, a pre-flight check before the truck leaves, and a controlled way to reopen a trip already in transit.
- 03An offline queue with idempotency keys: scans made outside coverage survive, and the server drops duplicates when the device retries.
- 04Versioned routing rules per construction: the system knows which station a part is due at next and records a mismatch as a conflict with a reason category.
- 05Station access by request and approval; shipment operations are allowed only to workers assigned to that trip's station.
- 06Entry and exit logging at the gate — via the guard's console or a QR code scanned off a tablet at the door — plus live notifications over a socket and push to the phone.
Roles
- Station worker
- Station supervisor
- Gate security officer
- Production manager
Industry
polymer products manufacturingScreens
A similar task at your company?
This system was built around one client's process. Describe yours and we will tell you what carries over from what you see here and what has to be built anew.