HS Codes, Cargo Descriptions, and Manifest Data: Three Compliance Deadlines Tightening in 2026

Key Takeaways

Saudi Arabia (MAWANI): Effective May 1, 2026, all import cargo manifests arriving at Saudi seaports must include a valid 6-digit HS code, cargo volume data, and hazardous goods details. Manifests that are incomplete or inaccurate will be rejected, and regulatory penalties will apply.
European Union (ICS2 Release 3): Now fully operational across all transport modes. Carriers and freight forwarders must submit 6-digit HS codes, accurate cargo descriptions (no generic “stop words”), and valid EORI numbers in the Entry Summary Declaration (ENS) before cargo arrives. An updated stop words list takes effect May 4, 2026.
United States (CBP): Since September 2025, CBP automatically rejects manifests missing complete shipment details. Valid 6-digit HS codes and accurate cargo descriptions aligned to the HTS are required for US, Puerto Rico, and Canada-bound cargo.
These three requirements share a common pattern: customs authorities worldwide are moving from tolerating vague or incomplete cargo declarations to actively rejecting them. The operational burden falls on shippers, forwarders, and their origin partners to get the data right before booking.

Who This Is For

This post is for freight forwarders, NVOCCs, customs brokers, and shippers (both importers and exporters) who manage documentation for ocean-bound cargo to the EU, the US/Canada, or Saudi Arabia. If your team submits shipping instructions, booking requests, or manifest data, these requirements affect your workflow.

Saudi Arabia: MAWANI Mandatory Fields (May 1, 2026)

The Saudi Ports Authority (MAWANI), in coordination with the Zakat, Tax and Customs Authority (ZATCA), has issued a circular requiring three additional mandatory fields in import cargo manifests submitted to Saudi seaports.

Effective May 1, 2026, shipping agents must:

Enter the HS code (global HS code, first six digits) for each shipment in the import cargo manifest.
Enter cargo size data within the cargo manifest for export, import, and transshipment.
Specify the type and details of hazardous goods where applicable.

The circular states that failure to complete these fields, or inaccuracy in the data provided, will result in manifest rejection and regulatory action against violators.

This is not the first data quality push from MAWANI. It follows Circular No. 9 of 2025 (advance data submission regulations), Circular No. 5 of 2024 (mandatory importer data in manifests), and Circular No. 1 of 2023 (port operational regulations). The May 2026 requirement is a continuation of a multi-year tightening of cargo data standards at Saudi ports.

What to do:

Confirm that your shipping instructions for Saudi-bound cargo include a valid 6-digit HS code for every commodity line.
Ensure cargo volume is declared in the manifest. If your booking system does not currently capture this, add it to your SI workflow.
For hazardous goods, verify that DG details (UN number, proper shipping name, class) are included in the manifest, not just the DG documentation.
Communicate these requirements to origin shippers and booking teams. The rejection happens at manifest level, which means the carrier’s agent in Saudi Arabia gets blocked, but the root cause is usually missing data from origin.

European Union: ICS2 Release 3 and the Stop Words Update (May 4, 2026)

The EU’s Import Control System 2 (ICS2) is now fully operational for all transport modes: air, ocean, road, and rail. Since September 2025, carriers, freight forwarders, and consolidators must submit an Entry Summary Declaration (ENS) with detailed cargo data before goods arrive at the EU border.

The ENS requires:

A minimum 6-digit HS code for each product
An accurate and complete cargo description reflecting the composition, nature, and intended use of the goods
A valid EORI number for the EU consignee/importer (and for other EU-based parties where applicable)
Buyer and seller information
Payment terms

The system performs automated risk analysis on every ENS. If the data is incomplete, inaccurate, or triggers a risk flag, the system can issue a “Do Not Load” instruction, meaning the cargo cannot be loaded at origin.

The May 4, 2026 stop words update: The European Commission has published an updated list of “stop words” that take effect on May 4. Stop words are generic cargo descriptions that ICS2 will automatically reject. Examples from previous lists include terms like “auto parts,” “clothing,” “fruit,” “machinery,” “goods,” “samples,” and “personal effects” when used alone without further specification. The updated list should be checked against your product description templates.

What to do:

Audit your product master data. Every SKU or commodity you ship to or through the EU should have a validated 6-digit HS code and a specific cargo description that avoids stop words.
Confirm EORI numbers are current and validated. Hapag-Lloyd has flagged that many customers provide invalid EORI numbers, requiring time-consuming corrections and re-filings.
For consolidated (LCL) shipments, clarify who files the house-level ENS: the freight forwarder, the consolidator, or the NVOCC. Under ICS2, house-level data filing is now mandatory.
Check the updated stop words list before May 4. If your descriptions use any of the flagged terms, update them now.

