Most Europe cargo delays no longer start at the destination port. They start in a carrier system in Shanghai, twenty-four hours before loading, when an Entry Summary Declaration is rejected and the container is struck off the loading list. Since the last ICS2 transitional waivers expired in mid-2026 and the major ocean carriers moved to a strict no-reference-no-load policy that autumn, the ENS has stopped being paperwork a forwarder handles after booking. It is a gate your cargo passes before it ever leaves China — and the data in it comes from you.
ICS2 replaced the old import control system in releases spread over several years: express and postal traffic first, then air cargo, then maritime, road and rail. For a China-origin shipper the relevant sequence is compressed into one year.
Through mid-2026 the maritime transition windows finally closed. The waivers that had allowed partial data, or carrier-only filing, ended by 1 June 2026, and the legacy system was retired. From that point a sea shipment to or through the EU customs territory — including Norway, Switzerland and Northern Ireland — needs a complete ENS, filed by every party in the chain, and there is no fallback route.
The second change was commercial rather than regulatory. From 30 September 2026 the largest ocean carriers began enforcing no-reference-no-load as a hard booking rule on all EU-bound and EU-transiting ocean cargo: no valid Movement Reference Number (MRN) by the container cut-off, no slot on the vessel. A rejected declaration now costs a sailing, not a phone call. In the same period, pan-EU marketplace programmes began requiring a matching MRN for inbound shipments from non-EU sellers, which pushed the reference number into the replenishment workflow of every Amazon and multi-channel seller shipping into European fulfilment centres.
The practical reading is simple. ENS compliance used to be an exception handled by a broker at the destination. It is now a pre-condition of loading, evaluated by machine, on data your supplier provides.
The single most common misunderstanding is that the carrier's filing covers the shipment. Under the multi-filing model it does not. Each party files its own layer, and the layers are linked by the MRN issued to the master declaration.
| Layer | Who files | What it covers |
|---|---|---|
| Master level | Ocean carrier or master loader | Vessel and voyage, routing, master bill of lading parties, container and weight totals |
| House level | NVOCC, consolidator or freight forwarder holding the house bill | Shipper and consignee at house level, goods description, HS code, packages, weight, buyer and seller where they differ |
| Lowest house level | The party holding the lowest house bill in a co-load or re-consolidation | Full data set for the actual consignee; intermediate levels do not repeat the filing |
Two consequences follow. First, in an LCL container with a dozen consignees there are a dozen house-level declarations, each assessed separately, each capable of failing on its own. One bad line holds the whole box, because the container cannot be partially loaded. Second, master and house data must agree. If the carrier declares one consignee and gross weight and the forwarder declares a different consignee or a weight that does not reconcile, the mismatch is visible to the risk engine before the vessel sails — and it is read as a discrepancy rather than a typo.
Timing is measured from the start of loading operations at the origin port — the first container on the vessel, not yours. For deep-sea containerised cargo from China the ENS is due at least twenty-four hours before that moment. Short-sea voyages work to a much tighter window measured in hours before arrival.
| Mode | Deadline | What it means in practice |
|---|---|---|
| Deep-sea ocean (containerised) | 24 hours before loading commences at origin | Data must be complete when the container is gated in, not when the vessel berths |
| Short-sea ocean (containerised) | 2 hours before arrival at the first EU port | No realistic correction window; the data must be right before departure |
| Short-sea (non-containerised) | 4 hours before arrival | Ro-ro and breakbulk traffic has the same practical constraint |
| Air cargo | Before departure, with pre-loading data ahead of it | Consolidated air freight needs house-level data at warehouse receipt |
| Rail (China–Europe block trains) | Before the train reaches EU customs territory | Terminal dwell at the border is not a correction period |
Amendments are allowed before arrival at the first EU port but not after it. That distinction matters operationally: a container substituted at the last minute, a late change of consignee, or a re-weighed load all require an amendment filed while the vessel is still at sea. Once the ship is alongside, the option is gone and the cargo faces inspection instead.
Rejections are rarely about exotic rules. They cluster in the same handful of fields, and each one has a fix that belongs upstream of the port.
| Field | Why it fails | Where to fix it |
|---|---|---|
| Goods description | Generic terms such as accessories, spare parts, electronics or general merchandise are rejected as unverifiable; the description must state what the product is, what it is made of and what it is for | Supplier invoice and packing list, rewritten at order confirmation |
| HS code | Six digits minimum, and it must be consistent with the description; a code that belongs to a different product family reads as misdeclaration | Classification agreed at purchase order, not at booking |
| Consignee EORI | Missing, expired, or registered to a different legal entity than the consignee named on the bill | Validated against the EU register once per customer, stored as a master record |
| Party identifiers | Consignor, consignee, notify party, and seller or buyer where they differ, each need a valid identifier | Customer master data, not re-keyed per booking |
| Weight and packages | House figures that do not reconcile with the master declaration or the verified container weight | Weighed at the origin warehouse and passed through one record |
| Container and routing | Container number changed after filing, or a transhipment leg not declared | Amendment triggered by the container assignment itself |
Note where the fixes sit. Five of the six are sourcing and master-data problems, not customs problems. A broker at the load port cannot invent a manufacturer part description, decide which of a supplier's three HS codes is correct, or verify an EORI that the customer supplied last year. This is why sellers who treat ICS2 as the forwarder's responsibility discover the gap at the worst possible moment: the container is at the terminal, the cut-off is hours away, and the missing element is a sentence about the product that only the factory can write.
Because the MRN is now quoted in booking systems and marketplace portals, it is easy to treat it as proof that the goods are cleared. It is not. The ENS is a safety and security declaration: it says the cargo has been declared and risk-assessed for loading, not that duty and VAT have been settled or that the goods may be released.
Import clearance remains a separate act, with its own declaration, its own duties and taxes, and its own release process at the destination. A shipment can hold an MRN and still be stopped on arrival for valuation, classification, product compliance or VAT. For low-value e-commerce consignments the two layers now interact closely, because the same product data feeds the import declaration, the duty treatment and the product identifier requirements — but they are still two filings, and confusing them leads sellers to assume a green light that was never given.
Port-to-port cargo absorbs an ENS failure as a delay. Replenishment cargo absorbs it as an out-of-stock event. Three features make the difference.
The mitigation is boring and effective: treat the ENS data set as part of the purchase order rather than as part of the shipping document, and reconcile it against the warehouse appointment before the container is gated in.
Europe clean-and-deliver is a core lane for MJDT Global (明杰供应链), and ICS2 pushed a large part of that work to the origin side of the booking. The workflow we run for China-to-EU cargo:
See our freight forwarding services for the Europe corridor and global network for the lanes we operate.
Send us a sample of your SKU list with descriptions, HS codes and consignee details. We'll tell you which lines are likely to be rejected, what the correct level of description looks like, and where your EORI or party data needs fixing — before it costs you a sailing.
Review My EU Filing Data →