Airbase vs Procurify for Industrial Field Service Teams

If the part is already stocked on the truck, there's no purchase to authorize at all; the cost just needs to be logged against the work order. If it's a run to a local supply house, that's a card purchase with a preset limit, approved by the technician's own judgment because waiting for a sign-off would leave the customer's equipment down longer than necessary. If it has to come from the OEM on a lead time, that's a purchase order, because the cost and delivery date both need tracking against the job.

Most service organizations already sort calls into these three buckets informally, in the technician's head. The gap is usually that the purchasing process doesn't match that mental model, forcing every purchase through the same approval regardless of which bucket it belongs in.

Every part purchase, regardless of which of the three paths it took, needs to land against the specific work order it served. That's what lets you see whether a job was actually profitable once parts cost is accounted for, and it's the piece that's easiest to lose when a technician's card purchase doesn't get coded correctly in the moment.

A service manager who only reviews labor hours against a job, without the matching parts cost, is looking at half the picture. Margin on a repair call depends on both, and a supply-house run that never gets coded to the right work order quietly erodes that number without anyone noticing until the quarter's numbers come in low.

For OEM parts on backorder, a formal purchase order with a tracked delivery date does real work: it gives you a record to follow up on if the part is late, and it lets you commit the cost to the job before the invoice arrives, which matters when you're quoting the customer a completion date that depends on that part showing up.

The local supply-house run is exactly what a card with a set limit is for. Nobody benefits from a technician waiting on approval for a routine parts purchase while a customer's production line sits down, and a card gives you same-day visibility into what was spent without slowing the technician down in the field.

Set a dollar threshold below which a technician's card purchase needs no prior approval, and above which it routes to a service manager, regardless of whether the purchase is urgent. Pair that with a rule that any part ordered from the OEM, regardless of dollar amount, goes through a purchase order so the delivery date gets tracked. That combination covers all three purchase paths without slowing down the ones that genuinely can't wait.

Sort each part purchase with these rules:

• A part already stocked on the truck needs no authorization, only a log entry against the work order it served.
• Supply-house runs go on a card with a preset limit, so a technician isn't waiting on sign-off while a customer's equipment sits down.
• Purchases above the dollar threshold route to a service manager, whether or not they are urgent.
• Any part ordered from the OEM goes on a purchase order with a tracked delivery date, regardless of dollar amount.
• Code every purchase to its work order at the time it is made, not later from memory.

Parts cost against work orders is the kind of thing that's easy to review once a month and hard to fix once a month, because by the time a coding error shows up in a monthly report, a dozen more calls have made the same mistake. A weekly pass through recent card purchases and open purchase orders, checking that every line has a work order attached, catches the gap while it's still one technician's habit rather than the whole team's.

That weekly review doesn't need to be long. Ten minutes spent scanning the past week's card transactions for a missing work order number, and following up with the technician directly, fixes the habit far faster than a policy memo ever will.