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 exclusively by the DLA Logistics Information Service and are foundational to federal procurement and defense logistics systems.
In modern federal workflows, CAGE codes operate alongside the Unique Entity ID (UEI). Together, they form the backbone of government entity validation—distinguishing who a company is from where contract work is performed.
Federal Identity Framework (2026)
Government contracting relies on a layered identity model. Each identifier serves a distinct purpose:
UEI (Unique Entity ID)
- Identifies the legal business entity
- Assigned automatically during SAM.gov registration
- Replaced DUNS for federal contracting
- Required for federal award eligibility and entity validation
CAGE Code
- Identifies a physical operating location
- Assigned after UEI validation as part of SAM/DLA processes
- Used for logistics, inspection, shipping, and payment routing
- Does not expire, but records must remain current
Key distinction: UEI identifies the company. CAGE identifies the facility. One does not replace the other.
UEI vs CAGE vs DUNS: Lifecycle and Where Each Fits
Many searches still reference 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 facility/location identifier.
Legacy
DUNS (Entity ID)
Older federal registrations used DUNS to identify the legal entity.
Current
UEI (Entity ID)
UEI is the modern entity identifier assigned through SAM.gov.
Location layer
CAGE (Facility ID)
CAGE identifies each physical location performing contract work.
Practical takeaway: DUNS may still appear in older systems, but UEI is the active entity identifier for SAM. CAGE remains the facility identifier used for logistics, shipping, inspection, and payment routing.
Registration Flow: How UEI and CAGE Work Together
- Register your entity in SAM.gov
- UEI is assigned to the legal business entity
- DLA validates physical location details
- CAGE code is issued for each contract-performing site
What CAGE Codes Are Used For
- Federal procurement, contracting, and invoicing
- Defense logistics and supply-chain traceability
- DODAAC assignment and shipping authorization
- Audit trails, inspections, and compliance reviews
Subcontractors: The “Soft” Requirement
Many subcontractors assume a CAGE code is optional. In practice, prime contractors frequently require CAGE codes for:
- Facility security validation
- Supply-chain documentation
- Flow-down compliance clauses
- Logistics and delivery authorization
Important: Even if not required by SAM, prime contractors may mandate a CAGE code before onboarding subcontractors.
CAGE vs NCAGE (International Entities)
| Code | Applies To | Authority | Primary Use |
|---|---|---|---|
| CAGE | U.S. entities | DLA Logistics Information Service | U.S. federal contracting |
| NCAGE | Non-U.S. entities | NATO / National Codification Bureaus | NATO & defense procurement |
Industry Classification Still Matters
Neither UEI nor CAGE describes what a business actually does. That role is fulfilled by SIC and NAICS codes, which are required for:
- SAM.gov eligibility screening
- Contract set-aside qualification
- Agency-specific solicitations
- Risk and compliance reviews
Before registering or updating SAM: Verify your SIC and NAICS codes to prevent misclassification, delays, or contract ineligibility. See What is a SIC Code? and What is a NAICS Code?.
Common Reasons for CAGE Validation Failure
CAGE validation issues are usually caused by address mismatch, entity identity inconsistency, or facility purpose conflicts. Use the guide below to troubleshoot the most common rejection causes.
| Common rejection reason | What it looks like | How to fix it |
|---|---|---|
| Physical address mismatch | SAM address does not match USPS format, lease/utility documentation, or location records. | Update SAM.gov so the physical address matches proof documents exactly (suite formatting, abbreviations, ZIP+4 where used). Avoid P.O. Boxes. |
| Virtual office / mail-drop address | Location cannot be verified as a real operating facility where work occurs. | Use a verifiable facility address. If using shared space, be prepared to show a dedicated suite and evidence of on-site operations. |
| Entity name inconsistency | Legal name, DBA, or punctuation varies across SAM, IRS/tax records, bank records, or proof documents. | Standardize the legal name across registrations and supporting documentation. Ensure SAM reflects the same legal naming used in authoritative records. |
| Duplicate / conflicting entity at address | Multiple companies appear to claim the same address, or an entity relationship is unclear. | Clarify suite/unit identifiers, ensure unique facility descriptors, and provide proof of possession for the specific business location. |
| Unable to validate business presence | DLA requests additional documentation (proof of possession) or cannot confirm location activity. | Provide a lease, utility bill, or facility documentation that confirms the business operates at that address. |
| Facility purpose conflicts with declared activity | Location type and declared business activity appear inconsistent (e.g., storage-only address listed for service delivery). | Ensure your SIC/NAICS classification and facility description reflect reality. Re-verify codes if your operating model changed. |
High-impact fix: If your business model changed, re-verify your SIC/NAICS codes before updating SAM. Misclassification can slow validation and trigger eligibility questions.
CAGE Code Change of Address & Compliance Guide
Relocating your business is the most common reason a CAGE code becomes inactive, mismatched, or temporarily unusable. In 2026, synchronization requirements between SAM.gov and the DLA Logistics Information Service have tightened to reduce identity fraud and supply-chain risk.
Compliance alert: Under FAR 52.204-18, contractors must notify the government of a location change within 30 days. Failure to synchronize your CAGE address can trigger payment delays, inspection holds, or “stop work” actions through WAWF and related systems.
The 4-Step CAGE Synchronization Process
| Step | Action Required | Why It Matters |
|---|---|---|
| 1. Re-Verify Industry | Confirm your primary SIC and NAICS codes. A new facility location may change your dominant revenue activity or eligibility profile. | Agencies validate set-aside status (e.g., HUBZone, small business) based on industry activity tied to the physical facility. |
| 2. Update SAM.gov | Select “Update Entity” in SAM.gov and update the physical address to match lease or utility documentation exactly. | This automatically triggers a CAGE re-validation request with the DLA. |
| 3. DLA Re-Validation | DLA processing typically takes 10–15 business days. Monitor email from dlacontactcenter@dla.mil. |
If USPS or commercial records cannot verify the address, DLA will request proof of possession (lease or utility bill). |
| 4. Notify the ACO | Email your Administrative Contracting Officer (ACO) to update Ship-To and Pay-To details on active awards. | Ensures your CAGE code remains correctly linked to the appropriate DODAAC for logistics and payments. |
Virtual Office & P.O. Box Restrictions
To maintain an active CAGE code at a new address, the DLA requires a verifiable physical presence:
- No P.O. Boxes: The address must be a real facility where work is performed or goods are stored.
- Virtual offices: Mail-drop or shared virtual addresses often fail validation unless you can prove a dedicated suite and on-site staff.
Risk control: Address mismatches between SAM, CAGE, and USPS records are a leading cause of validation failure and payment disruption.
Template: CAGE Address Change Notification
Use the template below to notify contracting officials after your SAM.gov update is complete:
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 CAGE code records have been updated to reflect this change. There is no change to our Unique Entity ID (UEI) or our primary SIC/NAICS classification.
Please ensure this updated location is reflected in all active Ship-To and Pay-To instructions for Contract #[Contract Number].
Why This Matters Long-Term
CAGE codes are not static identifiers—they are continuously validated against physical presence, classification accuracy, and federal records. Keeping your address, industry codes, and SAM profile synchronized protects contract continuity, inspection eligibility, and payment flow.
Frequently Asked Questions
- Did UEI replace CAGE codes?
No. UEI identifies the entity; CAGE identifies the facility. - Did UEI replace DUNS?
Yes for federal registration. DUNS may appear in legacy records, but UEI is the active entity identifier assigned through SAM.gov. - Can one company have multiple CAGE codes?
Yes. Each physical contract-performing location may receive its own CAGE code. - Do subcontractors need CAGE codes?
Often yes. Many prime contractors require them for compliance and logistics. - Do CAGE codes expire?
No, but SAM registration and business location data should remain current to avoid disruptions. - What should I do if my CAGE validation fails?
Start with address format consistency and proof of possession, then confirm your facility purpose and SIC/NAICS classification match your real operating activity.
Looking Ahead
As federal procurement continues to emphasize supply-chain integrity, cybersecurity, and entity verification, CAGE codes remain a cornerstone of government identity infrastructure—working in tandem with UEI and industry classification to ensure transparency and accountability.