Verizon Open Development: homologation after PTCRB/GCF

Author Hugues Orgitello Last updated 11 July 2026 ~15 min read

Guide · Verizon Open Development

You have obtained PTCRB or GCF certification and you thought the North American cellular chapter was closed. Verizon then adds a mandatory layer: Open Development (OD) device certification, driven from the Open Development portal (ODP). PTCRB and GCF prove multi-carrier radio conformance, OD certification proves that the product behaves correctly on the Verizon network specifically. This page describes where OD sits relative to PTCRB and GCF, how the portal workflow operates, the module/device structure, the Fast Track process, eUICC requirements, and the pitfalls that delay US market entry.

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, however, cover the same scope.

Criterion	PTCRB	Verizon Open Development
Nature	Cross-carrier programme (AT&T, T-Mobile, Verizon, Bell, Rogers, Telus)	Verizon-specific programme
Reference	PTCRB test plans based on 3GPP TS 36.521 and TS 38.521	Verizon test campaign (TECC) built from the OD requirement documents
Scope	Generic multi-carrier radio conformance	Verizon bands, RF OTA (TIS/TRP), FOTA, eSIM, IoT security, field testing
Granted by	CTIA Certification (PTCRB scheme)	Verizon Open Development Product Team (ODPT)
Outcome	EPC (End Product Certification) or Modular Certification	OD Notice of Certification, IMEI loaded into the Verizon Device Management Database (DMD)
Required for Verizon activation	PTCRB or GCF is the radio prerequisite	Yes, in addition

Radio conformance certification is a prerequisite but not sufficient. Verizon's published process requires GCF certification for LTE-capable devices before OD conformance testing can start, and its Fast Track process accepts either a PTCRB or GCF certificate with RF OTA results on the Verizon bands. Two further entrance criteria apply before OD testing: an FCC ID and an export-control classification (BIS ECCN/CCATS). 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 works on the Verizon network. The second requires the first; the first does not include the second.

The Open Development portal (ODP), entry point

The Open Development portal is the Verizon entry point any manufacturer must use to submit a cellular product. The programme was historically launched as the Open Development Initiative (ODI), and the login URL still uses that name; Verizon today simply calls it Open Development. Access to the detailed documents requires executing an NDA, after which the developer receives a unique VZW-ID used to track its devices. The portal provides:

• the Requirement & Test Plan documentation (login required);
• the public approved modules list and the certified device showcase;
• the device submission workflow (device info, marketing info, forecast, release notes, pre-submission documents);
• the Device Lock Down (DLD) review that freezes the dossier and triggers the test campaign (TECC);
• the device ID upload into the Verizon DMD once certification is granted (via ODP or EDI);
• the Device Evolution declarations for post-certification changes.

Two contractual documents must be completed before certification is granted: the Certification Agreement (CA) and a Certificate of Insurance (COI). For a first-time non-US submitter, this administrative phase takes real calendar time and should start early. Test costs are paid directly to the labs.

The portal also links to ThingSpace, Verizon's IoT platform for connectivity management, which is the operational side of running a certified fleet on the network.

For early development, Verizon offers the Early Network Access Program (ENAP): up to 20 development activations when using a Verizon-approved module, 2 without. After successful PTCRB, CTIA or GCF testing at a Verizon-authorized ITL, the Safe For Network path allows up to 1200 test activations per project for pilots and trials.

Two-tier structure, module and device

Verizon certification follows a two-step logic very similar to PTCRB: a host device is certified using an approved module or chipset, and modules or chipsets are approved through the ODP under Verizon's Module Guidelines. A PTCRB-certified module is not automatically Verizon-approved; the approved modules list is published on the portal.

Tier 1, module or chipset approval

Applies to cellular module manufacturers (Quectel, u-blox, Telit, Sierra Wireless, Murata, Sequans, Fibocom and so on). Approval covers, among other things:

