GB 38031-2025: A Buyer's Guide to EV Battery Safety Documents

GB 38031-2025 is the current mandatory Chinese national standard for electric-vehicle traction-battery safety. It took effect on 1 July 2026 and fully replaced GB 38031-2020. An official English version is listed by China's national standards services. Buyers should still verify product scope, edition, language, referenced documents and test evidence instead of treating the standard number alone as proof of compliance.

This guide is for procurement, engineering and quality teams assembling an EV battery document package. It does not reproduce test procedures, approve a battery design or decide regulatory applicability for a particular vehicle. Those decisions belong with the responsible technical and regulatory specialists using the complete authorized text.

1. Start with the current edition record

The official Chinese record lists GB 38031-2025 as current, published on 28 March 2025 and effective on 1 July 2026. The national standards information record states that it fully replaces GB 38031-2020. Record these facts with the date on which you checked them; do not rely on an undated supplier catalogue.

Control field	What to record	Why it matters
Standard	GB 38031-2025	Avoids accepting a report that identifies only “GB 38031”.
Publication date	2025-03-28	Distinguishes the edition from later amendments or drafts.
Implementation date	2026-07-01	Supports the project edition decision.
Replaced edition	GB 38031-2020, fully replaced	Triggers a review of older specifications and reports.
Language and source	Chinese original and, where used, official EN record	Keeps translation provenance visible.

The dates above are edition-control facts, not a conclusion that every product manufactured before or after one date is automatically accepted or rejected. Contract terms, certification arrangements, vehicle approvals and transition instructions may add project-specific rules. Keep those instructions in the same record.

2. Confirm that the standard fits the battery and vehicle task

The official title is “Electric vehicles traction battery safety requirements.” That title should not be expanded into every lithium battery, every electric mobility product or every stationary storage system. Describe the product and its intended vehicle application before selecting the document.

• Identify whether the item is a cell, module, battery pack or battery system and how it enters the vehicle project.
• Record the vehicle category and the role of the traction battery.
• Separate product safety requirements from performance, dimensions, transport, recycling or other document needs.
• Ask the responsible engineer to resolve any scope boundary using the complete standard and applicable vehicle rules.

A supplier statement that a battery “meets GB 38031” is therefore incomplete for procurement. The statement should identify the edition, product configuration, tested object and evidence being offered. Use the standard-number guide to preserve the year and full identifier in purchase records.

3. Build a controlled document package

The standard is one part of a usable technical package. Request the exact edition and language needed by the engineers who will review it. Then list the referenced documents, amendments, project specifications and evidence that the team actually needs.

1. Chinese source text: retain the official record and the authorized document used for decisions.
2. English version: record its source and relationship to the Chinese edition.
3. Referenced documents: obtain the editions called up by the clauses relevant to the project.
4. Supplier specification: identify the model, configuration and interfaces covered.
5. Test evidence: connect each report to the tested object, standard edition and test scope.
6. Decision record: identify open questions, owners, dates and approvals.

Do not turn a catalogue title or an English filename into a claim that the full document has been reviewed. Our English-document guide explains why an English title, an official English publication and a third-party translation are different things.

4. Treat the 2020-to-2025 change as an evidence review

Because the official record says the 2025 edition fully replaces the 2020 edition, teams using a 2020 report should not simply change the year in a checklist. Ask which requirements and test configurations were assessed, whether the product has changed and what transition or supplementary evaluation is required for the current project.

A practical change review has four columns: old evidence, current requirement source, identified gap and disposition. The disposition might be a documented equivalence review, additional testing, a new report or a decision that the evidence is not applicable. This article does not supply technical equivalence conclusions.

Procurement rule: “Full replacement” identifies the edition relationship. It does not prove that a particular old test report remains acceptable, nor that every old result is unusable.

5. Check reports without over-reading them

Before accepting a report, verify the report number, issuing organization, issue date, sample identity, model and configuration, standard edition, clauses or test scope, result pages and any limitations. Confirm that the sample can be linked to the item being purchased. A report date alone does not establish the correct edition.

Also separate three questions: whether the report appears internally complete, whether the laboratory and report are acceptable for the intended scheme, and whether the product satisfies all project obligations. The first can be checked from the document package; the latter two require the relevant authority, certification body, customer or competent specialist.

6. Use the official English version with clear provenance

The official English-version record identifies GB 38031-2025 Foreign, language EN, as published and displays 28 March 2025. A separate foreign-language project record lists 6 January 2026 as its publication date and names the organizations responsible for the translation project. Because the services use different records and date labels, retain both source URLs and identify the actual file supplied rather than collapsing them into one undocumented date.

Record the actual file source rather than merely writing “English available.” For bilingual work, keep clause references aligned and escalate any apparent conflict against the authoritative source used by the project. Do not describe an unofficial translation as the official English version.

7. Buyer checklist before ordering or testing

• Complete code: GB 38031-2025, not a shortened number.
• Product and vehicle application written in project-specific terms.
• Chinese and English document needs stated separately.
• Official source and file provenance recorded.
• Old GB 38031-2020 specifications and reports identified for review.
• Referenced-document list assigned to an owner.
• Supplier model, configuration and sample linkage defined.
• Required test or certification scheme confirmed by the responsible party.
• Open gaps, due dates and approval owner retained with the order.

Frequently asked questions

Is GB 38031-2025 already in force?

Yes. The official record lists 1 July 2026 as its implementation date and shows the standard as current. Recheck the record when making a new decision, and keep any project-specific transition or certification instructions with your evidence.

Does GB 38031-2025 replace GB 38031-2020?

Yes. The national standards information service records a full replacement. That edition relationship triggers an evidence review; it does not by itself decide whether a particular report needs supplementary work or complete retesting.

Is an official English version available?

Yes. China's official standards services list an EN foreign-language version. Verify the exact file and source you receive. An English title in a database or an unofficial translation should not be represented as that official version.

Review the current GB 38031-2025 record and document options, then use the standard-search workflow to identify other project documents. The goal is a traceable package, not a one-line claim of compliance.