FAR 2.101 Definitions and Thresholds Guide Sep 2026

FAR 2.101 sits at the front of the Federal Acquisition Regulation for a reason: every threshold, every procedural branch, and every clause obligation downstream depends on the definitions it anchors. Where many pursuit teams get tripped up is treating these as background knowledge instead of working references. The distinction between "offeror" and "contractor," the micro-purchase and simplified acquisition thresholds, and the commercial product versus commercial service split all have real consequences for how a proposal is structured and scored.

TLDR:

• FAR 2.101 serves as the FAR's master dictionary; terms defined there carry uniform meaning across 48 CFR Chapter 1 unless a specific part overrides them.
• Misreading "offeror" vs. "contractor" in pre-award sections can create ambiguity around pricing and liability that evaluators often flag.
• The micro-purchase threshold rose to $15,000 (effective Oct 1, 2025); the SAT rose to $350,000 (effective Oct 1, 2025), where full competition requirements and small business set-aside analysis kick in.
• Whether a solicitation runs under FAR Part 12 or Part 15 changes clause flow-down, certifications, and cost or pricing data requirements; identify the applicable part before building the compliance matrix.
• GovEagle's compliance matrix generation parses Sections C, L, and M to surface threshold-sensitive and commercial-item-dependent obligations before drafting begins.

What is FAR 2.101?

FAR 2.101 is the definitions clause sitting at the front of the Federal Acquisition Regulation, serving as the FAR's master dictionary. As acquisition.gov states, a word or term defined in this section carries the same meaning throughout 48 CFR Chapter 1 unless the context clearly requires otherwise or another FAR part provides a different definition for a specific portion.

That structure carries real practical weight. When an RFP clause references "commercial product" or "micro-purchase," the contracting officer and the contractor are reading from the same definitional baseline. Where a term is defined differently in another FAR part, FAR 2.101 includes a cross-reference, and that part's definition governs within its own scope, so the section also functions as a routing mechanism, directing readers to the right definition depending on context.

For proposal teams, misreading a single term can mean pricing against the wrong threshold or missing an eligibility requirement entirely. That kind of terminology failure often surfaces late, at Red Team or in a post-award debrief, when correcting it is costly. FAR 2.101 is where that risk originates, which is why requirement-traceability workflows that anchor to precise regulatory language tend to catch compliance gaps earlier in the pursuit cycle.

FAR 2.101 Core Acquisition Terms

The definitions in FAR 2.101 draw distinctions that look minor on the surface but carry real weight in how proposals are structured and scored.

As FAR 2.101 defines it, "acquisition" begins the moment an agency identifies a need and runs through contract closeout, extending beyond the award event. That scope matters when reading solicitation language that assigns obligations at specific points in the process. "Contract" covers any mutually binding agreement using appropriated funds, while "offer" is a solicitation response that becomes binding upon government acceptance.

Where many proposal teams get tripped up is the distinction between "offeror" and "contractor." An offeror has submitted a proposal; a contractor has executed an agreement. Using "contractor" in pre-award sections can create ambiguity around pricing and liability that evaluators flag.

FAR 2.101 Acquisition Thresholds

Acquisition thresholds in FAR 2.101 are where procurement procedures branch. Get the threshold wrong and you may price against the wrong competition framework or expect a formal solicitation that will never arrive.

Micro-Purchase Threshold

FAR 2.101 defines the micro-purchase threshold as the ceiling below which agencies can buy without soliciting competitive quotes and without applying most FAR clauses. FAC 2025-06 raised the micro-purchase threshold for most acquisitions. Below that ceiling, agencies buy directly, which means no formal solicitation reaches a contractor's inbox. For proposal teams, this boundary marks where their work begins.

Simplified Acquisition Threshold

The simplified acquisition threshold (SAT), currently $350,000 for most acquisitions, separates simplified acquisition procedures from the full competitive requirements under FAR Parts 14 and 15. Below the SAT, contracting officers can use purchase orders or blanket purchase agreements with reduced clause burdens. Above it, full and open competition typically applies, triggering the formal RFP and proposal process.

FAR 2.101 Commercial Product and Service Definitions

The commercial product and commercial service definitions in FAR 2.101 carry outsized consequences for how an acquisition is structured. In 2021, the FAR Council revised terminology to split the prior "commercial item" definition into two distinct terms, aligning FAR language with 41 U.S.C. 103 and 103a.

What Qualifies as a Commercial Product

Under FAR 2.101, a commercial product is one customarily used by the general public and sold competitively in the marketplace, including items with minor modifications. When a contracting officer makes a commercial item determination, the acquisition typically moves to FAR Part 12 expedited procedures, reducing cost accounting requirements and audit exposure. For proposal teams, this affects both pricing strategy and which certifications must accompany the submission.