• radio conformance and RF OTA on the Verizon bands (notably B13 700 MHz, B66 and B4 AWS, B2, B5 in LTE; n5, n66, n77 C-band and n260/n261 mmWave in NR; the binding list of required bands and EN-DC combinations is defined in the OD requirement documents);
• Verizon base-band FOTA capability, using OMADM or LWM2M device management;
• LWM2M diagnostics, required for all modules and chip-on-board devices;
• security compliance documentation or test results, required before the module DLD;
• eUICC validation with the Verizon profile where eSIM is supported.

On success, the module is added to the public approved modules list, making it usable as a pre-approved building block by integrators.

Tier 2, device certification

Applies to the end product integrating a cellular module. Even with an approved module, device certification remains mandatory. The scope is integration, not the module radio itself:

• product antennas and RF OTA performance (TIS/TRP on the required Verizon bands; an external antenna with a cable lead over 20 cm and no TIS/TRP results triggers additional RF supplementary testing);
• verification that the module's Verizon FOTA capability is still functional in the end product;
• application firmware and its interaction with the cellular stack;
• product-level eSIM/eUICC behaviour;
• field interoperability testing (DFIT) where required by the test campaign;
• IoT security compliance, with penetration testing at Verizon-approved security labs.

See PTCRB procedure for how this module-plus-device structure maps onto the project timeline.

The value of a Verizon-approved module, and the Fast Track

Selecting a module already on the approved modules list is the single most profitable optimisation in a Verizon programme.

With an approved module:

• the module approval is already done, so the device campaign is faster and cheaper;
• ENAP allows up to 20 development activations instead of 2;
• the official DFIT field test is waived for host devices using approved modules, except for 5G SA VoNR and 5G RedCap;
• most importantly, the device may qualify for the Fast Track certification process.

Verizon certifies a host device through Fast Track when the following criteria are met:

• the network technology is 4G LTE or 5G NSA and the device is data-only (no voice);
• the device uses a Verizon-approved module;
• a final PTCRB or GCF test report and certificate are provided, including TIS/TRP RF OTA measurements for all required Verizon bands and EN-DC combinations;
• self-test reports are provided for FOTA compliance and IoT Security compliance;
• eUICC test results are provided if the device supports eUICC;
• the device is not classified as Performance Critical or Verizon Response Verified (VRV).

This decision belongs in the design phase, not after the fact. The approved modules list evolves; it must be checked at T0 of every project directly on the ODP.

OD test categories

The test campaign (TECC) is defined by the ODPT per device. For the equivalent PTCRB tests, see PTCRB tests. The main families:

RF conformance and OTA performance

The radio baseline is the PTCRB or GCF campaign on 3GPP TS 36.521-1 and TS 38.521-1, run on the Verizon bands at a Verizon-authorized ITL. On top of that, Verizon expects TIS/TRP OTA measurements meeting its RF OTA requirements on all required bands and EN-DC combinations; CTIA OTA test plan version 10 includes the Verizon bands as part of PTCRB. Devices with long external antenna leads and no TIS/TRP results get RF supplementary testing.

Field and interoperability testing

Beyond lab conformance, the campaign can include Domestic Field Interoperability Testing (DFIT) on the live Verizon network, Global FIT (GFIT) for devices that roam, and interoperability (IOT) lab sessions run with network vendors (Ericsson, Motive for FOTA). For host devices on approved modules, official DFIT is only required for 5G SA VoNR and 5G RedCap.

Self-testing via the Auto-Certification Platform

Verizon's Auto-Certification Platform (ACP) enables OEM self-testing for supported GCF and Verizon test plans for devices, chipsets and modules. It is free for OEMs to use and portable, subject to conditions (completed DLD among them).

Additional testing for Verizon services

Depending on the features supported, Verizon adds service-specific test flows, for example LBS/aGPS/SUPL application testing for location features, or MMS server testing for MMS-capable devices, plus dedicated flows for private network (On Site) products.

Security and provisioning

