Standards · DFARS 252.211-7003

DFARS 252.211-7003 (IUID): A Supplier’s Guide.

The clause that turns IUID marking from optional into contractual. What it requires, what gets marked, what gets registered, how it connects to DD-250 acceptance, what flows down to subcontractors, and the failures that most often hold a delivery at the dock.

What the clause is

DFARS 252.211-7003 — titled Item Unique Identification and Valuation — is the Defense Federal Acquisition Regulation Supplement clause that obligates contractors to apply IUID marking and to submit per-item data to the DoD IUID Registry. The clause is descended from a 2003 DoD policy (Under Secretary of Defense memo, “Policy for Unique Identification of Tangible Items”) that created the IUID program as the DoD’s system of record for serially-managed tangible property.

DFARS 252.211-7003 is the contractual vehicle that enforces that policy on suppliers. It is paired with DFARS 211.274 in the prescription clauses, which tell contracting officers when to insert the clause. Once inserted, the clause obligates the contractor to: identify which items must be marked, mark them per MIL-STD-130N, register a UII record for each, and report the item’s acquisition cost. The marking and the registry submission are inseparable obligations — marking without registry submission is non-compliant; registry submission without an actual mark on the item is fraud.

Which items get marked: the five triggers

DFARS 252.211-7003 enumerates the categories of items that must be IUID-marked. Any item falling into any one of these five categories must be marked — they are not cumulative, and meeting one trigger is sufficient.

  1. Items with an acquisition cost of $5,000 or more. Acquisition cost is the unit cost of the individual item, not the line-item total or the contract value. A contract for one $5,000 item triggers marking; a contract for 1,000 items at $7 each does not (on this trigger alone — other triggers may still apply).
  2. Items identified as serially managed. The program office or contracting officer designates items the DoD intends to track by serial number across their life cycle.
  3. Items identified as mission essential. Items the program office has designated as essential to the operational mission and therefore subject to tighter tracking.
  4. Items designated as controlled inventory. Items requiring custody tracking for accountability, security, or regulatory reasons.
  5. Items the contracting officer specifically identifies. A catch-all for items the program office wants marked outside the standard categories. Typically the SOW or a technical exhibit lists these by part number.

A practitioner reading a new contract should locate the DFARS clause in the contract terms, then locate any item-specific marking call-outs in the SOW, drawings, or technical exhibits. The two together define the universe of items that must be marked.

The IUID Registry submission

For each item marked under DFARS 252.211-7003, the contractor submits a record to the DoD IUID Registry. The Registry is accessed today through the Procurement Integrated Enterprise Environment (PIEE), which consolidates the older standalone IUID Registry interface with related DoD systems (Wide Area Workflow, EDI, etc.). The submission record includes:

  • The UII itself — the canonical encoded identifier
  • The enterprise identifier and the issuing-agency code, if used
  • Part number and serial number as separate fields, mirroring the UII construct
  • Marking method — how the symbol was applied (label, DPM, etc.)
  • Acquisition cost — the valuation half of “Item Unique Identification and Valuation”
  • Contract and delivery information — tying the item to the procurement

Registry submission is usually aligned to the DD-250 delivery acceptance. The receiving inspector verifies the items physically, confirms the UIIs match the registered records, and the DD-250 is signed off. Items that were marked but not registered — or registered but not marked — will hold the DD-250 until reconciled.

Flowdown to subcontractors

DFARS 252.211-7003 contains a flowdown provision: the prime contractor must include the substance of the clause in subcontracts at any tier where the subcontractor will deliver items that meet the marking triggers. For an IUID labeling shop operating as a sub-tier supplier, this is the mechanism by which the prime’s contractual obligations attach to the sub.

In practice the prime should:

  • Flow the clause down explicitly in the subcontract or purchase order, not by reference alone.
  • Specify who performs the IUID Registry submission. If the sub is producing the label and physically applying it to the item, the sub may also be the party submitting to the Registry — but only if the sub has the prime’s authorization and access. More commonly the prime submits the Registry record using data the sub provides.
  • Define the verification record the sub will produce. The DD-250 inspector needs documentation of the ISO/IEC 15415 grade per symbol or per lot; the sub should know the format the prime needs.
  • Coordinate the timing so that registry submissions, physical delivery, and DD-250 acceptance line up.

See IUID labels for prime contractor sub-sourcing for the sub-tier supplier’s side of this arrangement.

DD-250 acceptance and the IUID hold

DD Form 250 (Material Inspection and Receiving Report) is the document by which the government accepts a delivery. For contracts subject to DFARS 252.211-7003, the DD-250 cannot be signed off until the receiving inspector has verified:

  • That the items are physically marked with a symbol meeting MIL-STD-130N
  • That the symbol encodes the UII registered in the IUID Registry
  • That the registered record matches the part number, serial number, and acquisition cost expected for the line item

A mismatch between the symbol and the registry, an unreadable symbol, a missing verification record, or a registry submission that has not yet propagated through PIEE will hold the DD-250. The supplier becomes responsible for resolving the discrepancy — typically by re-submitting to the registry, providing the verification record, or in the worst case re-marking items in the field.

