Why is PTCRB or GCF not enough to activate a product on the Verizon network?

Because Verizon runs its own Open Development (OD) certification on top of industry certification. Its process document (version 41, December 2025) requires an FCC ID, a BIS export classification (ECCN and CCATS) and, for LTE-capable devices, GCF certification before OD conformance testing starts. The device is then tested against a Verizon test campaign (TECC) at a Verizon-authorized lab. Only after certification can the manufacturer upload device IDs into the Verizon Device Management Database (DMD); devices not uploaded through ODP or EDI cannot be activated.

What is the difference between module approval and device certification at Verizon?

The process document states that a host device is certified using an approved module or chipset, and that modules and chipsets are approved through the Open Development portal (ODP) under the Module Guidelines. The Verizon FAQ is explicit that approved modules are not certified devices: every host device using an approved module must itself be certified. An approved module does open the Fast Track route for data-only LTE or 5G NSA host devices and raises the early development allowance from 2 to 20 activations.

How long does Verizon Open Development certification take?

Verizon publishes no service level. Its FAQ only says it expects typical lab time to be weeks rather than months, and encourages an approved module to reduce testing time. Two published clocks matter for planning: testing at the lab should begin within 90 days of the final TECC release, and a submission left inactive for more than six months is set to INACTIVE and may have to meet the most recent requirements on reactivation.

Does Verizon charge a certification fee?

No. The Open Development FAQ states that Verizon does not charge developers for device certification. Testing costs are set by the external labs and paid by the manufacturer, and Verizon may impose costs for access to lab facilities.

Which labs are authorized for Verizon Open Development testing?

Section 7 of process version 41 lists Bureau Veritas (formerly 7Layers), Cetecom, ATMC Labs (formerly Intertek), Element Materials Technology (formerly PCTEST), SGS, Tech Mahindra and the Wireless Research Center for conformance and OTA work; Arclight Wireless and Accenture (formerly umlaut and P3) for field testing; Ericsson and Motive for interoperability and FOTA; and Carve Systems, Spirent and Palindrome for IoT security penetration testing. All listed addresses of the conformance labs are in the United States.

Does eUICC change anything in the Verizon certification procedure?

Yes. Process version 41 documents two architectures: M2M eUICC (GSMA SGP.02, SM-SR and SM-DP) and Consumer eUICC (GSMA SGP.22, SM-DP+ and an LPA). An M2M eUICC must already have Verizon Technical Acceptance, and a partner eUICC must pass Verizon eUICC Validation. For Consumer eUICC the OEM fills in the RSP Functionality Matrix; an eUICC not previously validated goes through eUICC Validation with the Verizon SIM profile before any device testing. The document does not describe an SGP.32 path.

Is re-certification required after a firmware or hardware change?

Section 6 requires the developer to notify the Open Development Product Team (ODPT) of any update to certified software or hardware and to provide updated submission documents. The ODPT and the NDET lab decide the level of regression testing, which an OD-authorized lab runs; the ODPT then certifies the Device Maintenance Release. The OD Notice of Certification also sets a Certification Period for each device.

What happens if a product is shipped without Verizon certification?

Device IDs are loaded into the Verizon DMD only for certified devices, and the process document states that devices not uploaded through ODP or EDI will be prevented from activating. For rogue devices or Certification Agreement violations, Verizon can ask for 2 samples within 48 hours, restrict or deactivate the device, de-certify it and stop provisioning further units.

Verizon Open Development: certification after PTCRB/GCF

Hugues Orgitello updated 7 Oct 2026 17 min read

You have obtained PTCRB or GCF certification and you thought the North American cellular chapter was closed. Verizon then adds its own layer: Open Development (OD) device certification, driven from the Open Development portal (ODP). This page follows the public Verizon process document, version 41 of December 2025, and the Open Development FAQ, line by line: what must exist before testing starts, the Fast Track route, the activation allowances during development, the two eUICC paths, the authorized labs, and the readings of the process that the texts contradict.

Open Development vs PTCRB, the right separation

PTCRB and Verizon Open Development are often conflated because they happen during the same project phase and share part of the testing effort. They do not cover the same scope.