Chipsets, modules and devices must provide security compliance documentation or test results before DLD; non-compliant features require a disclosed and approved waiver. Verizon maintains a list of approved IoT security penetration-testing labs and recommends its IoT Security Credentialing service for device fleets.

eUICC and RSP, what Verizon actually documents

Since the release of GSMA SGP.32 in 2023 and its gradual industry adoption, eSIM has become a structuring topic for cellular IoT certification. It is also the topic where manufacturers are most often caught out, so it is worth being precise about what Verizon's published process actually requires.

Three GSMA references, SGP.02, SGP.22 and SGP.32

Distinguish:

• GSMA SGP.02: M2M architecture (push model), built on SM-SR and SM-DP servers.
• GSMA SGP.22: Consumer RSP, consumer eSIM (smartphones, watches, tablets). The device has a local LPA (Local Profile Assistant) that talks to a carrier SM-DP+. Profile downloaded via QR code or application.
• GSMA SGP.32: IoT RSP, designed for the constraints of connected objects (no UI, large fleets). Introduces the eSIM IoT Manager (eIM) role and the IPAd/IPAe split.

The two paths in the Verizon process

The current published edition of the Open Development Device Certification Process documents two eUICC paths: the M2M architecture (SGP.02) and the Consumer architecture (SGP.22). In both cases:

• the eUICC must have completed Verizon Technical Acceptance or eUICC Validation with the Verizon SIM profile before device testing can start;
• the OEM declares the eUICC and the LPA used in the RSP Functionality Matrix form available on the OD portal;
• for M2M eUICC, additional prerequisites apply: compliance with the Verizon network-access requirement document, APN switching via AT commands, a SIM slot and logging capability for test purposes, and, for third-party eUICCs, integration between the partner SM-SR and the Verizon infrastructure (SMPP binds, ES3 integration).

SGP.32 is the direction the IoT industry is taking, but the certification path for a given Verizon project must be confirmed against the current requirement documents on the ODP rather than assumed. Locking an eSIM architecture before that check is one of the most expensive mistakes on a modern cellular product.

Frequent eUICC pitfalls

• eUICC never validated with the Verizon profile: the eUICC Validation process must complete before any device testing, adding weeks if discovered late.
• LPA capabilities not declared or not matching the RSP Functionality Matrix submitted on the portal.
• Architecture mismatch: an M2M (SGP.02) integration where the project assumed Consumer (SGP.22) flows, or vice versa; the prerequisites differ.
• Headless product on a consumer flow: QR-code based activation is painful on a device with no screen; the architecture question must be settled at design time.

These pitfalls are not covered by PTCRB, which does not test the eUICC and provisioning chain with a real carrier profile.

Authorized labs

Not every PTCRB lab is authorized for Verizon testing. Verizon publishes the list of authorized Independent Test Laboratories (ITL) in its certification process document. The current edition names:

• Bureau Veritas (formerly 7Layers);
• Cetecom;
• ATMC Labs (formerly Intertek);
• Element Materials Technology (formerly PCTEST);
• SGS;
• Tech Mahindra;
• Wireless Research Center (OTA);
• field-test specialists: Arclight Wireless (DFIT) and Accenture (formerly umlaut/P3, DFIT and GFIT);
• interoperability and FOTA labs: Ericsson, Motive;
• IoT security penetration testing: Carve Systems, Spirent, Palindrome.

The list evolves with each revision of the process document and must be checked before booking each campaign. The authorized conformance ITLs are US-based; European manufacturers should plan device logistics accordingly (GFIT campaigns are run internationally). Note that for the Safe For Network and Fast Track paths, even the PTCRB, CTIA or GCF testing must be conducted at a Verizon-authorized ITL for the reports to count. For planning, see also certification costs and certification timeline.

Qualitative cost and schedule

Verizon does not publish a public rate card. Certification costs depend on:

• the product category (module, data-only device, feature-rich device);
• the presence or absence of an approved module, which decides Fast Track eligibility (the single biggest lever);
• the number of target Verizon bands and EN-DC combinations for OTA;
• the eUICC path (none, M2M, Consumer) and whether the eUICC is already validated;
• the number of iterations to expect if the first campaign fails.

