Ask a customs declarant what they were trained to do, and you'll hear about classification, valuation, duty calculation, and compliance. Ask them what actually fills their day, and you'll get a different answer: emails. Phone calls. Follow-ups. Chasing down the one missing invoice line or the document that never arrived. Somewhere between the job they trained for and the job they actually do, customs declarant information gathering has quietly become the main event, and declaring goods has become the thing squeezed in around it.
Most declarations don't start with clean, complete data. They start with an email. An end-customer (the shipper, importer, or exporter who needs goods declared) sends a message with some attachments and a description of what they need. There's no fixed format, no required fields, no checklist. It's whatever the sender thought to include.
That works fine until the declarant actually opens the file. That's when the gaps show up: a missing certificate of origin, a weight that doesn't match the packing list, an HS code that was assumed rather than confirmed. Nothing is technically wrong yet, it's just incomplete or inconsistent, and someone has to sort it out before the declaration can move forward.
A single shipment can easily touch three or four of these small gaps at once. None of them are hard to resolve on their own, a quick confirmation, a re-sent document, a corrected figure. The problem is that resolving them isn't quick when it depends on someone else's inbox, and a declarant juggling dozens of active dossiers can't afford to wait on any single one of them.
Here's where the real cost shows up. There's no structured way to flag what's missing, so the declarant writes an email or picks up the phone. The end-customer replies when they get to it, maybe today, maybe in two days. If the answer raises a new question, the loop starts again. Multiply that by dozens of active dossiers, and a declarant isn't managing a queue of declarations anymore. They're managing a queue of open conversations, each one waiting on someone else to reply.
This is more than a delay. Every interruption pulls focus away from the parts of the job that require concentration (checking classifications, verifying duty treatment, catching genuine compliance risks). Declarants end up doing detailed, high-stakes work in the gaps between fielding requests, which is exactly backwards from how it should work.
Because there's no structured process for this, the tracking falls on the individual. Which dossiers are stuck waiting on a customer reply? Which ones have been sitting for three days? Which end-customer always sends incomplete paperwork? In most operations, that information lives in someone's inbox, or in their memory. There's no dashboard for "cases blocked on missing information," so nothing gets escalated until it's already late.
That lack of visibility doesn't just cost the declarant. It means team leads and managers can't see where the bottlenecks are either. They can't tell whether a particular customer consistently causes delays, or whether the problem is spread evenly across the book of business. Without that insight, there's no way to fix the pattern, only to keep reacting to it, one dossier at a time.
It's tempting to frame this as a customer problem, if only they sent complete information the first time. But most end-customers genuinely don't know what "complete" looks like. Customs requirements vary by commodity, origin, destination, and procedure, and the average shipper isn't expected to know them by heart, that’s why you utilise a Customs broker. Without clear guidance on what's required before they hit send, they submit what seems reasonable to them, and find out it wasn't enough only when a declarant follows up. Sometimes days later.
That's a bad experience on both sides. The end-customer feels like they're being asked for things piecemeal, with no sense of what else might come. The declarant is stuck re-explaining basic requirements over and over, to different customers, for the same categories of missing information.
The fix isn't asking declarants to work harder or faster. It's giving the process structure it currently lacks: guided submission that tells end-customers what's needed upfront, a clear and trackable way to flag and follow up on gaps, and visibility into which dossiers are stuck and why. When information gathering has structure, declarants stop being the ones who chase, the process does the chasing, consistently, without depending on any one person remembering to follow up.
That shift changes what a declarant's day looks like. Less time spent re-sending the same requests. Less mental overhead tracking which conversation is with whom. More time actually available for the work that determines whether a declaration is accurate, compliant, and fast. Which, after all, was the job description to begin with.
At Customaite, this is exactly the gap we're building tools to close, giving declarants a structured way to request, track, and receive the information they need, instead of chasing it dossier by dossier.