Commercial Services and the Contractor's Stake

A commercial service under FAR 2.101 is one sold competitively in the commercial marketplace at published catalog or market prices for specific tasks. IT, consulting, and staffing firms should identify during the initial RFP shred whether the solicitation invokes Part 12 or Part 15 procedures. Note that the Defense Federal Acquisition Regulation Supplement may impose additional clause obligations beyond the base FAR framework. The evaluation criteria structure and clause burden differ substantially between the two. Note that FAR Part 15 solicitation structures are subject to ongoing rulemaking under EO 14275 and may change. Proposal teams managing both FAR and DFARS obligations should consult the FAR and DFARS guide for proposal teams for a fuller treatment of how these frameworks interact.

Catching this distinction before the compliance matrix is built prevents downstream rework when the wrong clause set gets drafted into a volume.

Why FAR 2.101 Matters in Federal Contracting

FAR 2.101 definitions carry practical weight at every stage of the pursuit cycle. Terms like "offer," "acquisition," and "commercial product" have FAR-specific meanings that diverge from commercial usage, and misreading them at the RFP shred stage produces compliance gaps that surface at Red Team when the cost of correction is highest.

A few areas where definition precision matters most:

• Acquisition thresholds govern which procedures apply. The micro-purchase threshold ($15,000) and the simplified acquisition threshold ($350,000) determine competition requirements, clause applicability, and solicitation type. BD teams should map each opportunity against these thresholds during bid/no-bid analysis, not after pursuit is underway.

Proposal automation tools built for federal work parse Sections C, Section L, and M, where FAR-defined terms appear most densely, to extract threshold-sensitive and commercial-item-dependent clause obligations line by line. GovEagle's compliance matrix generation does exactly that, surfacing these obligations before drafting begins and not waiting until a color team flags them. The GovEagle proposals solution integrates this workflow end-to-end, from RFP shred through final submission.

Final Thoughts on Applying FAR 2.101 Across the Proposal Lifecycle

FAR 2.101 is where your compliance exposure either gets managed or gets deferred. Thresholds determine which procedures apply, commercial product determinations shape the clause set, and terminology consistency across pre- and post-award sections affects how evaluators read your submission. Anchoring your RFP shred workflow to precise FAR language is how those risks get caught before they cost color team cycles. GovEagle's compliance matrix generation parses Sections C, L, and M line by line to surface threshold-sensitive and commercial-item-dependent obligations before drafting begins, not after a color team flags them. Proposal teams that want to see that workflow in action can request a demo.

FAQ

What is the difference between "offeror" and "contractor" under FAR 2.101?

An offeror is an entity that has submitted a proposal but has not yet been awarded a contract; a contractor is the party to an executed agreement. Using "contractor" in pre-award proposal sections can create ambiguity around pricing and liability that evaluators flag during review.

What are the FAR 2.101 acquisition thresholds proposal teams need to know?

FAR 2.101 defines two thresholds that govern which procurement procedures apply: the micro-purchase threshold ($15,000 effective October 1, 2025), below which agencies buy without competitive solicitation, and the simplified acquisition threshold ($350,000), above which full and open competition typically applies under FAR Parts 14 and 15. BD teams should map each opportunity against these thresholds during bid/no-bid analysis, before pursuit is already underway.

How do I know whether an RFP will run under FAR Part 12 or FAR Part 15 procedures?

The determination turns on whether the contracting officer makes a commercial product or commercial service determination under FAR 2.101. If the offering is sold competitively in the commercial marketplace at published prices, Part 12 expedited procedures typically apply; otherwise, Part 15 governs. Catching this distinction before the compliance matrix is built matters because the evaluation criteria structure, clause burden, and cost or pricing data requirements differ substantially between the two parts. Note that FAR Part 15 solicitation structures are subject to ongoing rulemaking under EO 14275 and may change.

FAR 2.101 definitions RFP shred: when do terminology errors actually surface in a federal proposal?

Terminology gaps introduced during the initial RFP shred most often surface at Red Team, when correcting them is costly: wrong thresholds get priced against, eligibility requirements get missed, and clause sets get drafted for the wrong acquisition type. GovEagle's compliance matrix generation parses Sections C, L, and M line by line to surface these threshold-sensitive and commercial-item-dependent obligations before drafting begins, not after a color team flags them.

Should I treat the FAR 2.101 definition of "acquisition" as covering just the award event or the full contract lifecycle?

FAR 2.101 defines acquisition as beginning the moment an agency identifies a need and running through contract closeout, extending beyond the award event. That scope matters when reading solicitation language that assigns obligations at specific points in the process, and it shapes how proposal teams interpret clause applicability and performance requirements tied to particular lifecycle stages.