ICS2 ENS Data Handoff Checklist: China Supplier to Forwarder

Your supplier’s packing list says “silicone kitchen utensils, 100 pcs/carton, 10 cartons.” Your forwarder asks for an ENS with a commodity code, a consignor, a consignee, a goods description, and a reference number. Those two documents are not the same shape. Somewhere between the factory gate and the EU pre-loading filing, the data has to be reconciled — and every reconciliation is a chance for a wrong HS code, a wrong consignor, or a description that the carrier cannot use.

You may also be told that ICS2 is “the buyer’s responsibility” or “the supplier’s responsibility.” Neither is accurate. The carrier or freight forwarder is the legal filer of the ENS. The supplier and the buyer are the people who have to hand them the data that goes in it.

This guide walks through what fields the supplier and the China-side agent actually need to deliver to the carrier or forwarder, where the boundary of responsibility sits, and what a buyer can verify before the goods leave China.

Quick Answer: What Is ICS2 ENS and Who Files It?

ICS2 is the EU’s Import Control System 2 — the pre-arrival security and safety filing framework that applies to goods brought into the EU customs territory. The instrument that is filed before loading is the Entry Summary Declaration (ENS).

The rule is straightforward:

• The carrier or freight forwarder is the party who files the ENS with the EU.
• The supplier and the buyer are the parties who have to provide the underlying data the filing is built from.
• The ENS data set is broader and more structured than a normal packing list or commercial invoice. It includes consignor, consignee, buyer, HS code, goods description, packaging marks, transport references, and a routing/witness sequence depending on the transport mode.

This is not a destination-clearance filing and not a customs declaration in the destination sense. It is a pre-loading security/safety filing. The EU’s own guidance distinguishes ICS2 from IOSS, import VAT, customs duty, and the temporary €3 duty on low-value consignments. Those are separate processes and they are not the subject of this article.

What this article is about is the data handoff between the supplier and the forwarder that lets the ENS be filed cleanly.

Important — scope. This article is operational guidance on the data the supplier and the forwarder need to share. It is not a legal interpretation of EU customs rules, not a guarantee of clearance, not a representation about ICS2 Release or the absence of an EU control, and not a substitute for advice from a qualified EU customs professional. EU rules, ICS2 versions, and ENS data fields change over time. Always verify the current ENS data set against the EU’s official documentation and the carrier or forwarder’s own ENS filing instructions on the day of shipment.

Why the ICS2 ENS Data Handoff Breaks in Practice

Most operational problems with the ENS are not caused by the carrier. They are caused by three different data shapes that have to be reconciled before the ENS can be filed:

1. Supplier’s commercial packing list — usually a Chinese-language Excel or PDF with carton count, internal SKU, quantity per carton, gross weight, and dimensions. The HS code is often missing, guessed, or copied from a listing page.
2. Buyer’s commercial invoice and contract — usually an English-language document with the agreed unit price, total invoice value, and the contractual buyer / seller names. The consignor field may not match the actual factory address.
3. Carrier or forwarder’s ENS template — usually a structured Excel or web form with the exact ENS data fields the EU expects, in a specific order, with specific format requirements (number of characters, allowed values, language rules).

Each transition is a chance to introduce a typo, a wrong HS code, a missing reference, or a description that is too vague to satisfy the carrier’s ENS form. Multiply that by 50 SKUs and several cartons per SKU, and the error surface is large.

The fix is not a “better supplier.” It is a pre-shipment data pack that the China side prepares so the ENS can be filed without rework.

The Scope of ICS2 (What It Applies To — and What It Does Not)

ICS2 ENS applies to goods entering the EU customs territory. It is a pre-arrival security/safety filing, not a destination clearance declaration and not a duty calculation.

Concretely, this means:

