The uncovered-loads auto-classifier.

The problem

The TMS export literally cannot tell two load programs apart (every row carries the same customer name), but they post at different rates. Operators picked a converter by eye and sometimes guessed wrong. A wrong guess is a mispriced live posting.

How it works

• For each committed-but-uncovered load, the platform calls the TMS API and reads the reference field that names the program, then applies that program's deterministic rate rule.
• One program prices at a fixed percentage; the other from an owner-editable box-count table stored behind a clamp that guarantees well-formed tiers, so a garbled payload can physically not corrupt rate math.
• Before posting, every uncovered load re-proves it is still committed with no carrier, by a live read, so a load that was covered minutes ago never goes back on the board.
• Transient API failures retry rather than mis-file. A separate reference counter keeps batch numbers from ever colliding with the main sequence.

// an unclassifiable load is held for human review, never posted at a guessed rate

The result

Rate guessing eliminated. Three manual converter variants collapsed into one auto-classifying flow, and the owner edits his own rate percentages in the UI instead of asking for code changes.