NATO Codification for a Foreign Supplier: NCAGE and NSN

Codification is how NATO gives every item its forces buy a single, unambiguous identity, so that the same bolt, radio or drone is not re-described from scratch by each nation that touches it. The system is the NATO Codification System (NCS): its rules are set by the AC/135 group of national codification directors, and the NATO Support and Procurement Agency (NSPA) runs the shared catalogue and the code tools. For a supplier, it resolves to two things you obtain.

NCAGE — the code for your company

A five-character alphanumeric code that identifies one legal entity at one location — who makes or supplies the item. You get one, once, and it is the first line of most allied supplier questionnaires and NSPA tenders.

NSN — the code for each item

A 13-digit NATO Stock Number that identifies one item of supply. The first four digits are the NATO Supply Classification (a supply group and class); the next nine are the item identification number, whose first two digits record which national bureau assigned it — not the country where the item is made.

Without an NSN, your item is a line on one contract with one customer. The next buyer has to re-specify it from first principles, and nothing connects the two orders. With an NSN, the item exists as a single reference across every allied logistics system — findable, stockable, reorderable by number, and comparable against alternatives.

Be precise about what that does and does not mean. Codification does not create demand or hand you a contract, and it does not exempt anyone from their own procurement rules. What it removes is the catalogue barrier— the gap between “sold once in Ukraine” and “visible to the whole alliance as a known, orderable item.” For a supplier that entered through the most demanding proving ground in the world, that is how one foothold compounds into a market of 32 allies and dozens of partner nations.

You request an NCAGE through NSPA's public code tool. NSPA then routes the request by where your company is physically located:

• In a NATO or Tier 2 nation — NSPA forwards the request to your national codification bureau, which assigns and maintains the code.
• Anywhere else (outside the United States, NATO and the Tier 2 nations) — NSPA assigns and maintains the code itself.
• United States entities obtain a CAGE code through SAM.gov as part of federal registration.

It is free, and you should allow roughly ten business days. The point to hold onto as a non-Ukrainian supplier: your NCAGE does notcome from Ukraine's bureau — that serves Ukrainian makers. Yours comes from your own country's bureau or from NSPA. Get it early; it gates everything downstream, and it is the identifier an allied buyer or an NSPA tender asks for first.

The NSN is not something you file speculatively for a whole product line. It is assigned by the codification bureau of the nation where the item's design control sits, when that nation is in NATO or at Tier 2, and it is triggered by a real order, on the strength of a technical data pack that describes the item precisely enough to catalogue it.

This is where the Ukrainian route matters. When Ukraine procures your item, the request runs through Ukraine's own bureau, which has worked at Tier 2 since 2019. Under the NATO codification manual (ACodP-1), an item designed in a NATO or Tier 2 nation gets its NSN from that nation's bureau at Ukraine's request, and Ukraine is registered as a user of it; an item designed outside those nations is codified by Ukraine's bureau itself. Either way the number lands in the same NMCRL, and its two country digits show which bureau assigned it.

The formal side is quick. Ukraine's rules give ten days from the moment the state customer receives the item's specifications, and there is no state fee. That clock starts only once a complete, defensible package exists. Teams that run full codification for Ukrainian makers describe the real path as seven stages of up to a month each, some of them in parallel: three months at best, typically up to six for an item starting from zero.

Two things shorten it. If the item's specifications are already registered, the first stage falls away, saving one to one and a half months. If trials are already done, roughly another month goes, and what remains is mostly writing up the methodology, drawing up the acts and the commission. The first commission usually returns remarks, with about two weeks to fix them. Resubmitting is normal: the law does not cap the number of submissions, and a first refusal is not a verdict.

A bilingual package, translated by a technical translator

A foreign item codified through Ukraine goes in with a bilingual package. The translation has to be certified (notarised) and done by a translator qualified in technical translation for that language pair. A capable general translator is a real failure point: the commission reads the methodology and the acts line by line, and a mistranslated parameter reads as a wrong one.

Components can be codified on their own

Anything that can be supplied as a separate item — a stabilised camera gimbal, a battery, an aerostat envelope apart from its payload — can be codified by itself. A system that integrates it then references the codified component instead of codifying it again. For a component maker, that is often the shortest way into the catalogue.

There are two ways to run it: with Brave1 support, or independently with a specialised team — counsel who carries the procedure and certified domain experts who write the methodology, attend the trials and defend the data at the commission. Both end at the same number. The choice comes down to how many stages are already closed and how much capacity the company can put behind the rest. The independent route, stage by stage, is laid out on the NATO codification service page.

1. 1Get your NCAGE. Through NSPA (routed to your national bureau) or SAM.gov for a US entity. Do it early — it is the prerequisite for everything that follows and for most supplier registrations.
2. 2Land the procurement. Codification follows a real order, not the reverse. A Ukrainian contract through the procurement single window, a Danish-model line, or an allied purchase all qualify as the trigger.
3. 3Request the NSN.Through the procuring nation's codification bureau, with the technical data pack for the item. The bureau classifies it and issues the number. Through Ukraine, that is the seven-stage path above — plan three to six months.
4. 4Land in the NMCRL.Once assigned, the item is in NATO's shared catalogue — identifiable and reorderable by every participating nation, not just the one that bought it first.
5. 5Stack the rest. Codification sits alongside, not instead of, your export licence, your quality certification and your commercial terms. It is one layer of the entry, not the whole of it.

Codification is powerful precisely because it is narrow. It answers one question — “which item is this, and who makes it” — and leaves the others to their own instruments. An NSN is not:

• An export licence.What may cross a border is still governed by your home export-control regime and Ukraine's end-use rules. See the legal and controls map for that layer.
• A quality certificate.AQAP or ISO 9001 answer “is it built to standard”; the NSN only answers “which item is this.” A buyer wants both.
• A contract or a guarantee of demand. It makes you findable and orderable; someone still has to place the order. The route from there to a paid invoice is the funding question.
• A NATO endorsement.A stock number is an identifier, not a seal of approval or a statement about the product's merit.

None of that diminishes the point. The catalogue barrier is real, it is the one most foreign suppliers hit late, and clearing it costs preparation rather than fees. Start that preparation alongside the entry, and the work you did to land in Ukraine keeps paying out across the alliance.