Purchase Orders in Field Service Software: What Commercial Kitchen Service Companies Actually Need

A purchase order feature has 7 jobs, and the one that decides the rest is carrying cost onto the job it was created for. Products differ less on whether they have purchase orders than on whether the purchase order knows which work order it belongs to.

The short version

Almost every field service product will answer yes to "do you have purchase orders". The word covers everything from a printable form to a record that ties a supplier, a job, a cost and a bill together.

For a commercial kitchen service company the difference is not cosmetic. It decides whether you know what a job made:

• A purchase order created inside a job carries its cost to that job
• A purchase order created separately lands in a general expense account
• The second option leaves every parts-heavy repair looking profitable on labor alone

Roopairs put it in one line on their own site: parts is where you make your profit. If that is true, a purchase order that does not reach the job is not an administrative gap. It is the margin figure being wrong.

A homeowner job has no supplier in the middle

This is why the capability is uneven across the category rather than a matter of product maturity.

A residential service call is usually one visit, one technician, one invoice, with whatever the technician carried. Nobody orders anything from a third party, so no cost arrives three days later needing to find its way to a job that is already closed.

Commercial kitchen work has that gap on most parts-heavy repairs. Diagnose Tuesday, order Tuesday afternoon, part arrives Thursday, fitted Friday, supplier bills you the following week. Four things have to survive the gap: which job it belongs to, what you paid, what you are charging, and whether the customer approved it.

Products built for homeowners never had to solve that, which is a statement about what they were designed around rather than a criticism of them.

7 things a purchase order feature has to do

Use this as a demo checklist rather than a feature comparison. All seven are demonstrable in about ten minutes and the answers separate products fast.

#	Requirement	What breaks without it
1	Create a purchase order from inside a work order	Two records with no link, and somebody re-types the job reference
2	Cost lands on the job when the part is received	Job margin is labor only, and it looks better than it is
3	Receive into the service company, then issue to a van or a job	Parts are counted as consumed on arrival, so stock figures drift immediately
4	Partial receipts	A three-line order with two lines delivered has no correct state
5	Handle a part ordered and not used	Returns are ordinary in this trade and become manual corrections
6	Vendor record with purchase history	No view of what you buy from whom, at what price, with what lead time
7	Reach the accounting system as a bill, matched	Somebody types the supplier bill a second time and reconciles from memory

Requirements four and five are the ones that expose a purchase order feature added late. A product that models a purchase order as a document will handle the happy path and have no answer for a partial delivery or a return.

Roopairs describes its own version as creating customizable purchase orders for third-party vendors, keeping track of vendors and purchase history, attaching purchase orders to work orders, and tracking them in real time through the delivery lifecycle. That is the shape the seven above describe, and Ray has written about why purchase orders and inventory belong in the same place as the work order from the product side.

The purchase order belongs to the job, not to the month

If you test only one thing, test this.

Ask the vendor to create a purchase order for a part on a specific work order, receive it, and then show you that job's cost. The number should include the part at what you paid, without anyone allocating anything.

Where products fail, the failure is usually invisible in a demo unless you ask for the job cost afterwards. The purchase order gets created, the part arrives, everyone nods, and the cost sits in a purchasing ledger that nobody reconciles against jobs until quarter end, if ever.

The consequence at a service company with three or four technicians is not subtle. On a parts-heavy repair the part can be most of the job value. A margin built from labor and a flat parts markup assumption is a guess dressed as a report.

What "we have purchase orders" can mean

Four levels, and vendors at all four answer the question the same way.

1. A printable document. You fill in a form and email it. Nothing connects to anything.
2. A tracked record. The purchase order exists as an object with a status, but lives beside jobs rather than inside them.
3. Linked to the job. Created from the work order, cost lands on the job on receipt. This is the level most service companies need.
4. Closed loop. The supplier bill comes back, matches the purchase order, and reaches the accounting system without rekeying.

Level three is the threshold at which job costing becomes true. Level four is what removes a real job from somebody's month end. Knowing which level a product sits at is worth more than any feature list, and the only way to find out is to ask for the job cost after the receipt.

Two stages this page does not cover

Purchase orders are a chain, and two stages have enough in them to deserve their own treatment.

Who approves the spend. Once more than one person can commit money, you need a threshold and a route. That becomes urgent at roughly the same size as everything else in this trade, around three or four technicians, and it is a policy question before it is a software question.

The handoff to your books. The supplier bill arriving after the customer was invoiced, matched against the purchase order that caused it, is where parts spend either reconciles or leaks. That is the accounting end of the same chain.

Both are covered separately on this blog. This page is about the capability itself.

Where parts inventory fits alongside it

Purchase orders and inventory are one feature wearing two names. A purchase order that does not receive into an inventory location leaves you with a cost and no idea where the part is.

What to check together: whether receiving puts the part into the service company or straight onto the job, whether van stock is a location, and whether minimum and maximum thresholds exist so reordering is a signal rather than somebody noticing an empty shelf. Roopairs names minimum and maximum threshold alerts and the ability to search OEM and non-OEM parts across manufacturers, which is the reordering and identification half of the same system.

The parts sourcing decision sits on top, since availability, price and return terms differ between an original part and an equivalent. Roopairs covers where OEM and non-OEM each make sense in this trade.

The 10 minute version of this demo

Bring one real job. Ideally one where a part was ordered for one customer and fitted at another, because that job tests the whole chain.

Ask the vendor to do five things, in order: create a purchase order from inside the work order, receive the part, show the job cost, receive only part of a multi-line order, and then return a part that was not used.

Whatever happens at steps four and five is your answer. Every product handles the first three.

Roopairs runs a product tour where you can bring that job and follow it from the purchase order to the supplier bill.

What service companies in the trade say

“Since I have brought on Roopairs for my invoicing and scheduling needs it has saved me quit a bit of time doing paper work from using QB invoicing to theirs hands down a 100% improvement time and headache.” — Daryl Harris, Hot & Cold Commercial Kitchens (Atlanta)

Also worth reading

• Purchase Order Approval Workflows in Service
• Purchase Orders and Job Costing Are One Number
• Which field service management software do I choose

Frequently asked questions

What is a purchase order in field service software?

A record of what you ordered from a supplier for a specific job, at what cost, and its status through delivery. In a commercial service business it is the link between a part you bought and the work order it was bought for, which is what makes job costing accurate rather than estimated.

Do I need purchase orders if I only buy a few parts a month?

Probably not as a formal process, and you still need the cost to reach the job. Below a handful of ordered parts a month, a note and a habit works. The point at which it stops working is when more than one person is ordering, because that is when nobody can hold the picture.

Can I use QuickBooks for purchase orders instead?

You can, and the gap is the link to the job. Accounting systems know what a part cost and are poor at which work order consumed it. If purchase orders live in accounting and jobs live in field service software, somebody reconciles the two by hand, which is the manual step this capability exists to remove.

What is the difference between a purchase order and a work order?

A work order is the job you are doing for a customer. A purchase order is what you are buying from a supplier to complete it. They point in opposite directions, and on national account work you will also receive purchase orders from your customer, which is a third thing again.

How do purchase orders affect job costing?

They are what makes it real. Without the cost of ordered parts landing on the job, margin is calculated from labor and whatever markup assumption someone typed. On a repair where the part is most of the value, that produces a number that is confidently wrong.

What should I ask a vendor that a feature list will not answer?

Ask what happens when a three-line order arrives with two lines, and what happens when a part is ordered and not used. Both are ordinary in this trade and both are absent from products where purchase orders were added as a document rather than modeled as a process.