EU ICS2 Restored: Do Parcels Need More Data?

Yes. Restoring ICS2 means the system can again receive and process electronic filings; it does not remove the obligation to provide accurate cargo data. New EU-bound parcels still need identifiable descriptions, quantities, values and shipper or consignee information required by the active route. An MRN identifies a record, but it does not by itself prove customs release.

Key takeaways

• System availability and filing duty are separate questions.
• An accepted record is not the same as a customs decision.
• MRN supports traceability, not automatic clearance.
• Consolidated parcels need a final item-level reconciliation.

What the 12 August ICS2 update confirmed

Maersk stated on 12 August 2026 that the EU Import Control System 2 downtime had been resolved, customs responses and MRNs were being received again, the outage backlog had been cleared, and real-time filing had resumed. The update describes system operations. It does not say that future cargo can enter without the required advance data.

ICS2 is the EU system used to receive safety and security information for goods entering the customs territory. During downtime, filers may be unable to transmit data or receive responses normally. Once service returns, the transmission channel works again, but the quality and truthfulness of each filing still determine whether it can proceed.

This distinction prevents a common error: treating a technical recovery notice as a regulatory exemption. The outage ended; the data obligation did not.

Why system, submission and customs decision are three layers

Layer one is system availability: can a filer send data and receive a response? Layer two is record acceptance and identification: has the submission produced a traceable reference such as an MRN? Layer three is customs processing: does the authority request more data, assess risk, inspect or release the goods?

The Maersk notice confirms recovery at the first layer and renewed responses at the second. It cannot decide the third layer for every shipment. Customs treatment remains shipment-specific and depends on the submitted information and applicable rules.

An MRN, or Movement Reference Number, links a declaration or movement record to later events. It is useful because the carrier, filer and authority can discuss the same record. It is not a delivery scan, a guarantee of data accuracy or proof that all customs actions are complete.

What to verify before a new EU parcel leaves China

The final filing should describe what is physically packed. Avoid broad labels such as “gift,” “accessories” or “daily goods” when they hide different products. A consolidated carton should reconcile item names, quantities, values and relevant attributes after parcels have been combined.

Data field	Useful standard	Frequent failure
Item description	Specific, recognisable product	Generic category only
Quantity	Matches the packed item count	Multiple items reported as one
Value	Supported and consistent with the order	Omitted or arbitrary value
Parties and address	Accurate names, address and postcode	Spelling or postcode mismatch
Cargo attributes	Material, use and sensitive characteristics	Missing liquid, battery or regulated detail

For EU-bound parcels consolidated through YANCHAO, the warehouse can compare inbound records and inspection images with the final packing list, then check that item counts and descriptions still match after consolidation. This is where forwarding adds practical value: it aligns the physical carton with the data set being submitted. It does not replace customs assessment or justify incomplete descriptions.

Outage recovery vs normal filing

Operating state	Main question	Appropriate action
System unavailable	Can data be sent or responses received?	Preserve the full filing and follow official recovery instructions
Backlog recovery	Did an earlier record receive a response?	Trace the existing MRN and avoid duplicate records
Real-time service	Is the new shipment data complete and accurate?	Reconcile the final carton before dispatch

After recovery, old and new records should not be confused. Use the existing MRN to follow a filing created during the outage. Submit a new parcel through the live process with its own accurate cargo data.

Summary

ICS2 restoration fixes system availability, not the parcel's filing obligations. Separate system status, record acceptance and customs decision. An MRN makes a record traceable but does not prove release. Before dispatch, reconcile descriptions, quantities, values, party information and physical contents, especially after consolidation. If more information is requested, respond through the existing record rather than inventing a new description.

Get the ICS2 Parcel Data Checklist

Use a checklist for item descriptions, quantities, values, shipper and consignee fields, postcode, cargo attributes, final packing list, filing response and MRN. Record the latest response and next required action so warehouse, filer and carrier work from one version.