PCBA Component Lot and Date-Code Traceability

PCBA component lot date code traceability connects component identities received from suppliers to the finished boards that contain them. For risk-critical assemblies, use board-and-reference traceability as the reference target: link 100% of fitted critical positions to a board serial and an identifiable source lot before release. Capture original labels, material changes and replacement history. Keep manufacturer lot codes, date codes and supplier shipment identifiers separate. A printed date code alone establishes neither the affected-board population nor a universal component expiry date.

Lot Codes and Date Codes Answer Different Questions

A manufacturer lot code identifies a production grouping within that manufacturer’s system; a date code identifies a defined time period or processing event. Buyers need both when available. Several lots can share a date code, and a shipment or container can include more than one production grouping. Neither identifier replaces the finished-board serial that makes individual assemblies searchable.

Preserve the original code before interpreting it. Check the manufacturer’s rule. A short alphanumeric marking is not automatically a four-digit year/week code, and even a familiar format needs the correct product-family and package context. Store the manufacturer and complete manufacturer part number, or MPN, alongside the code so identical strings from unrelated parts do not become one database record.

A documented flash-memory marking example distinguishes a package-assembly date in YYWW format from a mark-and-pack date in YWW format. Those dates describe different operations and can legitimately differ. Apply that convention only to the covered products; it is not a decoder for every semiconductor.

Age acceptance is a separate decision. Suitability depends on the product, packaging, moisture sensitivity and storage conditions. An older date code calls for the relevant handling evidence and purchase requirements, not automatic rejection or acceptance. Moisture exposure after opening also has its own clock.

Capture Original Labels Without Losing Supplier Context

Receiving records should preserve the original manufacturer identification together with the supplier transaction and the physical container received. Photograph readable labels, retain the decoded barcode payload and create searchable fields for manufacturer, full MPN, lot, date code, quantity and receipt ID. Keep the raw strings, including leading zeros, punctuation and letter case.

Store any decoded date separately. Record the manufacturer rule used to interpret it; normalization must not replace the original label value or silently turn a packing date into a manufacturing date.

A supplier’s replacement label must remain connected to the original evidence. Record the supplier name, purchase-order line, delivery reference and any manufacturer container or shipping trace code. If the received quantity spans several lots, give each lot-to-container relationship its own entry instead of compressing the information into a single convenient date.

Barcode capture and label capture serve different purposes. In one documented seal-date label format, the visible DDMMMYY field was not included in the associated 2D barcode. Scanning that barcode therefore would not capture every visible date. Define the required fields against the actual label format.

Assign a unique internal ID to each reel, tray, tube or cut-tape container used in production. Splitting a reel creates child-container IDs that retain the parent link and original lot information. A new internal ID does not create a new manufacturer lot.

For unclear labels, retain the image and record a material-identification exception for resolution before release to the affected operation. Do not reconstruct a missing lot code from the date code. If source identity cannot be established, the traceability requirement has not been met, even when the part number and quantity are correct.

Map Component Lots to Work Orders and Board Serials

Component genealogy requires a recorded path from the received material container through its actual use to the finished-board serial. A material issue to a work order establishes allocation; a placement or controlled assembly record establishes use. Keep that distinction explicit when evaluating a supplier’s traceability report.

The BOM defines the intended parts and reference designators. The component placement list, or CPL, defines component position, rotation and side. Neither file identifies the production lot actually consumed. The referenced supplier describes these separate input-file roles in its BOM and CPL guidance.

Use this record chain for the required positions:

Original manufacturer label + supplier receipt
    -> Unique material-container ID + preserved lot/date fields
    -> Work order + released BOM/CPL revision
    -> Feeder/load or manual-install event + reference designator
    -> Panel ID + cavity position, where panels are used
    -> Finished-board serial + original and replacement history

Each arrow represents a stored relationship that a query can follow. One lot can feed several work orders; one board can consume several lots. Preserve both directions. For a panel, map every populated cavity to its finished-board serial after separation. The panel barcode cannot identify loose boards without that mapping.

Choose the required depth

The following four practical options describe what the OEM can retrieve. They are purchasing descriptions, not IPC traceability-level names.

Start with board-and-reference traceability for the critical component set. The reference target is 100% of fitted critical positions, not a sample of boards or a percentage of BOM lines. Other components can use a less detailed, agreed record chain when the resulting containment population is acceptable.

The actual manufacturer and MPN must survive an approved substitution. A generic internal part number alone cannot show whether two boards received different approved alternatives. Preserve the original build baseline and the authorization that permitted the change.

Handle Mixed Lots, Reel Changes and Partial Consumption

Mixed lots require separate source identities, while reel changes require a verified consumption boundary. Record which material reached each required position, not merely when someone installed a reel. A reel ID identifies a physical supply container; it does not guarantee a single manufacturer lot or date code.

One documented packaging rule permits an intermediate pack to contain up to four date codes no more than 52 weeks apart. That specific allowance is neither a universal purchasing limit nor a shelf-life statement. Check the received label for multiple identities and apply the packaging and purchasing requirements relevant to the actual part.

If a container holds several lots without a recoverable component-by-component boundary, record the complete candidate-lot set. Exact single-lot assignment then requires a different material supply or a usable identification method. Assigning the newest date code to the whole reel would conceal the uncertainty and cannot satisfy an exact critical-position mapping requirement.

Capture the point of consumption

Give every material transition an event ID. Retain the old and new container IDs, feeder/slot, machine, work order, affected reference designators, event sequence and the last confirmed old-material and first confirmed new-material placements. Include timestamps with a timezone and a recorded operator or system identity. Time alone does not prove the boundary.