Most IUID holds at DD-250 are resolvable in days when the supplier has the marking and registry data in hand. The holds that turn into weeks are the ones where the supplier has to re-create marking records from memory or chase verification reports across multiple production lots.

Common supplier failures

  1. Missing the marking trigger entirely. The supplier reads the contract and sees DFARS 252.211-7003 but does not identify which line items meet the marking triggers. The delivery arrives unmarked.
  2. Marking the item but not registering it. The label is on the item; the UII never made it into the IUID Registry. DD-250 holds until the Registry record exists.
  3. Registry record does not match the physical symbol. A typo in the registry submission, or the symbol was re-printed and the registry was not updated.
  4. Verification record absent or unacceptable. The inspector wants documented ISO/IEC 15415 grades; the supplier has only a “we read it back, looks good” statement.
  5. Acquisition cost mismatched. The valuation reported to the Registry does not match the contract line-item price or the delivery invoice.
  6. Subcontracted marking with no flowdown. The prime relied on a sub for IUID marking but did not flow the clause, did not agree on who registers, and did not receive a verification record. The prime is non-compliant with the government and has no contractual leverage with the sub.
  7. Class 0 substrate where Class 1 was required. A MIL-STD-130N non-compliance that surfaces through the DFARS gate at DD-250. See MIL-STD-130N: Class 1 vs Class 0.

How Front Range Marking supports DFARS 252.211-7003

Front Range Marking operates as a sub-tier IUID label supplier for primes whose contracts invoke DFARS 252.211-7003. FRM produces the physical Class 1 marks per MIL-STD-130N, reads every symbol back at the press, and delivers a verification record that the prime’s receiving inspector can put in front of a DD-250 reviewer.

FRM does not, by default, submit to the IUID Registry on the prime’s behalf — the Registry submission is part of the prime’s contractual relationship with the government and is best done by the party that holds the contract. FRM provides the data the prime needs to make the submission: UII encoded, marking method, substrate, verification grade, lot identification.

For primes who have won a contract and just discovered DFARS 252.211-7003 is in it: FRM’s typical quote turnaround is one business day, with production lead time measured in days from PO for stock substrate. Single-principal accountability, no minimum order quantity, no third-party form vendor in the workflow.

Frequently asked questions

What does DFARS 252.211-7003 require?

Marking of items meeting any of five triggers per MIL-STD-130N, submission of a UII record to the IUID Registry for each marked item, and reporting of the item’s acquisition cost (valuation).

Is the $5,000 threshold unit cost or contract total?

Unit cost of the individual item. The contract’s total value is irrelevant to this trigger; only the per-item acquisition cost.

How does the IUID Registry submission happen?

Through the Procurement Integrated Enterprise Environment (PIEE), which is the DoD’s consolidated portal that includes the IUID Registry. The contractor submits the UII, enterprise identifier, marking method, acquisition cost, and contract information for each item.

Does the clause flow down to subcontractors?

Yes. The prime must include the substance of DFARS 252.211-7003 in subcontracts at any tier delivering items meeting the marking triggers.

What is the connection to DD-250?

DD-250 is the delivery-acceptance form. It cannot be signed off until the IUID-marked items have been registered, the registered UIIs match the physical symbols, and the verification record is on file. Missing or mismatched IUID data is a routine cause of DD-250 hold.

Can a sub-tier labeling shop submit to the Registry on the prime’s behalf?

Technically yes if the prime authorizes Registry access for the sub, but in practice the prime submits the Registry record because the submission is part of the prime’s contractual obligation to the government. The sub provides the marking data.

What happens if items arrive without IUID marks?

DD-250 hold. The supplier is responsible for remediation — field marking, return-to-shop, or interim corrective action with a permanent-marking schedule. Repeated failures can escalate to a corrective-action request or a Cure Notice.

What is the relationship between DFARS 252.211-7003 and MIL-STD-130N?

DFARS 252.211-7003 says “mark these items”; MIL-STD-130N says “here is how to mark them.” The DFARS clause is the procurement instrument that invokes the MIL-STD-130N marking standard.

Standards MIL-STD-130N The marking standard DFARS 252.211-7003 invokes. Class 1 vs Class 0, methods, and verification. Standards IUID Marking Guide UII constructs, the IUID Registry, and the item-life-cycle view of IUID data. Sub-Sourcing For Prime Contractors Sub-tier IUID label sourcing when DFARS 252.211-7003 lands in a contract you didn’t price for.

Contact

Request a Quote or Capability Statement

Joshua Hickman, Principal · Longmont, Colorado · Quote in one business day

Your contact

Request details

Submissions route to Joshua directly — no third-party form vendor. For Controlled Unclassified Information (CUI), don’t use the form; note the CUI scope in a short message and we’ll coordinate an out-of-band channel. See the privacy notice for details.

Prefer email? joshua@frontrangemarking.com