Bulk gives each machine its own works order and route, with bought-in parts booked to it and supplier certs attached, and signs off every stage with the fitter, bay and time. FAT results and NCRs land on the same build, so the project engineer sees the machine and its open issues in one place. Order to invoice on the same record.
Bulk is engineer-to-order manufacturing software for machine builders and equipment makers: one live record per machine, bought-in parts with their certificates attached, factory acceptance tests and quality issues, with the order and the invoice on the same record. It is not CAD or PLM. It runs beside them and holds the build as it happens.
Every machine gets its own record and its own route, because no two builds are the same. Fitting, wiring, hydraulics and commissioning book the fitter, the stage and the time as they happen, so the project engineer sees where the build is and what it has cost without walking the bay.
Drives, gearboxes, castings and safety components are booked to the works order as they are used, with their cost, and the supplier certificate is attached as a file. Serial or heat references go in custom fields on the build, searchable in the grid, so when an assessor asks where a part came from the answer starts from the machine record.
FAT checklists are run as forms on the machine record, with each test, its reading and who witnessed it. A failed test raises a quality issue on the build, and putting the order on hold freezes its jobs until it is closed. The FAT sheet, the customer witness sheet and any open punch list sit on the build, ready for the SAT.
Drawings at the shipped revision, the risk assessment, supplier certificates and the FAT report attach to the build, and travellers and job sheets print from it in your layout. When you compile the technical file, the evidence is in one place. The commercial loop runs on the same record, so milestones are invoiced from the build stages rather than from a spreadsheet.
Castings and bought-in drives are booked to the works order as they are used, supplier cert attached.
See inventory
Each assembly stage records fitter, bay and inspection on the build as it goes together.
See production
FAT results and any NCR land on the build; the 8D closes against that machine's works order.
See quality
Drawings, the FAT report and supplier certs are already on the build; the invoice is raised from the same record.
See invoicing
Both, on one record. An MES is built for repeat lines and chokes on one-offs; an ERP holds the order and the invoice but never sees the build. Bulk runs the build record itself (production, quality and stage sign-offs on the assembly floor) and the commercial loop around it: the customer order, stock, invoices and credit notes. Install the apps you need one at a time; where you keep an accounts package, Bulk syncs both ways with it.
That's exactly what it's for. Each build gets its own live record and route rather than a fixed line sequence, so a bespoke special-purpose machine and a made-to-order standard model both track cleanly. Configure the route for the build; the build record follows whatever you actually did.
For anything built on Bulk, the build record is there the moment a warranty or field-failure query comes in: stages signed off, parts used with their cost, FAT results, quality issues and the attached drawings and certs. It is a record of the build, not a serial-by-serial parts tree; Bulk does not track the serial numbers of bought-in parts in stock, though you can hold them in custom fields on the build. For machines built before you moved onto Bulk, attach their records as files.
It holds the evidence; it does not write the file. Drawings, parts used, test reports, risk assessments and supplier certs live on the build record, so whoever compiles the technical file finds them in one place instead of pulling them together by hand each time. Bulk does not generate the technical file or the declaration; sign-off and conformity assessment stay your responsibility.
Bought-in drives, castings, motors and sub-assemblies are booked to the machine's works order as they are used, with their cost, and the supplier cert is attached to the works order as a file. Stock levels by item show what has arrived, so a late delivery is visible before the stage that needs it rather than on despatch day.
One per-site price with every module included — no per-module upsell, hosting and rollout in the figure. Rollout is never a big-bang cutover: we take one machine end to end first, prove the build record on a real build in weeks, then the rest of your builds follow the same pattern. You can start with a free trial, no card needed.
