For freight forwarders, the operational challenge is rarely the act of sending a message to a system. It is obtaining reliable data from the right party early enough to validate it, allocating filing responsibility clearly, and responding quickly when customs asks questions.
Start with the movement, not the declaration
Before collecting data, establish whether ICS2 applies to the specific movement. ICS2 concerns safety and security declarations for goods entering or moving in transit through the relevant customs territory. A consignment moving only within Great Britain is not an ICS2 movement, while a movement from Great Britain into the EU or Northern Ireland may require an ENS under the applicable rules.
The transport mode matters. Air, maritime, inland waterway, road and rail movements have different operational timelines and data arrangements. Filing deadlines can also depend on the type of cargo, whether it is containerised, and the route. Do not build a process around a single cut-off time copied from another trade lane. Confirm the requirement for the mode, port or airport, and journey in question before accepting the booking.
This first check should also identify the party with the legal obligation to ensure that the ENS is lodged. In many cases, the carrier is responsible. However, data can be submitted by more than one supply chain party through multiple filing arrangements. A freight forwarder may provide part of the dataset, file on behalf of a carrier where authorised, or coordinate the process between the carrier, shipper and consignee.
A commercially sound rule is simple: put filing ownership in writing before cargo moves. State who files, which data each party supplies, when it must be supplied, and who monitors customs responses outside normal office hours.
Build an ICS2 data pack at booking stage
The most reliable way to prepare ICS2 declarations is to make data collection part of the booking workflow, not a last-minute request when the trailer has been sealed or the vessel cut-off is approaching. Ask for the information in a structured format and apply the same validation rules across branches, agents and customers.
An ENS dataset commonly requires information about the parties, the transport, the route, the goods and the packaging. The exact fields depend on the movement and filing model, but your operational team should be ready to obtain:
- the consignor and consignee details, including valid names and addresses;
- relevant economic operator identification numbers where required;
- carrier, transport equipment and conveyance information;
- loading, unloading and routing details;
- package count and type, gross weight, and container or vehicle references where applicable;
- a precise goods description and the appropriate commodity classification data; and
- commercial references such as transport document numbers.
The goods description deserves particular attention. Descriptions such as “general cargo”, “spares”, “samples”, “equipment” or “parts” do not provide sufficient detail for meaningful risk assessment. A description should say what the item actually is in ordinary commercial terms. For example, “stainless-steel hydraulic valve components” is more useful than “metal parts”; “cotton women’s knitted T-shirts” is more useful than “garments”.
Do not confuse an ICS2 ENS with a full import declaration. Their purposes differ, and a safety and security filing does not remove the need for later customs formalities. Yet the information should still be consistent across documents. Contradictions between the booking, bill of lading or CMR, commercial invoice, ENS and subsequent customs entry are a clear warning sign for both authorities and customers.
Validate the source, not just the field
A technically complete declaration can still be wrong. The most common failures occur when information has been copied from an outdated booking, a generic product description, or an unverified overseas agent’s instruction.
Create a simple evidence trail for each key data element. Record who supplied it, when it was received and what document supports it. If a shipper supplies the commodity description, retain the commercial invoice or packing list that confirms it. If the carrier supplies equipment details, reconcile them against the final transport document before filing.
This discipline matters most when you work through overseas partners. A dependable agent should be able to provide complete, timely operational data and take ownership of corrections. Before allocating regular traffic, assess their credentials, reviews, customs capability and responsiveness. Trusted networks reduce the time spent chasing basic information, but they do not replace clear written procedures.
Assign responsibilities before the cargo cut-off
ICS2 performance depends on handovers. Sales teams receive the enquiry, customer service confirms the booking, operations gathers data, a carrier or authorised representative files, and someone must watch for system messages. If responsibility is assumed rather than assigned, declarations become vulnerable at precisely the point when time is shortest.
Use a responsibility matrix for each trade lane. It does not need to be complicated, but it should answer four questions: who owns the ENS filing; who supplies each data group; who approves amendments; and who responds to customs messages.
Where multiple filing is used, agree the identifiers that allow separate data submissions to be connected correctly. Share transport document references and party details in a controlled manner. A partial filing arrangement can work well when each party has direct access to the data it owns. It fails when one party believes another has submitted information that has not actually been filed.
For owner-managed forwarders, this is also a commercial control. A customer may expect you to manage the process even where the legal filing obligation sits elsewhere. Make the service scope clear in quotations and booking confirmations. Explain what information is required, the deadline for providing it, and the consequence of late or inaccurate instructions.
File early enough to correct errors
Submitting an ENS before the statutory deadline is necessary, but filing at the last possible minute leaves no margin for correction. Early filing gives your team time to resolve a rejected message, missing reference or inconsistent commodity description without disrupting the departure plan.
Use your customs software or authorised service provider to validate mandatory fields before submission. Check that names, addresses, references, package data and transport details match the latest operational documents. Once accepted, retain the movement reference and communicate it to the parties who need it under your agreed workflow.
Changes happen frequently in forwarding. A container can roll, a trailer registration can change, cargo can be split, or the consignee can be amended after booking. Your procedure must identify which changes affect the ENS and who is responsible for amending it. Treat a late operational change as a declaration review point, not merely a transport update.
It is sensible to set internal deadlines earlier than the legal deadline, especially for new customers, high-volume consolidations and shipments involving several overseas agents. The right buffer depends on the trade lane and transport mode, but the principle remains the same: use time to verify data before the border has to use time to question it.
Monitor ICS2 messages until the movement is clear
Filing is not the final step. Customs risk analysis may produce a request for additional information, a screening instruction or, in serious cases, a do-not-load notification. Someone in your business, or an agreed partner, must monitor the relevant channel and have authority to act.
Set an escalation path for these messages. Operations should know who contacts the shipper for clarification, who speaks to the carrier, and who informs the customer of a potential delay. Keep responses factual and supported by documents. Speculation, rushed amendments and conflicting explanations create further risk.
A short post-movement review is valuable when an issue occurs. Was the problem caused by poor source data, an unclear role split, a software validation gap or a late change? Correct the process, not just the individual declaration. Over time, this creates a reliable data standard that protects margins and strengthens your standing with customers and partners.
Make compliance part of partner selection
ICS2 declarations expose the quality of a forwarding network. A partner that provides precise data promptly, understands its role and responds professionally under pressure is easier to trust with strategic traffic. A partner that repeatedly sends incomplete instructions creates risk well beyond one shipment.
Use compliance performance as part of your agent review process. Look for evidence of professional operating standards, relevant certifications, credible peer feedback and clear communication. Platforms such as Trust A Forwarder can support more informed partner decisions by helping freight professionals assess the operational credibility behind a company profile.
The practical goal is not simply to submit an accepted ENS. It is to build a repeatable process in which accurate data arrives early, responsibility is visible and every supply chain partner understands that border compliance is part of service quality.