Automate customs clearance with custom software
Appfront builds custom software for freight forwarders, customs brokers, importers, exporters, multinationals and 3PLs that want to automate their customs flows. AGS declarations, ENS pre-arrival and ICS2, NCTS transit, EUDR reporting and export control (DUL) come together in one system, integrated with Douane NL via DTV, with AI for HS code classification and automated sanctions screening.
What is customs process automation?
Customs process automation means preparing, submitting and archiving customs declarations and related compliance flows in software, without a declarant having to key in every line by hand. The software pulls data from your sales, purchasing or TMS system, fills in the declaration fields automatically, connects directly with Douane NL via DTV and stores the full file in line with Union Customs Code requirements. What remains for your customs staff is reviewing exceptions, not retyping rules that already exist elsewhere.
In practice, such a system doesn't replace just one tool but several: an AGS declaration package for imports and exports, a separate solution for ENS pre-arrival and ICS2, an NCTS tool for transit, a CBAM portal for carbon reporting and standalone spreadsheets for sanctions screening and HS classification. Bringing these flows together under one roof stops the same product information from differing across three places, a common source of inspections, back-duties and fines. We often see this pattern in custom transport software projects, where customs is one of the heaviest compliance components.
Appfront designs these systems so they never become a black box. Declaration fields, classification decisions, sanctions checks and model output are inspectable by your own declarants, AEO auditors and Customs itself. Integrations run over standard REST and webhooks, documented to OpenAPI, so ERP vendors, TMS partners and customer portals can connect almost straight away. We describe the approach behind this more broadly on our page about smart API integrations.
Declarations that fill themselves in
Product data, consignment details and HS codes are pulled from your own ERP or WMS and placed automatically into the AGS or NCTS message. Declarants only review what deviates: an unusual goods code, a new consignor, a missing permit.
ENS pre-arrival filed well in advance
ICS2 data is generated from the house or master airway bill, sea B/L or CMR and submitted automatically within the statutory deadline. No more forgotten ENS message leaving a container stranded in Rotterdam or putting a shipment on hold at Schiphol.
Open integration with your ERP and TMS
The software runs alongside SAP, Microsoft Dynamics, Exact, AFAS or a custom TMS. Orders, product data and consignment details come in via REST or message queues, while declarations and MRN numbers flow back. No vendor lock-in.
Behind every declaration sit the permits that determine what is allowed. For bonded warehousing, inward processing and recording in your own accounts, there is software for customs procedures and recording.
Our process for custom customs software
A good customs system doesn't start with code, but with the declarants and compliance staff who do the work today. We work alongside them to surface the real rules, often unwritten knowledge about exceptions, customer-specific arrangements and historical post-clearance corrections that explain why the existing process looks the way it does. Only then do we choose the architecture, the integrations and the AI components. This way we build a system that is legally sound and also earns the trust of the team that signs off the declarations.
We join the declaration workflow and map restrictions, exceptions and risk patterns. Which goods codes cause the most problems? Which countries attract extra checks? Without that context, any automation fails within the first few months.
Which declaration types we include (AGS, ENS, ICS2, NCTS, CBAM, EUDR), which Customs systems we integrate with directly, and which data comes from which source system. We record the data model and the OpenAPI contracts.
Iterative development with automated tests, sandbox declarations and shadow runs alongside your current process. Declarants see results and give feedback before we go live. No big-bang go-live.
Controlled rollout by declaration type or client, with monitoring of acceptance rate, check percentage and processing time. This is followed by ongoing maintenance, model updates and adjustments to new legislation.
What customs automation concretely delivers
Every customs system is set up specifically for the type of goods, the type of declaration and the existing IT environment. Below are the components we consistently see, which can be combined depending on your scenario. What is on this page builds on the broader context we describe on our transport planning API page, translated to specific customs challenges.
Preparing AGS declarations
Import and export declarations are generated from your sales or purchasing system, validated for completeness and submitted automatically via DTV. Acceptance messages, releases and any control notifications come back and are linked to the original order, without declarants having to switch between systems.
ENS pre-arrival and ICS2
Pre-arrival data is taken from the master or house level of the bill of lading, supplemented with shipper, consignee and goods data, and submitted to ICS2 within the statutory deadline. The system accounts for air, sea and road-specific rules per transport mode.
NCTS transit declaration
Transit declarations for goods moving through the EU under customs transit, including guarantees, customs seals, offices of departure and destination, and the transit accompanying document. The software sends the correct status messages to NCTS and archives the complete movement history.
AI-powered HS code classification
Product descriptions, often free text from a sales or purchase order, are matched to the correct ten- or twelve-digit HS code using a dedicated language model. Each prediction comes with a confidence score; where confidence is low, the declaration is automatically routed to a declarant for manual confirmation.
Sanctions screening
Every party involved, including the shipper, consignee, end user, bank and carrier, is checked automatically against EU sanctions lists, the OFAC SDN list and the UN Security Council lists. Hits are routed to a compliance officer with the matching context: name match, address match and list version. The checks remain in the audit trail.
Export control and dual-use (DUL)
For goods covered by the Dual-Use Regulation or national export controls, the software automatically checks whether a licence is required, whether it is valid and what the restrictions are per destination country. Licences are linked to goods codes and quantities, so the system raises an alert before they run out.
CBAM reporting
For carbon-intensive imports (steel, aluminium, cement, fertilisers, hydrogen, electricity), embedded emissions, country of production and production method are recorded per shipment. The system generates the quarterly report for the CBAM portal and stores the supporting evidence.
EUDR deforestation declarations
For goods under the EU Deforestation Regulation (wood, soy, palm oil, coffee, cocoa, cattle, rubber), we link the geolocation of production areas, due diligence statements and HS codes. The software compiles the Due Diligence Statement (DDS) and archives the traceability file in line with EU requirements.
OCR for invoices and CMR
Incoming invoices, packing lists, CMR consignment notes and certificates of origin are read via OCR and captured in structured form. Product descriptions, weights, values and batch data flow directly into the declaration form, where declarants only need to review the exceptions.
Typical scenarios in practice
A customs system looks different depending on the type of business. We see a number of scenarios recurring structurally, and for each we have a recognisable approach that takes into account the specific rules, restrictions and systems common in that market. We describe the wider context of this sector on our transport planning API page; this page focuses on the customs layer on top of that.
Freight forwarders and customs brokers
Freight forwarders and independent customs agents who process declarations daily for multiple clients. The system keeps separate audit trails, terms and licences per client and automatically routes declarations to the right declarant. Existing Descartes, AEB or Customs4Trade integrations can be retained where that makes sense, and replaced where custom development delivers more.
Importers and exporters with an in-house team
Manufacturers and wholesalers with their own customs department who want to keep handling import and export declarations themselves, but wish to automate the routine work. Our software pulls order and product data directly from SAP, Microsoft Dynamics, Exact or AFAS and gives declarants a workspace in which only exceptions and risk cases surface for manual handling.
Multinationals with multi-country customs
Internationally operating businesses that need to file declarations in multiple EU and non-EU countries. The system supports the Dutch AGS flow, but is designed to be extendable to the Belgian PLDA, German ATLAS or UK CDS. Tariff differences, rules of origin (EU-UK, EU-South Korea, USMCA) and preferential trade agreements are managed centrally.
3PL with customs as a service
Logistics service providers that offer customs clearance as an additional service to their clients. Our software provides a client portal in which shippers can view their consignments, upload documents and track declaration status in real time. White-label options, branded notifications and a multi-tenant architecture are built in as standard.
Brexit border controls & post-Brexit customs
Businesses with substantial trade with the United Kingdom. Since the EU-UK Trade and Cooperation Agreement came fully into effect, declarations must be made on both sides of the border. The software supports UK CDS integrations, handles origin declarations under the Trade and Cooperation Agreement and takes account of the Northern Ireland Protocol exceptions.
CBAM importers (steel, aluminium, cement)
Importers of carbon-intensive goods covered by the Carbon Border Adjustment Mechanism. The software retrieves embedded emissions data from non-EU suppliers via a structured portal, archives supporting evidence, calculates the CO₂ levy and compiles the quarterly report. Ready for the transition from the transitional phase to the full paying regime.
Technology we use
We tailor the tech stack to your scale, declaration volume and existing IT landscape. We use proven open-source components where possible and our own models where they add value. The software is built in a language and framework that your own team can continue to maintain: no vendor lock-in, no secret sauce, no hidden costs when you renew the contract.
For trade within the EU, where there is no customs declaration but Intrastat applies, there is our Intrastat submission integration.
For the European rules on electronic freight information and what they mean for your document flow, see our article on eFTI 2027 and digital transport documents.
For the file per consignment, bringing together the customs documents, transport documents and costs, see our app for the consignment forwarding file.
Why choose Appfront for customs software?
Appfront has experience building APIs for transport and logistics, and with the specific compliance requirements of customs flows. We know that a declaration system only works if declarants trust it, that an HS classification model only becomes valuable when it is trained on your own historical data, and that a DTV integration is only stable if its retry logic is well thought through. That is why we start with your declarants and your existing ERP or TMS, not with a blank form.
For every integration, we write clear documentation and OpenAPI contracts so that your own team or a future supplier can understand and manage what is running. No black box, but transparent code and clear agreements on model versions, monitoring, audit trail and maintenance. This keeps you independent and in control of your customs flows at all times, which is becoming increasingly important legally under the AI Act and the Union Customs Code for risk routing and classification algorithms.
You work with a fixed point of contact who understands both the compliance and the integration side. This keeps lines short, prevents miscommunication between your customs relationship manager, ERP vendor and in-house IT, and speeds up decisions when choices need to be made during the build around data models, retention policies or risk thresholds. For a more general introduction to our AI approach, see AI development; for teams who want to train their own people, we offer the practical AI workshop for transport.
See also our broader overview of integrations we build and how we approach API integrations in general. A customs system is a specialised application of that.
- Experience with DTV, AGS, NCTS and ICS2 integrations
- Specialist in transport and logistics software
- Custom HS classification models based on your declaration history
- Sanctions screening against EU, OFAC and UN lists
- OCR for invoices, CMR consignment notes and certificates of origin
- CBAM reporting and EUDR notifications
- Experienced with SAP, Dynamics, Exact, AFAS and TMS integrations
- OpenAPI 3 contracts, no undocumented endpoints
- Secure by default: API keys, scoped permissions, rate limiting
- EU-resident hosting (Azure West Europe, AWS Frankfurt, Dutch cloud)
- Declaration data retained for seven years in line with the UCC
- A fixed point of contact, no account managers passed around
Compliance: UCC, GDPR, AEO and AI Act
Customs data is sensitive and heavily regulated. Declaration records, personal data of declarants and end users, proof of origin and sanctions checks fall under the Union Customs Code (UCC), the GDPR and, for AI components, the European AI Act. Appfront builds to the OWASP ASVS and, for every customs implementation, explicitly defines which personal data is required, who has access and how long it is retained.
We host within EU residency by default, whether on Azure West Europe, AWS Frankfurt or a Dutch cloud of your choice, and encrypt data both in transit and at rest. We document the data flows between ERP, TMS, customer portal and customs systems so that your record of processing activities is complete and you can demonstrably comply with the GDPR. Declaration data is retained for at least seven years as the Union Customs Code requires, with an audit trail showing who made which change and when, which is essential for AEO audits and any inspections by customs.
For the AI components, such as HS classification, risk routing and any allocation algorithms, we deliver model cards, a description of training data provenance and evaluation metrics. This enables you to demonstrate under the AI Act that decisions are transparent and explainable. For algorithms that steer on declaration volume or risk thresholds, we provide an impact assessment and human oversight steps, in line with the requirements for high-risk AI. See also our information security policy and vulnerability disclosure policy.
- UCC-compliant declaration flow and seven-year retention
- GDPR-compliant processing of declarant and customer data
- EU residency: Azure West Europe, AWS Frankfurt or Dutch cloud
- AEO-friendly audit trail per declaration
- AI Act: model cards, dataset provenance, evaluation metrics
- Impact assessment for risk routing algorithms
- EORI validation and AEO status checks
- Sanctions screening against EU, OFAC and UN lists
- Encryption in transit (TLS 1.2+) and at rest
- API key rotation and role-based access
- Rate limiting and DDoS protection for public endpoints
- Documentation for your record of processing activities
Frequently asked questions about customs software
Answers to the questions we are asked most often about custom customs clearance automation for freight forwarders, importers and 3PLs.
Customs clearance automation covers the software-driven preparation, submission and archiving of customs declarations and related compliance flows. In practice, that means AGS declarations for imports and exports, ENS pre-arrival and ICS2 for goods entering the EU, NCTS for transit movements, export control and dual-use licences (DUL), CBAM reporting for carbon-intensive imports and EUDR notifications for deforestation-free products. Supporting processes include HS code classification, sanctions screening against EU and OFAC lists, licence management, document management (CMR, invoices, certificates) and an audit trail retained for seven years.
Our clients are freight forwarders and customs agents who process dozens to hundreds of declarations every day, importers and exporters with an in-house customs team, multinationals looking to harmonise their customs flows worldwide, and 3PL and logistics providers who offer customs as part of their service. Their profiles differ, but their pain points overlap: standard SaaS packages such as Descartes, AEB or Customs4Trade do not always cover their specific business rules, integration requirements or compliance exceptions.
We integrate directly with the official channels of Dutch Customs: AGS (Common Sector Declaration) for imports and exports, DTV (Digital Transparent Traffic) for message exchange, NCTS for transit and the CBAM portal for carbon reporting. For goods entering the EU by air, sea or land, we integrate ENS pre-arrival and ICS2. The integrations run via SOAP or REST endpoints with the correct certificates and EORI number validation. We build retry logic, error handling and monitoring so that a temporary outage of a customs system does not bring your declaration process to a halt.
Yes. We train classification models on your own historical declarations to link product descriptions, often free text from a sales or purchase order, to the correct 10- or 12-digit HS code. The model comes with a confidence score and suggests alternatives; where there is doubt, we automatically route the declaration to a customs officer for manual confirmation. This keeps declarant liability within your team while routine work falls away. Combine this with our wider AI development service if you want multiple AI components in one project.
Sanctions screening runs through automated checks against the EU Consolidated Financial Sanctions List, the OFAC SDN list, the UN Security Council lists and any additional lists your sector requires. Every party involved, including the shipper, consignee, end user, bank and carrier, is checked before a declaration is sent to Customs. Hits are not rejected automatically; they are routed to a compliance officer with the matching context (name match, address match, list version) so that an informed decision can be made. All checks are logged in the audit trail.
CBAM (Carbon Border Adjustment Mechanism) and EUDR (EU Deforestation Regulation) are relatively new obligations that require a different dataset than a traditional customs declaration. For CBAM, we collect the embedded emissions, country of production and production method for each carbon-intensive import, and generate the quarterly report for the CBAM portal. For EUDR, we link geolocation data of production areas, due diligence statements and HS codes for relevant goods (wood, soy, palm oil, coffee, cocoa, cattle, rubber). Both flows integrate with your existing customs workflow, so you have one workspace, not three.
Yes. We build in line with the requirements of the Union Customs Code (UCC) and its implementing regulations, and we comply with GDPR for personal data that appears in customs flows (drivers, declarants, end users). Declaration data is retained for seven years as required, with an audit trail showing who made which change and when. Hosting within EU residency is standard. For algorithms that steer declaration volumes or risk routing, we provide model cards and evaluation metrics so you can demonstrate under the AI Act that decisions are transparent.
Yes. Many of our projects don't start from scratch: we build an AI classification module on top of an existing expense system, connect CBAM reporting to an ERP already used for import declarations, or replace a legacy batch import process with real-time DTV integrations. We review the current architecture, document what is running and draw up an improvement plan. From that point, we can also take on ongoing maintenance and further development for you.
Talk to us about your customs software
Tell us how you currently handle declarations, which ERP or TMS you use and which customs flows you want to automate, be it AGS, ENS/ICS2, NCTS, CBAM, EUDR, export control or AI-driven HS classification. We are happy to help you think through scope, priorities, data model and alignment with your existing customs relationship manager and IT suppliers. A no-obligation first conversation will give you a clear picture of what is achievable for your situation.