Criterion	PTCRB	Verizon Open Development
Nature	Industry programme administered by CTIA Certification; ptcrb.com listed 17 participating operators on October 7, 2026, Verizon among them	Verizon-only programme
Reference	PTCRB test plans based on 3GPP TS 36.521 and TS 38.521	Verizon test campaign (TECC, Test Entrance Criteria Checklist) built from the OD requirement documents
Verizon in the band list	PVG.11 V5.24.0 names Verizon on no single LTE or NR band, only on some EN-DC combinations	Required Verizon bands and EN-DC combinations defined in the OD requirement documents (login required)
Granted by	CTIA Certification	Verizon Open Development Product Team (ODPT)
Outcome	PTCRB certification	OD Notice of Certification, then device IDs (IMEI, or IMEI with ICCID or EID) loaded into the Verizon Device Management Database (DMD)

Section 3.1 of the process document sets the entrance conditions: every device must be type approved by the FCC and classified by the Bureau of Industry and Security (BIS ECCN and CCATS) before OD conformance testing, and LTE-capable devices must receive GCF certification before OD conformance testing can commence. The FAQ repeats it: "All LTE devices must receive GCF compliance prior the OD certification process begins". PTCRB enters the Verizon process in two places: the Fast Track route (PTCRB or GCF report and certificate) and the extended test-device allowance (PTCRB, CTIA or GCF testing at a Verizon-authorized lab). See PTCRB scope for the multi-carrier baseline.

A simple reading: PTCRB and GCF certify that the radio respects 3GPP, Verizon Open Development certifies that the product is acceptable on the Verizon network. Even that has limits: the FAQ says certification does not mean Verizon has made any determination on call quality or that the device will operate without error.

The process at a glance, with the numbers Verizon publishes

Parameter	What the Verizon text says	Where
Portal access	NDA required; each developer gets a VZW-ID (format VZW followed by digits) used in the device tracking ID	Process 3.1
Entrance criteria	FCC ID, BIS ECCN and CCATS, GCF certification for LTE-capable devices	Process 3.1, 3.1.1
FOTA	All LTE-capable devices must support radio layer FOTA; a device on an approved module must show the module Verizon FOTA still works	Process 3.1
Security	Security compliance documents or test results before DLD; non-compliant features need an approved waiver	Process 3.1
Samples	2 samples to the ODPT, besides those sent to the lab	Process 3.2
Test start	Lab testing should begin within 90 days of the final TECC release, otherwise the certification manager decides whether a new TECC is needed	Process 3.2
ENAP development activations	Up to 20 with a Verizon certified module or approved embedded modem, up to 2 without; test lines disconnected no later than 60 days after testing	Process 3.4.1
Safe For Network (SFN)	Up to 500 activations per project after successful SFN testing at a Verizon-authorized lab	Process 3.4.1
Pilots and trials	Up to 1200 activations per project after PTCRB, CTIA or GCF testing on the Verizon bands at a Verizon-authorized lab (heading: when using a Verizon approved module)	Process 3.4.1
External antenna	Cable lead over 20 cm with no TIS/TRP results triggers RF Supplementary testing	Process 3.4.2, 3.4.3
Inactivity	Submission inactive more than 6 months becomes INACTIVE; reactivation may require the latest requirements	Process 3.4.8
ID upload	ODP upload of CSV or text file loads into the DMD within up to 15 minutes	Process 4.2.1
Rogue device	2 samples within 48 hours of a formal request	Process 5
Fee	Verizon does not charge for device certification; lab costs are paid by the manufacturer	FAQ

The Open Development portal (ODP), entry point

The programme was launched as the Open Development Initiative (ODI); the portal login address still carries the ODI name. After the NDA, the developer reaches the Requirement & Test Plan documentation (login required), which holds the requirement documents the process refers to, such as the Module Guidelines, the LTE_3GPP_B13_NetworkAccess requirement and the FOTA compliance guidelines. Section 3.1.2 describes the flow:

