CPSC Micromobility Battery Standard: Retailer Comment Deadline

Key Takeaways

The Consumer Product Safety Commission has proposed a safety standard for lithium-ion batteries in micromobility products, published at 91 FR 38162, addressing hazards such as thermal runaway of lithium cells. It is a notice of proposed rulemaking: nothing is in force and no compliance date exists. Written comments must be received by August 24, 2026, when the record closes.

Does this reach your product line?

For most retailers, importers and marketplace sellers, the first question is not what the standard would say. It is whether the catalogue contains anything the proposal would touch. That is a scope question, and the honest answer is that the Federal Register summary draws the boundary loosely on purpose — at the proposal stage, the scope is one of the things comment is being invited on.

Here is what the summary does and does not settle. Treat the right-hand column as the reason to read the notice itself rather than a checklist substitute.

That last row is the one to be careful with. Coverage of this proposal in trade press has attached specific standard designations to it. The Federal Register summary names none, so this page names none — and a seller scoping work off a standard number should confirm that number in the notice text, not in a summary of it.

What the notice proposes

The mechanism is indirect, and that is the part worth understanding. Rather than writing test criteria from scratch, the proposal would have electrical systems using lithium-ion batteries in micromobility products comply with applicable voluntary standards, with modifications. The modifications are not described in the summary, so the substance of what would change sits in the notice itself. Federal Register

The Commission states the risk it is addressing as an unreasonable risk of death and injury associated with lithium-ion batteries used in micromobility products, due to hazards such as thermal runaway of lithium cells, which can lead to fires, explosions, gas releases, burns, overheating, and smoke inhalation. That hazard language is the agency's own, quoted from its summary rather than characterised. Federal Register

The third-party-testing add-on

This is the provision a retail compliance owner should read twice, because it changes evidence obligations rather than product design.

Because some micromobility products are children's products requiring third party testing, the notice also proposes adding this rule to the list of rules that require such testing. That list is 16 CFR Part 1112, and unlike the standard itself, it exists and is readable today.

The operational consequence of a rule appearing on that list is not subtle. It shifts what a seller has to be able to produce, per product and per shipment, from an assurance to a document — a test report from a body that qualifies, and a certificate that points at it. The mechanics of producing and filing those certificates are their own subject; CPSC certificate of compliance eFiling covers them, and this page does not restate them.

What is worth saying here is the timing. Nothing on this list changes today. But a seller who already struggles to retrieve a supplier test report on request would struggle harder under a rule that expects one, and that gap is visible now, before any of this is settled.

Who would be affected

The reader set is the commercial chain around micromobility products rather than the manufacturers alone: retailers, importers and marketplace sellers, plus the sourcing, QA and product-compliance functions inside them.

Responsibility usually splits across those functions in a way that makes evidence hard to assemble. Sourcing holds the supplier relationship and often the only copy of a test report. Import operations hold the commercial documents. Product compliance owns the certificate. Merchandising owns the listing that describes the product. None of them individually can answer "show me the evidence for this SKU," which is exactly the question a rule on the third-party-testing list would eventually pose.

Marketplace sellers sit in an awkward position here, because the platform relationship can obscure who the responsible party is. That is a question for counsel and for the platform's own terms, not one this brief resolves.

What the record and the CFR show today

Two things in that table are easy to misread. The first is that 16 CFR Part 1265, the part the proposed rule would create, is where the standard would sit, not where it sits — searching the electronic CFR for it today returns nothing, because the part is not populated. The second is that the eCFR is a dated snapshot rather than a live feed, which is why the stamp is printed alongside the claim.

Evidence a seller can organise before the record closes

None of the following is required by anything today. It is the work that a rule on the third-party-testing list would make visible, and it is work a compliance owner can scope now without waiting for an outcome.

The last row is the one that fails in practice. Firms usually have the documents. What they lack is a way to retrieve the right one, for the right shipment, on the day someone asks.

Operationalizing the workflow at volume

At a handful of SKUs this is a shared drive and a diligent person. At catalogue scale it is a routing problem: reports arrive from suppliers in different formats on no fixed schedule, certificates are generated per shipment rather than per product, and the link between them is the thing that quietly goes missing. The pattern that holds up is one case per SKU, with every report, certificate and exception attached to that case as it happens.

US Tech Automations agentic workflows handle the mechanical half of that: a supplier report is routed into the SKU case on arrival, a certificate record is generated per product per shipment and linked to the report that supports it, and any shipment whose case has no report triggers an exception queue instead of shipping unnoticed. The compliance owner still decides whether the evidence is sufficient.

Retrieval is the other half. Because each certificate is connected to its report at the case level, US Tech Automations can return the supporting document for a given SKU and shipment as one step rather than a search across mailboxes and drives. That is document routing and recordkeeping. It is not testing, not certification, and not a judgement about whether a product meets a standard.

Frequently asked questions

Is the micromobility battery standard in force?

No. It is a notice of proposed rulemaking. Nothing in it applies to any product today, no compliance date exists, and the Federal Register entry carries no effective date. Federal Register

When does the comment period close?

Written comments on the notice or on the Paperwork Reduction Act must be received by August 24, 2026. That is the close of the rulemaking record, not a deadline to do anything to a product. Comment periods can be extended or reopened, so confirm the current date on the document before planning around it. Federal Register

Which voluntary standard would the rule incorporate?

The Federal Register summary does not name one. It says applicable voluntary standards would apply, with modifications, and identifies neither the standard nor the modifications. Any specific designation would have to come from the notice text itself, which is why this page links to it rather than filling the gap. Federal Register

Why would this rule appear on the third-party-testing list?

Because some micromobility products are children's products requiring third party testing, the notice proposes adding the rule to the list of rules that require such testing. That list is 16 CFR Part 1112.

Which hazards does the proposal say it addresses?

The Commission names thermal runaway of lithium cells, which can lead to fires, explosions, gas releases, burns, overheating, and smoke inhalation. That is the agency's own hazard language from its summary of the notice. Federal Register

What evidence should a retailer be able to produce for a tested product?

At minimum, the supplier test report, the certificate that relies on it, and the link between them for the specific shipment in question. That is an operational answer about retrievability, not a statement of what any rule would demand — the proposal is not final, and what a finalised rule would require is a question for the notice and for counsel.

What can a seller still do before the record closes?

Comment. A proposal is the stage at which scope questions, evidence burden and feasibility are still open, and the record closes on August 24, 2026. Commenting is an opportunity rather than an obligation, and a seller who cannot tell whether the proposed scope reaches their catalogue has said something useful by saying exactly that. Federal Register

Related guidance

• Neck float toy safety standard

• Water bead toy safety standard

Source: Federal Register / eCFR — 91 FR 38162.

Last reviewed: July 28, 2026

Reviewed by Garrett Mullins, Workflow Specialist at US Tech Automations.

Every date, citation, RIN, CFR reference, and figure in this post is copied verbatim from the Federal Register and eCFR as of the snapshot date. Nothing is estimated, modeled, or extrapolated. This is not legal or tax advice.

Disclaimer

This page is for informational purposes only. It is not legal or tax advice, creates no attorney-client relationship, and does not determine whether a product would fall inside the proposed scope or whether any evidence is sufficient. Consult a qualified professional about the rulemaking, a particular product line, and the obligations that would apply to it.

A proposal can be withdrawn, changed or reproposed, and a comment period can be extended, so verify the current status on the Federal Register document before relying on any date here. Review pricing when the team is ready to scope report intake, certificate records and retrieval around its own reviewers.