Short answer: ICS2 is the EU's pre-loading and pre-arrival security filing system. For e-commerce, the carrier or postal operator files the entry summary declaration, but it can only file what the seller provides: complete shipper and consignee data, accurate goods descriptions, HS codes, and values. US Shopify brands do not file ICS2 themselves, yet incomplete product and customer data is the most common reason parcels get held under it.
What ICS2 actually requires
The Import Control System 2 requires an entry summary declaration before goods are loaded onto the aircraft or vessel bound for the EU. The filing includes who is shipping, who is receiving, what the goods are, and their value. For express and postal e-commerce flows, the filing usually happens per consignment based on the data the seller passes to the carrier at label creation. The security screening runs against that data: sanctions lists, risk profiles, and description plausibility.
The key detail for Shopify sellers is that ICS2 does not accept vague data. A description like "gift" or "clothes" with no HS code and a rounded value will not clear the automated screening cleanly. The declaration gets flagged, the carrier holds the parcel for more information, and the customer sees a tracking status that says customs clearance delayed with no further explanation. The seller rarely learns the real cause unless they ask the carrier directly.
Why this lands on the seller even though the carrier files
Carriers and brokers file the declaration, but they file your data. When an ICS2 filing is incomplete, the carrier's system kicks the consignment back to the shipper for corrections, which in a DTC flow means the brand. Brands that pass clean, complete data at label creation almost never hear about ICS2. Brands with sloppy SKU data hear about it constantly, usually as unexplained delivery delays in the EU.
The data that matters most: full consignee name and address (no initials, no PO-box-only addresses where the carrier requires a street), a goods description concrete enough to match the HS code, the correct HS code itself, and an accurate declared value in a stated currency. If your catalog already carries clean HS and origin data, you are most of the way there. If it does not, ICS2 turns every EU shipment into a small gamble.
The multiple-filing trap in e-commerce
E-commerce shipments under ICS2 can involve more than one filing: a pre-loading filing with a minimum dataset and a full pre-arrival filing. Different parties may be responsible for each, typically the carrier for the master level and the postal operator or express carrier for the house level. Misalignment between the two is where parcels stall: the pre-loading data says one thing, the house-level data says another, and the system flags the consignment for reconciliation.
For brands, the practical takeaway is to use one carrier flow and one data source. Shipping labels generated from your store's checkout data, passed straight through to the carrier's system without manual re-entry, produce consistent filings. Brands that retype addresses or descriptions in a separate carrier portal introduce the mismatches that ICS2 is designed to catch.
What to fix this week
First, audit your SKU data for the fields ICS2 needs: description, HS code, value, weight, and country of origin. This is the same cleanup that accurate duty calculation requires, so one project serves both. Second, check what data your carrier receives at label creation. If your shipping app passes truncated descriptions or placeholder values, fix the integration before you blame customs. Third, ask your carrier what their ICS2 rejection rate is for your account. A rate materially above their average means your data is the problem, and they can usually show you exactly which fields are failing.
ICS2 is not a tax and it does not change what you owe. It is a security screen that runs on data quality, and data quality is entirely within the seller's control. Brands that treat it as a data project sail through. Brands that treat it as the carrier's problem keep getting surprised.
Do I need to register for ICS2 as a US seller?
No. The filing obligation sits with the carrier or the party bringing the goods into the EU. Your obligation is providing complete and accurate consignment data. If you use a freight forwarder as the declarant for other purposes, confirm with them who files what for your shipments.
Does ICS2 affect DDP shipments differently?
No. ICS2 is a security filing, independent of whether duties are paid at checkout (DDP) or on delivery (DAP). It applies the same way regardless of the Incoterm. Duty strategy and ICS2 readiness are separate projects that happen to share the same SKU data cleanup.