developer registration and NDA;
add new device, a five-step entry (device info, marketing info, forecast, release notes, pre-submission documents); the registered model name should match the FCC filing;
Device Lock Down (DLD) review (submission, agreements, documents, test campaign, schedule, sample devices);
testing at an authorized lab, with FOTA update documentation supplied by the developer;
contractual agreements: the Certification Agreement (CA) and a Certificate of Insurance (COI), required before certification; the CA can be reviewed in parallel with registration and testing;
device ID upload and launch into the DMD, through the ODP or EDI.

Since January 2018 each certification is recorded in an OD Notice of Certification, which carries device-specific requirements and the Certification Period; the CA allows use of the Verizon mark on written request under the Verizon branding guidelines. The portal also links to ThingSpace, Verizon's IoT connectivity platform.

Module, chipset and host device

Section 3.2 states the structure in two sentences: a host device is certified using an approved module or chipset, and modules and chipsets are approved through the ODP under the Module Guidelines. The ODP publishes approved chipsets, approved modules and a separate list of modules approved for Private Wireless Network (On Site) use only. A PTCRB-certified module is not, by that fact, on the Verizon list.

What applies to modules and chipsets in the process document:

security compliance documentation or test results before the module or chipset DLD, with a disclosed and approved waiver for any non-compliant feature;
LWM2M Diagnostics testing for all modules and chip-on-board devices (section 3.4.7.7);
Verizon base-band FOTA, through which Verizon upgrades the module or chipset firmware over the air, using OMADM or OMA LWM2M (section 3.4.7.8);
device management reference clients for OMADM 1.2 or LWM2M OTADM on the ODP (section 3.4.7.6).

What applies to the host device:

device certification is mandatory even with an approved module; the FAQ says "Approved modules are not certified devices";
the Verizon FOTA capability of the approved module must still be functional in the host;
RF OTA (TIS/TRP) on the required Verizon bands and EN-DC combinations, or RF Supplementary testing when a long external antenna lead comes without TIS/TRP results;
field testing where required (see DFIT below), additional service tests, penetration testing for some devices.

For a product built on LTE-M or NB-IoT, Verizon describes both as fully supported by its 4G LTE network, and the Open Development FAQ notes that Cat M1 approved chipsets, modules and certified devices exist on the showcase. See PTCRB procedure for how the module-plus-device structure maps onto the project timeline.

The Fast Track route (section 3.4.3)

Process version 40 (June 2025) added Fast Track, and version 41 (December 2025) updated it. Verizon certifies a host device through Fast Track when the OEM has completed PTCRB or GCF testing on the Verizon 4G/5G bands and:

the technology is 4G LTE and 5G NSA;
the device uses a Verizon-approved module;
the device is data-only, with no voice;
a final PTCRB or GCF test report and certificate includes TIS/TRP RF OTA measurements for all required Verizon bands and EN-DC combinations, meeting Verizon RF OTA requirements;
the OEM provides self-test reports for FOTA compliance and IoT security compliance;
eUICC test results are provided if the device supports eUICC;
any additional feature gets the additional testing Verizon prescribes;
the device is not classified Performance Critical or Verizon Response Verified (VRV).

Fast Track is therefore a module-selection decision: it is decided at design time, when the module is chosen from the approved list on the ODP.

Test families in the OD campaign

The ODPT issues the TECC per device. The developer picks an authorized lab from section 7, works directly with the interoperability (IOT) labs on schedule and payment, and provides FOTA documentation (own solution, module vendor solution or Verizon/Motive solution) by the time of final results. The ODPT then passes, conditionally passes or fails the device. For PTCRB equivalents, see PTCRB tests.

RF conformance and OTA performance

The radio baseline is the industry campaign on 3GPP TS 36.521-1 and TS 38.521-1. Section 3.4.2 adds TIS/TRP OTA on the required bands and EN-DC combinations and notes that the CTIA OTA test plan version 10 release includes the Verizon bands as part of PTCRB.

Field testing: DFIT, pre-DFIT and GFIT

If a module or host must perform official DFIT (Domestic Field Interoperability Testing), pre-DFIT is required first; the OEM may run pre-DFIT with its own staff, any third-party lab or another organization.
For host devices on Verizon approved modules, official DFIT is only required for 5G SA VoNR and 5G RedCap.
For 5G SA data-only hosts on approved modules, 5G SA pre-DFIT is required and must be done at a Verizon approved lab; the official 5G DFIT is no longer required.
GFIT (Global FIT) follows the Global FIT test plan for devices roaming outside the United States.

