WeBOC Troubleshooting: Common Goods Declaration Errors and How to Fix Them
Quick Answer
Common WeBOC errors that delay clearance include: incorrect HS code classification triggering a tariff-rate mismatch, a declared CIF value below the valuation database reference, documents attached to the wrong field or in an unsupported format, a consignee name that does not match the PSW profile exactly, and unit-of-measurement errors where the declared unit differs from the tariff schedule unit. Each generates a formal query under FCA that stops the clearance clock.
| Top error | HS code misclassification — a wrong code triggers the wrong duty rate and an assessment query |
|---|---|
| Second most common | Valuation discrepancy — declared CIF value below the WeBOC database reference for that HS code and origin |
| Document errors | Attachments in the wrong format, missing mandatory attachments, or documents not matching the declaration data |
| Entity mismatch | Consignee name on the bill of lading does not match the PSW-registered importer name exactly |
| Unit error | Declaring in a unit of measurement — kilograms, litres, pieces — that differs from the First Schedule tariff unit for that HS code |
A goods declaration that clears WeBOC on the first filing means the container gates out the same day. A declaration that bounces back with a query means the container sits at the terminal while the clearing agent diagnoses the error, prepares a response, and waits for the assessing officer to review it. The difference is measured in demurrage at USD 85 to 290 per container per day. This guide covers the WeBOC filing errors that cause the most trouble at Karachi Port and Port Qasim, how to identify them, and how to fix them.
HS code misclassification
The single most common cause of a WeBOC query is an HS code that does not match the goods. Under FCA, the assessing officer compares the declared HS code against the goods description, and if the two do not align — "machinery" declared under a seed heading, for example, or a fertiliser declared under a heading reserved for pesticides — the officer raises a query.
The fix is to classify before filing, not after. Use the FBR Pakistan Customs Tariff to identify the correct 8-digit heading based on the goods' composition, function, and technical specification. For agricultural imports, our HS codes reference page covers the main headings for seeds, fertilisers, and machinery.
If a query on HS code classification arrives, the clearing agent must respond with the correct code and supporting justification — the relevant heading text from the tariff, the explanatory notes, and, where available, a prior classification ruling for the same or similar goods. The response must be in WeBOC, attributed to the agent's licence, and the officer can accept or reject it. If the officer rejects the response and assesses at a different code, the importer can appeal through the valuation and classification appeals process.
Valuation discrepancy
A declared CIF value that falls below the WeBOC valuation database reference for the same HS code and origin triggers a valuation query. The officer will ask for supporting documentation: the supplier's commercial invoice, the sales contract, proof of payment, and the freight and insurance invoices.
The importer who has the full documentation set — a genuine transaction with a verifiable payment trail — can respond with confidence. Our customs valuation guide covers the valuation process and the evidence that supports a declared value.
The importer who does not have the documentation — because the invoice was understated for customs purposes — faces a painful choice: admit the under-declaration and face revaluation and penalty, or attempt to support an unsupportable value and risk an escalated investigation. The prevention is to declare the actual transaction value from the start, which is the legal requirement and the fastest path through assessment.
Document attachment failures
WeBOC requires specific documents to be attached to the goods declaration depending on the commodity and the regulatory path. Missing, incorrectly formatted, or misplaced attachments cause rejection at filing or a query during assessment.
Common document errors:
- Wrong format. The system accepts PDF attachments. Scanned images saved as JPEG, PNG, or TIFF, password-protected PDFs, or files that exceed the size limit will be rejected.
- Missing mandatory attachment. For seed imports, the DPP import permit must be attached. For FTA claims, the certificate of origin must be attached. For machinery claiming the budget exemption, the MNFSR certificate must be attached. Filing without these triggers an immediate query.
- Mismatched attachment. The attached document does not match the declaration data — a different supplier's invoice, a permit for a different consignment, a stale certificate. The assessing officer will identify the mismatch and raise a query.
The fix is a pre-filing document checklist: every attachment verified for format, content, and relevance, and uploaded to the correct field before the declaration is submitted.
Consignee name mismatch
The consignee name on the bill of lading must match the importer's registered name in the Pakistan Single Window exactly. A single character difference — "ABC Trading" versus "ABC Trading (Pvt) Ltd" — can prevent the system from matching the goods declaration to the incoming cargo manifest, and the declaration will not proceed to assessment.
The fix is to verify the consignee name on the bill of lading draft before the vessel sails. If the supplier entered the wrong name, the bill of lading must be amended at origin, before the vessel departs. An amendment after the vessel has sailed is slower, more expensive, and may require a letter of indemnity from the shipper.
Unit-of-measurement mismatch
The First Schedule to the Customs Act specifies the tariff unit for each HS code. If the importer declares the quantity in a unit that differs from the tariff unit — for example, declaring a machinery consignment in kilograms when the tariff unit is "u" for number of units — the system may flag the inconsistency.
The fix is to check the tariff unit for the HS code before filing and declare in that unit. For goods that are naturally measured in a different unit, an explanatory note in the declaration can explain the conversion.
The fastest path through WeBOC
| Error type | Prevention | Fix if queried |
|---|---|---|
| HS misclassification | Classify against the FBR tariff before filing | Respond with correct code and justification |
| Valuation discrepancy | Declare actual transaction value with documentation | Provide invoice, contract, payment proof |
| Document attachment | Pre-filing checklist: format, content, relevance | Re-upload in correct format |
| Consignee mismatch | Verify BL draft before vessel sails | Amend BL at origin, letter of indemnity |
| Unit mismatch | Check tariff unit, declare in that unit | Open-unit amendment with explanation |
The operational truth about WeBOC is that every error is fixable, but every fix costs time, and time costs demurrage. The importer and clearing agent who invest in pre-filing accuracy — HS classification confirmed, documents verified and formatted, consignee name checked against the bill of lading, value supported by transactional evidence — clear faster than those who treat WeBOC as a form to fill rather than a compliance system to satisfy.
Olympic Agencies files goods declarations in WeBOC daily at Karachi Port and Port Qasim and has done so since 1982. Our customs clearing service in Karachi includes pre-filing document review, HS classification, and valuation support. WhatsApp us your cargo details and we will ensure your goods declaration is filed correctly the first time.
Stuck with a WeBOC error or FCA query? Contact our team to resolve it today.
WhatsApp us your shipment details →Frequently Asked Questions
My goods declaration was rejected — what are the most common reasons?+
Rejection at the filing stage — before assessment — is usually due to a data format error: an invalid HS code, a missing mandatory field, an uploaded document that exceeds the file-size limit or is in an unsupported format, or a system-level mismatch between the PSW profile data and the goods declaration data. Rejection at the assessment stage is an FCA query triggered by the assessing officer — typically HS classification, valuation, or missing regulatory permits. A filing rejection can usually be corrected and resubmitted immediately. An assessment query requires a formal response and the clearance clock is stopped until the response is accepted.
How do I fix an HS code error after the goods declaration has been filed?+
If the error is discovered before assessment, the clearing agent can amend the declaration. If the error is discovered during assessment — the assessing officer identifies the wrong HS code and raises a query — the agent must respond with the correct code and the supporting justification for why that code applies. If the correct code carries a higher duty rate, the additional duty becomes payable. If the correct code carries a lower rate, the difference is refundable. In either case, the amendment restarts the assessment clock, so getting the HS code right at filing is the single most valuable error to avoid.
Why does WeBOC reject my document attachments?+
WeBOC accepts specific file formats — typically PDF — and has file-size limits. A scanned document that exceeds the size limit, a photograph of a document saved as a JPEG rather than a PDF, or a password-protected PDF will all be rejected. The system may also reject an attachment if the file name contains special characters. The fix is to convert all attachments to standard PDF format, keep file sizes within the limit, and use simple file names.
What is a unit-of-measurement error, and why does it matter?+
The First Schedule to the Customs Act specifies the unit of measurement for each HS code — it may be kilograms, tonnes, litres, pieces, square metres, or another unit. If the importer declares the quantity in a different unit — for example, declaring a machinery consignment in kilograms when the tariff schedule specifies 'number of units' — the system may flag the inconsistency. The fix is to look up the tariff unit for the HS code before filing and declare in that unit. For goods that are naturally measured in a different unit — for example, machinery that is sold by weight but the tariff unit is pieces — an explanatory note in the declaration can prevent a query.
Olympic Agencies
Clearing agricultural cargo - seeds, fertilizers, and machinery - at Karachi Port and Port Qasim since 1982. Members of PIFFA and the Chamber of Commerce.
More on customs process & costs
- How to Dispute a Customs Assessment in Pakistan: the Adjudication and Appeals Process
- Karachi Port vs Port Qasim: Which Port Should Your Agricultural Cargo Use?
- Pre-Kharif Import Readiness Checklist: Cotton, Rice, and Maize Inputs for April-to-June Sowing
- Pre-Rabi Import Readiness Checklist: Ordering, Shipping, and Clearing Before October Sowing
- Understanding Customs Examination in Pakistan: Green, Yellow, and Red Channels Explained
- CIF vs FOB for Agricultural Importers in Pakistan — Which Should You Buy On?
- How Much Does Customs Clearance Cost Per Container in Pakistan? (2026 Breakdown)
- Why Do Shipments Get Stuck at Karachi Port? The Main Causes of Clearance Delays — and the Fixes
- Demurrage and Detention Charges at Karachi Ports — Free Time, Rates, and How to Avoid Them
- What Is Faceless Customs Assessment in Pakistan? FCA Explained for Importers
- How Long Does Customs Clearance Take at Karachi Port and Port Qasim? (2026)
- Is EIF Still Required in Pakistan? What Replaced the Electronic Import Form
- How to Register on PSW and WeBOC in Pakistan — a Step-by-Step Guide for New Importers (2026)
- WeBOC vs PSW vs FCA — Which Pakistani Import System Does What in 2026?
- Our service: Customs Process & Costs clearance →