How to Set a Product Retention Sample Program With Your Supplier
When a complaint arrives months after delivery, teams often search for “a sample” and find only an old marketing photo, a damaged unit with no lot code, or an unopened carton whose product version is unknown. That makes comparison harder than it needs to be. A product retention samples program keeps identified physical examples and the records needed to explain what they represent.
A product retention samples program is an operational control for retaining a defined sample, linking it to the product and lot records, controlling access, and testing whether the team can retrieve it. It does not prove that every unit in the shipment matches the sample. It does not replace required testing, a certificate, a recall process, or product-specific legal advice.
For a product retention samples program, retain the evidence, not just the item; the product retention samples program record must stay retrievable.
Table of contents
- Why should an importer keep retention samples?
- What question should a product retention samples program answer?
- How should a retained sample be identified?
- Who should store the samples and records?
- How should samples be stored and accessed?
- Which records should be linked to every sample?
- How can a retrieval drill test the program?
- Which changes should reopen the retention-sample file?
- What are the limits of a retention sample?
- Frequently asked questions
Why should an importer keep retention samples?
A stored physical sample can help a buyer compare a returned item, complaint photo, safety concern, test finding, supplier notification, packaging issue, or customer question with a known product version. The benefit does not come from putting a random box on a shelf. It comes from the link between the sample and its product identity, production history, delivery, and related evidence.
A product retention samples program can make an investigation more disciplined. If a supplier tells you that a component lot may be affected, the team can find the retained finished-good sample, confirm its product configuration, review the bill of materials, and locate the associated shipment and inventory records. If the sample cannot be linked to a lot or configuration, it has far less comparison value.
CPSC’s tracking-label guidance gives a specific U.S. children’s-product example of why identification matters. It says tracking marks must make information ascertainable about manufacturer/importer/private-labeler identity, production location and date, manufacturing-process detail such as batch or run information, and other source-identifying information. [1] CPSC says these labels can improve recall effectiveness and help identify products that may contain a component identified as a hazard source. [1]
That tracking-label rule has a defined legal scope. For other products, use the same logic as an internal evidence control, not as a claim that every import needs the same mark or sample arrangement.
In a product retention samples program, a stored sample without a record is a mystery item.
What question should a product retention samples program answer?
Design the program backward from the investigation you may need to run. Do you want to compare a complaint item with the as-sold label? Determine whether a production run used a particular component? Confirm which packaging revision reached a market? Support a qualified laboratory’s review? The answer decides which sample, records, and storage controls are useful.
For a product retention samples program, write the questions before choosing a sample count or shelf. A small importer may need a simple as-received product and package sample linked to each material product version. A more complex supply chain may need separate supplier-side production samples, importer-side inbound samples, and laboratory sample records. The right design depends on the product, risk, business system, market, and agreement.
| Program purpose | Sample or evidence focus | Records that should connect | Limitation to state clearly |
|---|---|---|---|
| Compare customer return with known shipped product | As-received or as-sold product and packaging | Product photos, SKU, label version, lot, order and warehouse receipt | One retained unit does not prove every customer unit is identical |
| Investigate a supplier component issue | Finished-good sample and component relationship | BOM version, component lot, supplier batch, production record, test evidence | A sample may not contain the suspected component unless the record says it does |
| Check artwork or packaging change | Product, inner package, carton, instructions, label placement | Approved artwork, print proof, date, lot, product version | A sample does not prove every print run used the approved art |
| Support a quality or lab review | Sample that is identified and controlled before transfer | Sample intake, condition, chain-of-custody/access log, test request | A retained sample is not automatically an authorised test sample |
| Prepare for traceability investigation | Lot-linked product sample with supply-chain records | Supplier lot, importer lot, shipment, warehouse and outbound records | Sample retention does not replace a full recall or notification process |
A product retention samples program should name what it cannot answer. This prevents a buyer from treating a reference unit as conclusive evidence in a technical, legal, or recall decision.
For a product retention samples program, purpose determines the sample; write that purpose into the product retention samples program file.
How should a retained sample be identified?
In a product retention samples program, the sample label should help a future reviewer find the supporting record without guessing. It may use a physical label, sealed bag, container tag, barcode, QR identifier, or other controlled method, depending on the product and storage environment. The method should be legible and durable enough for the program’s intended use, but no universal medium or format is right for every product.
At intake, the product retention samples program should connect the sample to the product model/SKU, product version, lot/batch/run, factory or production location, production date or range, supplier, component or bill-of-material revision where relevant, destination/label version, sample source, intake date, photographs, and storage location. Record whether the item is unopened, opened, inspected, returned, conditioned, tested, or otherwise altered.
FDA’s food traceability guidance gives a narrow but useful example of record linkage. It defines a traceability lot code as a descriptor, often alphanumeric, that uniquely identifies a lot within the code source’s records. It describes linking the code to related information on documents or in the same electronic record. [2] The FDA material is food-specific and does not create a general imported-product sample rule. It does show why the identifier and its associated records must work together.
| Sample-identity field | Why it belongs in the record | Example control question |
|---|---|---|
| Sample ID | Provides one internal reference for the physical unit and database row | Does the container, photograph, access log, and document index use the same ID? |
| Product/SKU and configuration | Separates products that look similar but have different materials or functions | Does the retained sample match the product version sold or shipped? |
| Lot/batch/run | Connects the unit to production and traceability records | Can the supplier and importer both decode or cross-reference it? |
| Factory and date | Helps identify production source and time window | Is the location and date recorded from a controlled record rather than memory? |
| BOM or component version | Links a finished good to potentially relevant parts or materials | Is the component revision the one used in the retained unit? |
| Market and artwork version | Captures destination-specific label, instructions, or claims | Does the sample show the final market-facing artwork? |
| Intake condition and photos | Records the sample state before later access or analysis | Is packaging sealed, damaged, opened, or incomplete at intake? |
| Storage location and owner | Makes retrieval possible after personnel changes | Can a second person find it from the record alone? |
For a product retention samples program, do not write vague descriptions such as “black charger sample” or “approved product.” A product retention samples program needs identifiers that distinguish model, lot, and version, especially when colors, materials, firmware, labels, or suppliers change.
Who should store the samples and records?
In a product retention samples program, a supplier and importer can each hold part of the evidence, but neither should assume the other will preserve it. The supplier is often best positioned to retain a production-side sample and manufacturing records. The importer may be best positioned to retain the as-received or as-sold sample, inbound documents, local packaging, warehouse records, and market-facing label. A laboratory may retain test materials under its own agreement, but that arrangement is different from an importer retention file.
For a product retention samples program, assign each sample an owner, physical location, access authority, and intended purpose. Record whether the supplier sample is from production, whether the importer sample came from the received shipment, and whether a laboratory sample was tested, consumed, or retained independently. Do not call three different samples “the retained sample” without distinguishing them.
| Sample holder | Useful role | Core record to retain | Handoff control |
|---|---|---|---|
| Supplier | Production configuration, batch/run, component and assembly context | Production/batch record, BOM, factory photos, supplier lot | Supplier confirms identity and notifies importer before any change or disposal under the agreement |
| Importer | As-received or market-facing configuration and shipment link | Receipt record, entry/shipping records, warehouse location, product photos | Intake log records date, condition, quantity, lot, and storage place |
| Laboratory | Test specimen and test process evidence | Laboratory agreement, sample receipt, test request, report/chain records | Confirm whether samples are returned, retained, consumed, or disposed under the laboratory process |
| Distributor or retailer | Downstream packaging and sale-channel evidence where agreed | Channel SKU, shipment and allocation records | Keep boundaries and data-access rights clear in the commercial agreement |
For covered U.S. children’s products, CPSC says tracking marks may help identify products associated with a component that has been identified as a hazard source. [1] That makes a supplier-held production sample and an importer-held received sample potentially complementary. They can show different sides of the same traceability chain.
For a product retention samples program, ownership should be written down.
How should samples be stored and accessed?
In a product retention samples program, storage is about preserving comparison value. A sample crushed under unrelated cartons, exposed to unsuitable conditions, stripped of its original label, or borrowed without a log loses value. The right storage conditions depend on the product and its intended investigation purpose. Do not impose temperature, humidity, quantity, or duration rules without product-specific analysis.
At intake, photograph the unit and packaging, record condition, apply the internal sample ID, place it in the designated storage location, and record access restrictions. If the product needs product-specific environmental control, safety measures, or separate treatment, obtain that direction from the relevant qualified source instead of copying a general warehouse rule.
A product retention samples program should control access. Every removal, opening, inspection, transfer, test request, return, or disposition should be recorded. The record needs the requester, reason, date, person who approved release, condition at release, receiving party, purpose, and final result. That log preserves the difference between an untouched comparison sample and one that has been opened or tested.
| Access event | Record before the event | Record after the event | Why it matters |
|---|---|---|---|
| Visual inspection | Sample ID, requester, purpose, location, condition | Reviewer, observations, new photos if needed, seal/package status | Keeps ordinary inspection from becoming an undocumented alteration |
| Transfer to laboratory | Approval, test request, sample photos, condition, shipping reference | Laboratory receipt, test status, return/disposition, report link | Connects the tested unit to the evidence file |
| Supplier comparison | Supplier request, claimed lot/configuration, access authority | Supplier findings, documents reviewed, any sample handling | Stops an unverified party from changing the sample state |
| Product complaint review | Complaint ID, product/lot question, review owner | Findings, comparison photographs, records located, follow-up owner | Separates facts from conclusions about a customer issue |
| End of retention decision | Owner, reason, applicable agreement/policy, condition | Approved disposition, date, person, record preserved | Prevents routine disposal from erasing a relevant sample history |
A product retention samples program is not a reason to ship suspect goods, open a damaged battery, destroy a sample, or perform a safety test without appropriate authority. If an actual incident, regulator contact, or recall question exists, preserve evidence and obtain qualified advice for the specific facts.
Which records should be linked to every sample?
A product retention samples program without a digital or paper file creates a retrieval problem. The product retention samples program record should link the sample to upstream evidence, movement history, and any later investigation. Use an internal folder or database that a trained backup owner can access, not one employee’s private drive.
The file may include supplier confirmation, product specification, photos, approved bill of materials, production record, lot/batch/run record, inspection record, test-report reference where relevant, label and package artwork, packing list, commercial invoice, transport documents, warehouse receipt, inventory lot, outbound allocation, customer or distributor information where appropriate, access log, drill result, and change history.
| Record group | Example contents | Retrieval question it answers |
|---|---|---|
| Product identity | SKU, model, configuration, photos, BOM, claims, label/packaging revision | What is this sample, exactly? |
| Supplier and production | Factory, batch/run, date, component traceability, inspection information | Where and when was it made, and with which inputs? |
| Testing and technical evidence | Test-request link, report, laboratory identity, sample reference, known limits | What was tested, and did the test sample match this configuration? |
| Shipment and receipt | Packing list, invoice, shipping reference, container/airway bill, receipt record | Which incoming goods did the importer receive? |
| Warehouse and distribution | Location, internal lot, stock movement, distributor/channel allocation | Where did related goods go, and what remains? |
| Sample custody | Storage location, access log, condition checks, transfers, disposition | Who handled this sample and what happened to it? |
| Change control | Product, supplier, factory, material, label, market, and process changes | Does the retained unit still represent the current product? |
For a product retention samples program, keep an evidence index that states which record is authoritative when duplicate documents exist. A current bill of materials should not silently replace the version that describes the stored sample.
For a product retention samples program, link before you need it.
How can a retrieval drill test the program?
A product retention samples program retrieval drill asks the team to recover evidence under a controlled scenario. Choose a stored sample, a supplier lot, a complaint photo, or a hypothetical component issue. Then ask the team to locate the sample, decode the lot, find the product version, identify supplier and import records, state the sample condition, and show what inventory or distribution records are linked.
CPSC’s recall guidance provides a broader library of recall materials, including a recall checklist, guidance on conducting a recall, initial-report information, recall-handbook materials, notification resources, reverse-logistics guidelines, and recall-effectiveness tools. [3] A retention sample supports an investigation inside that broader process. It does not replace a recall plan or decide whether a recall is required.
For product retention samples program drills, document the starting question, owner, time, records requested, sample location, condition, links found, unresolved gaps, and corrective actions. Do not impose a generic speed target. Accuracy, completeness, and repeatability matter more than a claimed number of minutes.
| Drill question | Expected evidence | Gap that requires correction |
|---|---|---|
| Can we locate the physical sample? | Storage location, sample ID, owner, current condition | Location record is obsolete or only one person knows it |
| Can we identify its product version and lot? | SKU, photos, batch/run, production/date record, BOM version | Sample label is vague or factory and importer codes do not cross-reference |
| Can we link it to received goods? | Packing/transport data, receipt, internal inventory lot | Sample was retained but never connected to shipment or warehouse record |
| Can we identify related inventory and distribution? | Warehouse location, outbound lot allocation, channel record | System tracks SKU but loses lot relationship |
| Can we explain whether it is untouched? | Access log, seal/condition record, transfer/test information | Unit was borrowed, opened, or tested without a documented event |
Run the drill after a product or system change and on a schedule that suits the business’s risk process. For a product retention samples program, the aim is to uncover missing links while the shipment, supplier, and documents are still accessible.
Which changes should reopen the retention-sample file?
In a product retention samples program, a retention sample can become a historical artifact without becoming useless. The problem is calling it representative of a new product when materials, components, factory, assembly process, product version, firmware, label, packaging, market, code format, or supplier has changed.
For a product retention samples program, treat each material change as a review trigger. Record the old sample’s scope, the new product fact, responsible reviewer, decision, and any new sample needed. Keep the prior sample and its records as historical evidence unless the agreed policy calls for a controlled disposition. Do not overwrite the sample ID or change the label to make a new item appear to be the old one.
CPSC’s third-party testing guidance gives a specific example for covered U.S. children’s products: a material change can require retesting for affected rules and a new CPC. [4] A retention sample does not replace that testing obligation. It can help the team compare the prior and changed configuration while a qualified party determines the applicable evidence route.
| Change | Why review is needed | Retention control |
|---|---|---|
| New material or component source | The stored sample may not represent current construction | Link the new BOM/component lot and decide on a new representative sample |
| New factory or line | Production traceability and process context have changed | Create a separate factory/line record rather than mixing histories |
| Product revision or firmware change | Function, user interface, performance, or safety evidence may differ | Retain the previous version and label the new version distinctly |
| New package, label, or destination | As-sold warnings, instructions, responsible party, or claims may differ | Store the market-specific package or evidence file with destination label |
| Supplier code or ERP change | The old lot may no longer decode through the new system | Maintain a crosswalk and test retrieval of both code formats |
| Storage site or provider change | Sample location and access process can be lost | Reconcile transfer inventory, photos, access authority, and condition at move |
A product retention samples program should make history legible, not erase it.
What are the limits of a retention sample?
A retained unit helps identify and compare. It does not establish that all goods in a lot are identical, prove a test result, determine a product’s safety, make a formal recall decision, or fulfill every documentation duty. The sample can be damaged, unrepresentative, altered during access, or outside the issue under investigation.
The CPSC tracking-label guidance relates to children’s products. [1] The FDA traceability-code example relates to the food traceability context. [2] The CPSC recall resources address wider recall activities. [3] None creates a universal legal requirement for every import to hold a defined number of retention samples.
Seek qualified product-safety, laboratory, legal, or regulator guidance when a real complaint, safety event, test failure, regulator question, or potential recall occurs. Preserve the product, records, and access history. Do not alter, destroy, test, or release the sample based on a generic article.
For a product retention samples program, the sample is evidence, not an answer. This product retention samples program treats the record link as equally important.
Frequently asked questions
What is a product retention samples program?
A product retention samples program is a controlled process for storing identified product samples and linking them to product, lot, supplier, shipment, and access records. It can support a later investigation but does not replace testing, certification, or a recall procedure.
Should the importer or supplier keep the sample?
Both may hold useful evidence. A supplier can retain a production-side sample and manufacturing records, while an importer can retain an as-received or as-sold sample and shipment records. Define ownership, location, access, and purpose for each sample.
How many retention samples should I keep?
There is no universal number. Decide based on product risk, lot definition, product configuration, intended investigation use, storage practicality, market obligations, and your agreement. Do not copy a sample count from an unrelated product category.
What should be written on a retained-sample label?
Use an internal ID linked to the product SKU/model, version, lot or batch, factory, production date/range, sample source, intake date, storage location, and supporting photos or records. Keep the detail in the controlled record if label space is limited.
Does a retained sample need to be unopened?
It depends on the program purpose. An unopened sample can preserve an as-sold comparison state; an opened or inspected sample can still be useful if its condition and access history are documented. Do not treat them as identical.
Can a retention sample replace a test report?
No. A physical sample may support an investigation or later qualified test request, but it does not provide a test result or establish compliance with a product rule.
What is the difference between a retention sample and a laboratory sample?
A retention sample is stored for future identification or comparison. A laboratory sample is transferred under a defined test request and may be consumed, conditioned, altered, or retained under the laboratory’s process. Link them when they are the same unit, but do not assume they are interchangeable.
Why should sample access be logged?
An access log records who removed, opened, inspected, transferred, tested, or disposed of the unit and why. It protects the difference between an untouched reference sample and one whose condition has changed.
Do retention samples help with recalls?
They can support product identification and investigation, especially when linked to lot and distribution records. CPSC says tracking labels can improve recall effectiveness for covered children’s products, but retention samples are only one part of a broader recall process. [1] [3]
What changes should trigger a new sample review?
Review when materials, components, supplier, factory, process, product version, software, label, package, destination, lot-code system, or storage arrangement changes. Keep historical samples separate from new configurations.
What should I do if a safety issue involves a retained sample?
Preserve the unit, records, photographs, and access history. Do not alter or destroy it. Seek qualified product-safety, laboratory, and legal guidance for the specific product and market before taking further action.
References
[1] U.S. Consumer Product Safety Commission, Tracking Label Business Guidance
[2] U.S. Food and Drug Administration, Traceability Lot Code
[3] U.S. Consumer Product Safety Commission, Recall Guidance
[4] U.S. Consumer Product Safety Commission, Third Party Testing Guidance
Related reading
Continue with lot coding traceability recall, accredited testing lab selection, magnetic toy compliance, and customs detention release planning.