Self-testing on the Auto-Certification Platform (ACP)

The ACP enables OEM self-testing for supported GCF and Verizon test plans for devices, chipsets and modules, free for OEMs. Before shipment the device must have completed DLD and the COI must be in place. The ACP ships only to US business addresses and to persons employed by the OEM; moving it abroad needs Verizon approval and export rules apply.

Additional testing for Verizon services

Standard lab testing comes first. Then, depending on features: LBS/aGPS/SUPL application testing, MMS testing with the Verizon MMSC for MMS-capable devices, On Site private 4G/5G testing at the Verizon Boston lab (credited to the device if the module already passed it), Verizon Response Verified for public safety devices, and NTN (Non-Terrestrial Network) certification, for which the scope is set with the certification manager.

Inbound Permanent Roaming

This matters for IoT devices sold with a foreign SIM. Verizon treats a device as roaming non-incidentally if its home operator says so, if it is fixed or of limited range, if it uses the Verizon network for 3 or more consecutive monthly billing cycles with more than 60% of its global traffic there, or if it carries a non-US profile while registered or licensed in the United States. Such devices follow a dedicated certification process described on the ODP.

Security

Some devices need penetration testing by a Verizon approved security lab. For a Parent/Child device family, the OEM provides a separate penetration report for each Parent and Child; a Child report may reuse the Parent scope and findings and must include a comparison matrix, and unfixed findings need a waiver request with a fix plan.

eUICC and RSP, what Verizon actually documents

Section 3.4.7.15 describes two architectures and no third.

Item	M2M eUICC (GSMA SGP.02)	Consumer eUICC (GSMA SGP.22)
Servers	SM-SR and SM-DP	SM-DP+, with an LPA in the device
Network-access requirement	LTE_3GPP_B13_NetworkAccess section 1.3.1.3.15, M2M eUICC parts	Same section, Consumer eUICC parts
eUICC status	Verizon Technical Acceptance; a third-party eUICC must pass Verizon eUICC Validation	RSP Functionality Matrix declares eUICC and LPA; an eUICC not yet validated goes through eUICC Validation with the Verizon SIM profile before any device testing
Device prerequisites	APN change by AT commands, handling of ICCID switch between operators, SIM slot (adapter) and logging capability	None beyond the matrix
Third-party integration	API for RSP, SMPP binds from the partner SM-SR to the Verizon SMSC and the partner SMSC, ES3 from partner SM-SR to Verizon SM-DP	Not applicable
Device testing	Per the M2M eUICC process guide on the ODP	None if the Verizon profile is preloaded on a validated eUICC; E2E Consumer eUICC testing if the profile is downloaded by RSP (headless M2M/IoT devices may test remotely)

After full M2M or Consumer eUICC certification, the OEM may use any eUICC already validated or Technically Approved by Verizon without further device testing, provided it sanity-tests before large deployment and accepts liability for eUICC feature failures.

Global IoT Orchestration (GIO) uses ThingSpace APIs to swap a Verizon US eSIM profile and a local-carrier profile over the air on SGP.02. It requires M2M eUICC (SGP.02) certification and a global-capable, GFIT certified device (through the module, the device, or a "GFIT LITE" run of GFIT test cases 9.1 and 9.2 in at least one target market).

Where SGP.32 stands

GSMA SGP.32, the eSIM IoT Technical Specification, was first published as version 1.0 on May 26, 2023; version 1.2 is dated June 27, 2024. It introduces the eSIM IoT remote Manager (eIM) and the IoT Profile Assistant, either in the device (IPAd) or in the eUICC (IPAe). Process version 41 does not mention SGP.32. A project counting on an SGP.32 eIM for Verizon has to confirm the path with the certification manager and the current ODP requirement documents rather than assume it.

Frequent eUICC pitfalls

eUICC never validated with the Verizon profile: validation must finish before any device testing.
LPA not declared, or not matching the RSP Functionality Matrix.
Architecture mismatch: M2M (SGP.02) prerequisites assumed for a Consumer (SGP.22) integration, or the reverse.
GIO assumed without GFIT: GIO eligibility requires GFIT or GFIT LITE.