A splice can enter the feeder before it reaches the pickup point. Track its arrival at consumption. When buffered boards, skipped placements, feeder reloads or parallel machines interrupt the expected sequence, preserve the actual placement history and identify which boards could have received either material source. An unresolved interval requires a wider candidate-board set.

Consider this fictional example: work order WO-260923-01 uses one U7 per board. Reel RL-A contains lot L-A; reel RL-B contains lot L-B. Verified placement events identify B0042/U7 as the last placement from RL-A and B0043/U7 as the first from RL-B. The change record links those placements to the feeder event; it does not infer the boundary from the numerical order of the board labels.

If a change occurs inside a panel, retain cavity/reference detail. Marking the entire panel as “new lot” would erase the old-lot placements.

Keep remaining material and replacements connected

For a partially consumed reel, preserve its identity or a parent-linked child identity, remaining quantity and subsequent issue history. Reconcile issued material with placements, rejects, setup loss and returns. Quantity reconciliation detects missing records; it cannot locate individual placements by itself.

Record every replacement at the board serial and reference designator: removed identity, installed identity, reason, event time and authorization. Preserve both the original and current configuration. If B0045 later receives L-A at U7 during rework, a search for L-A must find B0045 even though its original line placement used L-B.

Use Traceability Records for Targeted Containment

Traceability records identify the boards that could contain a suspect component lot. The search must follow every material branch, including split containers, later work orders and replacement operations. A match identifies potential exposure; it does not establish the failure mechanism or authorize product release.

Start from the manufacturer’s actual suspect identifiers. Preserve the manufacturer, MPN and complete lot or shipment trace code, plus any stated date or location restrictions. Searching on date code alone can pull in unrelated lots or miss another identifier used by the manufacturer’s notice.

Follow the relationships in both directions:

1. Find all received containers and child containers matching the suspect identity.
2. Retrieve their material-use events across work orders, lines and manual operations.
3. Resolve those events to board serials and references, including replacements.
4. Separate confirmed installed material, historical removed material and unresolved candidate exposure.
5. Join the board list to shipment or higher-level product serials where that downstream mapping is required.

Return the reason each board entered the result and the evidence supporting any exclusion. Check completeness first. If a reel transition or repair record is missing, a query returning no rows cannot establish that no boards were exposed. Keep an ambiguous candidate in the result until the relevant link is resolved.

Before production release, test one backward lookup from a board and one forward lookup from a component lot. Include the transition and rework examples in that demonstration. An order-level material report cannot demonstrate board-level resolution. The quality team then uses the resulting population in its separate containment and disposition process.

Define a Record Request That Matches Product Risk

A PCBA component lot date code traceability request should define the covered positions, required links, change events, export format and acceptance check before the build. For critical positions, specify the 100% board-and-reference coverage target explicitly. A general promise of “full traceability” does not identify what the supplier will capture or what the OEM can retrieve.

Use the following request matrix during the manufacturing review. The entries describe required content, not a completed supplier audit.

For example, ten boards each fitted with critical positions U1, U7 and Q3 require 30 resolved position links. With only 29, coverage is 29 / 30 × 100% = 96.7%, below the 100% target. Count the fitted release configuration, including approved replacements. Document legitimate do-not-populate positions separately. Resolve missing links before release, or process a specifically authorized deviation that states the lost resolution; the deviation does not turn incomplete coverage into 100%.

Specify interfaces and applicable standards

An export can use CSV or JSON with separate material, event and board records joined by stable IDs. Define each field and whether it can have multiple values. Preserve multi-lot relationships as separate records, and keep identifier columns as text so leading zeros survive spreadsheet import. Corrections need a history. Retain the previous value, replacement value, reason and responsible operator or system. A PDF report can aid review, but does not replace a queryable record set when that is the requirement.

IPC-1782 addresses manufacturing and supply-chain traceability with requirements selected around agreed risk. Specify the contractual revision and required scope instead of assuming an assembly class automatically defines all traceability fields. IPC-1782 public scope Moisture handling is a different subject: IPC/JEDEC J-STD-033D addresses handling, packing, shipping and use of sensitive devices, rather than a universal expiry rule derived from a date code. J-STD-033D public contents

Set record retention in the actual agreement: duration, starting event, included record types, retrieval obligations and access after a supplier or system change. Define record ownership too. Align the schedule with product support and applicable obligations. A manufacturer’s internal retention practice is not automatically the PCBA supplier’s commitment to the OEM.

Apply the Record Depth to Five Build Scenarios

Traceability depth should follow the cost and consequence of losing component-to-board identity. The same factory can support projects with different record requirements, but each project needs an explicit scope. These five scenarios show where the links matter most.

Choose the simpler depth only when its larger suspect population is acceptable. Include manual work. For high-consequence positions, confirm that capture continues through manual installation, offline rework and service replacement, because an automated placement record covers only the operations that actually feed it.

Frequently Asked Questions

PCBA buyers should distinguish source identity, production history and acceptance conditions when reviewing lot and date-code records. The answers below apply those distinctions to the purchasing decisions that determine whether a board can be traced after delivery.

Prepare the Traceability Review Before the Build

A useful traceability review starts with the released BOM/CPL, critical component list, board-serialization plan and required record fields. For a build discussion with JASPER, bring those inputs together with any date-code purchasing restrictions and the required retention terms. Review the scope alongside PCB assembly services.

Ask for a sample record export showing one reel transition and one replacement. Verify that a board lookup returns its source identities and that a lot lookup returns every relevant board. Agree the required depth and acceptance evidence before materials enter production.