!An honest scope conversation

Freight fraud prevention — where CarrierShield helps, and where it doesn't.

Freight fraud is a real and growing problem: double-brokering, carrier impersonation, stolen MC numbers, and forged insurance certificates. We are not a fraud-prevention engine — but compliance hygiene closes a real subset of the gaps fraudsters exploit.

Where we help

Compliance hygiene that narrows fraud exposure.

These are not anti-fraud features. They are basic compliance practices that, when done consistently, reduce the surface area fraudsters work with.

Current COIs on file

An expired or missing certificate is one of the easiest ways for an unverified carrier to slip through. CarrierShield keeps current COIs in front of your team.

Renewal directly from the carrier

Reminders go to the carrier's insurance contact and accept uploads through a tokenized link. That helps keep COIs sourced from the carrier, not forwarded through a chain.

Broker review before status change

Extracted certificate dates are suggestions. A broker user must confirm before a carrier becomes "active." Nothing flips silently based on an upload alone.

Audit trail of every action

If a load goes wrong, you can reconstruct exactly which document was on file, when it was uploaded, who approved it, and what reminders went out.

Workspace-scoped access

Role-based access (owner, admin, editor, viewer) limits who can change carrier status or edit certificate dates inside your brokerage.

No shared logins

Each team member has their own account, so audit history attributes actions to a real person — not a shared inbox.

Out of scope

What CarrierShield does not do for fraud.

If a vendor promises to "prevent freight fraud" with one tool, ask hard questions. The honest answer is that fraud prevention is layered, and no single product covers all of it.

FMCSA authority verification

We do not check operating authority, MC/DOT status, safety ratings, or out-of-service orders. Use a dedicated authority verification service alongside CarrierShield.

Identity / impersonation checks

We do not verify that the person uploading a COI is the legitimate carrier. A tokenized link helps, but it is not an identity proof.

Double-brokering detection

We do not detect when a carrier you've booked re-brokers the load to another carrier. That is a routing- and load-monitoring problem, not a COI tracking problem.

Certificate authenticity verification

We extract dates and store the file. We do not verify with the insurance issuer that the certificate is genuine and currently in force.

Watchlists / shared fraud databases

We do not subscribe to or operate industry fraud watchlists. Pair CarrierShield with the watchlist services your brokerage already uses.

Payment fraud / banking changes

Banking, factoring, and pay-to changes are out of scope. Those are handled in your TMS or accounting system with their own change-of-banking controls.

Honest stance

Compliance hygiene is one layer of fraud defense.

Use CarrierShield for current COIs, reminders, broker review, and audit history. Pair it with authority verification, identity checks, and watchlists for the rest.