Authorized labs (section 7, version 41)

Lab	Capabilities listed by Verizon
Bureau Veritas (formerly 7Layers)	4G Class 3 APN, LWM2M and OTADM FOTA, DFIT
Cetecom	4G, 5G NR FR1 OTA
ATMC Labs (formerly Intertek)	LTE, 5G lab test, RedCap, live network test, VoLTE, OTA, VoWiFi, DFIT
Element Materials Technology (formerly PCTEST)	5G and 4G lab conformance, RedCap, DFIT, OTA
SGS	LTE, multi-mode, VoLTE, VoWiFi, OTA, 5G FR1 and FR2, RedCap, DFIT
Tech Mahindra	5G FR1/FR2 Verizon supplemental RF and protocol, RedCap, VoNR, LTE, VoLTE, DFIT, OTA
Wireless Research Center	LTE OTA
Arclight Wireless	DFIT
Accenture (formerly umlaut and P3)	DFIT (US entity), GFIT (international entity)
Ericsson, Motive	Interoperability (IOT); Motive also FOTA
Carve Systems, Spirent, Palindrome	Penetration testing for IoT security

The list changes with each revision; check it before booking. For Safe For Network and for the 1200-activation allowance, the testing itself must be done at a Verizon-authorized lab for the reports to count. For planning, see also certification costs and certification timeline.

Dated milestones

Date	Event	Source
December 31, 2016	Verizon stops accepting new CDMA-only equipment for OD certification	Verizon CDMA retirement page
January 2018	Certifications recorded in the OD Notice of Certification, no more per-device CA addendum	Process 3.3
June 2022	Version 36: eUICC process references, IoT security moves to "Penetration Testing"	Process revision history
September 2022	Version 37: up to 1200 test devices with approved module and PTCRB/GCF/CTIA reports from approved labs	Process revision history
December 31, 2022	Verizon 3G CDMA network retirement completed; the network became inaccessible	Verizon CDMA retirement page
January 3, 2023	Verizon states it has decommissioned its CDMA network	Verizon CDMA retirement page, OD FAQ
May 26, 2023	GSMA SGP.32 version 1.0	SGP.32 v1.2 document history
2024	Version 39: CDMA references removed, TECC validity added, DFIT/GFIT and PTCRB updates, On Site only category	Process revision history
June 27, 2024	GSMA SGP.32 version 1.2	SGP.32 v1.2
June 2025	Version 40: Fast Track added, ACP update, GIO section, M2M and Consumer eUICC updates, NTN section started	Process revision history
December 2025	Version 41: Fast Track and section 3.4.2 updated with DFIT and RF OTA requirements	Process revision history

Claims the texts contradict

Common claim	What the Verizon, PTCRB or GSMA text says
"PTCRB is the radio prerequisite for Verizon"	Process 3.1 requires GCF certification for LTE-capable devices before OD conformance testing; PTCRB counts for Fast Track (PTCRB or GCF) and for the 1200-activation allowance (PTCRB, CTIA or GCF)
"Band 13 is the Verizon band in PTCRB"	PVG.11 V5.24.0 names Verizon on no single LTE or NR band, only on some EN-DC combinations; the Verizon band list sits in the OD requirement documents
"Safe For Network gives 1200 activations" (this page said so before)	SFN gives up to 500 activations per project; 1200 comes from PTCRB, CTIA or GCF testing on the Verizon bands at a Verizon-authorized lab
"A TECC is valid for 90 days"	Section 3.2: testing should begin within 90 days of the final TECC release; if not, the certification manager decides whether a new TECC is needed
"An approved module means the product can be activated"	FAQ: "Approved modules are not certified devices"; every host device must be certified
"Official DFIT is always required"	For hosts on approved modules, official DFIT only for 5G SA VoNR and 5G RedCap; 5G SA data-only hosts do pre-DFIT at an approved lab instead
"Verizon charges a certification fee"	FAQ: Verizon does not charge developers for device certification; lab costs apply
"Verizon certification takes months"	FAQ: typical lab time is expected to be weeks rather than months; no service level is published
"Verizon accepts SGP.32 eSIM IoT devices through a defined path"	Process version 41 documents SGP.02 and SGP.22 only; SGP.32 calls its server the eSIM IoT remote Manager (eIM), not "eSIM IoT Manager"
"Consumer eUICC always means device eUICC testing"	No additional device testing if a validated SGP.22 eUICC has the Verizon profile preloaded; E2E testing only when the profile is downloaded by RSP
"CDMA fallback is still possible"	CDMA retirement completed by December 31, 2022; Verizon no longer activates 1X, 3G or 4G non-VoLTE devices

