Main Street Docs

Supply Order Template: Fields, Examples, and How to Use It

Updated November 7, 2026

Blank template:PDFWord

Supply Order Template: Fields, Examples, and How to Use It

A supply order template is a reusable form for requesting or purchasing goods, with fields for item details, quantities, prices, delivery information, and approval. Use the blank template below to record what is needed, make the request easy to review, and create a clear reference for receiving the order.

What a Supply Order Is For

A supply order documents a request to obtain materials or products. Depending on an organization’s process, it may be an internal requisition, an order sent to a supplier, or a record used to prepare a formal purchase order. These documents can look similar, but they do not always serve the same purpose: an internal request asks for authorization, while an order sent to a supplier communicates what is being purchased and on what terms.

Agree on what the form represents before using it. If your organization already requires a specific purchasing document or approval sequence, follow that process rather than treating a simple template as a substitute. A well-completed order helps the requester, approver, supplier, and receiving staff work from the same item descriptions and quantities.

Supply Order Template

Blank supply order form

Field Details
Order or request number
Date requested
Requester and department
Supplier and contact details
Delivery address and requested date
Item description or SKU
Unit of measure
Quantity
Unit price and currency
Line total
Shipping, taxes, or other charges
Order total
Approval name, date, and status
Notes or special instructions

Short sample — fictional details

Field Sample entry
Order or request number REQ-1042
Date requested November 7, 2026
Requester and department Jamie Lee, Facilities
Supplier Northfield Office Supply (fictional)
Delivery address and requested date Receiving desk; November 14, 2026
Item, unit, quantity Copy paper, ream, 12
Unit price and line total $5.00; $60.00
Shipping, taxes, other charges To be confirmed
Order total Pending final charges
Approval Pending

What to Include and Why

Each field reduces a different kind of ambiguity. Use consistent units and enough detail for someone unfamiliar with the request to identify the right product. A quantity of “10” is incomplete if the form does not say whether that means pieces, boxes, cases, or another unit.

  • Identification: Give the request or order a unique reference number and date. This makes it easier to discuss, file, and match with later documents.
  • People and destination: Identify the requester, department, supplier, delivery location, and a contact for questions.
  • Item information: Include a plain-language description and, where available, a supplier item number, size, model, color, or other distinguishing specification.
  • Quantity and price: State the unit of measure, quantity, currency, unit price, and line total. Show additional charges separately when known.
  • Timing and authorization: Record the requested delivery date and the approval status or approver required by your process.
  • Notes: Mention relevant delivery instructions, acceptable substitutions, or other constraints. Avoid vague notes such as “usual item” unless the reference is clear to everyone involved.

How to Complete and Process an Order

  1. Describe the need and check existing stock or internal purchasing rules before requesting more supplies.
  2. Enter a precise description, unit, quantity, and requested date. If an item has specifications, include them rather than relying only on a familiar name.
  3. Confirm the supplier and delivery details. Ask for a quote or current price if the amount is uncertain, and mark unknown charges as pending instead of guessing.
  4. Calculate each line total as quantity multiplied by unit price. Add shipping, taxes, or other applicable charges separately, and verify the arithmetic.
  5. Submit the request for the required review. Do not label a request “approved” or send it as a confirmed order unless the authorized process permits that step.
  6. After approval and ordering, retain the record and compare delivered goods with the item descriptions and quantities. Note shortages, damage, or substitutions for follow-up.

For example, an order for 12 reams at $5 each has a merchandise subtotal of $60 before any shipping or applicable taxes. The sample leaves those charges pending because they depend on the actual transaction; a reusable form should not imply that unknown costs are zero.

Choosing and Adapting the Form

A small team may need only a one-page request with a few item rows. A department ordering many products may need a line-item table with repeated rows and a separate section for approvals and delivery. Choose the simplest format that captures the information required by the people who will review, fulfill, and receive the order.

  • Add more item rows or attach a clearly referenced list for large orders.
  • Use an additional field for a project, location, or internal reference only if it helps route or track the request.
  • Include a requested substitute or “no substitutions” instruction where product differences matter.
  • Keep a consistent numbering method and date format so records can be found and compared.
  • Separate a requested delivery date from a supplier’s confirmed delivery date; they are not necessarily the same.

A spreadsheet can be useful when totals need to be calculated across many lines, while a printable page may suit occasional requests. Either way, the document should be readable, easy to review, and stored where authorized staff can retrieve it.

Common Mistakes and Misunderstandings

A supply order template is not automatically a purchase order, proof of approval, invoice, or receipt. Its role depends on how the organization uses it and whether the appropriate person has approved the purchase. Do not assume that filling in the form alone authorizes a supplier to ship goods.

Common errors include omitting units, using descriptions too broad to identify the product, confusing the requested date with a confirmed date, and entering a total without showing how it was calculated. Another frequent problem is mixing a budget estimate with a supplier’s confirmed price. Label estimates clearly and update the record when verified costs are available. If a transaction raises legal, tax, or financial-planning questions, ask a qualified professional.

Frequently Asked Questions

What is the difference between a supply order and a purchase order?
A supply order is a broad term for a document requesting or ordering goods. A purchase order is commonly a formal purchasing document sent to a supplier after the required approval, but terminology and workflows vary by organization.

Can I use this template for an internal request?
Yes. Use it as a request form by completing the requester, item, quantity, and delivery details, then adding the approval information your organization requires. Make clear that it is pending approval until authorized.

Should prices include tax and shipping?
Record the unit price and line totals separately from shipping, taxes, and other charges when possible. If a charge is unknown, mark it as pending or to be confirmed rather than inventing a figure.

What if the supplier changes an item or quantity?
Document the change and confirm it with the appropriate requester or approver before treating the revised order as accepted. Keep the original reference so the change can be understood later.

How should I number supply orders?
Use a consistent, unique sequence or another internal reference method. Avoid reusing numbers, and include the number on related communications or records when practical.

Keeping a Clear Order Record

Save the completed request, approval, supplier confirmation, and receiving notes together according to your organization’s recordkeeping process. A clear sequence—from request through delivery—helps resolve questions about what was ordered, what was authorized, and what arrived. Review the template occasionally as purchasing requirements change, but retain only fields that serve a real operational purpose.

Related