• ICS2 ENS is filed before loading for most transport modes, with timing rules set by the EU. The carrier or forwarder carries the responsibility for when and how to file.
• ICS2 ENS is not the same as the import customs declaration. Once the goods arrive, the import declaration is a separate process that involves the customs broker, importer of record, and the destination Member State’s rules.
• ICS2 ENS is not the same as the temporary €3 customs duty on low-value EU distance-sale consignments, nor is it the Product Identifier (PID) process. Those are separate EU mechanisms.
• ICS2 ENS is not the same as IOSS (Import One-Stop Shop) for VAT, nor is it the buyer’s payment evidence.
• ICS2 ENS is not a US CBP entry filing. The CBP / Trade.gov “product-spec-to-cargo-description” checkpoint retained in our daily analysis is a separate, US-scoped workflow. Do not reuse US cargo-description guidance as ICS2 evidence.

For anything affecting the destination filing, the duty outcome, the VAT outcome, or the eligibility of a specific HS code, the right party to confirm is the carrier, the forwarder, or a qualified EU customs adviser — not the supplier, and not the buyer’s listing page.

Who Owns What in the ENS Data Handoff

A clean handoff has a clear owner at each step. The ownership map is the same for most transport modes; the labels can vary slightly for air, sea, road, or rail.

This is the operational handoff map. It does not waive any legal obligation of any party; it only describes the data movement.

Body image 1 — ICS2 ENS data-handoff ownership map Placement: inside ## Who Owns What in the ENS Data Handoff, immediately before the role table. Concept: a five-card horizontal flow diagram showing the buyer → agent → supplier → forwarder → broker with the data direction arrow. SEO alt: ICS2 ENS data handoff ownership map from buyer to forwarder

Body Image 1 — ICS2 ENS Data Handoff Ownership Map

• Placement node: inside ## Who Owns What in the ENS Data Handoff, immediately before the role table.
• Body role: shows the data direction and the responsibility boundary — the forwarder files, the agent and supplier provide the data, the buyer confirms the buyer-side reference.
• Factual scene / labels: five horizontal cards with the labels Buyer (overseas), China-side agent, Supplier (factory), Carrier / forwarder, EU customs broker. Below each card a single line: “Owns: …”. A subtle divider line between the forwarder card and the broker card with the label “ENS filing boundary ends here at origin.”
• Title attribute: ICS2 ENS data handoff ownership map.
• Avoid: no EU / Member State logos, no real EU customs authority names, no real forwarder brands, no fabricated company details.

What the Supplier’s Data Pack Must Contain

Before the carrier or forwarder files the ENS, the China side must hand over a complete data pack. Each field below maps to an ENS field that the carrier typically needs.

1. Consignor (supplier) details

• Legal name of the supplier (factory or trading company exactly as the contract names it).
• Registered address, including country, province, city, street, and postal code.
• Contact person and phone (these stay in the supplier-side data pack; do not put them in the ENS description).
• If the supplier is a trading company, the actual factory address goes in a separate factory field, not in the consignor field.

2. Consignee (buyer) details

• Legal name of the buyer (foreign legal entity, not “Style Sourcing” or a generic name).
• Address, country, and contact for the destination.
• If the buyer uses a third-party warehouse in the EU, the warehouse address is the consignee; the ultimate destination is a separate field on the carrier’s form.

3. HS code (commodity code)

• 6-digit HS code minimum, or the full EU Combined Nomenclature (CN) code if the carrier / broker needs it.
• One HS code per SKU, not one HS code per shipment.
• If the supplier is guessing, the China-side agent should reconcile with the supplier’s product description and the buyer’s documentation before sending it to the forwarder.

4. Goods description

• Plain-language description that matches the physical product, not the marketing copy.
• Avoid vague terms like “gift,” “sample,” “free with order,” “promotion,” “household item.”
• Use the same wording across the invoice, packing list, and ENS.

5. Packaging and packaging marks

• Type of packaging (carton, pallet, polybag, blister pack).
• Number of packages.
• Package marks (carton numbers, pallet numbers, “fragile,” orientation arrows).
• Any UN numbers, if applicable for dangerous goods.

6. Reference numbers