United States: CBP Manifest Rejection and HS Code Requirements

Since September 27, 2025, U.S. Customs and Border Protection (CBP) has automatically rejected manifests that do not include complete shipment details. This applies to all cargo entering the US, Puerto Rico, and Canada.

The requirements include:

A valid 6-digit Harmonized System (HS) code using the official HTS portal
A cargo description where the first line reflects the true nature of the goods and aligns with the declared HS code
Complete consignee and shipper information (name and address)

CBP has published a reference list of unacceptable vs. acceptable cargo descriptions. Generic descriptions like “FAK” (freight all kinds), “general cargo,” or “sundry goods” are flagged for rejection.

Maersk has issued guidance noting that if HS codes or descriptions are missing or inaccurate, shipping instructions may be rejected and cargo may face delays, rollovers, inspections, or customs rejection. For rail cargo entering via Canada (e.g., CPKC), complete and accurate shipping instructions are also required; errors may cause additional delays.

What to do:

Verify that every US/Canada-bound shipment has a valid 6-digit HS code declared on the shipping instructions and manifest.
Cross-check cargo descriptions against the CBP acceptable description list.
Ensure consignee and shipper details are complete. “To order” BLs without a named consignee may trigger rejection depending on the filing.

The Common Pattern: Why This Is All Happening Now

These three requirements (Saudi, EU, US) are independent regulations from different authorities, but they share a common driver: customs systems worldwide are moving toward pre-arrival risk assessment based on structured cargo data. Generic, vague, or incomplete declarations that would have passed five years ago are now being actively rejected by automated systems before the cargo even arrives.

For logistics professionals, this means:

Data quality is no longer a back-office problem. If the HS code is wrong, the description is vague, or the EORI is invalid, the shipment stops. Not after arrival, but before loading (in the EU’s case) or at manifest submission (in Saudi Arabia’s case).

The burden is shifting upstream. Origin shippers and booking teams need to provide accurate commodity data at the shipping instruction stage, not leave it for the destination broker to sort out. Carriers are increasingly rejecting SIs that do not meet these standards.

“FAK” and generic descriptions are dying. Freight All Kinds, general merchandise, sundry goods, and other placeholder descriptions are being systematically eliminated from cargo data. If your team still uses them as defaults, it is time to change.

Operational Note: When customs authorities reject a manifest or ENS, the resulting delay often traces back to data that was missing or incorrect at the booking stage. For teams managing hundreds of shipments, catching these data gaps before submission requires structured validation at the point where shipping instructions are created. Connecting cargo data to shipment-level visibility helps flag exceptions before they become customs holds.

Quick Reference: What Each Authority Requires

Requirement	Saudi Arabia (MAWANI)	EU (ICS2)	US (CBP)
HS code	6-digit, mandatory for imports	6-digit minimum, mandatory	6-digit, mandatory
Cargo description	Required	Must avoid stop words; must reflect goods accurately	First line must reflect true nature of goods
Cargo volume	Mandatory (export, import, transshipment)	Not separately required in ENS	Not separately required
Hazardous goods details	Mandatory if applicable	Required (UN no., class, etc.)	Required per existing IMDG/DOT rules
Consignee ID	Per existing ZATCA rules	EORI number mandatory	Name and address mandatory
Effective date	May 1, 2026	Operational since Sep 2025; stop words update May 4, 2026	Operational since Sep 27, 2025
Consequence of non-compliance	Manifest rejected; regulatory penalties	“Do Not Load” instruction; cargo blocked at origin	Manifest rejected; delays, inspections, rollovers

What to Watch

Saudi MAWANI enforcement posture after May 1. New requirements sometimes have a soft enforcement period before strict penalties apply. However, MAWANI’s language (“regulatory procedures will be applicable against violators”) suggests immediate enforcement. Monitor carrier advisories from ONE, Hapag-Lloyd, and MSC for any updates on implementation.
EU ICS2 stop words list (May 4, 2026). The updated list is published on the European Commission’s CIRCABC platform. If you ship to or through the EU regularly, download and cross-reference it against your SI templates.
CBP continued tightening. CBP has been progressively raising the bar on data quality. The September 2025 auto-rejection was one step; further tightening is possible, especially as IEEPA refund processing (via the CAPE system) increases CBP’s focus on entry-level data accuracy.
Carrier system changes. Carriers like Hapag-Lloyd and Maersk have updated their booking platforms to add mandatory HS code and description fields. If your booking workflow uses third-party platforms (INTTRA, CargoWise, etc.), confirm they have been updated to capture the required fields.