PTA CoC Process in Pakistan (2026): A Practical Commercial Import Guide

What is PTA CoC process in Pakistan?

For commercial imports, Certificate of Compliance (CoC) is the consignment-level compliance process used for SIM/IMEI-based terminal equipment that has already been type approved. Pakistan’s Trade Information Portal specifically gives examples such as mobile phones, trackers, tablets and point-of-sale machines.
The cleanest distinction is: Type Approval is model-level regulatory approval, while commercial CoC handles the imported units and their IMEIs against a shipment. A model can already be type approved and still require commercial CoC for the imported consignment.

Before filing PTA CoC Process in Pakistan: confirm the exact approved model

Do not rely on a similar marketing name. Match the exact model identity used in the PTA approval record. This is especially important for cellular modules, embedded trackers and POS terminals where the host-product name can differ from the cellular module or radio model used for approval.

Prepare the shipment dataset

⦁ Commercial DIRBS/DRS access and the relevant FBR/WeBOC account/workflow.
⦁ Commercial invoice with exact model and quantity.
⦁ AWB/HAWB or other shipment reference that the clearing agent can reconcile to the GD.
⦁ Correct HS code used consistently across the application and customs documentation.
⦁ IMEI CSV in the exact required format, cleaned of duplicates and formatting errors.
⦁ SIM-slot count per device so the expected IMEI count is understood.
⦁ Type-approved model/TAC confirmation before the goods are cleared.

Step-by-step commercial PTA CoC Process in Pakistan flow

1. Sign in to the PTA Device Registration System (DIRBS/DRS) using the commercial account.
2. Create the relevant commercial CoC application and enter shipment and equipment data. Upload the IMEI file and supporting documents required by the current portal.
3. Submit the case. The official TIPP description says DIRBS validates IMEIs, including checks that they are GSMA-valid and not duplicated or reported stolen.
4. After PTA-side validation, the application is transmitted through the DIRBS integration to FBR WeBOC. This is a handoff state, not necessarily final CoC issuance.
5. Complete the applicable customs/GD process and ensure the customs-side data match the DIRBS case.
6. Once the required FBR/WeBOC response is completed, the commercial CoC can be generated through the integrated process.
   Editorial note: Do not interpret ‘processed and sent to WeBOC’ as ‘CoC fully approved’. Operationally it means the case has moved into the customs-integrated stage and the GD/shipment data still need to reconcile.

Why clean data matters more than repeated follow-up

Many delays are not radio-compliance failures. They are reconciliation failures: wrong HS code, wrong waybill reference, quantity mismatch, wrong model identity, a dirty IMEI file or a GD that does not correspond to the PTA case. For repeat importers, keep one controlled shipment sheet containing invoice, AWB/HAWB, GD, HS code, model, TAC, SIM count, physical quantity and IMEI range.

Partial shipment: where importers get into trouble

If an order is invoiced as one shipment but physically arrives in lots, do not casually submit every IMEI against the first lot. Confirm which pallets/cartons and IMEIs are actually part of the current GD. Keep the balance segregated for the later clearance path. The important principle is reconciliation between the specific devices being cleared and the customs record being processed.

If PTA requests verification

A verification request should be answered with evidence that links the submitted IMEI to the exact device/model. For embedded devices or modules, use clear photographs of labels, model markings and IMEI output/screens where applicable. Generic brochures are weaker than evidence that connects the physical unit to the submitted identity.

Where the process could improve

The underlying integration makes sense: PTA checks device identity/compliance while FBR handles customs. The weakness is user-facing status clarity. A stronger portal would show a timeline such as PTA validation complete -> transmitted to WeBOC -> GD linked -> customs response received -> CoC generated, and it would identify the exact mismatch field when something fails.

FutureByte verdict

PTA CoC Process in Pakistan is manageable when the model is already approved and the shipment dataset is clean. The real difficulty is the handoff among supplier, importer, clearing agent, DIRBS and WeBOC. Good pre-shipment data control prevents more delay than chasing the application after submission.

FAQ

Is Type Approval the same as commercial CoC?
No. Type Approval is model-level approval; commercial CoC is the shipment/device-IMEI compliance step for applicable imported units.
What does sent to WeBOC mean?
It means the DIRBS-side case has moved to the integrated FBR/customs stage. It is not, by itself, the same as final CoC generation.
Can a tracker, POS or cellular tablet require CoC?
Yes. The official TIPP measure explicitly includes SIM/IMEI equipment such as trackers, tablets and POS machines when the relevant conditions apply.
Why can an already type-approved device still get stuck?
Common causes include IMEI/TAC issues and mismatch in HS code, shipment reference, quantity or customs/GD data.