Do I need MIL-STD-129 or MIL-STD-130 for my defense contract?

Usually both, applied to different things. MIL-STD-129 governs how the unit pack, intermediate pack, and shipping container are marked so DoD logistics can receive, store, and route them. MIL-STD-130 governs marking the deliverable item itself with its identifying data — and, when the contract invokes IUID (DFARS 252.211-7003, typically for items over the $5,000 threshold, serially managed, or mission essential), a machine-readable Data Matrix carrying the Unique Item Identifier. Read the contract’s marking clauses; the box and the item are separate obligations.

What goes on a MIL-STD-129 shipping label?

Identification markings built around the National Stock Number (NSN), CAGE code, part number, quantity, contract or purchase order number, plus address markings for the ship-to activity — with linear barcodes for key fields and, for many shipments, a passive RFID tag at the case and pallet level per contract clauses. Serial-tracked items add serial number markings.

How permanent does a MIL-STD-130 mark have to be?

The mark must remain legible and machine-readable for the life of the item — through its maintenance, refinishing, and environmental exposure. That is why IUID marks on hardware are often direct part marks (laser, dot peen), while label-based marks use materials in the polyimide and metallized polyester class with verified Data Matrix grading. A shipping label’s job ends at receipt; an item mark’s job ends at demilitarization.

Home GuidesMIL-STD-129 vs. MIL-STD-130

Defense Contract Marking

MIL-STD-129 vs. MIL-STD-130: The Box and the Item Are Different Jobs

New defense suppliers mix these up on their first contract and get the rejection letter to prove it. The rule of thumb that never fails: 129 is for the logistics system, 130 is for the item's whole life. One label comes off with the packaging; the other must scan at a depot twenty years from now. Everything else — data content, barcode symbology, material choice — follows from that split.

Military-specification identification marking on defense hardware — the permanence class MIL-STD-130 requires

Figure 1: Item-level defense marking — built to outlive every package it will ever ship in.MIL-STD-130 permanence class

1. Side by Side

Parameter	MIL-STD-129 (Package Marking)	MIL-STD-130 (Item Marking / IUID)
What gets marked	The package: unit pack, intermediate container, shipping container, pallet	The item itself — the deliverable hardware
Purpose	Logistics: receive, store, issue, route	Item identity: traceability and asset accountability for the item’s life
Core data	NSN, CAGE, part number, quantity, contract number, ship-to	CAGE/enterprise ID, part number, serial number — concatenated into the UII when IUID applies
Machine-readable form	Linear barcodes (Code 39 / Code 128 usage), RFID at case & pallet per contract	Data Matrix ECC 200, verified to quality standards (ISO/IEC 15415 / AIM DPM)
Lifetime	Until the package is opened at destination	Life of the item — through paint, solvents, and depot maintenance
Typical label stock	Durable coated shipping label; weather-resistant for outdoor staging	Polyimide (B-724 class), metallized polyester (B-428), or direct part marking

2. The Material Split Follows the Lifetime Split

129 stock: durable until delivery

Weather-resistant polyester earns its keep here — containers stage outdoors at depots and ports. B-8591 (-70°C to +110°C, UL 969) or B-423 with resin ribbon keeps the barcode scannable through rain and handling. The linear barcode rules are ordinary barcode engineering: quiet zones, picket-fence orientation, grade before ship.

130 stock: durable for the item's life

Label-based IUID marks live on B-724 polyimide (-70°C to +330°C) for electronics and B-428 metallized polyester for equipment plates — printed at 600 dpi (i5100 class) so the Data Matrix modules land on whole printer dots and grade cleanly. Where labels cannot survive, direct part marking takes over.

Registry submission is part of the deliverable

When IUID applies, marking the item is half the job — the UII data is reported to the DoD IUID Registry (via WAWF/PIEE workflows) as a contract deliverable. A perfect Data Matrix that was never registered is still a nonconformance.

3. First-Contract Router

Find the marking clauses in the contract — MIL-STD-129 appears via packaging requirements; IUID arrives through DFARS 252.211-7003.
Build the 129 label set from the contract data: NSN, CAGE, part number, contract number, quantity — then verify barcode grades before the truck, not after the rejection.
Determine IUID applicability per item (threshold, serial management, mission essentiality) — the contracting officer’s answer beats your interpretation.
Choose item-mark method by survivability: label stock where the surface and environment allow, direct part mark where they do not.
Register the UIIs and keep the verification reports — the paper trail is audited with the hardware.

Deep dive: the MIL-STD-130 standard itself

The MIL-STD-130 hub covers UII construction, marking quality requirements, and the compliant material matrix in full detail.

Open the MIL-STD-130 Hub