Choosing the best customs clearance software is less about finding the longest feature list and more about finding a product that fits how your team actually lodges entries, whether in Australia, New Zealand or both. This guide sets out eight tests you can apply to any shortlist, explains where the two jurisdictions differ, and walks through a selection process that gives leadership a clear rationale for the decision.
Why Customs Clearance Workflows Outgrow Spreadsheets and Legacy Tools
Many small to mid-sized forwarders begin with spreadsheets, email and a basic lodgement tool. That combination works while volumes are low and one experienced broker knows every client by name. As volumes rise and new staff join, the cracks start to show. Entries wait on the one person who knows the history, and mistakes surface only after a query from the border agency.
The core problem is fragmentation. Shipment data lives in the freight system, commercial documents arrive by email, and declarations are prepared somewhere else entirely. Every hand-off between those places is a chance for an error, a delay or a missing record. If this sounds familiar, our article on signs your freight forwarding software can't keep up covers related warning signs across the wider operation.
Common Pain Points in Daily Customs Clearance
Operations teams tend to report the same frustrations:
- Data re-keying: consignee, tariff and value details typed into more than one system.
- Document chasing: invoices, packing lists and permits scattered across several inboxes.
- Lodgement friction: rejected or queried declarations that need manual correction and resubmission.
- Status blind spots: no single view of where each entry sits in the customs clearance process.
- Thin audit trails: difficulty showing who changed what, and when, if a regulator asks.
Each issue is manageable on its own. Together they eat into broker time, slow turnaround for clients and raise compliance risk, usually at the busiest points of the month.
The Business Case for Dedicated Customs Software Solutions
Dedicated tools address these problems by capturing data once, validating it before lodgement, connecting to your freight platform and recording every action against the entry. The business case usually rests on four outcomes that leadership cares about:
- fewer errors and queries from customs
- faster clearance turnaround for clients
- lower compliance exposure
- more entries handled without adding headcount at the same rate
Frame your proposal around these outcomes, not features. Quantify them using your own numbers: how many declarations were queried or amended last quarter, how many hours brokers spent re-keying or chasing documents, and how long the average entry takes from document receipt to clearance. Even rough internal estimates give decision makers something concrete to weigh against implementation cost.
Key Evaluation Criteria for the Best Customs Clearance Software
To make 'best' measurable, assess every product on your shortlist against the same eight criteria. Score each from 1 to 5 based on evidence you saw in a demonstration, not claims in a brochure. Then weight the criteria to reflect your operation. A brokerage with heavy import volumes may weight lodgement and validation highest, while a forwarder running its own freight platform may put integration at the top. Multiplying each score by its weight produces a total that is easy to compare and easy to defend.
The Evaluation Criteria Table
| Criterion | What good looks like | Questions to ask |
|---|---|---|
| Declaration and lodgement support | Supports the import and export declaration types you lodge, with clear status tracking | Which declaration types are supported for each country you clear in? How are rejections handled? |
| Data capture and validation | Data entered once and checked before submission | Which fields are validated? Can data flow from shipment records? |
| EDI and system integration | Reliable exchange with your freight and accounting platforms | Which integration methods exist? Who maintains the connections? |
| Compliance and audit trails | Full history of changes, users and submissions | Can you produce a change history for any entry quickly? |
| Usability | Brokers complete common tasks without workarounds | How long does a new user take to become productive? |
| Reporting | Visibility of volumes, status, exceptions and workload | Can managers build the reports they need? |
| Scalability | Handles growth in entries, users and locations | What changes as volumes double? |
| Vendor support | Local, responsive support and ongoing product updates | What are support hours and channels? How are regulatory changes delivered? |
Treat these eight rows as a starting point rather than a fixed list. If your operation handles a commodity with extra permit requirements, or you clear a high share of low-value consignments, add a row for it or raise the weighting on the closest existing criterion.
Integration and EDI: The Criterion Most Often Underestimated
A product can look excellent in isolation and still fail if it does not connect cleanly with your freight management system. Poor integration simply recreates the re-keying you set out to remove, only now across two new screens. Electronic data interchange has long been a standard way for trading partners and agencies to exchange structured documents, but the quality of each vendor's implementation varies widely.
Ask vendors to show live data flowing from a shipment record into a declaration, then back again as a status update. Check who builds and maintains each connection, what happens when a message fails, and how errors are surfaced to the user. For more on how these links work in practice, read our explainer on EDI integration as the bridge between freight forwarding and customs.
Compliance and Audit Trails
Compliance leads should test this criterion themselves instead of relying on a sales summary. Ask the vendor to pick a completed entry and show every change, the user responsible and the timestamp. Check how long records are retained, how user access is controlled, and whether reports can be exported in a usable format if a regulator requests them. Software cannot make you compliant on its own, but it should make compliant practice the easy path for every broker on the team.
AU vs NZ Considerations When Choosing Software
Australia and New Zealand run separate customs systems with their own lodgement channels, data requirements and regulators: the Australian Border Force on one side of the Tasman and the New Zealand Customs Service on the other. If you clear goods in both countries, jurisdictional fit becomes a deciding criterion, not a nice-to-have.
The practical risk is assuming a product built for one market handles the other equally well. Some customs software solutions support one jurisdiction in depth and the other only partly, or not at all. Confirm coverage for each country separately, and use your own declaration types as the test in place of a generic demo entry.
Regulatory change is the other consideration. Border agencies update reporting rules and system interfaces over time, and new obligations can appear for particular trade lanes, as our piece on ICS2 compliance for AU and NZ freight forwarders shows. A vendor's track record in delivering those updates on time matters as much as its current features.
For a full breakdown of how the two regimes differ, see our guide to AU vs NZ customs clearance: key differences.
Questions to Ask About Jurisdictional Fit
- Which jurisdictions does the product support for lodgement today, and which declaration types does it cover in each?
- How does the vendor keep the software current when regulatory or system requirements change?
- Can one team work across Australian and New Zealand entries in the same interface, or are they separate?
- How are country-specific data fields and validation rules handled?
Ask for evidence in a live demonstration instead of accepting a tick on a checklist.
How to Run a Shortlist and Selection Process
A structured selection process protects you from choosing on presentation quality alone. It also gives leadership a documented rationale for the investment, which matters when the decision is revisited a year later. The four steps below suit most small to mid-sized forwarders and brokerages, and they can usually run alongside normal operations without a dedicated project team.
Map Your Current Customs Clearance Workflows
Before speaking to any vendor, document how an entry moves through your business today. Note where data originates, who touches it, which systems are involved and where errors or delays tend to occur. A simple flow diagram for your top three declaration types is enough; you do not need a formal process model. Mark the steps where information is typed in twice or where staff sit waiting on documents. This map becomes the yardstick for every demonstration, because you will ask each vendor to show how their product changes those specific steps.
Define Must-Have Criteria and Involve the Right People
Use the criteria table to separate must-haves from nice-to-haves. Involve the people who will live with the decision: brokers who lodge every day, a compliance lead, operations management and whoever owns your freight system. Each group sees different risks. Brokers notice clumsy screens, compliance leads notice gaps in record keeping, and system owners notice integration problems. Agree the weightings before demonstrations begin so that scoring stays objective and nobody adjusts the numbers to favour a preferred vendor.
Request Demonstrations Against Real Scenarios
Give each vendor an identical set of scenarios drawn from your workflow map. A practical set might include a routine import, an export that needs additional permits, and a declaration that must be corrected after a query. Ask them to work through each one live, with realistic data, rather than switching to prepared slides. Have every evaluator score immediately afterwards while details are fresh, then compare notes as a group. Large gaps between individual scores are worth discussing, since they often reveal a concern one person spotted and others missed.
Assess Implementation and Integration Effort
Ask each vendor to describe implementation in practical terms: data migration, integration with your freight system, user training and the internal time required from your staff. Clarify who is responsible for each task, what happens if a milestone slips, and what ongoing support looks like after go-live. Find out how product updates arrive once you are live and whether they require any work on your side. A strong product with an unrealistic rollout plan is a risk to daily operations, particularly if go-live lands during a peak period for your clients.
Where Expedient Software Fits and Next Steps
Expedient Software builds software for freight forwarders and customs brokers, treating customs clearance as one part of a connected freight operation instead of a standalone tool. That approach lines up with several criteria in this guide, particularly reducing re-keying between freight and customs work. For context on the wider landscape, our freight and logistics software guide explains how the different systems fit together.
We encourage you to apply the same scoring framework to Expedient Software as you would to any other option on your shortlist: test it against your own scenarios, score it honestly and weight the result. To see the product and its current capabilities, visit our customs clearance features page. When you are ready to discuss your requirements, Contact Us.
Frequently Asked Questions
What should a small forwarder look for in customs software?
Look for a product that captures data once, validates it before lodgement and connects directly to your freight platform. Beyond that, check usability for brokers, change history on every entry, useful reporting and responsive local support. Scoring each of these from 1 to 5 during demonstrations gives you a fair comparison between vendors.
How do I compare customs software vendors fairly?
Use a weighted scoring model applied identically to every vendor. Agree your criteria and weightings before any demonstration, then give each vendor the same real scenarios from your own operation, such as a routine import and a queried declaration. Have each evaluator score straight after the session while details are fresh.
Can one customs product handle both Australian and New Zealand declarations?
Some can, but coverage is often uneven, with one country supported in depth and the other only partly. Australia and New Zealand have separate regulators, lodgement channels and data requirements. Confirm support for each country separately by asking the vendor to process your own declaration types in a live demonstration.
Why does EDI integration matter so much when choosing customs software?
Without reliable integration, staff end up re-keying shipment details into declarations, which brings back the errors and delays you wanted to remove. Ask vendors to show data moving from a shipment record into a declaration and a status update flowing back. Also confirm who maintains each connection and how failed messages are reported.
How long does it take to implement new customs software?
It depends on data migration, the number of integrations and how much training your brokers need. Ask each vendor for a practical plan covering those tasks, who owns each one and the internal time required from your team. Avoid scheduling go-live during a peak period for your clients.