Post-certification lifecycle

Section 6 runs its own change process, separate from FCC permissive changes (see FCC change management):

for any update to certified software or hardware, the developer notifies the ODPT and provides updated submission documents describing the changes;
the ODPT and NDET lab decide the level of regression testing, run at an OD-authorized lab in coordination with NDET;
after the regression criteria pass, the ODPT certifies the Device Maintenance Release and issues an official notification.

The Notice of Certification carries a Certification Period, and the FAQ adds that equipment not re-certified after the end of that period, or after a modification, will not get additional activations. Test devices sold as production units must be re-uploaded as certified devices through ODP or EDI.

Common pitfalls

1. Planning on PTCRB alone

The Verizon text asks for GCF before OD conformance for LTE devices, and uses PTCRB only in the Fast Track and pilot allowances. Check which certificate the TECC expects before booking the radio campaign.

2. Picking a non-approved module

The approved-module choice decides Fast Track eligibility, ENAP allowances (20 or 2), the 1200-activation pilot allowance and DFIT waivers. Switching modules mid-project repeats the antenna, FCC, PTCRB or GCF and Verizon work.

3. Radio lab not authorized by Verizon

For Safe For Network and the 1200-activation allowance, the PTCRB, CTIA or GCF testing must be done at a Verizon-authorized lab. Testing elsewhere means testing again.

4. eUICC not validated with the Verizon profile

A GSMA-certified eUICC is not enough: it needs Verizon Technical Acceptance or eUICC Validation, and the eUICC/LPA pair must be declared in the RSP Functionality Matrix.

5. Stale requirement documents and expired TECC

The process document changed in 2024, June 2025 and December 2025. Re-check document versions on the ODP at each project gate, start lab testing within 90 days of the final TECC release, and avoid letting the submission go inactive for more than six months.

6. Underestimating the administrative entrance criteria

NDA, FCC ID, BIS ECCN and CCATS, Certification Agreement and Certificate of Insurance are all entrance or certification conditions. Start them with the design work, not after the radio campaign.

7. Mixing Verizon with AT&T and T-Mobile

Each US carrier runs its own programme on top of industry certification: AT&T Network Ready (with IoT Network Certified as its industry step) and the T-Mobile device certification. Verizon Open Development is Verizon-only. See PTCRB pitfalls for the broader view.

Project timing, the right sequence

Design phase: select a module from the Verizon approved list, settle the eSIM architecture (SGP.02 or SGP.22) against the current ODP documents.
Administrative phase: register on the ODP (NDA), start the Certification Agreement and insurance, secure the FCC ID and BIS classification.
Early testing phase: ENAP activations for development; Safe For Network (500) or PTCRB/CTIA/GCF at an authorized lab (1200) for pilots.
Radio certification phase: GCF (and PTCRB where used) at a Verizon-authorized lab, with TIS/TRP OTA on the required Verizon bands and EN-DC combinations.
OD certification phase: device submission and DLD, TECC, lab testing within 90 days, DFIT where required, FOTA and IoT security reports, eUICC results.
Activation phase: device ID upload into the DMD (ODP or EDI), commercial launch.
Lifecycle phase: Device Evolution notifications for every hardware or software change, regression testing, Certification Period tracking.

For the global EU + US sequence including CE/RED, see EU + US dual certification and certification timeline.

Connection with other US certifications