• Buyer’s PO number.
• Supplier’s order number or contract number.
• Air waybill, sea waybill, CMR, or other transport reference number (assigned by the carrier).
• Any seal number or container number (for sea freight).

7. Consignor–consignee relationship

• Whether the consignor is the actual supplier, or the supplier has sold to a third party in another country.
• If there is an intermediate party, the EU Carrier has to record the buyer and seller fields carefully.

8. Weight and dimensions

• Gross weight per carton.
• Net weight per carton.
• Carton dimensions.
• Total shipment gross weight and dimensions.
• These should match the carrier’s booking record, not just the supplier’s estimate.

9. Routing mode

• Air, sea, road, rail, or multimodal transport.
• For sea freight: container number, seal number, vessel name and voyage, port of loading, port of discharge.
• For air freight: master AWB number, flight number, airport of loading, airport of discharge.

This is not a complete ENS data set; it is the supplier-side data pack that feeds the ENS. The carrier or forwarder usually adds transport-mode-specific fields on top of it.

The Supplier -> Agent -> Forwarder Hand-off Steps

A practical handoff has four logical steps. Each step has a defined input, a defined owner, and a defined output.

Step 1: Supplier -> Agent (China-side)

• Input: the factory’s commercial invoice, packing list, and any supplier-side reference (contract number, order number).
• Owner: the supplier’s merchandist or the buying organisation’s China-side agent.
• Output: a reconciled data pack with consignor, consignee, HS code, goods description, packaging and packaging marks, weight and dimensions, and reference numbers.
• Risk to manage: the supplier’s commercial description is too vague; the HS code is copied from the Alibaba listing; the consignor address is the trading company while the actual factory is elsewhere.

Step 2: Agent -> Buyer (commercial owner)

• Input: the reconciled supplier data pack plus the buyer’s purchase order, buyer-side reference, and any destination warehouse or broker reference.
• Owner: the China-side agent.
• Output: a buyer-confirmed data pack that matches the buyer’s contract, that the buyer has explicitly approved consignee name and reference, and that has the buyer’s PO number attached.
• Risk to manage: the buyer has not confirmed the consignee name; the buyer is using a forwarding agent’s address as the consignee without realising that the carrier’s ENS will record that address.

Step 3: Agent -> Forwarder (ENS templating)

• Input: the buyer-confirmed data pack.
• Owner: the China-side agent.
• Output: the data pack typed into the carrier or forwarder’s ENS template, with the carrier’s own transport references added.
• Risk to manage: the forwarder’s ENS template requires fields the agent does not have (for example a specific UN number, a specific EORI number, or a specific destination operator code). The agent must ask the forwarder what is missing, not guess.

Step 4: Forwarder -> ENS filing

• Input: the completed ENS template.
• Owner: the carrier or freight forwarder.
• Output: the ENS filed with the EU’s ICS2 system before the goods are loaded.
• Risk to manage: the carrier asks the agent for additional data after the booking is created. The agent must answer quickly, or the goods may not be loaded.

Body image 2 — supplier-side data pack spreadsheet on a laptop Placement: inside ## The Supplier -> Agent -> Forwarder Hand-off Steps, immediately before ### Step 1: Supplier -> Agent (China-side). Concept: a laptop screen showing a supplier-side data pack spreadsheet with HS code, description, carton count, gross weight, and dimensions per SKU. SEO alt: Supplier-side data pack spreadsheet for ICS2 ENS data handoff

Body Image 2 — Supplier-Side Data Pack Spreadsheet

• Placement node: inside ## The Supplier -> Agent -> Forwarder Hand-off Steps, immediately before ### Step 1: Supplier -> Agent (China-side).
• Body role: shows the source data shape — supplier-side information that has to be reconciled before the ENS can be filed.
• Factual scene / labels: laptop screen with a spreadsheet. Column headers SKU, HS Code, Goods Description, Cartons, Qty / Carton, Gross Weight, Dimensions, Consignor, Consignee, Buyer Reference. Three to five sample rows using a non-海关 / non-realistic SKU placeholder pattern SKU-ENS-XXX-N. HS code column uses placeholder pattern NNNN.NN. No EU member-state logos, no real brand names.
• Title attribute: Supplier-side data pack spreadsheet — ICS2 ENS.
• Avoid: no real consignor or consignee names, no real EU EORI numbers, no real HS code that could be misread as a customs ruling.

