Five tools. Or one thread.
Most floors run five systems that don't talk — every hand-off a re-key, a copy, a chance to drift. Bulk runs the whole floor on one record.
What is Bulk One Data Thread?
Bulk's One Data Thread runs the whole floor on a single record instead of five systems that don't talk. One job — intake to invoice — is read and written back by every module: it only ever gains detail, and nobody types it twice. No re-keying, no copies drifting apart.
Pull the thread: JOB-8821.
One job, intake to invoice. Every module reads the same record and writes back to it — it only ever gains detail, and nobody types it twice.
Born from a PO
A customer PO lands as a PDF. Bulk reads it, matches the part and customer, and creates the order and the job. This is the only time anyone types it.
Compiled into steps
Routing rules compile against this exact job — six ordered steps and an automation — without re-stating a thing about the part or the order.
Run at the terminal
An operator loads the same job on CNC-204, runs the timer, counts good parts. Every action is an immutable transaction on the record.
A defect, owned
A scrap tap on the floor opens an issue tied to this job and asset — escalating to an NCR with its root cause, all hanging off the same record.
Billed from the truth
The invoice line is drawn straight from the finished job — quantity, part, price. The bill and the floor can never disagree.
Five tools, five frayed lines. Every hand-off is a re-key, every copy a chance to drift — and "which number is right?" becomes a meeting.
One thread doesn't fray.
Questions, answered.
What is Bulk One Data Thread?
It's the architecture that runs your floor on one record. A job is created once at intake and every module — routing, production, quality, invoicing — reads the same record and writes back to it, so nobody types it twice.
Do I have to replace my ERP to use it?
The idea is to end the relay race, where the same order is keyed into an ERP, a spreadsheet, a paper traveller and a whiteboard. Bulk keeps one live record the whole floor references instead of copying between systems.
How does one job stay consistent from intake to invoice?
A customer PO lands as a PDF, Bulk reads it and creates the order and the job — the only time anyone types it. Routing, production, quality and invoicing then all reference that same job, so it only ever gains detail.
Where does an invoice get its numbers?
The invoice line is drawn straight from the finished job — quantity, part and price. Because the bill comes from the same record the floor ran, the two can never disagree.
What happens to a defect found on the floor?
A scrap tap opens an issue tied to the job and the asset, escalating to an NCR with its root cause. The defect hangs off the job, so quality, the report and the invoice all see it.
Why is one record better than five systems?
Five tools mean five frayed lines: every hand-off a re-key, every copy a chance to drift, and "which number is right?" becomes a meeting. With one thread there is one number, and the board is the live system, never last night's export.
Intake to invoice, one thread.
We'll take one real order and walk it end-to-end on a single record — so you can watch the re-keying disappear.