FCC: an FCC ID is required before OD conformance testing and before any activation on the Verizon network, including test devices.
FCC radio bands: overlap with Verizon bands, but the regulatory and carrier test plans are separate.
FCC tests: cover regulatory emissions; the Verizon campaign adds carrier network conformance.
PTCRB tests: the multi-carrier baseline. Verizon completed its 3G CDMA retirement by December 31, 2022 and no longer activates 1X, 3G or 4G non-VoLTE devices; new devices are LTE (including LTE-M and NB-IoT) and 5G.

A cellular product sold on Verizon in the United States therefore accumulates: an FCC ID, the BIS classification, GCF or PTCRB certification as the Verizon route requires, the Verizon OD Notice of Certification, and device identifiers loaded in the Verizon DMD.

For the vocabulary (PVG, LPA, SM-DP+, eUICC), see the spilma glossary.

Frequently asked questions

Why is PTCRB or GCF not enough to activate a product on the Verizon network?: Because Verizon runs its own Open Development (OD) certification on top of industry certification. Its process document (version 41, December 2025) requires an FCC ID, a BIS export classification (ECCN and CCATS) and, for LTE-capable devices, GCF certification before OD conformance testing starts. The device is then tested against a Verizon test campaign (TECC) at a Verizon-authorized lab. Only after certification can the manufacturer upload device IDs into the Verizon Device Management Database (DMD); devices not uploaded through ODP or EDI cannot be activated.
What is the difference between module approval and device certification at Verizon?: The process document states that a host device is certified using an approved module or chipset, and that modules and chipsets are approved through the Open Development portal (ODP) under the Module Guidelines. The Verizon FAQ is explicit that approved modules are not certified devices: every host device using an approved module must itself be certified. An approved module does open the Fast Track route for data-only LTE or 5G NSA host devices and raises the early development allowance from 2 to 20 activations.
How long does Verizon Open Development certification take?: Verizon publishes no service level. Its FAQ only says it expects typical lab time to be weeks rather than months, and encourages an approved module to reduce testing time. Two published clocks matter for planning: testing at the lab should begin within 90 days of the final TECC release, and a submission left inactive for more than six months is set to INACTIVE and may have to meet the most recent requirements on reactivation.
Does Verizon charge a certification fee?: No. The Open Development FAQ states that Verizon does not charge developers for device certification. Testing costs are set by the external labs and paid by the manufacturer, and Verizon may impose costs for access to lab facilities.
Which labs are authorized for Verizon Open Development testing?: Section 7 of process version 41 lists Bureau Veritas (formerly 7Layers), Cetecom, ATMC Labs (formerly Intertek), Element Materials Technology (formerly PCTEST), SGS, Tech Mahindra and the Wireless Research Center for conformance and OTA work; Arclight Wireless and Accenture (formerly umlaut and P3) for field testing; Ericsson and Motive for interoperability and FOTA; and Carve Systems, Spirent and Palindrome for IoT security penetration testing. All listed addresses of the conformance labs are in the United States.
Does eUICC change anything in the Verizon certification procedure?: Yes. Process version 41 documents two architectures: M2M eUICC (GSMA SGP.02, SM-SR and SM-DP) and Consumer eUICC (GSMA SGP.22, SM-DP+ and an LPA). An M2M eUICC must already have Verizon Technical Acceptance, and a partner eUICC must pass Verizon eUICC Validation. For Consumer eUICC the OEM fills in the RSP Functionality Matrix; an eUICC not previously validated goes through eUICC Validation with the Verizon SIM profile before any device testing. The document does not describe an SGP.32 path.
Is re-certification required after a firmware or hardware change?: Section 6 requires the developer to notify the Open Development Product Team (ODPT) of any update to certified software or hardware and to provide updated submission documents. The ODPT and the NDET lab decide the level of regression testing, which an OD-authorized lab runs; the ODPT then certifies the Device Maintenance Release. The OD Notice of Certification also sets a Certification Period for each device.
What happens if a product is shipped without Verizon certification?: Device IDs are loaded into the Verizon DMD only for certified devices, and the process document states that devices not uploaded through ODP or EDI will be prevented from activating. For rogue devices or Certification Agreement violations, Verizon can ask for 2 samples within 48 hours, restrict or deactivate the device, de-certify it and stop provisioning further units.