Step 1: Supplier -> Agent (China-side)

• Input: the factory’s commercial invoice, packing list, and any supplier-side reference.
• Owner: the supplier’s merchandist or the China-side agent.
• Output: a reconciled supplier data pack with all the fields in ## What the Supplier's Data Pack Must Contain.
• Risk to manage: vague goods description, miscopied HS code, consignor address mismatch.

Step 2: Agent -> Buyer (commercial owner)

• Input: the reconciled supplier data pack plus the buyer’s PO and buyer-side reference.
• Owner: the China-side agent.
• Output: a buyer-confirmed data pack with the buyer-approved consignee name and reference.
• Risk to manage: buyer has not confirmed the consignee; the buyer uses a different reference number on the contract than on the forwarder’s booking.

Step 3: Agent -> Forwarder (ENS templating)

• Input: the buyer-confirmed data pack.
• Owner: the China-side agent.
• Output: the carrier or forwarder’s ENS template populated and ready for the carrier’s transport references.
• Risk to manage: the forwarder requires fields the agent does not have; the agent must ask the forwarder what is missing.

Step 4: Forwarder -> ENS filing

• Input: the completed ENS template.
• Owner: the carrier or freight forwarder.
• Output: the ENS filed with the EU’s ICS2 system before the goods are loaded.
• Risk to manage: the carrier may ask the agent for additional data after booking; the agent must respond quickly.

Body image 3 — buyer-side confirmation email on a laptop Placement: inside ## The Supplier -> Agent -> Forwarder Hand-off Steps, immediately after ### Step 2: Agent -> Buyer (commercial owner). Concept: a laptop screen showing a buyer-side confirmation email with the consignee name, buyer reference, and a row of “confirmed” checkboxes. SEO alt: Buyer-side confirmation email for ICS2 ENS consignee and reference

Body Image 3 — Buyer-Side Confirmation Email

• Placement node: inside ## The Supplier -> Agent -> Forwarder Hand-off Steps, immediately after ### Step 2: Agent -> Buyer (commercial owner).
• Body role: shows the buyer-side sign-off step — confirms that the consignee name, reference numbers, and consignor are what the buyer actually wants in the ENS.
• Factual scene / labels: laptop screen with an email from the buyer to the agent. Subject line Re: ENS data pack — buyer confirmation. The body has the line Consignee name and address: confirmed. Buyer reference: confirmed. EU warehouse address: confirmed. A row of three green checkboxes follows. No real customer name, no real brand, no real EU address.
• Title attribute: Buyer-side confirmation email — ICS2 ENS.
• Avoid: no real EU EORI, no realistic-looking EU addresses, no real warehouse name.

Worked Example: 6-SKU EU Order Handoff

Imagine a buyer is importing a 6-SKU order of kitchen silicone products from a Yiwu trading company, with one destination warehouse in the EU. Here is how the four handoff steps map to a single SKU:

• Supplier SKU: TC-220-SIL-RED-S
• HS code (placeholder): 3924.10
• Goods description: Silicone kitchen spatula, red, small, retail-pack of 1.
• Cartons for this SKU: 4
• Quantity per carton: 50
• Gross weight per carton: 8.2 kg
• Carton dimensions: 50 x 40 x 30 cm
• Consignor: Yiwu trading company (as named in the contract).
• Consignee: EU destination warehouse (as named by the buyer).
• Buyer reference: PO-2026-EU-0814-SET1.

The data must flow like this:

If any cell changes silently between Step 1 and Step 4, the ENS is at risk. The carrier may refuse to file, may have to amend the ENS after the booking is created, or may file a description that the EU flagging logic interprets as vague.

