Semiconductor Sourcing | Quality & Traceability
A supplier offers you an IC with a 2021 date code. It is now 2026. Is the component too old to use?
Not necessarily. A semiconductor date code usually identifies manufacturing timing or related traceability information. It is not, by itself, an expiration date.
Yet an older date code should not be accepted automatically. The condition of the component, its packaging, storage history, moisture sensitivity, solderability and source documentation may all affect whether it is suitable for a particular order.
Quick Answer: How Old Is Too Old for an Electronic Component?
There is no universal two-year, three-year or five-year expiration rule for all semiconductors. Older ICs should be assessed against manufacturer guidance, packaging and storage conditions, moisture-handling requirements, traceability, solderability risk and the buyer's own acceptance criteria. A customer may still impose a mandatory date-code limit even when the component has not been technically shown to be unusable.
For procurement teams, this distinction is especially important when reviewing surplus, long-term or hard-to-find inventory. As explained in our guide to electronic component availability, a part appearing in stock does not automatically mean that the offered quantity, packaging and conditions meet the buyer's requirements.
This article focuses primarily on semiconductors and moisture-sensitive components used in PCB assembly. Batteries, adhesives, some capacitors, connectors and other product categories may have different storage and aging mechanisms. Always apply the requirements relevant to the specific component.
1. What Does an Electronic Component Date Code Mean?
An electronic component date code is a manufacturer-defined marking or label identifier associated with production timing. It can support manufacturing-lot identification, traceability, inventory management and quality investigations.
Many components use a year-and-week convention. For example, under a hypothetical YYWW format, the code 2147 could indicate week 47 of 2021.
However, semiconductor markings are not universally formatted. Some manufacturers use abbreviated codes, package-specific conventions or additional lot identifiers. The correct interpretation should come from the relevant manufacturer's marking documentation.
Buyers should also distinguish between the component date code, the lot or trace code and the packaging seal date. These may describe different events.
In short, a date code helps answer when a component was made. It does not independently prove how well it has been stored or whether it is suitable for assembly today.
2. Date Code vs. Shelf Life vs. MSL Floor Life
Three separate concepts are frequently confused during semiconductor procurement.
| Concept | What It Means | What It Does Not Mean |
|---|---|---|
| Date Code | Manufacturing timing and traceability information | An automatic expiration date |
| Shelf Life | A defined storage period under specified product or packaging conditions | A universal age limit for all ICs |
| MSL / Floor Life | Moisture sensitivity and permitted environmental exposure before applicable reflow processing | The number of years since a device was manufactured |
Date Code: The Manufacturing Timeline
A date code helps identify production timing and supports lot-related records. Its practical importance may include customer date-code restrictions, inventory rotation and traceability investigations.
Shelf Life: The Defined Storage Period
Shelf life must be interpreted within a specific manufacturer's or standard's definition. For example, the storage period for a properly sealed moisture barrier bag is not necessarily measured from the semiconductor's manufacturing date.
Storage conditions matter. Temperature, humidity, packaging integrity, terminal finish and the component's materials can affect what storage guidance applies.
MSL Floor Life: The Exposure Before Reflow
Moisture Sensitivity Level, or MSL, classifies the moisture/reflow sensitivity of applicable devices. After protective packaging is opened, the permitted exposure before reflow depends on the applicable MSL and specified environmental conditions.
Analog Devices' explanation of Moisture Sensitivity Level describes the moisture-related risks associated with plastic-packaged semiconductors.
An MSL 1 classification does not mean unlimited shelf life in every respect. It addresses a particular moisture/reflow classification, not authenticity, solderability, traceability or all forms of long-term storage risk.
3. Does IPC/JEDEC J-STD-033 Mean Components Expire After 12 Months?
No. The frequently cited 12-month period in IPC/JEDEC J-STD-033D should not be interpreted as a universal semiconductor expiration date.
IPC/JEDEC J-STD-033D covers standardized methods for handling, packing, shipping and using moisture/reflow-sensitive devices. Its published description states that correctly implemented dry-pack procedures provide a minimum shelf life of 12 months from the seal date.
The important phrase is from the seal date—not from the component manufacturing date.
It is also a minimum dry-pack provision under defined procedures, not a statement that every bag or every semiconductor becomes unusable at the 12-month mark.
IPC/JEDEC J-STD-020F addresses moisture/reflow sensitivity classification for applicable nonhermetic surface-mount devices. J-STD-033 provides related handling guidance.
Three Different Checkpoints
Manufacturing: Date code and lot identification
Dry-Pack Storage: MBB seal date, packaging integrity and humidity-control evidence
Opening to Assembly: MSL floor-life exposure and applicable reflow handling
If a moisture barrier bag is damaged, its defined storage period has been exceeded, or its humidity indicator suggests unacceptable exposure, the material requires assessment under the applicable manufacturer instructions and handling procedures.
That assessment may involve controlled drying, baking or repacking where permitted. It should not be replaced by an automatic assumption that the devices are either safe or expired.
4. How Old Is Too Old for an IC? What Manufacturer Evidence Shows
There is no single age threshold that can reliably determine the condition of every semiconductor.
Texas Instruments' product shelf-life guidance states that the minimum useful life of a TI product is based on delivery to the customer rather than manufacturing date. TI also emphasizes that customer storage conditions and moisture-handling requirements remain important.
TI has conducted long-term storage studies involving selected semiconductor devices. Those studies challenge the assumption that older manufacturing dates automatically imply degraded electrical performance or solderability.
However, these findings must be understood within their scope. Research involving particular device materials, finishes and storage practices does not establish that every semiconductor from every source will perform identically after extended storage.
The practical conclusion is not “old ICs are always safe.” It is:
Component age should trigger the right questions, not replace the answers.
A five-year-old IC with credible provenance, appropriate packaging and documented handling may be a reasonable candidate for further evaluation. A recently manufactured IC with unexplained label inconsistencies or unknown exposure history may present more immediate concerns.
Neither case should be accepted solely on that description. The actual MPN, application and buyer requirements determine what evidence is sufficient.
5. What Can Actually Go Wrong With Older Components?
Moisture Absorption and Reflow Damage
Some plastic-packaged devices absorb environmental moisture. During solder reflow, rapid heating can create internal stresses that may cause package cracking, delamination or other damage.
For moisture-sensitive devices, the MSL classification, protective packaging and environmental exposure history therefore matter more than simply counting years from manufacture.
Compromised Moisture Barrier Packaging
Moisture barrier bags, desiccants and humidity indicator cards help protect appropriate devices during storage and transportation.
Buyers should ask whether the packaging is original and sealed, whether the seal date is available and whether the material has previously been opened or repacked.
An apparently sealed bag is not, by itself, proof that the handling history is acceptable.
Terminal Oxidation and Solderability
Depending on the terminal finish and storage environment, extended or unsuitable storage may affect surface condition and solderability.
For relevant risks, IPC J-STD-002F solderability test methods provide a recognized basis for evaluating electronic component leads and terminations.
Such testing should be specified according to the component, application and agreed acceptance criteria—not automatically imposed on every older lot.
Unknown Storage or Repacking History
Long-term stock may have passed through multiple warehouses or owners. If temperature, humidity, opening or repacking records are unavailable, buyers have less evidence on which to base acceptance.
Baking is not a universal restoration method. An approved procedure may address certain moisture-exposure conditions, but it cannot automatically reverse terminal oxidation, contamination or physical damage.
Traceability and Authenticity Risk
A recent date code does not prove that a component is genuine. An older date code does not prove that it is counterfeit.
Manufacturer labels, lot records, supplier history and chain-of-custody evidence are separate quality considerations. Material from an uncertain source may require a different inspection and documentation plan from material with continuous, verifiable provenance.
6. Engineering Acceptance vs. Customer Date-Code Requirements
This distinction is critical in real procurement decisions.
Engineering acceptance concerns whether a component is suitable for its intended assembly and application. Relevant evidence may include manufacturer specifications, packaging condition, storage records, moisture-handling compliance, solderability and other qualification requirements.
Commercial or contractual acceptance concerns whether the offered stock satisfies the buyer's agreed purchasing conditions.
For example, an OEM or EMS customer may require components manufactured within the previous 24 months. That requirement may come from an internal quality procedure, customer contract or project-specific policy.
Even if an older component appears technically suitable for evaluation, a supplier cannot disregard a binding customer date-code limit.
Conversely, when no such limit applies, an arbitrary two-year cutoff may unnecessarily exclude inventory that could be evaluated using appropriate technical evidence.
| Question | Engineering Review | Commercial Review |
|---|---|---|
| Is the component technically suitable? | Assess applicable product, handling and quality evidence. | Not sufficient by itself. |
| Does the date code meet the customer requirement? | Age alone may not determine reliability. | Must meet the agreed date-code range or obtain approval for an exception. |
| Can older stock be considered? | Possibly, subject to a risk-based assessment. | Only when customer and contractual requirements permit. |
A technically defensible component is not automatically a contractually acceptable component. Both questions should be resolved before purchase.
7. Manufacturer Guidance: What Buyers Should Actually Check
Semiconductor manufacturers publish different types of storage, marking and moisture-handling documentation. Buyers should consult the information relevant to the exact product rather than assume every manufacturer follows the same maximum date-code policy.
| Manufacturer | Useful Documentation | Procurement Implication |
|---|---|---|
| Texas Instruments | Product shelf-life guidance and storage studies | Distinguish manufacturing date from TI's controlled storage and customer-use conditions. |
| Analog Devices | MSL, dry-pack and humidity-control guidance | Check the device's moisture-handling requirements and packaging evidence. |
| NXP | Product-specific MSL and assembly guidance | Confirm requirements for the exact MPN and package. |
| onsemi | Marking, packaging, product quality and reliability documentation | Use product-specific information rather than an assumed company-wide age limit. |
| Microchip | Device-family storage and package-handling guidance | Apply the relevant product-family requirements. |
For product-specific examples, consult NXP's AN2265 application note and Microchip's AC441 storage guidance. Each document has a defined technical scope and should not be interpreted as a blanket policy covering every component sold by that manufacturer.
8. Old Date Code Component Verification Checklist
Before approving older semiconductor inventory, buyers should align the required evidence with the part number, supply channel, application and customer requirements.
- Complete manufacturer part number: Confirm suffix, package, temperature grade and packing option.
- Date code and lot code: Confirm the range, quantities and whether mixed lots are acceptable.
- Original manufacturer label: Request clear photographs and reconcile the information with the quoted stock.
- Source and traceability: Review the available supplier path, purchase evidence and chain-of-custody documentation.
- MSL and reflow requirements: Check the relevant manufacturer and package documentation.
- Moisture barrier bag: Determine whether the original packaging remains sealed and intact.
- Seal date, HIC and desiccant: Review available dry-pack evidence where applicable.
- Storage history: Request relevant temperature, humidity and warehouse records for aged or higher-risk material.
- Opening, baking and repacking: Establish the handling history of previously opened stock.
- Additional verification: Consider solderability, electrical or functional testing when justified by the application and sourcing risk.
The appropriate inspection plan is not identical for every order. For example, a routine commercial application and a high-reliability application may require different evidence and approval procedures.
Chip-seek's quality and traceability requirements page describes the importance of defining supplier, packaging, lot and documentation expectations for a specific quotation.
9. How to Specify Date-Code Requirements in an RFQ
A vague instruction such as “new date code only” may not tell a supplier enough to determine whether its stock is acceptable.
Instead, state the exact date-code and quality conditions that apply to the order.
Suggested RFQ Information
Manufacturer:
Complete MPN:
Required Quantity:
Acceptable Date Code Range:
Mixed Date Codes Acceptable? Yes / No
Single Lot Required? Yes / No
Required Packaging:
Original Sealed MBB Required? Yes / No
Applicable MSL / Handling Requirements:
Manufacturer Label Photos Required? Yes / No
Traceability / CoC Requirements:
Storage and Repacking Records Required?
Additional Testing Requirements:
Target Delivery Date:
Ship-to Country:
Other Customer Quality Requirements:
If a 24-month or 36-month restriction is mandatory, identify it before requesting quotations. If older date codes may be considered, specify what evidence or approval is required.
For multi-line requirements, the Chip-seek BOM & RFQ service provides a place to submit component details and describe the commercial and quality conditions that should be considered during sourcing review.
10. Frequently Asked Questions About Electronic Component Date Codes
Select a question to expand the answer.
Final Thoughts: Date Code Is One Data Point, Not a Complete Quality Decision
Older electronic components should not be accepted without appropriate evidence. But manufacturing age alone is not enough to determine that a semiconductor is unsuitable.
A better sourcing decision considers the specific device, packaging, storage conditions, moisture sensitivity, solderability, traceability and customer requirements.
When those conditions are clearly defined at the RFQ stage, buyers can compare offers more effectively and identify potential quality concerns before committing to an order.
Sourcing Components With Specific Date-Code Requirements?
Share your MPNs, quantities, acceptable date-code ranges, packaging preferences and documentation requirements so they can be considered during the sourcing review.
Submit Your BOM / RFQTechnical note: This article provides general component sourcing and handling information. It is not a product qualification, authenticity certification or guarantee of suitability. Follow the applicable manufacturer instructions, customer specifications and quality procedures.
