What Customs Brokers Actually Want

We spent three months talking to licensed customs brokers on both sides of the US-Canada corridor. We talked to solo practitioners in Windsor and large brokerage operations in Detroit. We talked to brokers who handle 50 entries a month and brokers who handle 5,000.

We asked them one question: What would make your job better?

The answer was remarkably consistent. It wasn't more software. It wasn't AI-powered classification. It wasn't another portal to log into.

It was cleaner inputs.

The Input Problem

Every broker we interviewed described the same workflow:

Receive documents from the importer (email, portal upload, sometimes fax).
Open the documents. Discover what's missing.
Email or call the importer. Wait.
Receive partial corrections. Discover new problems.
Repeat steps 3-4 until the filing deadline forces a decision.
File the entry with whatever documentation is available, noting gaps internally.

One broker in Buffalo described it this way: "I spend 40% of my day being a document detective. I didn't get my customs broker license to chase packing lists."

40% of broker time is spent on document retrieval and correction — not on classification, valuation, or compliance analysis.

What "Clean" Actually Means

When brokers say they want "clean inputs," they mean something specific:

Complete. Every required document is present before the broker opens the file. Commercial invoice, packing list, bill of lading, certificate of origin (where applicable), any supporting certificates or permits.

Consistent. The values across documents agree with each other. The quantity on the commercial invoice matches the packing list. The commodity description on the BOL matches the invoice. The country of origin on the certificate matches the invoice.

Current. HS classifications reflect the current tariff schedule, not last year's. USMCA certificates use the current template. Supplier information matches current records.

Contextualized. The broker can see why a shipment looks the way it does. If there's a tariff engineering argument, the evidence supports it. If there's a valuation method, it's documented. If there's a ruling, it's referenced.

What Brokers Don't Want

The brokers we talked to were equally clear about what they don't want:

They don't want another portal. Most brokers already juggle ACE, ACROSS, multiple client portals, email, and their own TMS. Adding another login is friction, not help.
They don't want AI making determinations. Brokers are the licensed professionals. They make the classification decisions. They make the valuation calls. What they want is better raw material to work with — not software that tries to do their job for them.
They don't want to train their clients' employees. Brokers shouldn't have to teach importers how to fill out a commercial invoice correctly. That's an upstream problem.

The Broker-Safe Principle

This insight led us to a design principle we call "broker-safe." Any system that sits between the importer and the broker must:

Never file entries. The broker files. The system prepares.
Never make binding determinations. The system can flag a potential misclassification. The broker decides whether it is one.
Never store broker credentials. The system operates in the importer's domain, not the broker's.
Always label outputs as advisory. Every recommendation, every flag, every confidence score is explicitly advisory — never authoritative.

This isn't just a product decision. It's an architectural constraint enforced in code. There is no code path in Peregon that files an entry, transmits to a government system, or makes a binding determination. Not because we chose not to build it. Because the architecture makes it impossible.

What This Means for Importers

If you're an importer, the message from your broker is clear: Fix the inputs.

Don't send partial document sets. Don't send invoices that contradict your packing lists. Don't send HS codes you haven't verified against the current tariff schedule.

The best thing you can do for your broker relationship is give them documentation that doesn't require detective work. When the broker opens your file, everything should be there, everything should agree, and everything should be defensible.

That's not a technology problem. It's a process problem. Technology just makes the process repeatable.

Peregon delivers broker-ready documentation packets — validated, consistent, and evidence-complete. Learn how it works →