Your rules, checked against the systems you trust

A clean shipment file can still be wrong. Checks looks up the facts your rules depend on, in the tracking, rate, hold-list, or ERP systems you've connected, on every shipment.

Run a no-cost 4-week test driveSee pricing

How every use case works

  1. 1

    Connect a system your team already uses.

  2. 2

    Write the rule in plain English.

  3. 3

    Review only the shipments where your data and the source disagree. Every lookup is on the record.

Freight invoice vs. contracted rate

The problem:
Invoices add up, but nobody compares every line to the contract. Duplicate surcharges, rates above contract, and charges the contract doesn't allow slip through.
The check:
“The freight charges billed on this shipment must match the contracted rates.”
Connect:
your rate or contract system.
What you see:
Overbilled, underbilled, and uncontracted charges are flagged, each with the billed and contracted amounts side by side. Small differences inside your tolerance pass. If there's no rate on file for the lane, the check says so.

Carrier ETA drift

The problem:
The carrier rolled the container, but your file still shows the old ETA. Your customer finds out before you do.
The check:
“The ETA must be within one day of the carrier's published ETA.”
Connect:
your carrier tracking or visibility provider.
What you see:
Shipments whose ETA disagrees with the carrier, with both dates in the explanation. If tracking can't be reached, the check asks for a person rather than passing the shipment.

Hold and restricted lists

The problem:
Your hold list only works if someone remembers to check it, on every shipment, for every party.
The check:
“The consignee and shipper must not appear on our internal hold list.”
Connect:
the system that holds your list.
What you see:
Any party that matches, flagged before the shipment moves. An unreachable list is never treated as a clean result.

Customer master data

The problem:
The delivery address on the booking doesn't match the account in your ERP, and the mismatch costs you a failed delivery.
The check:
“The consignee address must match the customer's account in our ERP.”
Connect:
your ERP or customer master.
What you see:
Bookings whose details drift from the account record, with both values shown.

Every plan can look things up. Advise: 1 system, 5 lookups. Assist: 5 systems, 10 lookups. Act: 10 systems, 20 lookups. Lookups are read-only.

Bring the rule you check by hand in another tab.

In a 4-week test drive, we'll connect the system it needs and run it on your own shipments.

Request your test drive

Ready to see what needs attention?

Try Checks with your own spreadsheet. AI finds the issues—you decide what matters.

Get started→View pricing