Let me start with a rant: factories do not take certification seriously. At all.
This March I brought in a batch of smart plugs with screens, getting ready to list on Amazon. The goods had barely landed at my US West Coast warehouse when the factory pushed an OTA update without a word. The companion app gained an "energy stats" page, and the WiFi setup flow changed. I thought nothing of it. The hardware was untouched. Just a software UI refresh. What could go wrong?
Then in early April, a big buyer asked before placing an order: "Does your FCC grant still cover this firmware version?"
I froze.
I called the factory. They swore up and down: "Hardware unchanged, certification is definitely still valid. Sell with confidence." I did not buy it. I went back to the lab that did our original certification. The engineer there woke me up with one sentence: "Untouched hardware does not mean untouched certification. A grant covers a hardware-plus-software combination, not hardware alone. First tell me what this OTA actually changed."
That is what this post is about: where software changes cross the compliance line.
What I did
Spoiler: the batch turned out fine. But I only kept selling after walking the full process.
Step one: get the change log from the factory. Get, not ask about. The factory first said "just some UI tweaks," and I shot back: send me the itemized change list. Five years working with factories taught me one thing: a verbal "just a small change" routinely unpacks into three or four line items.
The list showed the UI refresh and the energy stats page, plus a changed setup flow: the device used to broadcast only on 2.4 GHz during pairing, and now it scanned both bands.
Step two: take the list to the lab for a gap assessment. I brought three things: the factory's change log, the original grant, and a description of each firmware version. I still remember the engineer's exact words: "Pure UI changes that do not affect RF emissions need no certificate action. But the pairing flow changed, which can change emission behavior. That one follows the FCC change process."
Here is the bit I learned on the fly: FCC rule 47 CFR 2.1043 is fairly clear on this. Software changes that do not affect RF emissions need no additional filing. Anything touching RF emission characteristics goes through the permissive change process. Whether that lands as Class I or Class II depends on the nature of the change, so check the FCC's current published policy. This is a seller's war story, not legal advice.
Step three: the factory supplied the technical documents, the lab filed the change, and a few weeks later the updated paperwork came through. Only then did I push the batch to the big buyer with a clear conscience.
The single most important lesson from the whole episode: untouched hardware does not mean untouched certification. Counterintuitive, but true. The grant was issued for a specific hardware-plus-software combination. Change the software enough, and the combination changes with it.
The cautionary tale: two months down the drain
My own story had a happy ending, so here is someone else's disaster for balance.
Late 2025, a fellow seller in Shenzhen, Lao Chen, sells smart lights. An OTA update took his device from 2.4 GHz-only to dual-band 5 GHz support. His thinking: it is all WiFi, just one more band. But the 5 GHz emission parameters no longer matched the original grant filing, and the certificate stopped matching the product on the shelf.
Amazon's compliance review pulled his listing for "compliance documents not matching the version on sale." Re-certification and re-submission ate more than two months, straight through peak season. Lao Chen told me the profit he missed in those two months would have paid for ten certifications.
See the pattern? The loss is never the certification fee. It is time. Every single day the listing stays down is a day of sales that never come back.
The numbers: my change-classification framework
After these two episodes I built a decision framework. Now every factory OTA gets run through it. Three minutes, one answer.
| Change type | Examples | Risk | My move | | Pure UI | Icons, colors, copy, layout | Low | File internally; record which firmware version maps to which grant | | New app-layer features | Energy stats, timers, scene automation | Medium | Lab assessment to confirm nothing touches RF or safety logic | | RF-related | Pairing flow, transmit power, new bands, antenna behavior | High | Written confirmation from the certification body; expect a formal change filing | | Safety-related | Overload protection logic, child lock, leakage protection | High | Full re-evaluation; UL has specific requirements for safety-related software, so check UL's current published policy |
The order matters: classify first, get confirmation second, keep written records third. Never sell first and sort it out later.
One more practical note on dealing with the lab. When you walk in, bring the change log, the original grant documents, and a plain-language description of what each firmware version does differently. Labs bill by the hour. Showing up organized cuts the assessment time in half, and it signals to the engineer that you are serious, which gets you straighter answers.
Four hard-won rules
One: put it in the contract. The factory must give advance written notice before any OTA, with the change list attached. Pushing an update without notice counts as breach. This clause is now standard in every factory agreement I sign, from day one.
Two: demand the change log for every OTA and file it by category. A verbal "nothing much changed" counts as not provided. If it is not in writing, it did not happen.
Three: never trust a factory's verbal "it is fine." Get the certification body or the lab in writing. An email is enough. When it matters, paper beats a voice message every time.
Four: build a firmware-version-to-grant mapping table. Version number, OTA date, grant number, assessment outcome. Four columns in a spreadsheet. When a buyer asks, send the table.
Tried it myself. Works. Last month another buyer raised the certificate question, and I sent the mapping table in three minutes. They placed the order right after reading it. That spreadsheet outsells any sales pitch. Compliance looks like a cost line right up until the day it becomes the reason you win the order.
By Ah K, E-commerce Seller (5 yrs)