Body image 4 — Forwarder ENS template on a laptop Placement: immediately after Step 4 of the worked example table. Concept: a laptop screen showing the carrier or forwarder’s ENS template with fields populated for one SKU. SEO alt: Forwarder ENS template on a laptop for ICS2 ENS data handoff

Body Image 4 — Forwarder ENS Template

• Placement node: inside ## Worked Example: 6-SKU EU Order Handoff, immediately after the four-row worked example table.
• Body role: shows the operational form the forwarder actually uses — the destination shape the supplier-side data pack has to fit into.
• Factual scene / labels: laptop screen with an ENS template. Field labels Consignor, Consignee, HS code, Goods description, Cartons, Qty/carton, Gross weight, Dimensions, Buyer reference, Container / AWB. One row populated using the worked example’s TC-220-SIL-RED-S placeholder SKU. No EU / Member State logos, no real carrier name, no real EORI.
• Title attribute: Forwarder ENS template — ICS2 ENS.
• Avoid: no real carrier UI screenshot, no real brand name, no real EU EORI, no real HS code.

Common Failure Modes and How to Catch Them

The ENS data handoff is most fragile at three points: the supplier-to-agent transition, the agent-to-buyer transition, and the agent-to-forwarder transition.

Failure 1: HS code copied from a listing page

• What it looks like: the supplier copies an HS code from a 1688 or Alibaba listing page that has been auto-generated by the platform and does not match the actual product.
• Why it matters: the carrier’s ENS routing may flag the HS code, or the EU’s risk logic may treat a vague code as more likely to require examination.
• How to catch it: the agent cross-checks the HS code against the supplier’s product description, the buyer’s documentation, and the EU’s own published commodity classification if there is one.

Failure 2: Vague goods description

• What it looks like: the supplier’s commercial description is “silicone products” or “household items” or “gift set.”
• Why it matters: the carrier’s ENS form will reject vague descriptions, and the EU’s own validation logic does not accept generic terms as the primary goods description.
• How to catch it: the agent rewrites the description to match the physical product, the packaging, and the marketing copy, and the buyer confirms the wording.

Failure 3: Consignor address mismatch

• What it looks like: the supplier is a trading company in Yiwu, the actual factory is in another province, and the contract uses the trading company name; the consignor field ends up with one address while the actual shipping point is another.
• Why it matters: the ENS records the party responsible at origin; if the address does not match the actual origin, the ENS may be amended.
• How to catch it: the agent confirms the consignor address with the supplier in writing, and if the actual factory is in another province, both addresses are recorded in the data pack, with the consignor field set to the contract-named party.

Failure 4: Consignee name not buyer-confirmed

• What it looks like: the agent uses the buyer’s overseas head office as the consignee, but the buyer actually wants the EU destination warehouse to be the consignee.
• Why it matters: the ENS is filed with the wrong consignee, and the carrier may have to amend the ENS or refuse to file.
• How to catch it: the buyer explicitly confirms the consignee name and address in writing before Step 3, with the same wording that will appear on the carrier’s ENS template.

Failure 5: Reference number does not match the invoice

• What it looks like: the buyer uses PO-2026-EU-0814-SET1 on the purchase contract, but the forwarder uses the supplier’s order number instead.
• Why it matters: the ENS reference number does not match the buyer’s documents, and the buyer’s accounting or compliance reconciliation breaks.
• How to catch it: the agent reconciles the reference number across the PO, the commercial invoice, the packing list, and the carrier’s ENS template before filing.

Failure 6: Forwarder requires a field the agent does not have

• What it looks like: the forwarder asks for an EORI number, a destination operator code, a UN number, a specific port code, or a transport-mode-specific field that the supplier’s data pack does not include.
• Why it matters: the agent does not know how to fill it, and either guesses or stops the workflow.
• How to catch it: the agent asks the forwarder upfront which fields the forwarder’s ENS template requires beyond the supplier-side data pack, and the buyer supplies the buyer-side fields (for example EORI) before Step 3.

