Industry Insights
Old Date Code or Missing History? A Buyer's Guide to Legacy IC Evidence
Published · Updated
An old date code answers only one of the buying questions
A supplier has located the exact IC on your maintenance BOM. The price is not yet agreed, the production line needs a decision, and the label appears to show an older manufacturing period. It is tempting to turn that date into a single acceptance rule. Doing so can reject useful material while overlooking a recent-looking offer with an uncertain source. Start by separating the identity of the device, the history of the offered lot, its handling condition, and the evidence needed before assembly. Those are related questions, but they are not interchangeable answers.
A date code is not a universal expiration date. Manufacturers use different marking and packaging conventions; a short package marking may not even carry the complete purchasable order code. Preserve the exact text and its location before interpreting it. Record whether the observation came from the outer carton, a moisture barrier bag, a reel label, or the device body. If the meaning is unclear, ask for the manufacturer's applicable marking reference rather than assigning a year from a familiar-looking pattern. A guess copied into an RFQ can become an unintended contractual requirement.
Texas Instruments' product shelf-life guidance distinguishes its controlled internal storage from customer storage after delivery. It discusses packaging, moisture sensitivity and handling conditions; it does not provide a blanket approval for unknown material from every source. That distinction matters here. We use TI's guidance to explain why age and storage history are different dimensions, not to certify a legacy FPGA lot or extend another manufacturer's storage limit. The applicable manufacturer's current instructions and your receiving requirements still control the actual decision.
Consider two hypothetical offers for the same complete MPN. Offer A has an older stated code and a documented distribution and storage history. Offer B claims a newer code but cannot connect the photographs to the offered quantity. Neither description alone approves a purchase. The productive next step is to request the missing records and have the responsible quality and engineering teams assess them. Calling one offer good and the other counterfeit would go beyond the evidence. This guide helps turn that uncertainty into specific questions instead of a misleading confidence score.

Play the conceptual walkthrough (close to hide motion)