Qualitatively, OD certification adds to PTCRB or GCF in both schedule and cost. For an IoT product with an approved module on the Fast Track, the addition is limited; for a full campaign with field testing and eUICC validation, expect several additional weeks to months. These figures are indicative: the final quote depends on the test campaign (TECC) Verizon retains at submission, and should be built with an authorized ITL after scope definition.

Articulation with chipset pre-certification

Chipset vendors (Qualcomm, MediaTek, Sequans, UNISOC) produce pre-certification reports on their reference platforms covering radio conformance, IMS/VoLTE behaviour and eSIM pre-validation. In the Verizon model, chipsets themselves can be approved through the ODP, and a host device can be certified on the basis of an approved chipset.

These elements accelerate certification but do not replace it. The device-level campaign remains mandatory because it applies to the integrated product (real antennas, final PCB, application firmware, power management). The ODPT and the NDET lab define the device test campaign case by case, based on what the platform already covers.

Post-certification lifecycle management

Verizon does not use the FCC's Class I/II/III permissive-change vocabulary; it runs its own Device Evolution, Maintenance and Regression Testing process:

• for any update to certified software or hardware, the developer must notify the ODPT and provide updated submission documents describing the changes;
• the ODPT and NDET lab determine the level of regression testing required, executed at an OD-authorized ITL;
• after the regression criteria pass, the ODPT certifies the Device Maintenance Release and issues an official notification.

Two administrative details matter: the Notice of Certification defines a Certification Period for the device, and a submission left inactive for more than six months is flagged inactive and, upon reactivation, may have to be re-evaluated against the most recent requirements. Verizon also reserves the right to restrict, deactivate or de-certify rogue devices that harm the network or violate the Certification Agreement. Continuous dossier management is part of the total cost of ownership, not only the initial certification. (See FCC tests for the separate regulatory change-management logic.)

Common pitfalls

1. Assuming PTCRB or GCF is enough for Verizon

This is the structural error. A radio-certified product without OD certification cannot be activated commercially: device identifiers absent from the Verizon DMD are refused. The discovery often happens right before launch, when the commercial team attempts to activate the first Verizon SIMs.

2. Picking a non-approved module by default

Many teams select a module on PTCRB and cost criteria alone. If the project targets Verizon, the approved modules list filter must be applied at module selection, not afterwards: it decides Fast Track eligibility, ENAP allowances and DFIT waivers. Switching modules mid-project is costly in PCB redesign, antenna redesign, FCC re-validation, PTCRB re-test, and the Verizon campaign itself.

3. eUICC not validated with the Verizon profile

A GSMA-certified eUICC is not enough: the eUICC must have completed Verizon eUICC Validation or Technical Acceptance with the Verizon SIM profile, and the eUICC/LPA combination must be declared in the RSP Functionality Matrix. Discovering this at submission adds weeks.

4. Wrong eSIM architecture for the product

The Verizon process documents distinct M2M (SGP.02) and Consumer (SGP.22) paths with different prerequisites. Choosing a consumer pull-mode flow for a headless IoT product, or assuming an architecture Verizon has not validated for your eUICC, creates activation UX problems and re-engineering. Settle the architecture against the current ODP requirement documents at design time.

5. Working from stale requirement documents

The OD requirement and process documents are revised regularly (recent revisions removed CDMA references, added the Fast Track process, updated DFIT/GFIT and RedCap rules, and reworked the eUICC sections). Manufacturers who design against an old PDF find themselves out of conformance at submission. Re-check the current document versions on the ODP at each project gate; note also that a test campaign (TECC) is only valid for 90 days from the approval to start testing.

6. PTCRB lab picked by default

A PTCRB lab is not automatically Verizon-authorized. For the Fast Track and Safe For Network paths, the PTCRB, CTIA or GCF testing itself must be conducted at a Verizon-authorized ITL for the reports to count. Launching the radio campaign without checking this leads to a double bill: tests have to be redone elsewhere. To be scoped upfront.

