Your BMS Module's FCC ID Covers the Module, Not the Pack

An FCC ID on a wireless BMS module authorizes the module, not the battery pack it is installed in. Those are two separate obligations, and a pack supplier almost always holds only the first one. A module grant says that one specific transmitter, with one specific antenna, at one specific output power, was tested and certified. The host integration — the pack the module actually lives in, the antenna it actually uses, the enclosure around it, the RF exposure question, the label on the finished assembly — is the second obligation, and it belongs to whichever party puts the wireless pack on the market. Most procurement checklists squeeze both into one yes/no line, which is how a program closes with the buyer believing they bought an authorized pack and the file showing otherwise.

I sit on the buyer's side of that question most weeks. The packet that lands on my desk has a tab called Wireless Compliance, it is usually one page, and it is usually a photograph of a label with a character block in FCC ID shape — some characters, a hyphen, some more characters — plus a green checkmark. That page has cost me more calendar time than anything else in battery procurement, because the checkmark is true and the conclusion everyone draws from it is false.

The grant is narrow. That is the entire point of it.

When I first started reading these, I assumed an FCC ID was a stamp of approval on a product. It isn't. It's a certificate of tested configuration. A module grant is issued against a specific radio, a specific antenna type, a specific maximum conducted output power, a specific modulation, and a specific assumption about how the thing is used — commonly that it's a mobile transmitter, meaning it stays some distance from a human body. Change any of those and the grant stops describing what you're shipping.

The document itself will tell you this if you read past the first page. I've pulled grants where the conditions section reads like a list of things the integrator must not do: only with the antenna listed in the filing, not to exceed a stated power, and a note on simultaneous transmission if the module can transmit while another radio in the same product is transmitting. There's also a distinction that matters more than it sounds like it should — whether the grant is a single modular approval or a limited one. A limited module approval is the FCC's way of saying the module maker did not demonstrate everything needed to stand alone, so conditions attached that the host has to satisfy. Vendors quote both kinds as "FCC certified" and the phrase is equally true for both.

Look it up. The database is free and takes four minutes.

I stopped accepting FCC IDs as text a while ago. Every one gets looked up in the FCC's Equipment Authorization System before the page even goes into my folder. The search field takes the ID directly. What I want out of that search is one thing first: the grantee.

That single field has ended more conversations than any technical question I've asked. Sometimes the grantee is the module manufacturer — a company whose name has never appeared anywhere in the pack supplier's proposal. That's not fraud. That's a supplier legitimately reusing somebody else's certified radio. But it means the party who certified the thing has no relationship with the pack, and the integration conditions on that grant are now sitting on somebody's shoulders who may not have read them.

Sometimes the grantee is the pack supplier itself, which is a better sign, but still only answers half the question. And occasionally the grantee is a name I can't connect to anyone in the supply chain at all, which usually means the quoted ID belongs to a gateway or a telematics box somewhere up the food chain.

After the grantee, I read the conditions. Antenna type. Output power. Mobile or portable assumption. Simultaneous transmission notes. If the module is approved to work with a whip antenna and the pack's lid has a PCB trace antenna, the grant doesn't cover the pack, no matter how good the module is. That is a real thing I have run into: an antenna swap that made electrical sense inside a sealed aluminum enclosure and quietly invalidated the basis of the filing.

Whose obligation is the host one? It depends, and I make them write it down.

The honest answer to "who holds the host obligation" is that it depends on who sells the finished article. If the pack supplier sells a wireless BMS pack as a product — it leaves their dock with a radio in it, connecting wirelessly — then they are the host, and they either hold their own authorization on the pack or they are using the module strictly inside its grant conditions and carrying the host's own label and evaluation work. If instead the pack goes into a robot OEM's machine and the OEM ships the finished robot, the OEM may be the party on the hook for the host side. Both structures exist. I've bought under both.

Which means the ask isn't "do you have FCC?" The ask is: show me the grant, tell me whether it's the module or the pack, and put in writing which entity is the responsible party for the host product. I want the module part number and revision on the paper, because a pin-compatible replacement from a different vendor does not inherit the old FCC ID. I want the antenna described. I want the module maker's integration instructions, which the module manufacturer is supposed to publish with the module — the OEM integration manual that comes out of the Commission's modular transmitter guidance, KDB 996369 D03. If the supplier can't produce that document, the supplier cannot have read it.

And there's a third case that eats weeks: the pack has no radio at all. A hard-wired BMS with a CAN or isolated serial interface raises no FCC question whatsoever. But the brochure still says "FCC certified," because the wireless link is in a separate gateway box bolted somewhere on the robot chassis. I've chased that artifact more than once — a compliance document for a device that isn't the device I'm buying. The way to catch it early is to ask what physically transmits in the pack. If the answer is "nothing," then the FCC ID belongs to something else and the compliance conversation is about that something else.

The radio part is the small part of the evidence file

FCC authorization speaks to radio frequency compliance. That's it. It says nothing about whether the cells vent, whether the pack survives a crush, whether the BMS cuts off at the right threshold, or whether the shipment can legally fly. Those live in a different set of documents: the cell and pack safety test reports under UL 62133-2 or IEC 62619 depending on the application, UL 2054 for the pack in some industrial contexts, and a UN 38.3 test summary for transport.

I've watched a review meeting where a project manager said "the pack is certified" and everyone nodded, and it turned out the only certificate in the file was the module's FCC grant. One document, three unrelated questions, one word. I now keep the radio evidence and the battery safety evidence in separate tabs and never summarize them with the same sentence.

What I actually put in the RFQ

A short list, and it's the same list every time. A copy of the grant, not the ID. The grantee name. The module part number and hardware revision. The antenna type, gain, and whether it is the antenna named in the filing. The integration instructions from the module maker. A written statement of which party is the responsible party for the host product, signed by someone whose title suggests they know what they're signing. And if the pack itself holds an authorization, that grant — which will carry a different FCC ID than the module's, and I want to see both.

Then it goes into the supply agreement as a change clause. Any change to the module, the antenna, the antenna placement, or the enclosure shielding triggers a fresh compliance review before shipment. Not because I expect trouble, but because the failure mode here is silent. Nothing stops working. The pack performs fine. The evidence just quietly stops describing the thing on the pallet, and nobody finds out until a customer's regulatory review three years later, long after the people who knew have moved on.

Here's the part that took me a while to accept: the buyer's job is not to decide which authorization applies. That's the supplier's technical call and, frankly, their legal one. The buyer's job is to make the supplier state it in writing, and to know enough to notice when the answer changes shape between the proposal and the qualification packet. Two obligations, one module grant and one host integration. Ask which one you're holding. The answer is usually shorter than the checkmark suggests.