2026 Product Updates - Edition 9 (a)

Features available - 2026-11-03

Validation Rules: reason codes on late and early stops

Brokers can require a reason code whenever stops run early or late, so shippers get the reason behind the miss.

Why we built it

Shippers' EDI systems reject late or early stop status updates that carry no reason code. There was no way to make a dispatcher record why an actual arrival or departure fell outside the scheduled or appointment window. So reasons were skipped, buried in notes, or never captured, and the first sign of trouble was a rejection. We set out to capture the reason at the moment the time is entered, using the codes your shippers expect, and to send it along with the status update.

How it works

1. A Site Admin opens Validation Rules (Back Office → LSP → Validation Rules) and builds a rule for an Organization, limited to Shipment Types (All, or any of Small Package, LTL, Truckload, Domestic Freight, Cartage, Drayage).
2. Each rule card reads Trigger → Condition → Action. The trigger is "When a Stop is added or changed."
3. Conditions use Actual Arrival Time or Actual Departure Time:
• is within / is outside compare against the Scheduled or Appointment window.
• is at or after / is at or before compare against one time: Scheduled Ready, Scheduled Close, Appointment Ready or Appointment Close.
• Join conditions with And (all must be true) or Or (any must be true).
4. The Action is "Require <Reference Number> before save." Any reference number can be used. Its codes, display text and default come from its setup on Shipment Reference Numbers.
5. In Edit Stop and Check Call, rules are re-checked every time a date or time changes. A rule that fires adds the reference number as a required field, and Save (or the Check Call update and status buttons) stays disabled until it's filled. An info icon names the rule that asked for it. Moving the time back inside the window removes the requirement.
6. The value saves on the stop as a stop reference number and is included in the Shipment Status Update webhook, ready for your EDI mapping to send on 214s.

Window details: landing exactly on Ready or Close counts as inside. If one side of the window is blank, only the other side is checked. A date with no time is treated as 00:00.

Example

When a Stop is added or changed → Actual Arrival Time is outside the Appointment window → Require Late Reason before save.

Who can use it

• Used by: Dispatch and track-and-trace teams entering stop actuals in the Back Office, and integration teams passing stop reference numbers to shippers.
• Set up by: Users with the Site Admin role · Requires: a reference number set up with the codes your shippers accept.

Good to know

• Only Edit Stop and Check Call in the Back Office prompt for a reason. Times entered by API, carrier tracking integrations or the customer portal aren't checked.
• If the reference number has a Default, the required field arrives filled and doesn't block save. Leave Default unchecked when you want a deliberate choice.
• A firing rule makes the field required even when that reference number is set to Off at stop level.
• All active Stop rules for your organization and the customer organizations under it on the shipment apply together. When two require the same reference number, one value satisfies both.
• Rule changes can take up to 3 minutes to reach a shipment that's already open.
• Rules apply to stops only, and to times entered after the rule is active. Existing stops aren't backfilled.
• The reason reaches shippers through the Shipment Status Update webhook. Tai doesn't add it to the EDI 214s it generates directly.
• Tai keeps the captured value, not a record of which rule fired. To stop a rule, deactivate or delete it.

Get started

Validation Rules

Highway secure email addresses

Brokers using Highway can email carriers at Highway's secure domain without warning flags or rejected quotes.

Why we built it

Highway moved carrier email to a faster, more reliable address, @secure.highway.com, that isn't routed through Gmail. Tai didn't recognize the domain. Rate confirmations and messages to Highway carriers came back with "flagged … by Highway" warnings, and carrier quotes from those addresses could be auto-rejected. We set out to make Highway's secure domain work the same as any trusted carrier address, with nothing for you to set up.

How it works

• Validate Email Addresses (Send Message): an address on @secure.highway.com is always accepted, in any letter case, with surrounding spaces ignored. Tai trusts the domain directly instead of asking Highway, so it never comes back as a warning or a failure.
• To list (Send Message): a carrier remit email or contact saved as @highway.com is offered as @secure.highway.com. Your carrier profile and contacts aren't changed. This works whether or not Validate Email Addresses is on.
• Carrier quotes and Book It Now: a quote whose carrier email is on @secure.highway.com isn't rejected by the Highway email check.
• @highway.com and @gohighway.com addresses keep passing Highway's "Accepted email domain associated to multiple carrier profiles in Highway" result.

Who can use it

• Used by: Ops users who message carriers or work quotes.
• Set up by: No setup and no specific role · Requires: an active Highway integration that isn't in an error state, such as "Authentication Error." Without a Highway integration, the Validate Email Addresses toggle doesn't appear.

Good to know

• Tai doesn't build a Highway address from a carrier's DOT number. A secure address is offered only when a @highway.com or @secure.highway.com email is already on the carrier's remit email or contacts. Add the carrier's @secure.highway.com address to their contacts to use it.
• @gohighway.com addresses aren't rewritten or auto-accepted.
• Your Bypass Warning Email Classification setting works as before. It's separate from this.

Get started

Highway