A China supplier may send a document called a UN 38.3 report, a lithium battery test summary, a laboratory file, a product specification, a battery data sheet, or an email stating that a battery passed testing. These records can help a buyer identify what the supplier says about a battery or product. They do not, by themselves, determine a transport classification, packaging instruction, mark or label, shipper role, carrier acceptance, or shipment release.
China supplier lithium battery test summary evidence is buyer-side evidence that links a buyer item/version, battery or product model, supplier legal entity/site, stated battery chemistry and attributes, supplier-provided test summary, test-report reference, laboratory information, source record/date, product association, shipment association, and buyer owner. It does not establish that a cell or battery meets UN 38.3, that a test summary is complete, that a product is eligible for a transport path, that packaging or marking is correct, that a party is an offeror, that a carrier will accept a shipment, or that a shipment may be released.
The record should preserve supplier facts and their limits. Decisions about testing, summary completeness, transport classification, packaging, marks, labels, shipper or offeror roles, carrier acceptance, shipment documentation, product disposition, and release remain with qualified responsible functions.
Keep supplier test records separate from transport decisions
PHMSA says that lithium batteries must undergo a series of design tests under subsection 38.3 of the UN Manual of Tests and Criteria and publishes guidance on the lithium-battery test-summary requirement.1 This explains why buyers and distributors often request source records from a battery supplier. It does not mean that every supplier document resolves all transport questions for a particular product or shipment.
49 CFR 173.185 describes the testing and test-summary context for lithium cells and batteries. In the stated scope, manufacturers and subsequent distributors of specified cells or batteries must make a test summary available, and the provision lists required summary elements.3 A buyer can organize the supplier-provided source information related to those fields without deciding that a test summary is complete or that the transport requirements for a shipment are met.
PHMSA Interpretation 22-0044 draws a useful boundary. In the scenario addressed, PHMSA said a general manufacturer statement that attested to UN 38.3 testing but did not contain all required information did not satisfy the obligation to make a test summary available.2 A supplier declaration may still be a source record. It should not be labeled a complete summary simply because it contains a broad assertion about testing.
Set the evidence boundary before collecting battery files
A supplier file can identify a battery or product model, chemistry, stated attributes, laboratory, test-report reference, or product association. It can help a qualified reviewer find source information. It cannot establish a transport classification, complete summary, correct packaging, proper mark/label, shipper role, carrier acceptance, or release status.
| Buyer review subject | A supplier record can identify | A supplier record cannot establish |
|---|---|---|
| Buyer item/version | Buyer-stated commercial scope | Transport classification |
| Supplier legal entity/site | Stated source of information | Shipper or offeror role |
| Battery/product model | Supplier-stated product identity | Applicability of a transport path |
| Test summary/report | Supplier-provided source file | Complete summary or test adequacy |
| Laboratory information | Supplier-provided laboratory detail | Laboratory or test approval |
| Chemistry/attributes | Supplier-stated battery information | Correct packaging or marking |
| Product/shipment association | Stated product or transaction link | Carrier acceptance or release approval |
Use factual wording. “Supplier supplied summary TS-21 for battery model B-17” is a record entry. “Battery model B-17 is cleared for air shipment” is a transport conclusion that a supplier file cannot make.
Define item, battery model, test source, and association scope
Start with the buyer item or SKU, current version, product description, and battery or product model. Add the supplier legal entity and manufacturing site that supplied the record. Then capture supplier-provided test-summary and test-report references, laboratory information, stated chemistry and attributes, source record/date, product association, shipment association, and buyer owner.
A buyer product may have a retail SKU, while the supplier test document names a battery model or product model. A battery can be installed in more than one product. Do not assume a document covers a buyer item because the product category appears similar. Preserve the product relationship stated in the source and show any version or model mismatch as an open condition.
| Scope field | Buyer record purpose |
|---|---|
| Buyer item/SKU and version | Identifies buyer-stated product scope |
| Buyer product reference | Identifies buyer baseline |
| Battery/product model | Identifies supplier-stated source scope |
| Supplier legal entity/site | Identifies information source |
| Test summary/report | Identifies supplied evidence object |
| Laboratory information | Identifies supplier-provided laboratory detail |
| Chemistry/attributes | Identifies supplier-stated battery information |
| Source file/date | Identifies traceable evidence object |
| Product/shipment association | Identifies stated relationship |
| Buyer owner | Identifies responsible follow-up route |
Ask for facts, not a shipping determination
A buyer can ask a China supplier to identify the product and battery model/version, supplier legal entity/site, available test-summary and test-report references, laboratory information it can provide, chemistry and battery attributes it can provide, source document/date, product association, shipment association, and a contact for clarification. The supplier can also identify records it does not maintain or cannot share.
The request should not tell the supplier to decide transport classification, packaging, marking, labeling, shipper or offeror role, air eligibility, carrier acceptance, or release. PHMSA’s rules and interpretation describe separate transport obligations and required test-summary information in their stated contexts.2 A sourcing record should preserve the supplier file and route the transport question to the qualified function.
| Supplier-stated evidence | Buyer question | Review limit |
|---|---|---|
| Battery/product model | Which model/version does the supplier identify? | It does not classify for transport |
| Supplier/site identity | Which entity and site supplied the record? | It does not identify an offeror |
| Test summary/report | What source file and report reference are supplied? | It does not establish completeness or adequacy |
| Laboratory information | What laboratory details are supplied? | It does not approve a laboratory |
| Chemistry/attributes | What battery detail does the supplier state? | It does not choose packaging or markings |
| Product association | Which buyer product is linked by the supplier? | It does not establish a shipment path |
| Shipment association | Which transaction is stated? | It does not authorize carrier acceptance or release |
Keep related records separate
Supplier evidence, test-summary completeness review, test adequacy review, transport classification, packaging and marking review, shipper or offeror role, carrier acceptance, shipment documentation, legal review, supplier status, product disposition, and shipment release are separate records. They may all concern the same battery, but they do not have the same owner or conclusion.
49 CFR 173.185 identifies elements including manufacturer and contact information, laboratory information, unique test-report identification, test-report date, a description of the cell or battery, tests and results, relevant manual references, and a responsible-person name and title in the stated test-summary requirement.3 A buyer evidence map can store supplier-provided information associated with these fields. It should not declare that the record satisfies each element or that it is suitable for a particular shipment.
| Evidence object | Factual relationship to capture |
|---|---|
| Supplier product record | Supplier-stated item/version and source file |
| Battery/test source | Supplier-provided summary or report reference |
| Laboratory record | Supplier-provided laboratory information |
| Chemistry/attribute record | Supplier-stated battery detail |
| Product association | Supplier-stated battery/product relationship |
| Summary review | Separate qualified completeness review |
| Transport/package record | Separate controlled transport review |
| Carrier/release record | Separate controlled action or decision |
Map evidence to the exact battery and product version
Place the buyer item/version and battery or product model at the center of the evidence map. Link supplier legal entity/site, test-summary or report reference, laboratory information, stated chemistry/attributes, source record/date, product association, shipment association, and buyer owner. This lets another reviewer distinguish a source file from a conclusion about transportation.
China supplier lithium battery test summary evidence is useful when it makes the battery/product connection visible. A supplier may provide a test-summary source for a battery model, but a qualified review still needs to decide what that record means for the current product configuration and transportation process.
PHMSA’s interpretation says a complete test summary contains all the required information identified in the regulation in the scenario at issue.2 A buyer record can identify the fields the supplier supplied and any fields that appear absent or unclear. It should not make the final determination that a summary is complete, compliant, or sufficient for transport.
Preserve gaps without making transport conclusions
An unclear buyer or battery version, missing test summary, test/product mismatch, unclear laboratory identity, absent model association, unclear chemistry or attributes, missing shipment association, uncertain status, or unassigned owner needs a neutral record entry. The entry describes the evidence condition without deciding shipping eligibility or compliance.
| Record condition | Neutral buyer statement | It does not mean |
|---|---|---|
| Buyer/battery version is unclear | Supplier file does not identify a clear buyer model link | Battery is prohibited from transport |
| Test summary is missing | Supplier did not provide requested summary source | Testing never occurred |
| Test/product link is unclear | Source file lacks a clear buyer-product association | Report is invalid |
| Laboratory identity is incomplete | Supplier record lacks requested laboratory detail | Laboratory is unacceptable |
| Model association is absent | Battery record is not linked to a stated buyer item | Product cannot ship |
| Chemistry/attributes are unclear | Supplier source needs factual clarification | A packaging rule is selected |
| Shipment link is absent | Supplier file is not linked to a stated shipment | Carrier will reject or accept shipment |
| Owner is unassigned | Follow-up route is not recorded | Release is authorized |
| ## Use a restrained buyer review sequence |
Start with the buyer’s current product baseline. Record the buyer SKU, version, product description, and the identified battery or product model. Identify the supplier legal entity and site that supplied each file. This avoids treating an old test summary, a different battery variant, or a record from another supplier site as evidence for the current product.
Capture the supplier’s facts as supplied. Record the summary or report source, laboratory information, stated battery chemistry and attributes, product association, source date, and stated shipment link. Preserve original source files. A working translation can help a buyer route a question, but it does not turn a supplier document into a transport classification, a packaging decision, or a carrier acceptance.
Then name the owner of the next question. A responsible function may need to reconcile a buyer product with a battery model, evaluate a source summary, review a transport classification, confirm packaging or marking processes, or obtain carrier guidance. The evidence sheet should identify this route instead of using a generic status such as “UN 38.3 approved for shipping.”
| Review step | Buyer action | Boundary kept intact |
|---|---|---|
| Establish baseline | Identify item, version, and battery/product model | Does not classify the shipment |
| Identify source | Record supplier entity, site, file, and date | Does not identify offeror role |
| Capture statement | Preserve supplied test/lab/attribute information | Does not determine test adequacy |
| Map association | Link source file to battery, product, or shipment | Does not select packaging or marking |
| Surface gap | Log unclear or absent relationship | Does not decide carrier acceptance |
| Assign route | Name responsible owner and question | Does not authorize release |
The result is a more reliable handoff. A transport reviewer sees what the supplier supplied, which battery/product it refers to, and where a connection is still missing. The buyer does not need to solve the transport question in a sourcing spreadsheet.
Build a compact China supplier lithium battery test summary evidence record sheet
A compact record sheet should make source files retrievable without turning into a shipping approval form. It should identify the buyer item, battery model, supplier source, and open condition. Do not use it to label a battery tested, classed, packed, accepted, or released unless a separate controlled process has made that action or decision.
| Field | Example factual entry |
|---|---|
| Buyer item/version | Buyer SKU and controlled version reference |
| Buyer product reference | Current product specification or model |
| Battery/product model | Supplier-stated model reference |
| Supplier source | Supplier-stated legal entity and site |
| Test summary/report | Supplier-provided file and report ID |
| Laboratory information | Supplier-provided laboratory detail |
| Chemistry/attributes | Supplier-stated battery information |
| Product association | Supplier-stated battery/product link |
| Source record | File name, date, and supplier contact |
| Shipment association | Supplier-stated product/shipment link |
| Open condition | Missing detail, mismatch, or unclear relationship |
| Buyer owner | Function responsible for follow-up |
The test-summary provision in 49 CFR 173.185 identifies a unique test-report ID, test-report date, description of the cell or battery, tests and results, references, and responsible-person information in the stated requirements.3 A buyer record sheet can give source material a clear place. It does not decide whether every required field is present or correct.
Keep a generic supplier declaration separate from a test summary
PHMSA’s Interpretation 22-0044 addressed a situation in which a manufacturer supplied a statement that its cells and batteries had been successfully tested under UN 38.3, but the statement lacked all information required by the test-summary provision. PHMSA said that this did not meet the stated requirement to make a test summary available.2
That distinction is practical for buyers. A supplier declaration can be preserved as a declaration. A test-summary document can be preserved as a supplied record. The evidence log should not use the same status for both. It should identify the actual source document and route questions about required information to a qualified transport function.
China supplier lithium battery test summary evidence should keep the battery/product association exact. A source file that names a related battery, an older model, or a laboratory report without the buyer item link may still matter. It should be logged with its known relationship and an open condition, not treated as a completed shipping file.
Make handoffs readable for qualified owners
A useful handoff identifies the buyer item, battery model, source records, and unresolved question. Product or technical functions may need to compare a supplier battery specification to the current product configuration. A transport function may need source files and the proposed mode/process. Legal or compliance functions may need a factual record without an assumed shipping conclusion. Supplier-management staff may need to resolve the supplier/site or document-version relationship.
| Owner route | Question a buyer record can present |
|---|---|
| Product/technical function | What current product and battery relationships are documented? |
| Test-summary review function | What supplier source records are available for qualified review? |
| Transport-classification function | What factual battery/product information is available? |
| Packaging/marking function | What product and battery attributes are supplied? |
| Shipper/offeror function | What source information is available for its controlled process? |
| Carrier/logistics function | What product and battery associations are documented? |
| Legal/compliance function | What factual records and open questions need review? |
| Quality/supplier management | Which supplier entity/site and source file apply? |
| Disposition/release authority | Is a separate controlled decision recorded for item state? |
A complete China supplier lithium battery test summary evidence record allows a buyer to seek clarification from the China supplier while retaining transport and release decisions for the functions that own them.
Avoid predictable record-control failures
Do not rely on a document title. A supplier file called “UN38.3 certificate” may be a test report, a test summary, a declaration, a commercial document, or a partial scan. Record the issuer, source date, battery/product model, laboratory information, and stated relationship. If the link to the buyer item is unclear, show that condition.
Do not treat a lab name as proof of a transport outcome. Laboratory information can identify a source. It does not determine test adequacy, transport classification, packaging, marking, carrier acceptance, or release. Keep the laboratory record separate from those decisions.
Do not reuse an old battery record across a product change without mapping it to the current version. A buyer may keep the same retail SKU while changing battery model, cell arrangement, or supplier. The evidence log should show the actual product/battery relationship in the supplier source and route unclear links.
Do not combine supplier approval with shipping status. A supplier can be acceptable in a buyer’s vendor process while a product/version has unresolved battery records. A test summary may be available while transport classification or packaging questions remain. Keep supplier status, evidence, logistics actions, disposition, and release separate.
Frequently asked questions
Does a China supplier’s UN 38.3 statement replace a lithium battery test summary?
No. In its Interpretation 22-0044, PHMSA said that a general manufacturer statement without all required information did not satisfy the stated requirement to make a test summary available in the scenario addressed.2 Preserve the supplier statement as a source file and route questions about completeness to the qualified owner.
What can a buyer request from a China battery supplier?
Request product and battery model/version, supplier legal entity/site, available test-summary and test-report references, laboratory information, chemistry and attributes it can provide, source file/date, product association, shipment association, and a follow-up contact. Do not ask the supplier to decide transport classification, packaging, markings, shipper role, carrier acceptance, or release outside its role.
Does a lithium battery test summary authorize air shipment?
No. A test-summary source can support a qualified review. It does not itself establish a transport path, packaging, marking, air eligibility, carrier acceptance, or release. Keep those as separate controlled actions and decisions.
What if a report names a battery model but not the buyer product?
Record the buyer product/version, the supplier battery model, the report source, and the missing association. Do not assume the report covers the product because a battery appears similar. Route the product/battery relationship to the qualified function.
Does supplier evidence authorize shipment release?
No. Supplier evidence can help a qualified process locate battery and test information. It does not establish test adequacy, transport classification, packaging, marking, carrier acceptance, product disposition, or shipment release. Keep those as separate controlled records.
Keep supplier facts and transport actions distinct
A useful China supplier lithium battery test summary evidence record identifies the buyer item/version, battery/product model, supplier/site, supplied summary/report/laboratory information, stated attributes, source file/date, product and shipment association, open conditions, and owner. It makes a supplier file traceable without calling it a shipping authorization.
That boundary improves later review. Qualified functions can see what the supplier supplied, which battery and product it concerns, and what remains unresolved. The responsible transport, logistics, and release functions retain control of their separate actions.
Supplier Ally can help buyers organize supplier communications, product specifications, battery model records, test source files, laboratory details, shipment references, and evidence requests across China sourcing projects. Decisions about test adequacy, transport classification, packaging, marking, shipper or offeror roles, carrier acceptance, legal interpretation, product disposition, and release should remain with the buyer’s qualified responsible functions.
EN 
ES 