What customs brokerage software should do
The capabilities a customs broker needs from software: classification, denied-party screening, duty and landed cost, ACE-ready filing, and an auditable record per entry.
Key takeaways
- Customs brokerage software has one job: get every entry right, provable, and fast, without the broker rekeying data across tools.
- The core capabilities are HTS classification, denied-party and sanctions screening, duty and landed-cost calculation, and ACE-ready filing, with a complete record per entry.
- Spreadsheets and disconnected tools break down on volume and leave gaps a penalty or a hold can exploit.
- Integration matters as much as features: the software has to exchange data with CBP systems, carriers, and client ERPs.
- An auditable trail per entry is not a nice-to-have; it is what you show when CBP asks how a decision was made.
Most customs brokers do not lack tools. They have a classification lookup, a screening service, a spreadsheet for duty, and a separate interface for filing, and they rekey the same shipment into all of them. That is where errors and delays come from, not from any one tool being bad. Good customs brokerage software replaces that patchwork with one system that carries an entry from goods to filing without losing data along the way. Here is what it should actually do.
Classification in the entry flow
Every entry starts with getting the Harmonized Tariff Schedule code right, because the code drives duty, and a wrong code is both a cost and a liability. Software should help classify goods in the flow of building the entry, keep a history of how similar goods were classified before, and carry the duty rate straight into the calculation. Classification that lives in a separate lookup tool, disconnected from the entry, is where inconsistencies creep in.
Screening on every party
US importers and brokers are required to screen the parties they deal with against denied-party and sanctions lists. Doing this by hand does not scale, and a missed screen is the kind of gap that turns into a penalty. Capable software screens every counterparty automatically as the entry is built, flags matches for review, and records that the screen was run and what the result was. The record matters as much as the check.
Duty and landed cost
Duty is only part of what an import actually costs. Freight, insurance, fees, and other charges all belong in landed cost, and getting that number right is what lets an importer price and account correctly. Customs software should calculate duty from the classification and roll it together with the other charges into a landed cost per line, rather than leaving that to a month-end spreadsheet.
ACE-ready filing
US entries are filed electronically through CBP's Automated Commercial Environment. Software that is ACE-ready assembles the filing from the data you already captured during classification, screening, and documentation, then submits it. The alternative, re-entering everything into a separate ACE interface, is both slower and a fresh chance to introduce an error.
Integration, because the data moves
A customs entry touches more than the broker. Data comes from client ERPs and arrives from carriers, and the filing goes to CBP. Software that cannot exchange data with those systems does not remove the rekeying; it just relocates it. When evaluating a platform, ask how it connects to CBP, to carriers over EDI, and to the systems your clients already run.
An auditable record per entry
The quiet requirement behind all of this is proof. When CBP asks why a good was classified a certain way or whether a party was screened, the answer has to be on record, not reconstructed from memory. Every entry should carry a complete trail: the classification and its basis, the screening and its result, the duty and landed-cost calculation, the documents, and the filing. That record is what turns an audit from a scramble into a lookup.
What it adds up to
The test of customs brokerage software is simple. Can a broker take an entry from goods to filed, with classification, screening, duty, documents, and the ACE submission in one flow, and show exactly what was done at each step? Software that can do that removes the rekeying, closes the compliance gaps, and speeds up clearance. Kadmoon starts from the analytics that measure that flow, clearance time, exceptions, and screening coverage, and builds on it. If you are weighing a move off spreadsheets and point tools, see the platform, tell us how your entries run today, or read our approach to customs and compliance.
Frequently asked questions
What is customs brokerage software?
It is the system a customs broker uses to prepare and file entries and keep them compliant. A capable platform classifies goods under the Harmonized Tariff Schedule, screens every party against denied-party and sanctions lists, calculates duty and landed cost, assembles the required documents, and files to CBP through ACE, all with a record of what was done on each entry. The point is to replace spreadsheets and manual steps with one system that is accurate, fast, and auditable.
What should I look for in customs software?
Start with the core: classification, screening, duty and landed cost, and ACE-ready filing in one flow rather than four tools. Then check integration, because software that cannot exchange data with CBP, carriers, and client ERPs just moves the rekeying somewhere else. Finally, confirm there is a complete audit record per entry and that compliance rules are kept current as regulations change. Ask who maintains the rules and how updates reach you.
Can customs software file directly to CBP?
Yes. US entries are filed electronically through CBP's Automated Commercial Environment (ACE). Customs software that is ACE-ready prepares the filing from the entry data you already captured and submits it, rather than making you re-enter everything in a separate ACE interface. The value is that classification, screening, and documents flow straight into the filing with a record of each step.