A contractor purchase order template should do more than tell a supplier what to send. It should also protect the project budget, make receiving easier, and give the office a clean record when the vendor bill arrives.
The best PO template is clear enough for vendors and structured enough for internal cost control.
Header information
Every purchase order should start with basic identification:
- Contractor company name
- Company phone and email
- Purchase order number
- PO date
- Vendor name
- Vendor contact
- Project or job name
- Ship-to address
The PO number matters because it becomes the reference point for vendor communication, receiving, and bill review. Contractors should use a consistent numbering pattern so POs are easy to find later.
Vendor and delivery details
Vendor information should include more than the company name. Add the sales rep or account contact when possible, along with the email address used for order acknowledgments.
Delivery details should include the jobsite address, expected delivery date, delivery instructions, and pickup notes if the order is will-call. This helps avoid the common problem of material going to the office when it belongs on the jobsite, or arriving when nobody is ready to receive it.
Project and cost coding
A contractor PO should identify the project or job the purchase belongs to. Without that link, the purchase can disappear into general overhead or get assigned during cleanup weeks later.
For companies that track job cost categories, the PO template should also support cost codes or internal categories. Even a simple material, subcontractor, rental, or equipment classification can make project review more useful.
Line item fields
Line items are the heart of the purchase order. Each row should include:
- Description
- Vendor SKU or part number, when available
- Quantity
- Unit
- Unit cost
- Line total
- Taxable status if needed
Descriptions should be specific enough for the vendor to fulfill the order without guessing. A vague line like “wire” may work in a conversation, but it is weak as a purchasing record.
Terms, tax, freight, and totals
The template should include payment terms, subtotal, tax, shipping or freight, and grand total. If the vendor has default terms, the PO can prefill them, but the final document should still show the terms clearly.
Shipping and freight deserve their own line or total field. If freight appears later on the bill but was not expected on the PO, the office should be able to spot that variance during review.
Notes for vendors and notes for the team
Contractors often need two kinds of notes.
Vendor notes should be visible on the PO. They might include delivery hours, gate codes, jobsite contact names, or substitution instructions.
Internal notes should stay with the team. They might include budget concerns, approval context, or reminders for the project manager. Mixing these notes can either confuse the vendor or expose internal context that was not meant to be shared.
Approval and receiving fields
If a contractor has multiple people ordering material, the template should support an approval workflow. That may be as simple as an approval status, approver name, and approval date.
Receiving fields are just as important. A useful PO record should track whether the order has been acknowledged, partially received, fully received, or cancelled. It should also allow packing slip numbers and notes for damaged or missing material.
Bill matching fields
A good PO template makes bill review easier by preserving the original commitment. When the vendor invoice arrives, the office should compare the bill against the PO and receiving record.
That does not mean every difference is wrong. It means the difference should be visible before the bill is paid.
Soft CTA
If you are comparing purchase order workflows as part of a broader software decision, review the tradeoffs in Conduit vs ServiceTitan.