Reduced motion: use the static poster and transcript.
Read the walkthrough transcript
- EXACT MPN: Keep the original string
- CIRCUMSTANCES: Split lots? Opened? Unknown history?
- QUESTIONS: Ask for the missing records
- HANDOFF: Review owner and unresolved decision
Build a chain of records, not a folder of impressive documents
Begin with the approved BOM line and the offered line in separate fields. Keep the manufacturer, complete MPN, quantity and any allowed packaging preference visible. Ask whether the quantity is one lot, multiple identified lots, or a proposed consolidation that has not yet been assembled. If a supplier proposes several lots, require a quantity breakdown associated with each offered lot identifier. A document covering one reel cannot silently become evidence for every reel in a combined shipment. Keep commercial quotations separate from the records used to support identity and history.
The next question is where the material came from and which organizations handled it. Ask the seller to describe the available chain of supply, the records that can be shared, and any known breaks. Manufacturer-authorized channels are checked against the manufacturer's own distribution information, not a badge on a seller's website. Analog Devices, for example, explains the support associated with purchases through its authorized network. That is an ADI policy statement, not an assertion that FPGA.io or a supplier in your RFQ is an authorized distributor. Authorization is manufacturer-specific and should be verified for the relevant source and transaction.
A certificate, invoice extract, packing record and label image have different purposes. List the issuer, reference, date and exact material covered by each item. Look for a clear relationship between the records rather than treating the number of attachments as evidence quality. Where a seller cannot disclose an upstream commercial document, record that limitation and ask what verifiable alternative is available. Do not encourage alteration of documents or removal of information needed to establish their scope. Sensitive customer and pricing information should be exchanged through the agreed private review process, not embedded in a public quotation URL.
The resulting evidence chain may be incomplete. Preserve that finding explicitly: source not verified, quantity coverage not established, or document relationship unresolved. These are useful procurement states. They tell the next reviewer what to ask without making an unsupported accusation. If the evidence cannot meet your organization's acceptance conditions, keep the lot outside the approved purchase decision and identify who owns the exception process. A salesperson's availability message is not a substitute for that decision, and a buyer should not rewrite an unknown field as confirmed merely to move the order forward.
Ask what happened to the package between sealing and your assembly line
The package surrounding the IC is part of the handling story. Request the type of delivery container, whether the offered material remains in original packaging, and whether any opening, splitting, repacking or resealing is known. These are factual questions. Repacking is not by itself proof of a counterfeit device, and an apparently intact bag is not proof of an uninterrupted storage history. Keep observations distinct from the conclusions that a qualified receiving process may draw from them.
For moisture-sensitive surface-mount material, ask for the applicable moisture sensitivity information and the manufacturer's handling reference. Request the available seal, opening and exposure records where relevant to the offered packaging. A humidity indicator observation is a point-in-time observation associated with a particular bag; it should not be presented as a complete record of every condition the material has experienced. If a photograph was taken after opening, retain that context. Avoid collecting a visually attractive label image while losing the information needed to associate it with the actual shipment.
Storage conditions also need a scope. A statement that material was kept in a warehouse does not specify the conditions, monitoring period or handling process. Ask which records exist and what interval they cover. If history is unavailable, preserve that gap and let the receiving or assembly specialist determine what additional assessment is appropriate. This article does not prescribe a bake temperature, duration or recovery procedure. Those depend on the device, package, exposure and applicable instructions; applying a generic recipe can introduce a new problem instead of resolving the old one.
Build the handoff around the planned assembly event. The buyer needs to know which records must accompany the shipment, who will review them before use, and whether any identified condition changes the receiving plan. The assembler needs the actual packaging and handling information rather than a simplified sales description. Agree how discrepancies will be reported before material is consumed or mixed with other lots. Keeping packages and records associated until the review is complete makes a later investigation more practical, even when the original sourcing request was urgent and the quantity was small.
Choose inspection questions without pretending a test proves everything
Inspection should answer a defined question. A label and visual review can document observed markings, package condition and inconsistencies with supplied records. It cannot by itself establish the complete electrical behavior of every unit. An electrical check has a configuration, conditions, sample coverage and acceptance criteria. Passing that check does not automatically establish an uninterrupted supply chain, a complete lifetime history, or every performance specification in the datasheet. Treat the method, the result and the remaining uncertainty as separate fields.
Before requesting an inspection service, write down what decision the result is intended to support. Ask which samples or units would be covered, what identifiers will connect the report to the material, and which limitations will be stated. Agree the handling of inconclusive results and discrepancies in advance. A request for a generic test certificate is weaker than a scoped request that identifies the question, the material and the report requirements. This page does not offer a laboratory accreditation, guarantee a test capability, or claim that a particular inspection has been performed.
For programmable logic, a functional demonstration may depend on the programmed design, board, clocks, supplies and tool environment. A device that performs one task in one setup has not thereby passed every timing, temperature or package requirement of your product. Keep that distinction visible when evaluating an offered report. The exact-device tutorial helps preserve the ordering identity, while the legacy-notice guide addresses lifecycle evidence. Neither replaces the project-specific electrical and manufacturing acceptance work. Procurement can organize that work, but should not invent an engineering sign-off on its behalf.
A useful review conclusion can therefore be narrow: the supplied records cover the listed lot; the stated inspection covered the identified sample; a specific discrepancy remains unresolved. That is more actionable than writing authentic or approved without explaining the basis. If the offered evidence falls outside the agreed scope, send a focused clarification rather than expanding the conclusion to fit the deadline. The commercial consequence may be a hold, a different source, or an approved exception owned by the appropriate team. The evidence worksheet below intentionally generates questions and omissions, not a pass mark.
Use the evidence selector to make the gaps visible
Start the worksheet with the exact requested MPN and your actual quantity. Select only the circumstances that apply to the offer: unknown supply history, split lots, opened or repacked material, uncertain storage history, or an inspection report whose scope needs clarification. The output combines a common identity checklist with the questions triggered by those circumstances. It is a starting request you can review and edit. It does not decide whether the device is genuine, usable or acceptable for a specific application.
Try a hypothetical maintenance request for twenty-five components with two offered lots and an undocumented repacking event. The useful output is not a percentage risk score. It is a request for a lot-by-lot quantity allocation, records linking those lots to the supply history, the repacking details that are actually available, and a receiving decision before assembly. If the supplier cannot provide one of those items, keep the response beside the original question. That preserves the difference between not requested, requested but unavailable, and supplied for review.
The tool runs locally in the page. Generating or saving the text does not send it to FPGA.io, a supplier or a laboratory. Changing an input clears the previous result so that an older checklist cannot be mistaken for the current request. Use the plain-text fallback if scripting is unavailable: record identity and quantity, separate each lot, list source and packaging records, describe gaps, define the review owner, and state the acceptance decision still required. These steps are useful even when your organization already has a formal incoming inspection process.
Do not paste confidential customer names, full design files or private upstream documents into a shared URL. The component CTA carries only the reviewed MPN and quantity; the longer checklist is something you can submit through the agreed contact process after checking it. When no verified product page exists for an offered device, keep the inquiry factual rather than inventing a product recommendation. The examples linked here are engineering and procurement context, not inventory offers and not evidence about a lot currently held by a seller.
Prepare an evidence request
Local processing only. Nothing is submitted automatically.
Enable JavaScript for the worksheet, or use the static method below.
Static worksheet and method
Record exact MPN and quantity; separate lots; request source, packaging and storage records; state inspection scope and unresolved decision.
Turn the inquiry into a controlled receiving handoff
Before sending the RFQ, separate the items needed for a commercial response from those needed for material acceptance. A seller may be able to quote quantity and a proposed lead time while some traceability evidence remains under review. Record those states separately. Ask the seller to identify the exact MPN, offered quantity, lot structure, packaging condition, available supporting records and any stated limitations. Ask your internal reviewer which unresolved items prevent purchase or use. Do not allow a price response to imply that all quality conditions were accepted.
The request should also say whether substitutions are allowed. If they are, keep each proposed MPN on its own line and route it through a separate compatibility review. An old-date-code discussion is not a reason to merge a different package, voltage option or temperature grade into the original order. For example, the commercial and industrial Artix-7 comparison shows why a suffix question belongs in the technical record. That example explains an identity distinction; it says nothing about present availability, authenticity or storage condition of either part.
At receipt, reconcile the delivered quantity and identifiers with the agreed offer and the actual accompanying records. Escalate mismatches before the material is mixed into production inventory or consumed. Preserve the outcome and its scope so that a future buyer can understand why the lot was accepted, held or rejected. The exact records and retention requirements depend on your organization and application. This guide is a procurement workflow aid, not a substitute for a regulated quality system, a manufacturer's warranty terms or your agreed purchase conditions.
A component inquiry and a board project inquiry need different next steps. Use the component route when you have an exact MPN, quantity and evidence requirements. Use the project route when the shortage changes the board, assembly plan or validation work, and describe the controlled revision and decisions that need review. FPGA.io can receive that scope for evaluation; this page does not promise stock, test services, delivery or compatibility. The practical result is a request that another person can act on without guessing what the older date code was supposed to prove.
Source scope and editorial method
- Texas Instruments: Product shelf life — Official web guidance read 2026-11-03; TI-controlled storage versus customer storage. No universal age limit inferred.
- Analog Devices: Authorized distributors — Official web guidance read 2026-11-03; ADI channel/support scope only. No FPGA.io authorization claimed.
AI-assisted editorial preparation and second source/calculation review. Original workflow and hypothetical examples; no human engineering certification, laboratory result or customer case is claimed. Manufacturer sources support their stated technical scope, not the original cost model or a commercial offer.