---
title: "Introduction to aerospace ordering: quotes, purchase orders, and what a review looks like"
description: "PO vs quote checklist for aerospace and defense suppliers: what to compare on a customer purchase order before production, including revision, flow-downs, FAI, DPAS, and invoice matching."
url: "https://gndctl.com/insights-library/introduction-to-aerospace-ordering-quotes-purchase-orders-and-what-a-review-looks-like"
author: "GroundControl Editorial Team"
published: "2026-08-26"
updated: "2026-09-11"
insights_url: "https://gndctl.com/resources/introduction-to-aerospace-ordering-quotes-purchase-orders-and-what-a-review-looks-like"
category: "PO Review"
tags: ["Purchase Order","Contract Review","AS9100","Aerospace","Defense","PO Review","Supplier Quality","FAIR"]
---

# Introduction to aerospace ordering: quotes, purchase orders, and what a review looks like



> Full Markdown index: https://gndctl.com/llms.txt

> Human-readable version: https://gndctl.com/resources/introduction-to-aerospace-ordering-quotes-purchase-orders-and-what-a-review-looks-like



## Key takeaways

- A quote is the seller's offer. A PO is the buyer's authorization. Neither title by itself proves the documents match.
- Compare the PO to the specific quote revision the customer accepted: price, part identity, drawing revision, quantity, flow-downs, and terms.
- Confirm drawing revision, dash number, quality clauses, FAIR/cert deliverables, and special-process requirements before releasing production.
- Check delivery dates against capacity, and look for a DPAS rating that changes scheduling priority.
- Keep the chain together: quote, PO, written acknowledgment, FAIR/certs, and invoice with the correct PO number.

Before starting production on a purchase order (PO), it needs to be compared to the accepted quote for things like price, part number, dash number, drawing revision, quantity, quality flow-downs, FAIR and cert deliverables, delivery dates, DPAS rating, contract terms, and more. Matching total price at the bottom of the PO and quote documents is not enough as there are many other components that could be mismatched.

A purchase order is created by the buyer, and a quote document is typically created by the seller. When a customer emails a PO, most shops save the PDF, enter the job, and then send over material. That treats the PO as a copy of the quote. However, they're not always exact copies of each other. A PO and quote can have different dates, a different dash number, extra quality clauses, or something else.

A purchase order is not a filing document. It is the order you are being asked to accept. Under AS9100D, you must review requirements before committing to supply. Under the Uniform Commercial Code, beginning performance can constitute acceptance.

## Why purchase order review is different in aerospace and defense

:::html
<div class="form-section-wrap my-4 text-stone-600 leading-relaxed">
  <figure class="form-section-figure inline-figure--wrap-right">
    <div class="form-section-figure__inner">
      <img src="/images/insights/aerospace-po-review-fighter-jet.png" alt="Fighter jet climbing with afterburners against a blue sky" loading="lazy" />
    </div>
  </figure>
  <p>A promotional-goods distributor checking a PO is mostly protecting margin. An aerospace or defense supplier is also protecting configuration, airworthiness evidence, export-control posture, and on-time delivery scorecards.</p>
  <p>AS9100 requires a coordinated review before you commit to supply, including customer requirements, statutory and regulatory requirements, and any difference between the order and what was previously quoted. If the PO cannot be met as written, you should negotiate a mutually acceptable requirement before accepting it, while maintaining all records of the review.</p>
</div>
:::

## What is the difference between a quote and a purchase order?

The seller creates the quote document which describes what you are willing to supply, at what price, at which revision, and on which terms. The buyer creates the purchase order, which tells you what procurement has authorized for purchase.

Typically, the quote comes first and the PO follows internal approval. However, you should not treat the PO as a harmless copy of the quote. It may contain a different drawing revision, quantity, ship-to, quality manual, payment period, or set of standard terms.

