Automate customs clearance with custom software
Appfront builds custom software for freight forwarders, customs agents, importers, exporters, multinationals and 3PLs who want to automate their customs flows. AGS declarations, ENS pre-arrival and ICS2, NCTS transit, EUDR notifications and export control (dual-use) come together in one system, integrated with Dutch Customs via DTV, with AI for HS code classification and automated sanctions screening.
What is customs processing automation?
Customs processing automation means using software to prepare, submit and archive customs declarations and related compliance flows, 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, integrates directly with Dutch Customs via DTV and stores the entire file in line with Union Customs Code requirements. What remains for your customs staff is reviewing exceptions, not retyping data that already exists elsewhere.
In practice, such a system replaces not one tool but several: an AGS declaration package for import and export, a separate solution for ENS pre-arrival and ICS2, an NCTS tool for transit, a CBAM portal for carbon reporting and loose spreadsheets for sanctions screening and HS classification. By bringing these flows under one roof, you avoid the same product information being recorded differently in three places, a common source of inspections, post-clearance demands and fines. We often see this pattern in projects involving custom transport software: customs is one of the heaviest compliance components there.
Appfront designs these systems so they never become a black box. Declaration fields, classification decisions, sanctions checks and model output can all be inspected by your own declarants, AEO auditors and Customs itself. The integrations run via standard REST and webhooks, documented according to OpenAPI, so ERP vendors, TMS partners and customer portals can connect to them almost immediately. We describe the approach behind this more broadly on our page about smart API integrations.
Declarations that fill themselves in
Product data, party details and HS codes are pulled from your own ERP or WMS and placed automatically in the AGS or NCTS message. Declarants only review what deviates: an unusual commodity code, a new sender, a missing licence.
ENS pre-arrival well in time
ICS2 data is generated from the house or master airway bill, sea bill of lading or CMR and submitted automatically within the statutory deadline. No more forgotten ENS message that leaves a container stuck in Rotterdam or puts 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 party details come in via REST or message queues, while declarations and MRN numbers flow back. No vendor lock-in.
Behind the declaration lie the authorisations that determine what is permitted. For entrepôt, processing and registration in your own records, there is software for customs procedures and registration.
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 agreements and past post-clearance duty demands that explains why the existing process is the way it is. Only then do we choose the architecture, the integrations and the AI components. That way we build a system that is legally sound and earns the trust of the team that signs off the declarations.
We shadow the declaration flow and map out restrictions, exceptions and risk patterns. Which commodity codes regularly cause problems? Which countries require extra checks? Without that context, any automation fails within the first few months.
Which declaration types do we include (AGS, ENS, ICS2, NCTS, CBAM, EUDR), which customs systems do we integrate with directly, and which data comes from which source system. We define 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 to production. No big-bang go-live.
A controlled rollout per declaration type or customer, with monitoring of acceptance rate, inspection rate and lead time. After that comes ongoing maintenance, model updates and adaptation to new legislation.
What customs automation delivers in practice
Every customs system is configured specifically for the type of goods, the type of declaration and the existing IT environment. Below are the components we see time and again — they can be combined individually, depending on your scenario. What this page covers builds on the broader context we describe on our transport planning API page, translated into the specific challenges of customs.
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 inspection 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 waybill, supplemented with consignor, consignee and goods details, and sent to ICS2 within the statutory deadline. The system takes into account the rules specific to air freight, sea freight and road transport for each mode.
NCTS transit declarations
Transit declarations for goods moving through the EU under customs supervision, including guarantees, customs seals, offices of departure and destination, and the transit accompanying document. The software sets the correct status messages in NCTS and archives the complete journey history.
HS code classification with AI
Product descriptions — often free text from a sales or purchase order — are matched to the correct 10- or 12-digit HS code using a dedicated language model. The prediction comes with a confidence score; at low confidence, the declaration is automatically routed to a declarant for manual confirmation.
Sanctions screening
Every party involved — consignor, consignee, end user, bank, carrier — is automatically checked against EU sanctions lists, the OFAC SDN list and the UN Security Council list. Hits are routed to a compliance officer together 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 control, the software automatically checks whether a licence is required, whether it is valid and what the restrictions are for each destination country. Licences are linked to commodity codes and quantities so the system raises an alert when they are running low.
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 underlying supporting evidence.
EUDR deforestation declarations
For goods covered by the EU Deforestation Regulation (timber, soy, palm oil, coffee, cocoa, cattle, rubber), we link the geolocation of production areas, due diligence statements and HS codes. The software compiles the DDS (Due Diligence Statement) 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 imported in structured form. Product descriptions, weights, values and batch data go straight into the declaration form, where declarants only need to review the deviations.
Typical scenarios in practice
A customs system looks different for every type of business. We see a number of scenarios come up again and again, and for each of them we have a proven approach that takes into account the specific rules, restrictions and systems that are 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 & customs agents
Freight forwarders and independent customs agents who process declarations for multiple clients every day. The system keeps separate audit trails, terms and permits for each client and automatically routes declarations to the right declarant. Existing Descartes, AEB or Customs4Trade integrations can be kept where that makes sense and replaced where a custom solution delivers more.
Importers & exporters with their own team
Manufacturers and wholesalers with their own customs department who want to keep handling import and export declarations themselves, but want to automate the routine work. Our software pulls order and product data directly from SAP, Microsoft Dynamics, Exact or AFAS and gives declarants a worklist in which only exceptions and risk cases surface for manual review.
Multinationals with multi-country customs
Internationally operating companies that need to file declarations in multiple EU and non-EU countries. The system supports the Dutch AGS flow, but is set up so that it can be extended to Belgian PLDA, German ATLAS or UK CDS. Tariff differences, rules of origin (EU-UK, EU-KR, USMCA) and preferential trade agreements are managed centrally.
3PLs offering customs as a service
Logistics service providers who offer customs handling as an added service to their customers. Our software provides a customer portal in which clients can view their shipments, upload documents and follow declaration status in real time. White-label options, branded notifications and a multi-tenant architecture are part of the design as standard.
Brexit border controls & post-Brexit customs
Companies with substantial trade with the United Kingdom. Since the EU-UK trade agreement came fully into effect, declarations have to be made on both sides of the border. The software supports UK CDS integrations, handles origin declarations under the Trade and Cooperation Agreement and accounts for the Northern Ireland Protocol exceptions.
CBAM importers (steel, aluminium, cement)
Importers of carbon-intensive goods covered by the Carbon Border Adjustment Mechanism. The software collects 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 fully paid 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 no customs applies but Intrastat does, there is our Intrastat reporting 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 per-shipment file, with customs documents, transport documents and costs together in one place, see our app for the per-shipment freight forwarding file.
Why 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 the retry logic has been properly 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. That keeps you independent and lets you stay in control of your customs flows at any time, a requirement that is also becoming legally more important under the AI Act and the Union Customs Code for risk-routing and classification algorithms.
You work with a single point of contact who understands both the compliance and the integration side. That keeps lines short, prevents miscommunication between your Customs relationship manager, ERP supplier and in-house IT, and speeds up decisions when choices have 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 that want to train their own people, we offer the practical AI workshop for transport.
Also take a look at 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, CMRs and certificates of origin
- CBAM reporting and EUDR submissions
- Familiar 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 single point of contact, no passing you between account managers
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 in line with OWASP ASVS and, for every customs implementation, explicitly determines which personal data is needed, who has access and how long it is retained.
By default, we host within the EU (Azure West Europe, AWS Frankfurt or a Dutch cloud of your choice) and encrypt data in transit and at rest. We document the data flows between your ERP, TMS, customer portal and customs systems so that your record of processing activities is complete and you can demonstrate compliance with the GDPR. Declaration data is retained for at least seven years, as required by the Union Customs Code, with an audit trail showing who made which change and when. This is essential for AEO audits and any inspections by Customs.
For the AI components (HS classification, risk routing and any allocation algorithms), we provide model cards, a description of where the training data comes from, and evaluation metrics. This lets you demonstrate under the AI Act that decisions are transparent and explainable. For algorithms that steer on declaration volume or risk thresholds, we include an impact analysis and human-oversight steps, in line with the requirements for high-risk AI. Also read our information security policy and CVD policy.
- UCC-compliant declaration flow and seven-year retention
- GDPR-compliant processing of declarant and customer data
- EU residency: Azure West EU, AWS Frankfurt or a Dutch cloud
- AEO-friendly audit trail for every declaration
- AI Act: model cards, dataset provenance, evaluation metrics
- Impact analysis 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 get asked most often about custom customs-handling automation for freight forwarders, importers and 3PLs.
Customs-handling automation covers preparing, submitting and archiving customs declarations and related compliance flows in software. In practice, that means AGS declarations for imports and exports, ENS pre-arrival and ICS2 for goods entering the EU, NCTS for transit, export control and dual-use licences (DUL), CBAM reporting for carbon-intensive imports, and EUDR notifications for deforestation-free products. On top of that come supporting processes: HS code classification, sanctions screening against EU and OFAC lists, licence management, document management (CMR, invoices, certificates) and an audit trail that is retained for seven years.
Our clients are freight forwarders and customs agents who process dozens to hundreds of declarations a day, importers and exporters with their own customs department, multinationals that want to harmonise their customs flows worldwide, and 3PL and logistics providers that offer customs as part of their service. The profiles differ, but the pain points overlap: standard SaaS packages such as Descartes, AEB or Customs4Trade don't always cover their specific business rules, integration requirements or compliance exceptions.
We integrate directly with the official channels of Dutch Customs: AGS (Aangifte Gemeenschappelijke Sector) for imports and exports, DTV (Digitaal Transparant Verkeer) 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 right certificates and EORI number validation. We build in retry logic, error handling and monitoring so that a temporary outage of a customs system doesn't bring your declaration process to a halt.
Yes. We train classification models on your own historical declarations to match product descriptions — often free text from a sales or purchase order — to the correct ten- or twelve-digit HS code. The model returns a confidence score and offers alternatives; when in doubt, we automatically route the declaration to a customs officer for manual confirmation. That keeps declarant liability within your team while the routine work disappears. Combine this with our broader AI development service if you want multiple AI components in a single project.
Sanctions screening runs through automated checks against the EU sanctions lists (Consolidated Financial Sanctions List), OFAC SDN, the UN Security Council list and any additional lists your industry requires. Every party involved — sender, recipient, end user, bank, carrier — is checked before a declaration is sent to Customs. Hits are not rejected automatically: they are routed to a compliance officer together 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 data set from a classic 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 for 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 flow, so you have one work queue instead of three.
Yes. We build to the requirements of the Union Customs Code (UCC) and its implementing regulations, and we comply with the 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 drive 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 declaration system, connect CBAM reporting to an ERP already used for import declarations, or replace an outdated 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.
Talk to us about your customs software
Tell us how you currently submit declarations, which ERP or TMS you work with and which customs flows you want to automate — AGS, ENS/ICS2, NCTS, CBAM, EUDR, export control or AI-based HS classification. We're 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 gives you a clear picture of what is feasible for your situation.