Body image 5 — ENS field-mismatch red-flag card Placement: inside ## Common Failure Modes and How to Catch Them, immediately after the Failure 6 entry. Concept: a practical red-flag checklist card listing the six failure modes as checkboxes. SEO alt: ICS2 ENS field-mismatch red-flag card after data handoff

Body Image 5 — ENS Field-Mismatch Red-Flag Card

• Placement node: inside ## Common Failure Modes and How to Catch Them, immediately after the Failure 6 entry.
• Body role: acts as a single-page red-flag checklist the agent can mark off before the ENS is filed.
• Factual scene / labels: a laminated card on a clipboard with six checkbox lines. Line 1: HS code checked against supplier description. Line 2: Goods description specific, not vague. Line 3: Consignor address matches contract. Line 4: Consignee name confirmed by buyer in writing. Line 5: Buyer reference matches PO and invoice. Line 6: Forwarder-specific fields supplied by buyer / agent (EORI, etc.). No real EU / Member State logos, no real EORI.
• Title attribute: ENS field-mismatch red-flag card.
• Avoid: no decorative stock imagery, no real brand names, no real EU EORI.

ICS2 ENS Data-Pack Checklist (Pre-Booking)

Use this checklist as the operational pass / fail list before the carrier or forwarder files the ENS. Tick each item; if any item is not ticked, do not let the booking move forward.

Supplier side – [ ] Commercial invoice, packing list, and supplier-side reference (order / contract number) delivered. – [ ] Consignor name and address match the contract and the actual shipping origin. – [ ] Carton count, gross weight, and dimensions match the actual sealed cartons. – [ ] Goods description is specific, not generic (“silicone kitchen spatula, red, small, retail-pack of 1” — not “household items”). – [ ] Supplier-side reference (order number, contract number) recorded.

Agent / China-side – [ ] HS code (6-digit HS code or full CN code) per SKU, reconciled with the supplier’s product description. – [ ] One HS code per SKU, not one HS code per shipment. – [ ] Description reconciled across the invoice, packing list, and the carrier’s ENS template. – [ ] Packaging marks (carton numbers, pallet numbers, “fragile,” orientation arrows) recorded. – [ ] Special handling fields (UN number, dangerous-goods flag, battery flag) recorded if applicable.

Buyer side – [ ] Consignee name and address confirmed in writing by the buyer. – [ ] Buyer reference (PO number) confirmed and matches the contract. – [ ] EORI number or any destination-side identifier supplied to the forwarder. – [ ] Buyer-approved reply sent to the agent before Step 3.

Forwarder / carrier – [ ] Carrier’s ENS template received and reviewed for required fields. – [ ] Transport mode (air / sea / road / rail / multimodal) decided. – [ ] Transport references (AWB, sea waybill, CMR, container number) recorded. – [ ] ENS filed before loading, with the carrier’s own reference attached to the buyer-side data pack.

If any box above is unchecked, the ENS is not ready. Send it back, do not let the booking move forward.

Pre-Filing Change-Control Record — Freeze One Shipment Version

Before the forwarder turns the data pack into an ENS template, freeze one named shipment version. This makes a practical buyer check possible: the supplier, agent, buyer, and forwarder should be looking at the same invoice, packing, and routing facts rather than several near-matching files.

This is a change-control record, not a customs filing decision. Its purpose is to stop stale supplier information from being passed on as current shipment data.

What the Handoff Will Not Do

A clean ENS data handoff is a workflow, not a guarantee. It will not:

• Guarantee that the EU’s ICS2 release decision will be a “do not load” outcome, nor guarantee that the goods will not be selected for further control.
• Override the EU’s published ICS2 rules, the carrier’s own ENS filing requirements, or the destination Member State’s separate rules.
• Substitute for a qualified EU customs adviser, an importer of record, or a customs broker.
• Recover an ENS that has already been filed with the wrong data.
• Replace the buyer’s own contract review with the supplier, the forwarder, or the broker.

What the handoff will do is make the ordinary workflow much more likely to succeed, and make any extraordinary problem much easier to diagnose and respond to.

