What we changed, and when.

Product updates, month by month. Regulatory coverage, scanning behaviour, and platform changes — written for the person who has to trust the output, not for a press release.

August 2026
Faster extraction, a placarding correction worth reading, and two new public pages.

RegulatoryMissing weight units no longer disappear from the placard threshold

When a shipping paper listed a weight without a unit, that line contributed zero toward the 1,001 lb aggregate in the §172.504(c) Table 2 calculation — biasing the result toward not placarding. Lines with an unreadable unit are now flagged for your confirmation instead of being silently counted as nothing. If you scanned mixed loads before this change, it is worth re-checking any that came back close to the threshold.

RegulatoryVoluntary explosives placards under §172.502(c)

Determinations now surface where a placard is permitted but not required, so carriers who placard voluntarily as policy can see the option rather than infer it.

ScanningFaster page extraction

Migrated document extraction to a newer vision model. The most visible effect is speed — scans that used to take roughly half a minute now typically finish in a fraction of that. Accuracy was measured before and after on our internal test corpus and did not regress.

ScanningBetter results on shadowed and unevenly lit photos

A photo taken on a loading dock often has one bright corner and one dark one. The previous single-threshold conversion could wash out a whole region of such a page. Pages are now re-thresholded locally when that happens, which recovers text that was previously lost.

ScanningLonger documents no longer truncate silently

Multi-page shipping papers that exceeded the extraction ceiling could return a partial result. The ceiling was raised and the scanner now escalates instead of quietly stopping.

PlatformTwo new public pages

Trust & Security sets out our control monitoring and compliance status, including what we don't claim. Security Disclosure is a plain-language rendering of our vulnerability reporting policy.

PlatformStronger account protection

Minimum password length raised to 12 characters, and new passwords are screened against commonly used and easily guessed values. Existing passwords were not invalidated.

PlatformAutomated data retention

Retention periods published in our Privacy Policy are now enforced automatically rather than by hand, with legal-hold support so records under hold are never removed. Compliance evidence held under a locked seven-year retention policy is unaffected and cannot be deleted — that limit is stated in the policy.

PlatformFewer spurious sign-in blocks

Our sign-in location check depends on an outside provider. If that provider is unreachable, we now reuse its last known answer for an address we've seen before, so an outage on their side no longer locks out drivers on rotating cellular IPs.

July 2026
A large expansion of regulatory coverage, plus the shipper-side paperwork tools.

RegulatoryPlacarding thresholds now compute on gross weight

§172.504(c) thresholds are assessed on gross weight, not net. Determinations record which basis was used, so the arithmetic behind a placard decision can be re-checked later.

RegulatoryLimited quantity, materials of trade, and combustible-liquid relief

Added the §172.500(b)(2) limited-quantity exception, the §173.6 materials-of-trade advisory (advisory only, by design), and non-bulk combustible-liquid relief under §172.500(b)(5).

RegulatorySegregation: cyanides and acids, and Zone C/D routing

Enforced the §177.848(c) prohibition on transporting cyanides with acids, and corrected Division 2.3 Zone C/D handling so that loads with no actual restriction are routed as such with an informational advisory rather than a false conflict.

RegulatoryShipping-paper sequence auditor

Checks the §172.202(a) description order and cross-checks proper shipping name against packing group, so a paper that is complete but out of order gets flagged before it ships.

RegulatoryRoute plans and the California CHP overlay

Written route-plan triggers, a CHP 148A overlay for California, and PHMSA registration checks in carrier vetting.

RegulatoryCompany placarding policy modes

Carriers who placard beyond the regulatory minimum can set a standing policy — required only, specific classes, or placard all — and every scan path honours it.

RegulatoryEvery finding links to the regulation

Determinations are stamped with the regulatory currency date and deep-link to the exact eCFR provision applied, so you can read the rule rather than take our word for it.

ProductShipper Paper Studio

Generate a compliant §172.203 shipping paper, then have it recognized automatically when it is scanned at the dock. Includes the Shipper Fix Sheet, which turns flagged problems into a single correction artifact.

ProductScan provenance pages

Each scan can expose a shareable page at a one-off link, so an inspector or counterparty can view the determination without an account. Links are revocable, and views are recorded for the account that issued them.

ProductAbsent versus unreadable — the scanner stops guessing

A field the document doesn't contain and a field the camera couldn't read are different problems with different fixes. They are now reported differently, and neither is filled in with a guess.

ProductLight and dark themes

A theme toggle across the scanner and every signed-in tab. Cab in daylight, cab at 2am.

PlatformIndependent second-provider cross-check

Consequential extracted fields are cross-checked against a second, independent document provider. Where the two disagree, the disagreement is surfaced to you rather than resolved silently. Our Privacy Policy lists both providers.

PlatformVerification chain paging

The public audit-chain verifier now pages through long chains instead of attempting the whole history in one request.

How this page is written. Entries describe changes that affect what you see or what the software decides. Internal work — infrastructure, monitoring, test coverage, dependency updates — is not listed unless it changed something you would notice.

We publish accuracy improvements in plain terms rather than as headline percentages. Our measurements come from an internal test corpus that is smaller than the number a marketing figure would imply, and we would rather describe the change honestly than quote a precise number we cannot stand behind for your documents.

Something here wrong, or a change you expected and don't see? Tell us. For security issues specifically, see our disclosure policy.