CAGE Code Explained: UEI vs CAGE, Federal Identity, and Government Contracting
What is a CAGE Code? A Commercial and Government Entity (CAGE) Code is a five-character identifier used by the U.S. Federal Government to identify a specific physical business location involved in contracting, logistics, or supply-chain activity. CAGE codes are issued and maintained by the DLA Logistics Information Service and are used throughout federal procurement and defense logistics systems.
In current federal workflows, CAGE codes work alongside the Unique Entity ID (UEI). Together, they support entity validation by separating who the contractor is from where contract work is tied operationally.
Federal Identity Framework
Federal contracting relies on a layered identity model. Each identifier has a different purpose, and they should not be treated as interchangeable.
UEI (Unique Entity ID)
- Identifies the legal business entity
- Assigned through SAM.gov
- Replaced DUNS as the federal entity identifier
- Required for federal award eligibility and entity validation
CAGE Code
- Identifies a specific physical location
- Used in DLA and federal logistics-related workflows
- Supports shipping, inspection, and payment-routing processes
- Should remain current with entity and address records
Key distinction: UEI identifies the company as an entity. CAGE identifies the facility or location record used in government logistics and procurement systems.
UEI vs CAGE vs DUNS
Many searches still mention DUNS because it appears in legacy records, supplier portals, and historical award documentation. In current federal registration, UEI replaces DUNS as the entity identifier, while CAGE remains the location-oriented identifier used in related federal systems.
Legacy
DUNS (Entity ID)
Older federal registrations used DUNS to identify the legal entity.
Current
UEI (Entity ID)
UEI is the current entity identifier created through SAM.gov.
Location layer
CAGE (Facility ID)
CAGE identifies a specific physical location used in procurement and logistics workflows.
Practical takeaway: DUNS may still appear in old records, but UEI is now the active federal entity identifier. CAGE remains the facility-level identifier used in related systems.
Registration Flow: How UEI and CAGE Work Together
- Register your entity in SAM.gov or request a UEI through SAM.gov
- UEI is assigned to the legal business entity
- Location and related details are validated through the applicable federal process
- CAGE is linked for the facility record used in procurement and logistics workflows
What CAGE Codes Are Used For
- Federal procurement, contracting, and invoicing support
- Defense logistics and supply-chain traceability
- DODAAC-related and shipping authorization workflows
- Audit trails, inspections, and compliance reviews
Subcontractors: The Practical Requirement
Many subcontractors assume a CAGE code is optional. In practice, prime contractors often require it for facility and supply-chain validation.
- Facility security validation
- Supply-chain documentation
- Flow-down compliance clauses
- Logistics and delivery authorization
Important: even where a subcontractor is not handling direct SAM registration in the same way as a prime, prime contractors may still require a CAGE-related record for onboarding, compliance, or logistics reasons.
CAGE vs NCAGE
| Code | Applies To | Authority | Primary Use |
|---|---|---|---|
| CAGE | U.S. entities and locations | DLA Logistics Information Service | U.S. federal procurement and logistics |
| NCAGE | Non-U.S. entities | NATO / National Codification Bureaus | NATO and international defense procurement contexts |
Industry Classification Still Matters
Neither UEI nor CAGE describes what a business actually does. That role is handled by NAICS and, in some workflows, SIC.
- SAM eligibility screening
- Set-aside qualification and agency-specific solicitations
- Risk and compliance review
- Operational segmentation and legacy reporting
Before registering or updating federal profiles: verify your NAICS and SIC codes so your activity record matches your actual operations.
Common Reasons for CAGE Validation Failure
CAGE-related validation issues are usually caused by address mismatch, entity inconsistency, or facility-purpose conflicts. This guide covers the most common causes.
| Common issue | What it looks like | How to fix it |
|---|---|---|
| Physical address mismatch | SAM or related address data does not match proof documents or location records. | Standardize the physical address exactly across systems and supporting documents. Avoid P.O. Boxes for physical-location workflows. |
| Virtual office or mail-drop address | The location cannot be validated as a real operating facility. | Use a verifiable location and be prepared to support it with facility documentation. |
| Entity name inconsistency | Legal name, DBA, punctuation, or entity naming varies across systems. | Standardize the legal business name across registrations and authoritative records. |
| Duplicate or conflicting entity at address | Multiple companies appear tied to the same location or suite distinction is unclear. | Clarify suite and unit details and provide location-specific proof. |
| Unable to validate business presence | Additional documentation is requested or the location cannot be confirmed. | Provide lease, utility, or other proof-of-possession documents tied to the facility. |
| Facility purpose conflicts with declared activity | The location type appears inconsistent with the stated business activity. | Re-verify that your facility description and NAICS/SIC classification match real operations. |
High-impact fix: if your business model changed, re-check your NAICS and SIC codes before updating registration records. Misclassification can slow validation and create eligibility questions.
CAGE Code Change of Address and Compliance Guide
Relocation is one of the most common reasons a CAGE-linked record becomes mismatched or temporarily problematic. The critical issue is keeping SAM, location records, and facility documentation synchronized.
Contract clause point: FAR 52.204-18 states that the contractor must communicate any change to the CAGE code to the contracting officer within 30 days after the change so the contract can be updated. That clause speaks to a change to the CAGE code itself, not generically to every address change. If an address change results in a CAGE-related change or contract update need, the contracting officer should be notified promptly.
The 4-Step Synchronization Process
| Step | Action Required | Why It Matters |
|---|---|---|
| 1. Re-verify industry | Confirm your primary NAICS and SIC codes, especially if the new location changes how work is performed. | Industry classification affects eligibility, reporting, and how your location is interpreted. |
| 2. Update SAM.gov | Use the entity update workflow so legal and physical location data matches your documents exactly. | Inconsistent address data is one of the most common causes of downstream validation problems. |
| 3. Monitor validation | Watch for follow-up requests tied to entity or location verification. | Some records need extra proof of possession or clarification before final acceptance. |
| 4. Notify contracting contacts | Tell the contracting officer or administrative contact when the contract record needs an update tied to the location or CAGE record. | This helps avoid shipping, inspection, or payment misrouting. |
Virtual Office and P.O. Box Restrictions
For facility-based validation, the government generally needs a real physical operating presence.
- No P.O. Boxes for physical facility identity
- Virtual offices can be problematic if they do not represent a real operating location
- Shared spaces may require clear suite identification and proof of occupancy
Risk control: address mismatches across SAM, CAGE-related records, and postal or commercial records are a common source of validation failure and operational disruption.
Template: CAGE Address Change Notification
Subject: Notification of Business Address Change – [Company Name] – CAGE: [Code]
To: [Contracting Officer / ACO Name]
Please be advised that [Company Name] has relocated its primary operating facility.
New physical address:
[New Address]
Our SAM.gov profile and related location records have been updated to reflect this change. There is no change to our Unique Entity ID (UEI) or to our primary SIC/NAICS classification unless otherwise noted.
Please ensure this updated location is reflected in all applicable Ship-To, Pay-To, or contract administration records for Contract #[Contract Number].
Why This Matters Long-Term
CAGE-linked records are not just static identifiers. They are part of a larger federal identity and logistics infrastructure that depends on accurate location, classification, and entity data. Keeping address, activity codes, and SAM data synchronized helps protect contract continuity, inspection readiness, and payment flow.
Frequently Asked Questions
- Did UEI replace CAGE codes?
No. UEI identifies the legal entity, while CAGE identifies a location-oriented government record tied to facility use in federal workflows. - Did UEI replace DUNS?
Yes for federal registration and entity identification in IAE systems. DUNS may still appear in older records, but UEI is the active identifier of record. - Can one company have multiple CAGE codes?
Yes. Different physical locations can have separate CAGE-related records when federal workflows require location-level identification. - Do subcontractors need CAGE codes?
Often yes in practice, especially when primes require location, compliance, or logistics validation. - Do CAGE codes expire?
The code itself is not typically described as expiring, but the surrounding registration and location information must remain current to avoid disruption. - What should I do if my validation fails?
Start with address consistency, proof of possession, and confirmation that your facility purpose and NAICS/SIC classification match your actual operations.
Looking Ahead
As federal procurement continues to emphasize supply-chain integrity, cybersecurity, and entity validation, CAGE remains an important part of government identity infrastructure, working alongside UEI and industry classification to support accountability and operational traceability.