:::html
<div class="overflow-x-auto my-6">
<table class="w-full text-sm border-collapse border border-stone-200">
<thead>
<tr class="bg-stone-50 text-left">
<th class="border border-stone-200 px-4 py-3 font-semibold text-stone-900"></th>
<th class="border border-stone-200 px-4 py-3 font-semibold text-stone-900">Quote</th>
<th class="border border-stone-200 px-4 py-3 font-semibold text-stone-900">Purchase order</th>
</tr>
</thead>
<tbody class="text-stone-700">
<tr>
<td class="border border-stone-200 px-4 py-3 font-medium text-stone-900 align-top">Created by</td>
<td class="border border-stone-200 px-4 py-3 align-top">Seller or contract manufacturer</td>
<td class="border border-stone-200 px-4 py-3 align-top">Buyer, prime, or procurement team</td>
</tr>
<tr>
<td class="border border-stone-200 px-4 py-3 font-medium text-stone-900 align-top">Main purpose</td>
<td class="border border-stone-200 px-4 py-3 align-top">Offer scope, configuration, price, and commercial terms</td>
<td class="border border-stone-200 px-4 py-3 align-top">Authorize and record a purchase against a budget and contract</td>
</tr>
<tr>
<td class="border border-stone-200 px-4 py-3 font-medium text-stone-900 align-top">Typical timing</td>
<td class="border border-stone-200 px-4 py-3 align-top">After RFQ, before the buyer decides</td>
<td class="border border-stone-200 px-4 py-3 align-top">After internal approval, usually before production starts</td>
</tr>
<tr>
<td class="border border-stone-200 px-4 py-3 font-medium text-stone-900 align-top">Main reference</td>
<td class="border border-stone-200 px-4 py-3 align-top">Quote number and revision</td>
<td class="border border-stone-200 px-4 py-3 align-top">PO number, line items, and often a prime contract number</td>
</tr>
<tr>
<td class="border border-stone-200 px-4 py-3 font-medium text-stone-900 align-top">What it should match</td>
<td class="border border-stone-200 px-4 py-3 align-top">The drawing, process, and lead time you can actually perform</td>
<td class="border border-stone-200 px-4 py-3 align-top">The accepted quote, plus any flow-downs the buyer is required to pass through</td>
</tr>
<tr>
<td class="border border-stone-200 px-4 py-3 font-medium text-stone-900 align-top">Invoice role</td>
<td class="border border-stone-200 px-4 py-3 align-top">Supports the agreed price and exclusions</td>
<td class="border border-stone-200 px-4 py-3 align-top">Usually appears on the invoice for matching and payment</td>
</tr>
</tbody>
</table>
</div>
:::

Always ask the buyer to reference the quote number and revision on the PO so you can compare the two documents before you start work.

## A typical aerospace quote-to-PO workflow

:::html
<div class="form-section-wrap my-4 text-stone-600 leading-relaxed">
  <figure class="form-section-figure inline-figure--wrap-right inline-figure--workflow">
    <div class="form-section-figure__inner">
      <img src="/images/insights/aerospace-po-review-workflow-documents.png" alt="Illustration of people organizing quote and purchase order documents in a folder" loading="lazy" />
    </div>
  </figure>
  <ol class="resources-workflow-list">
    <li>The buyer sends an RFQ with a part number, drawing, and quality requirements.</li>
    <li>The seller sends a quote document with configuration, exclusions, price, lead time, and terms.</li>
    <li>The buyer completes internal approval, often through a procurement or MRP system.</li>
    <li>The buyer issues a purchase order, sometimes weeks later and sometimes from an older quote revision.</li>
    <li>You compare the PO with the accepted quote, the drawing, and your capability to deliver, including FAIR and certs.</li>
    <li>You send a written acknowledgment, with exceptions if the documents conflict.</li>
    <li>Production, special processes, and first article inspection begin only after the starting conditions are met.</li>
    <li>You invoice against the PO number and line items the buyer requires for payment.</li>
  </ol>
</div>
:::

## Aerospace purchase order review checklist