How Style Sourcing Can Support the ICS2 ENS Data Handoff

Style Sourcing does not replace your forwarder, your EU customs broker, or your EU importer of record. We are a Yiwu-based sourcing team. Within the China-side workflow, the team can:

• Build the supplier-side data pack from the supplier’s commercial invoice, packing list, and packaging marks.
• Reconcile the supplier’s HS code guess with the product description, the buyer’s documentation, and the forwarder’s dossier, and ask the supplier to update the description if it is vague.
• Confirm the consignor (supplier) name and address match the contract; flag any trading company vs factory mismatch.
• Send the buyer-confirmed data pack to the forwarder in the format the forwarder’s ENS template requires.
• Reply to the forwarder’s follow-up questions about the supplier-side data pack during booking.

For anything material — particularly any EU customs law, HS code classification, IOSS / VAT, ICS2 release outcome, broker fee, or destination clearance — ask an appropriately qualified independent adviser to review the actual evidence.

Frequently Asked Questions

Does the supplier need to know what ICS2 ENS is?

Usually no. The supplier’s job is to provide the inputs (consignor, packaging, description, weight, dimensions, packaging marks) accurately. The carrier or forwarder is responsible for turning those inputs into the ENS filing. Telling the supplier “this is for ICS2” is fine for context, but the supplier does not need to know the ENS field names.

Who is responsible for filing the ENS?

The carrier or freight forwarder files the ENS. The buyer and the supplier are responsible for providing the data that goes into it. The agent’s role is to coordinate the data so the forwarder can file cleanly.

Is ICS2 ENS the same as the EU import declaration?

No. ICS2 ENS is a pre-arrival security/safety filing. The import declaration is a separate destination process that involves the customs broker, the importer of record, and the destination Member State’s rules.

Is ICS2 ENS the same as the temporary €3 customs duty on low-value consignments?

No. The temporary €3 customs duty and the Product Identifier (PID) process are separate EU mechanisms covered by a different Style Sourcing page. ICS2 ENS is a pre-arrival security/safety filing framework with its own data set.

Can I use the supplier’s listing page HS code in the ENS?

Not without checking. The HS code on a 1688 or Alibaba listing page is often auto-generated by the platform and may not match the actual product. The agent should reconcile the code with the supplier’s product description, the buyer’s documentation, and the forwarder’s own dossier before sending it to the forwarder.

What if the forwarder requires a field the agent does not have?

The agent must ask the forwarder upfront which fields the forwarder’s ENS template requires beyond the supplier-side data pack. The buyer supplies the buyer-side fields (for example EORI) before Step 3.

Does ICS2 ENS apply to small parcels?

ICS2 has different versions and timelines for different transport modes. The applicability of ICS2 to a specific shipment, parcel, or transport mode is a question for the carrier or forwarder based on the EU’s current rules. Do not assume a small parcel is exempt without checking.

What if the supplier changes the description after the ENS is filed?

A material change in the supplier’s data pack after the ENS is filed may require an ENS amendment with the carrier. The agent should be notified before the goods are loaded, and the forwarder should be asked whether an amendment is needed.

Related Guides

• The supplier-side evidence record that should already exist before the ENS data pack is collected. See the 1688 before payment order evidence record checklist.
• The carton-level data handoff that has to happen between the supplier, the agent, and the 3PL. See the Amazon inbound carton data handoff supplier to 3PL checklist.
• The evidence packet that ties the supplier’s SKUs to the inspection checkpoints. See the QC photo evidence packet traceability guide.
• The EU low-value €3 duty and Product Identifier process, which is a separate EU mechanism. See the EU low-value imports 2026 product identifier and declarant handoff guide.
• The importer-of-record vs customs broker distinction in the destination country. See the importer of record vs customs broker China-to-US handoff guide.
• The supplier verification record that justified working with this supplier in the first place. See the 1688 supplier verification checklist.
• The inspection report that confirms the SKU and quantity before the goods are loaded. See the 1688 inspection service guide.