7. Underestimating the administrative phase

The NDA for portal access, the Certification Agreement, the Certificate of Insurance, the FCC ID and the BIS export-control classification are all entrance requirements. For a first-time European submitter, plan several weeks of administrative work before the first test.

8. Mixing Verizon certification with AT&T/T-Mobile homologation

Every US carrier has its own programme (AT&T Network Ready, T-Mobile's own device approval). Verizon Open Development is Verizon-only. A Verizon report has no value at AT&T and vice versa. To target the three US carriers, plan three distinct programmes on top of PTCRB/GCF. See PTCRB pitfalls for the broader view.

Project timing, the right sequence

The recommended order for a cellular product targeting Verizon:

1. Design phase: select a Verizon-approved module from the public list, settle the eSIM architecture against the current ODP documents.
2. Administrative phase: register on the ODP (NDA), start the Certification Agreement and insurance paperwork, secure the FCC ID and BIS classification path.
3. Early testing phase: use ENAP activations for development; after PTCRB/CTIA/GCF testing at an authorized ITL, request Safe For Network activations for pilots.
4. Radio certification phase: PTCRB or GCF campaign at a Verizon-authorized ITL, including TIS/TRP OTA on the required Verizon bands and EN-DC combinations.
5. OD certification phase: submission and DLD, test campaign (TECC) at the ITL, DFIT if required, FOTA and IoT Security reports, eUICC results.
6. Activation phase: device ID upload into the DMD (via ODP or EDI), activation verification, commercial launch.
7. Lifecycle phase: Device Evolution declarations 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

Verizon Open Development scope is distinct from other US requirements:

• FCC, intentional and unintentional emitters: independent, and a prerequisite; the FCC ID is required before OD conformance testing.
• FCC radio bands: overlap with Verizon bands but the test plans are disjoint; measurements can inform each other but reports are separate.
• FCC tests: cover regulatory emissions; the Verizon campaign adds carrier network conformance.
• PTCRB tests: form the multi-carrier baseline that the Verizon campaign extends. Verizon retired its 3G CDMA network at the end of 2022; the programme is now purely LTE and 5G.

A cellular product sold on Verizon in the United States therefore accumulates: FCC ID (regulator), PTCRB or GCF certification (radio conformance), the Verizon OD Notice of Certification, and device identifiers loaded in the Verizon DMD.

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

See also

• Telstra, Optus, TPG: cellular IoT acceptance in Australia
• HAC: Hearing Aid Compatibility (FCC 20.19, C63.19)
• T-Mobile US: cellular IoT device certification and DICE
• Orange Connected Validation: IoT device labels
• Vodafone Global IoT: device acceptance and eSIM
• Deutsche Telekom IoT: acceptance, nuSIM and Cloud of Things

Verizon cellular IoT programme

Let's scope your PTCRB/GCF + Verizon dossier in 30 minutes.

AESTECHNO designs the joint PTCRB/GCF and Verizon Open Development campaign, selects a Verizon-approved module compatible with your design, and secures the eUICC requirements, free, by video call.

Book a cellular audit

Sources & references

1. Verizon Open Development portal , Verizon opendevelopment.verizonwireless.com/
2. Open Development Device Certification Process (v41, 2025) , Verizon opendevelopment.verizonwireless.com/content/dam/opendevelopment/pdf/OpenAccessReq/OD_Certification_Process_v41.pdf
3. Verizon Open Development, approved modules , Verizon opendevelopment.verizonwireless.com/design-and-build/approved-modules
4. PTCRB Certification Program , PTCRB www.ptcrb.com/
5. GSMA eSIM Consumer and IoT specifications (SGP.22, SGP.32) , GSMA www.gsma.com/solutions-and-impact/technologies/esim/esim-specification/
6. 3GPP TS 36.521 and TS 38.521, UE RF conformance specifications , 3GPP www.3gpp.org/specifications-technologies