Every small job shop has a parts list that fits on one page — bushings, fasteners, fittings, the few SKUs that the floor pulls from every week. None of them are exotic. None of them are expensive. And yet one of them runs out every other month and the line goes down for forty minutes while the buyer drives across town.
That is not a vendor problem and it is not a buyer problem. It is an inventory reorder threshold problem. The threshold was set by gut feel years ago, and the buyer is the one paying for every time it was wrong. Automatic reorder thresholds for small job shops fix this by computing the reorder point from the data already on the floor — on-hand quantity, supplier lead time, and the buffer you actually need — so the same parts stop running out at the same cadence.
The three steps that replace "we ran out again"
Fortera's procurement pipeline already drafts the PO from the alert. The same loop, pointed at automatic reorder thresholds, becomes the line of defense between the buzzer and the outage.
The whole loop runs against the procurement pipeline shipped by Fortera — built around the small job shop's single buyer and single parts list. If you want to see what the drafted reorder looks like before you commit, the homepage has the interactive walkthrough, or check pricing.
What changes on the floor
A shop that stops losing forty minutes a month to "we ran out again" gets its line time back. The automatic reorder thresholds turn the parts list from a static spreadsheet into a live signal, and the same PO automation loop that drafts the purchase order already runs the rest. Anything else, talk to support.