:::html
<div class="overflow-x-auto my-6">
<table class="w-full text-sm border-collapse border border-stone-200">
<thead>
<tr class="bg-stone-50 text-left">
<th class="border border-stone-200 px-4 py-3 font-semibold text-stone-900">Check</th>
<th class="border border-stone-200 px-4 py-3 font-semibold text-stone-900 checklist-th-compare">What to compare</th>
<th class="border border-stone-200 px-4 py-3 font-semibold text-stone-900 checklist-th-mismatch">If it does not match</th>
</tr>
</thead>
<tbody class="text-stone-700">
<tr>
<td class="border border-stone-200 px-4 py-3 font-medium text-stone-900 align-top">Buyer entity and quote reference</td>
<td class="border border-stone-200 px-4 py-3 align-top">Legal name, bill-to, ship-to, CAGE, quote number and revision on the PO</td>
<td class="border border-stone-200 px-4 py-3 align-top">Confirm you are contracting with the right entity and the quote they actually accepted.</td>
</tr>
<tr>
<td class="border border-stone-200 px-4 py-3 font-medium text-stone-900 align-top">Price</td>
<td class="border border-stone-200 px-4 py-3 align-top">Unit price, NRE, tooling, FAI, certs, and total vs. the accepted quote</td>
<td class="border border-stone-200 px-4 py-3 align-top">Do not start work. Ask the buyer to reissue or confirm the delta in writing.</td>
</tr>
<tr>
<td class="border border-stone-200 px-4 py-3 font-medium text-stone-900 align-top">Part identity and revision</td>
<td class="border border-stone-200 px-4 py-3 align-top">Part number, dash number, nomenclature, drawing revision, model revision, PO revision</td>
<td class="border border-stone-200 px-4 py-3 align-top">Stop. Wrong revision is a configuration error and a common FAIR rejection.</td>
</tr>
<tr>
<td class="border border-stone-200 px-4 py-3 font-medium text-stone-900 align-top">Quality flow-downs</td>
<td class="border border-stone-200 px-4 py-3 align-top">Customer quality clauses, special processes, approved sources, packaging, FOD</td>
<td class="border border-stone-200 px-4 py-3 align-top">Confirm you can perform or subcontract each requirement before you accept.</td>
</tr>
<tr>
<td class="border border-stone-200 px-4 py-3 font-medium text-stone-900 align-top">Deliverables</td>
<td class="border border-stone-200 px-4 py-3 align-top">AS9102 FAIR, material certs, C of C, test reports, portal templates</td>
<td class="border border-stone-200 px-4 py-3 align-top">Price and schedule the paperwork. An unpaid FAIR is still a delivery obligation.</td>
</tr>
<tr>
<td class="border border-stone-200 px-4 py-3 font-medium text-stone-900 align-top">Delivery and DPAS</td>
<td class="border border-stone-200 px-4 py-3 align-top">Need date vs. quoted lead time; DX/DO rating and certification statement</td>
<td class="border border-stone-200 px-4 py-3 align-top">Flag an unachievable date now. Rated orders have a written accept/reject deadline.</td>
</tr>
<tr>
<td class="border border-stone-200 px-4 py-3 font-medium text-stone-900 align-top">Terms and penalties</td>
<td class="border border-stone-200 px-4 py-3 align-top">Payment terms, T&amp;Cs, LDs, chargebacks, termination, warranty</td>
<td class="border border-stone-200 px-4 py-3 align-top">Acknowledge subject to your quoted terms. Do not silently accept theirs.</td>
</tr>
<tr>
<td class="border border-stone-200 px-4 py-3 font-medium text-stone-900 align-top">PO revision delta</td>
<td class="border border-stone-200 px-4 py-3 align-top">What changed since the last PO revision you accepted</td>
<td class="border border-stone-200 px-4 py-3 align-top">Re-review only the changed lines, then update the job record before the floor uses the old PO.</td>
</tr>
</tbody>
</table>
</div>
:::

## What quality clauses and flow-down requirements are on the PO?

Aerospace POs rarely stop at "make this part." They incorporate customer quality manuals, supplemental specs, approved-processor lists, counterfeit-parts clauses, packaging and FOD requirements, and statutory flow-downs such as ITAR / EAR restrictions when covered defense information is in play.

- Read the quality notes and every document the PO incorporates by reference.
- Confirm you have the correct revision of each referenced spec.
- Confirm special processes (heat treat, plating, NDT, welding) can be performed by a customer-approved source.
- Confirm you can legally receive and store any technical data the order includes.

A clause you did not price, cannot perform, or cannot flow to your sub-tiers is not a paperwork issue. It is an acceptance decision.

## Is a purchase order acceptance of a quote?

It can be evidence of acceptance when it matches the quote but that is not a universal rule. A PO that introduces its own terms, a different revision, or extra deliverables may operate as the buyer's offer, or as a counter-offer, rather than as a clean acceptance of yours. Starting work or shipping hardware can have legal consequences even without a signature.

Use the same checks on every order:

- Make the quote number and revision visible on the quote you send.
- Ask the buyer to reference that version on the PO.
- Compare the documents before performance.
- Resolve conflicting terms in writing.
- Keep the final record together.

This article is practical commercial and quality guidance, not legal advice. Contract rules vary by jurisdiction and by whether the order is commercial, FAR-based, or a subcontract under a prime.

## What is the difference between a purchase order and an invoice?

A PO is not an invoice. The buyer uses the PO to authorize and track the purchase. You issue the invoice to request payment.

