Leo · 2026-11
This article tests one question against public FCC rules: does lab scope, rather than lab reputation, drive report acceptance?
Sources are two. First, the FCC’s own published equipment authorization rules, the recognized-lab database, and the FCC’s 29 October 2026 news release on lab reciprocity, all queried on 2026-11-04. Second, a worked schedule example you can recompute from the formula in the findings section, where every number is a stated assumption you can replace with your own.
What we add beyond the rules is pattern experience from our export team’s OEM workflow: the most common delay trigger appears when a buyer has already chosen a lab before confirming scope. Treat that as practitioner context, not as published data.
Limits are stated up front. We do not publish lab fees, we do not name labs, and we do not claim any lab result as our own certification.
If a lab holds FCC recognition, its report will be accepted for a 2-bay NAS.
You can test the claim yourself. Compare the recognized scope against the rule part and frequency range your device is tested against, and notice how often a listed lab turns out not to cover them.
FCC recognition is granted per test method, not per company.
A lab can be listed in the FCC database and still not be recognized for the rule part your device falls under. The database entry carries the scope. Read the scope, not the logo.
For a NAS, the relevant scope is usually unintentional radiators under Part 15 Subpart B.
A device with no intentional transmitter does not need transmitter testing, and paying for it wastes a build cycle.
Check the scope line against your device’s actual radio configuration before you sign a test order.
On 29 October 2026 the FCC adopted the Third Report and Order in ET Docket No. 24-136, document FCC 26-73. Per that order, starting 1 December 2028 all testing, certifying, and accreditation activities behind FCC equipment authorization must occur in the United States or a Reciprocal Economy. The FCC news release of 29 October 2026 is the Commission’s own official announcement of the adopted order and the source for every date and figure in this section; the full order text carries the same docket number, ET Docket No. 24-136.
During the transition you can keep working with a lab in a non-reciprocal economy, but any launch that slips toward or past 1 December 2028 should be matched to a qualifying lab early.
Your supplier should also be able to state in writing where the final compliance testing for your SKU takes place, and to explain how a launch-date slip would change that answer.
A Reciprocal Economy is one that holds a mutual recognition agreement or a comparable government-to-government arrangement with the US. Trade-press reporting on the order describes the list, which includes the UK, EU member states, Japan, South Korea, Vietnam, Hong Kong, and Taiwan, while mainland China and India are not on it (TSN Media, accessed 2026-11-04). Treat that count as reported context rather than a verified register: the authoritative list sits in the order’s own appendix, so confirm the current list on the date you make a lab decision. Separately, the FCC’s own news release quoted above — a primary source — states that “less than 4% of all electronic devices are tested in labs located inside the U.S.” at the time of the vote.
For buyers, two consequences follow. First, FCC recognized test lab requirements now carry a location dimension on top of the scope dimension described above. Second, the change is not retroactive: reporting on the order indicates that authorizations granted or applications received before 1 December 2028 are not disturbed, and devices already certified remain certified (GMA Labs, accessed 2026-11-04). Design and debugging work before formal testing can still happen anywhere.
Run these in order. Each one can stop the process.
Check 1, scope match. Confirm the recognized scope covers your rule part and frequency range. Ask for the database entry, not a summary email.
Check 2, accreditation body. Confirm which body accredited the lab and whether that accreditation is current. An expired accreditation behind a live FCC listing is a known trap.
Check 3, report format. Confirm the lab issues a report in the format your supplier’s compliance file expects, with the measurement uncertainty stated.
Check 4, sample condition. Confirm whether the lab tests a production-representative unit or an engineering sample. A report on a hand-built sample may not cover the shipped configuration.
Check 5, labeling. Confirm who prepares the label artwork and the compliance statement, and that the lab reviews it before the report closes.
Check 6, records retention. Confirm the lab will hold test data for the retention period your supplier needs, and that you can obtain copies later.
Most of the six checks are paperwork rather than measurement work, which is exactly why they are cheap to complete before you commit money.
[CHART: The six acceptance checks by type | type=bar | data=Derived from the six checks listed in this section | series=Paperwork:5;Measurement:1]
[CHART: Weeks added to FCC report timeline by failure point, NAS program | type=bar | data=Recomputable from the schedule formula below; assumes a 2-week first test round and a 1-week re-test | series=Scope mismatch:3;Accreditation lapse:2;Sample not representative:2;Label rework:1;No failure:0]
The chart above uses a simple schedule model, and you can recompute it, and every number in it is an assumption you can replace with your own, not a quotation.
Formula: added weeks = re-test weeks + re-submission weeks + queue delay.
Assume a 2-week first test round, a 1-week re-test, and a 1-week re-submission queue, and a scope mismatch forces all three. It adds roughly 3 weeks. A labeling rework adds one.
That model is deliberately conservative. It assumes the lab has capacity when you come back, which is often not true in a busy quarter.
The practical read: the check that costs nothing at quotation time is the one that costs three weeks later.
Take the A2 Pro as the worked case. Two 2.5-inch SATA bays, 48 TB raw, one GbE port, no cellular or Wi-Fi transmitter in the base configuration.
That configuration points at unintentional-radiator testing. It does not point at transmitter testing, because there is no intentional radiator to test.
If your SKU adds a wireless module, the scope changes and so does the lab requirement, and confirm the module’s own authorization status before you assume the NAS report covers it.
This is where buyers lose time. The base unit passes, then the wireless variant needs a separate path, and the schedule doubles.
FCC is one of six marks in a typical export bundle. The other five are CE, UKCA, RoHS, REACH, and WEEE.
Sequencing matters more than lab choice here. If you run FCC first and the enclosure changes for a CE-driven industrial design revision, you may re-test.
Our own OEM matrix lists all six as supported on our certifications page, and the practical advice is to freeze the industrial design before any lab booking.
Freeze the design, then book. Not the reverse.
| Decision point | What to confirm | Schedule impact if wrong (model estimate) | Who owns it |
|---|---|---|---|
| Lab scope match | Rule part and frequency range in the FCC database entry | +3 weeks if wrong | Buyer |
| Accreditation currency | Accrediting body and expiry date | +2 weeks if lapsed | Buyer |
| Sample representativeness | Production unit versus engineering sample | +2 weeks if re-test needed | Supplier |
| Label artwork | Who drafts, who reviews, when | +1 week if reworked | Shared |
| Design freeze | Enclosure and radio configuration locked | Prevents re-test entirely | Buyer and supplier |
Book the lab after the design freeze, not before.
Ask for the FCC database entry and read the scope line yourself. Do not accept a forwarded email summary as proof of scope.
If your SKU includes a wireless module, get the module’s authorization status in writing before you schedule anything, and the module is often already authorized, which shortens the path considerably.
For a distributor building a SKU ladder, the trade-off is straightforward, and a slightly higher lab fee with confirmed scope is cheaper than a three-week slip on a container booking. Take the confirmed scope every time.
Ask your supplier for the six-mark status in writing at quotation, and that single document answers most of the questions above before you spend anything. The woCyber FAQ hub keeps the short answers to these questions in one place, and the OEM and ODM overview explains how a private-label program is structured around them.
The schedule model is an estimate, not a measurement. Real queue times vary by quarter and by lab capacity.
We did not test a device in this article, and the findings rest on published FCC rules, the sources linked above, and practitioner experience, not on bench data.
Rules change. Verify the current database entry and rule text on the date you book, not on the date you read this.
Yes for the unintentional-radiator path under Part 15 Subpart B.
The lab still needs recognition covering that rule part, and a device with no intentional transmitter skips transmitter testing but does not skip the lab requirement.
Look up the lab in the FCC’s recognized-lab database and read the scope entry directly, and confirm the rule part and frequency range match your device. Ask the lab to send the database entry rather than a written summary.
Often yes. If the module already holds its own authorization, the NAS report may not need to cover it. Confirm the module’s status in writing before scheduling, because an unauthorized module forces a separate path and a longer schedule.
Plan one full build cycle for the first test round and a second for your supplier’s compliance file, and add roughly three weeks if scope, accreditation, or sample condition turns out to be wrong. Freeze the design before booking to avoid the largest delay.
Only if your SKU matches the tested configuration.
A different enclosure, a different radio module, or a different power supply can put you outside the tested configuration, and confirm configuration match in writing before you rely on an existing report.
FCC news release, FCC Proceeds on Device Test Lab Onshoring, Reciprocity Rules, 29 October 2026.
TSN Media, FCC Limits Device Test Labs to the US and Reciprocal Countries, accessed 2026-11-04.
GMA Labs, FCC Test Lab Reciprocity Rules Adopted: 2028 Cutoff Set, accessed 2026-11-04.
woCyber product specification pages for A2 Pro and S1, accessed 2026-11-04.
Whether you need surveillance storage, private cloud for business data or an OEM/ODM partner, our export team will map the right platform to your application — reply within one working day.
Shared storage for deskside AI clusters refers to a storage appliance on the office LAN that holds datasets, checkpoints and embeddings for…
November 3, 2026A cloud storage subscription cost is the recurring fee a business pays to keep its files on a provider's servers, billed per…
October 30, 2026NVMe in a Business NAS: Cache Pool or Storage Volume? NVMe in a business NAS means using M.2 or U.2 flash drives…
Ask our export team for the OEM/ODM cooperation guide and a written quotation.
