More than 40 countries use the NATO Codification System in some form within their logistics systems. The catalogue behind it holds around 16 million codified items, according to the NATO Group of National Directors on Codification (AC/135). Every one of those nations also runs its own item marking standard. A supplier delivering the same actuator to three allied customers can face three different marking specifications describing what is, in engineering terms, the same requirement.
The specifications are more aligned than the numbering suggests. This is what each one asks for, where they genuinely differ and how to build one marking process that satisfies all of them.
What STANAG 2290 requires
STANAG 2290 is the NATO Standardization Agreement covering Unique Identification of Items. Its job is to give a serialised asset one permanent identity that stays with it for its whole life, independent of which nation is holding it.
The agreement does three things. It defines a uniform structure for the Unique Item Identifier (UII) so the identifier is constructed the same way in every ratifying nation. It sets expectations for identification marking and for data matrix machine-readable content. It requires participating nations to maintain a registry holding the component data elements behind each UII, including original part number and serial number.
The registry requirement is the part most often underestimated. A UII with no registry entry is a serial number nobody can query. The mark and the record are one deliverable, not two.
STANAG 2290 also does not replace the NATO Codification System. Codification answers “what kind of item is this” with an NSN. Unique identification answers “which specific item is this” with a UII. Camcode Global’s published work on NATO interoperability sets out how the two disciplines combine with data cleansing to make allied asset data exchangeable.
How STANAG 2290 compares to MIL-STD-130
MIL-STD-130 is the US Department of Defense standard for identification marking of US military property. STANAG 2290 was built to be compatible with it rather than to compete with it, which is why suppliers already working to MIL-STD-130 find the NATO requirement familiar.
The shared ground covers the important mechanics:
- Both require a machine-readable 2D data matrix symbol alongside human-readable text.
- Both construct the unique identifier from an enterprise identifier plus a serial number, either serialised within the enterprise or serialised within an original part number.
- Both expect the mark to remain legible and scannable for the service life of the item.
- Both place the identifier in a registry so the physical mark resolves to a record.
The differences are about ownership and scope. MIL-STD-130 is a US national standard with its own registry and its own contract flow-down through the Defense Federal Acquisition Regulation Supplement. STANAG 2290 is an alliance agreement that each nation ratifies and implements through national policy, so the implementation detail sits in national documents rather than in the STANAG itself.
For a supplier, the practical consequence is this: the symbology, the data construct and the durability expectation transfer almost directly between the two. The registry destination, the syntax details and the contractual clause do not. Do not assume a MIL-STD-130 compliant mark is automatically accepted against a NATO contract without checking the customer nation’s implementing document.
Where the national standards fit
Three documents sit underneath or alongside STANAG 2290. These are the ones that actually appear in contracts.
Def Stan 05-132 is the UK Defence Standard covering unique identification of items for the Ministry of Defence. It is the document a UK supplier is contracted against. It implements the NATO approach within UK acquisition policy.
DAOD 3038-0, Materiel Identification, is the Canadian Defence Administrative Order and Directive covering how materiel is identified, including NATO codification and master data records.
EN 9132 is the European aerospace standard for data matrix quality requirements. It matters because it governs symbol quality rather than symbol content: a data matrix can carry perfectly correct data and still fail on contrast, cell fill or axial non-uniformity.
Read together, this is one technical approach expressed through several contractual routes. The identifier content is broadly common. The document you cite, the registry you populate and the quality grading you evidence are national.
Two jobs, two standards: Identity versus classification
The most common programme failure is treating unique identification and codification as alternatives.
Codification assigns one NSN per item type. It is what allows a partner nation to know that the object in front of them is a specific type of hydraulic filter, that they may already hold stock of it and that it interchanges with something they already have. The value of this discipline shows up in duplication rates. The NATO codification material reports that parts for brand new equipment match an existing catalogue item more than 30 percent of the time in the United States. In Canada and many other NATO nations the figure is closer to 60 percent.
Unique identification assigns one UII per individual asset. It is what allows anyone to know that this particular filter was fitted on a given date, has a given repair history and was condemned by a specific authority.
A programme that codifies without serialising ends up with accurate stock lists and no maintenance traceability. A programme that serialises without codifying ends up with traceable assets that partner nations cannot classify. Interoperability needs both.
What a compliant mark has to survive
Standards specify legibility for the life of the item. That phrase does the heavy lifting, because service life for a defence asset can mean 30 years of salt spray, hydraulic fluid, jet wash, abrasion, UV and heat cycling.
Marking media choice is therefore a compliance question rather than a procurement preference. Printed labels and adhesive media suit controlled indoor environments and short asset lives. They fail on externally mounted, deployed or maritime assets. Photosensitive anodised aluminium plates and laser-etched metal carry the mark inside the substrate rather than on top of it, which is why they appear in defence specifications for equipment that lives outdoors.
A useful test: if the item will be washed, fuelled, deployed or stored outside, assume any surface-applied mark needs replacing at least once in the asset’s life. Every replacement is a re-marking cost plus a registry update plus a window in which the asset is not properly identified.
Symbol quality is the second failure mode. A data matrix that grades poorly on contrast or cell modulation reads fine on a bench scanner under good light and fails on a handheld device in a dark warehouse. Verification against the applicable quality standard at the point of production is cheaper than discovering the problem at a receiving depot in another country.
A practical compliance sequence
- Establish which document governs. Identify the contracting nation and its implementing standard before designing the mark. STANAG 2290 sets the structure. The national document sets the obligation.
- Cleanse the source data. Duplicate, incomplete or conflicting register entries produce duplicate and conflicting UIIs. Fix the data before it is committed to metal.
- Construct the identifier correctly. Confirm the enterprise identifier, the construct type and the syntax the customer’s registry expects.
- Select media against the service environment, not against the unit price of the plate.
- Verify symbol quality at production, with grading evidence retained.
- Register every identifier and keep the registry synchronised with the maintenance system.
- Plan for legacy assets. Equipment already in service still needs identity. Mobile marking that goes to the asset avoids recalling equipment from the field solely to mark it.
Why the timing matters
NATO reports that European Allies and Canada spent more than 571 billion US dollars on defence in 2025 in 2021 prices, over 90 billion more than in 2024, under a Hague Summit commitment to reach 5 percent of GDP by 2035. The 2014 Wales pledge already committed allies to putting at least 20 percent of defence expenditure into major equipment and associated research and development.
That is a large volume of new materiel entering national catalogues over a short period. Items marked correctly on the production line cost a fraction of items marked retrospectively in a depot. The marking specification is set at contract award rather than at delivery.
Frequently asked questions
Does a MIL-STD-130 mark satisfy STANAG 2290? Technically the construct and symbology transfer well. Contractually it depends on the customer nation’s implementing standard and registry. Check the specific document cited in the contract.
Is STANAG 2290 a replacement for the NATO Codification System? No. Codification classifies item types with an NSN. STANAG 2290 identifies individual assets with a UII. Most programmes need both.
Who holds the registry? Participating nations establish UII registries under STANAG 2290. Suppliers submit the data elements, including original part number and serial number.
What marking media is acceptable? The standards specify performance rather than a product. The mark must stay legible and machine-readable for the life of the item in its service environment, which rules out printed and adhesive media for most deployed or externally mounted assets.
Leave a Comment