Primes and government paying offices match the invoice to the PO or contract. If the invoice does not carry the correct PO number, line item, or configuration, accounts payable can return it even when the hardware was conforming. Under FAR 32.905, a proper invoice on a federal contract must include the contract number or other authorization, including order number and line item number. Many OEM supplier portals apply the same matching logic to subcontracts: no valid PO number, no pay.

Check whether the buyer requires one invoice per PO, separate invoices per line, a supplier-portal submission, or evidence of delivery such as a packing list or FAIR package. Do not invent a PO number, reuse another job's number, or assume a program manager's email overrides purchasing.

## What a skipped PO review actually costs

A revision mismatch caught after production is rework, a rejected shipment, and a supplier-scorecard hit.

An undetected price gap is revenue that you cannot recover after delivery, a missed FAIR or cert requirement delays source inspection even when the part is good, and an unreviewed DPAS rating can put you in breach of a federal priorities rule.

The review takes minutes when it is a checklist. It takes weeks when it becomes a price discrepancy, a late shipment, and a commercial dispute. GroundControl's PO Review software runs that checklist against the actual documents, cites every finding back to the source clause, and drafts the discrepancy email so the buyer hears from you the same day.

## FAQ

### What is the difference between a quote and a purchase order?

The seller creates a quote to offer configuration, price, and terms. The buyer creates a purchase order to authorize and record a purchase. In a common aerospace workflow, the accepted quote comes first and the PO follows procurement approval. The PO still has to be checked against the quote before production starts.

### What should you check on an aerospace purchase order before starting production?

Compare the PO to your accepted quote for buyer entity, quote revision, price, part number, dash number, drawing revision, quantity, quality flow-downs, FAIR and certification deliverables, delivery date, DPAS rating, payment or penalty terms, and invoice instructions. Do not release production until mismatches are confirmed in writing.

### Do I need the PO number on my invoice?

Often yes. Many primes will not process payment without the PO number and line reference. On federal contracts, FAR 32.905 requires a proper invoice to include the contract number or other authorization, including order number and line item number.

### Does AS9100 require a contract review of every purchase order?

AS9100D requires the organization to review requirements before committing to supply products or services, including differences between the order and requirements previously expressed. For most job shops that review is the incoming customer PO against the quote, drawing, and capability to deliver.

### Should I accept a customer PO that conflicts with my quote?

No. Flag the conflict and ask the customer to reissue the PO or confirm the change in writing. Accepting the PO, or beginning performance, can bind you to the customer's document. Acknowledge the order only for the configuration, price, date, and terms you can actually meet.

### What is the difference between checking a PO against a quote and comparing PO revisions?

PO vs. quote catches conflicts between what you sold and what the customer ordered. PO revision comparison catches what changed since the last accepted PO: dates, quantities, revisions, added clauses, or dropped deliverables. Aerospace suppliers need both, because primes send revised POs as often as they send original ones.

<details>
<summary>Sources</summary>

- [SAE AS9100D, Quality Management Systems – Requirements for Aviation, Space, and Defense Organizations](https://www.sae.org/standards/content/as9100d/)
- [SAE AS9102C, Aerospace First Article Inspection Requirement](https://www.sae.org/standards/content/as9102c/)
- [15 CFR 700.12, Elements of a rated order (eCFR)](https://www.ecfr.gov/current/title-15/subtitle-B/chapter-VII/subchapter-A/part-700/section-700.12)
- [15 CFR 700.13, Acceptance and rejection of rated orders (eCFR)](https://www.ecfr.gov/current/title-15/subtitle-B/chapter-VII/subchapter-A/part-700/section-700.13)
- [BIS, Processing DPAS rated orders](https://www.bis.gov/about-bis/bis-leadership-and-offices/SIES/defense-priorities-allocations-system-program-dpas)
- [FAR 32.905, Payment documentation and process](https://www.acquisition.gov/far/32.905)
- [FAR 52.211-15, Defense Priority and Allocation Requirements](https://www.acquisition.gov/far/52.211-15)
- [UCC § 2-206, Offer and acceptance in formation of contract](https://www.law.cornell.edu/ucc/2/2-206)
- [UCC § 2-207, Additional terms in acceptance or confirmation](https://www.law.cornell.edu/ucc/2/2-207)
- [BIS, Deemed exports](https://www.bis.gov/deemed-exports)

</details>

---

Full site index: https://gndctl.com/llms.txt
