For bulk tea moving to or through the EU, do not treat ICS2 as a carrier-only black box. Freeze the route and filing model before booking, name who supplies each Entry Summary Declaration (ENS) dataset, send precise house-level shipment data before the legal cut-off, then retain the registration response and close every referral or correction before release. The carrier normally lodges the ENS, but an importer, consignee or freight forwarder that holds missing particulars may have a separate filing role.
This guide is about the EU's pre-arrival safety-and-security declaration. It complements the site's EORI and TARIC checklist and customs-broker handoff; it does not replace the import declaration, food-law checks or destination release.
Build one ICS2 handoff record
| Control gate | Buyer should freeze | Evidence to retain | Hold trigger |
|---|---|---|---|
| Scope and route | Origin, modes, transhipments, first EU entry office and final destination | Booking route and dated rule check | First entry or mode is still provisional |
| Filing model | Single filing or linked multiple filings; declarant and representative for each dataset | Written responsibility matrix | Parties assume another filer holds the data |
| Identities | Legal names, addresses, EORI numbers where required, buyer, seller, consignor and consignee roles | Validated master-data sheet | A role or identifier conflicts across records |
| Linking keys | Master and house transport-document numbers plus the carrier/house-filer identifiers required to link filings | Carrier-confirmed reference sheet | A partial filing cannot link to the master record |
| Goods | Precise description, commodity code at the required level, origin and item separation | Approved ENS item lines | Generic, aggregated or mismatched description |
| Packages and mass | Package type/count, marks, gross mass and container data | Packing list and loading record | Counts or mass change after submission |
| Timing | Legal deadline, carrier's earlier cut-off and internal data-freeze time | Timestamped submission plan | Complete data will arrive after cut-off |
| Status | Registration acceptance, completeness, assessment and any referral response owner | ICS2 or filer status messages | Incomplete, rejected, referral or do-not-load status remains open |
| Change and closure | Amendment, invalidation, rollover, split, reroute and arrival reconciliation method | Version trail and final arrival file | Booking changes are not reflected in the ENS |
Run a nine-step buyer workflow
1. Map the actual movement, including transit
Record every mode and the first point where the goods enter the EU customs territory. ICS2 also covers goods transiting through the EU. A container discharged in one Member State and cleared in another still needs the correct first-entry data. Confirm whether Northern Ireland, Norway or Switzerland is involved and obtain route-specific instructions from the carrier or competent customs service rather than copying an old EU shipment.
2. Separate the ENS from other declarations
The ENS supplies advance cargo data for safety-and-security risk analysis. It is not the import customs declaration, a tariff ruling, a pesticide-residue decision, a CHED-D, a phytosanitary certificate or proof that the tea meets contract quality. Keep those gates distinct. Use the EU border-control checklist where enhanced food controls apply and the arrival-release workflow for the physical lot.
3. Name the legal and operational actors
Under Union Customs Code Article 127, the carrier lodges the ENS as the general rule. The importer, consignee or another eligible person may lodge it, and a person holding particulars unavailable to the carrier may have to provide them. Do not turn that rule into a vague instruction to “let the forwarder handle ICS2.” Record the carrier, master filer, house filer, declarant, representative and technical sender. An IT service provider may transmit messages, but that does not automatically make it the declarant.
4. Choose single or multiple filing deliberately
Use a single filing when the responsible filer has every required master, house and goods-shipment element. If information is divided among parties, the Commission allows linked multiple filings. The parties should contractually allocate each partial dataset and exchange the identifiers needed for linking, including relevant EORI and transport-document references, before submission. Multiple filing is not permission to leave gaps; together the filings must form a complete ENS.
5. Work backward from the legal and carrier cut-offs
The deadline depends on mode and route. For ordinary deep-sea containerised cargo from China, the delegated UCC rule is generally no later than 24 hours before loading onto the vessel that will bring the goods into the EU. Air has a pre-loading minimum dataset and a later complete-data deadline; road, rail and inland-waterway rules differ. The carrier may impose an earlier operational cut-off. Put both times, their time zones and a buyer data-freeze time into the booking file.
6. Create precise house-level item data
Build item lines from the signed specification, commercial invoice, packing list and classification decision. State the tea plainly—for example, green tea, not fermented, origin China, in the actual bulk pack form—then use the validated commodity code and separate items where codes differ. Do not submit “foodstuffs,” “agricultural products,” “samples,” an internal SKU alone or an aggregate that hides different goods. Screen the wording against the Commission's current ICS2 stop-word guidance, updated for use from 3 August 2026.
7. Reconcile parties, packages and transport references
Check buyer, seller, consignor and consignee as defined for the selected ENS dataset—not merely the names copied from one document. Match house and master transport references, package type/count, marks, gross mass, container number and routing to the final booking and loading evidence. Link this check to the VGM handoff and container-loading plan, while remembering that VGM and ENS serve different legal purposes.
8. Verify acceptance and manage referrals
Ask the filing party for evidence that the declaration or linked filings registered successfully, not just a screenshot saying data was sent. Assign an owner to watch completeness, rejection, assessment and control messages. Customs may request additional information, screening or issue a do-not-load direction; the risk assessment does not resume until the applicable referral is answered. A booking confirmation is not proof that ICS2 has accepted complete data.
9. Control every change through arrival
After submission, compare any rollover, vessel change, transhipment, consignee change, split, package/mass correction or cancellation with the accepted data. Route the amendment or invalidation through the declarant under the applicable system rules. Article 129 limits amendment after specified customs actions, so do not assume every error can be edited indefinitely. At arrival, reconcile the ENS identifier and final status to the same transport documents and lot, then retain the messages with the controlled supplier and shipment file.
Keep five requirement types separate
- Legal requirement: the Union Customs Code and its delegated/implementing rules determine ENS scope, responsible persons, data, deadlines and amendment limits.
- System guidance: Commission ICS2 specifications, stop-word lists, message rules and national service-desk instructions explain how to comply operationally; they do not rewrite the law.
- Trade reference: a carrier template or previous filing can reveal expected fields but does not prove the current route, dataset or deadline.
- Buyer specification: controls the source data, accuracy checks, version freeze, evidence and internal hold/release decision.
- Contract requirement: allocates filing, data, cut-off, correction, delay and cost duties among parties; it cannot transfer a statutory duty where the law fixes responsibility.
Common buyer mistakes
- Confusing the ENS with the import declaration or food-control notification.
- Recording only the final EU destination and missing the customs office of first entry.
- Assuming the ocean carrier possesses lowest house-level buyer, seller and goods data.
- Using multiple filing without a written dataset and linking-reference matrix.
- Sending a generic goods description or one line for differently classified products.
- Giving the carrier an unvalidated commodity code, party role or EORI number.
- Treating the statutory deadline as the carrier's operational cut-off.
- Accepting “submitted” without registration and completeness evidence.
- Ignoring a rollover, split shipment, mass change or new transport document.
- Releasing the tea commercially because ICS2 risk analysis closed, while food-law or contract checks remain open.
Practical conclusion
Use the sequence map route - separate declarations - name actors - choose filing model - freeze cut-offs - build precise item data - reconcile shipment fields - monitor status - control changes. The buyer's useful output is a complete, linked and traceable pre-arrival data pack—not an assumption that the logistics provider solved it.
Connect the file to Yunjing Tea's bulk-tea specification template, sample-to-shipment quality controls and packing plan. Then send the product, pack, route and data deadline for a specification-based discussion.
Sources checked 20 October 2026: the European Commission's current ICS2 overview and 2026 operational updates, including the 1 June 2026 end of temporary derogations and the current stop-word notice; its current ICS2 FAQ on filing responsibility, multiple filing and linking data; the March 2026 ENS key-requirements leaflet; Union Customs Code Articles 127-130; and Delegated Regulation (EU) 2015/2446 Articles 105-110 on mode-specific time limits. Recheck the route, first entry office, filing model, current dataset, stop-word list, legal and carrier cut-offs, and national instructions for every shipment.
