2026 Product Updates - Edition 9

Release notes: October Release. Available October 27, 2026

Untracked loads, repeat loads, rate cons and account-level reporting all had one thing in common: someone chasing them by hand. This release takes the chasing out. Here's why we built each feature, how it works, and what to know before you put it to work.

Feature	What it does	For
Waterfall Tracking	Auto-escalates untracked loads tier by tier, so no shipment sits waiting for someone to notice.	Ops and track-and-trace teams. TMS Site Admins set it up.
Duplicate Shipment	Copies a shipment up to 20 times in one move, and you pick what carries over.	Broker ops teams, and customers booking repeat freight in Front Office.
Parent/Child Customer Reporting	Runs one Custom Report for a Parent Customer that covers every Child Customer under it.	Account managers, ops leads and Custom Report builders.
Highway Secure Rate Confirmation, on autopilot	Sends and tracks Secure Rate Confirmations automatically, so loads move to dispatch without manual steps.	Brokers using the Highway integration.
Report Previews	Opens big reports without stalling the browser, and still exports every row.	Anyone running Back Office reports or Custom Reports.
CloneOps Tracking Updates	Shows where each new tracking update came from.	Dispatchers and track-and-trace reps.

---

Waterfall Tracking

Brokers auto-escalate untracked loads tier by tier, so no shipment sits waiting for someone to notice.

Why we built it

When a carrier stops tracking or goes quiet, someone at the brokerage has to notice, chase the carrier, then chase the next contact in line. That work is manual, easy to miss and slow, and the shipment sits untracked the whole time. We built Waterfall Tracking so the escalation runs itself. Each tier of outreach gets the time you give it, and when that time runs out, the next tier is contacted. Each tier is its own automation that watches for the previous tier's alert. That lets every tier have its own timing and its own action, and the open tier alert always shows where a load stands.

How it works

Waterfall Tracking adds four building blocks to Workflow Automation:

1. Driver Tracking Canceled (trigger). Fires once when your tracking provider reports that tracking on the shipment was canceled, for example because the driver stopped tracking. Canceling tracking from inside the TMS doesn't fire it.
2. Shipment Action Log (trigger). When the selected entry is recorded on a shipment, the automation runs after a delay you set with Run After (Hours) and Run After (Minutes), at least 1 minute. Action Log Entry Type offers nine built-in entries, including Shipment Location Update, Shipment Status Update, Shipment Dispatched and Shipment Delivered. When the delay ends, the automation runs if it's still Active, and its filters check the shipment as it is at that moment.
3. Last Location Update Filter. Matches shipments whose latest location update is older than Hours Since Last Location Update (whole hours, minimum 1), or that have no location update at all. Any update counts, whatever its source.
4. Alert Created Comparison Filter. Matches when the shipment has an unresolved alert of a selected Alert Type that was created more than (Greater Than) or within (Less Than) a Period of Days, Hours or Minutes. Pick several alert types, and the filter matches if any one qualifies. Resolved alerts never count.

Example

A two-tier escalation, built with Shipment Scheduler, which runs every 30 minutes:

• Trigger: Shipment Scheduler
• Filter: Alert Created Comparison, "Tier 1 Carriers Contacted", Greater Than, 2, Hours
• Action: Resolve Alert, "Tier 1 Carriers Contacted"
• Action: Add Alert, "Escalate Tier 2 Carriers"

Resolving the Tier 1 alert is what stops this automation from firing again. For a third tier, build another automation that watches for the Tier 2 alert.

Who can use it

• Used by: ops and track-and-trace teams whose loads are escalated automatically.
• Set up by: TMS Site Admins, in Workflow Automation. There's no new permission.

Good to know

• Escalation runs on the Shipment Scheduler's 30-minute interval. It isn't instant.
• Shipment Action Log doesn't re-check the original action. If the action is undone before the delay ends, the automation still runs. Add a filter that re-checks the condition you care about.
• Every recorded entry schedules its own run. If the same entry is recorded twice, the automation runs twice.
• Shipment Dispatched and Shipment Delivered are recorded only when a user changes the status, not when a system or integration does.
• A driver force-closing the app or losing signal fires Driver Tracking Canceled only if the provider reports it as a cancel. To catch silent tracking, use a Scheduled automation with the Last Location Update Filter.
• The Action Log Entry Type list covers the nine built-in entry types. Custom action log entry types aren't available.
• Waterfall Tracking isn't related to the Waterfall Tendering building blocks, even though the names are similar.

Get started

Waterfall Tracking: Automated Tracking Escalation

---

Duplicate Shipment

Brokers copy a shipment up to 20 times in one move and pick what carries over, so repeat loads are ready faster.

Why we built it

Every shop runs repeat freight differently. One broker reuses the same pricing on every load, and the next treats every load as a fresh quote. Duplicate used to copy one fixed set of fields and make one shipment per click, so both kinds of broker cleaned up every copy by hand, and building out a day or a lane meant clicking Duplicate and saving over and over. We built Duplicate Shipment so you decide what carries over before the copy exists, and get a whole set of loads from one save. Every copy starts as an Incomplete Shipment, so nothing fires on a load you haven't reviewed.

How it works

1. Duplicate (Back Office: Tools menu) or Duplicate Shipment (Front Office: Shipment Detail) opens the Duplicate Shipment modal.
2. Duplicate Count defaults to 1 and takes whole numbers from 1 to 20.
3. Pickup and delivery locations and instructions, and Commodities, are always copied.
4. Optional toggles all start checked. In Back Office they are Additional Stop Locations and Instructions, Linehaul Carrier, Additional Transit Legs, Additional Carriers, Buy, Sell and Accessorials. Toggles for extra stops and legs appear only when the shipment has them. With Buy or Sell off, those amounts come over as $0.
5. Each reference number on the source has its own checkbox. A checked row copies the type and the value, and required default references are always added. Back Office also offers Stop Reference Numbers and Commodity Reference Numbers, all or nothing.
6. On Save, all copies are created together or none are. While alerts, commissions, mileage and carrier rep finish in the background, the modal shows "Finalizing N shipment(s)...". This takes up to 30 seconds.
7. With one copy, you land on the new shipment. With more, you land on Shipment Search, filtered to just the new copies.
8. Each copy's Activity Log says which shipment it came from, and the source's log lists its copies.

Who can use it

• Used by: broker ops users in Back Office, and customer users in Front Office.
• Permissions: there's no separate Duplicate permission. Duplicate is available on shipments whose customer is in your organization's accounting hierarchy.

Good to know

• Copies are set up for planning. A First Pickup date in the past moves to the current date and keeps its times, Last Drop dates are cleared, and actual arrival and departure times are always cleared.
• Some data is recalculated, not copied. Carrier Rep and its commission are recalculated, the factoring company comes from the carrier's current profile, and POD/BOL Attached and marketplace settings are reset.
• Some reference types are never copied, including POD Signed By, Carrier Rep and Insurance Certificate Id. Carrier references aren't copied when carriers are hidden.
• Front Office copies never carry Buy or Sell pricing, because the broker prices them. They also don't copy carriers on non-linehaul legs, or stop and commodity reference numbers.
• A copy has to be reviewed and saved before it can itself be duplicated.
• Duplicate is blocked when the customer is on credit hold or inactive, or the shipment's contact is inactive. The modal says why.

Get started

Duplicate Shipment: Choose What to Copy

---

Parent/Child Customer Reporting

Brokers run one Custom Report for a Parent Customer that covers every Child Customer under it.

Why we built it

Your biggest accounts aren't one company. They're a parent with divisions, locations and sub-accounts. A Custom Report built for a Parent Customer left out its Child Customers' shipments, and no column showed which parent a customer belonged to, so the full picture meant building several reports and merging them by hand. We built Parent/Child Customer Reporting so one report covers the whole account family, and every row shows where it sits in it.

How it works

• Shipment report rollup. When a Custom Report's organization is a Parent Customer, the report includes shipments for the Parent and all of its Child Customers, at any depth.
• Rollup by payer. A shipment is included when its bill-to is the Parent or one of its Child Customers. Pricing and payer name follow the same rule.
• Customer report rollup. The Customer report for a Parent Customer lists the Parent's own row alongside its Child Customers.
• New columns. Parent Customer Name and Parent Customer ID are on the Shipment report (Customer Information) and the Customer report (General Information). Select, order and export them like any other column.
• No hierarchy, no change. For a customer with no children, both reports return just that customer, as before.

Who can use it

• Used by: broker teams in Back Office who report on customers organized as Parents and Children.
• Permissions: the same as for Custom Reports. There's no new permission.

Good to know

• Rollup follows the payer. A shipment a Child Customer booked but billed to an organization outside the hierarchy doesn't roll up.
• The columns show each customer's direct parent. A grandchild shows its parent, not the top of the family. The columns are blank on the top-level Parent's own row.
• Exports and scheduled deliveries carry every row. The on-screen view shows the first 1,000 rows (see Report Previews).
• Front Office reporting is unchanged.

Get started

Custom Report Builder: Overview & Setup. See "Parent/Child Customer Support".

---

Highway Secure Rate Confirmation, on autopilot

Brokers on Highway get Secure Rate Confirmations sent and tracked automatically, so loads move to dispatch without manual steps.

Why we built it

Brokers using Highway Secure Rate Confirmation still had manual steps around it. A load booked through Highway Book It Now got an ordinary rate-con email, not a secure one. You couldn't send a Secure Rate Confirmation from a Workflow Automation. A carrier's accept or reject in Highway didn't move the shipment, so a dispatcher updated it by hand, and the Activity Log showed the same carrier action more than once. We built this so the secure rate con goes out on its own, the shipment status follows the carrier's answer, and the log stays clean.

How it works

1. Highway Book It Now. When a carrier books through Highway Book It Now, the Secure Rate Confirmation goes to the carrier through Highway with no extra click, and the shipment moves to Sent.
2. Send Secure Rate Confirmation Action. This new Workflow Automation action sends the shipment's rate confirmation to the linehaul carrier through Highway. It has no settings. It's sent on behalf of the workflow's Working As staff member. It supports LTL, Truckload, Domestic Freight and Drayage.
3. The right document. The rate con is the shipment type's carrier confirmation PDF, and it's attached to the shipment's documents. When the carrier signs, Highway's signed PDF is attached too.
4. Status follows the carrier. Accepted moves the shipment to Dispatched for Truckload, or Ready for other modes. Rejected moves it to Sent and adds the Rejected By Carrier and Carrier Confirmation Response alerts. Delivered, viewed, downloaded and canceled are logged only.
5. Forward only. A shipment already at Dispatched or later never moves back because of a carrier response.
6. Clean Activity Log. Each carrier action is logged once, even when Highway resends its history or events arrive out of order.

Who can use it

• Used by: dispatchers and ops teams at brokers whose Highway integration has Secure Rate Confirmations enabled. This covers Highway only.
• Set up by: admins. The Highway integration needs Secure Rate Confirmations enabled and a sending staff member set, and each carrier needs a Highway Carrier Id. Anyone who builds Workflow Automations can add the action. The action appears only for organizations with Highway Secure Rate Confirmations enabled.

Good to know

• If a Book It Now secure rate con can't be sent, the rate con is emailed to the carrier as before. There's no retry and no alert, and the Activity Log reads "A rate confirmation sheet has been sent directly to carrier email."
• A failed workflow step doesn't fall back to email. The Activity Log shows the workflow failed, and the reason is in the workflow's run log.
• If a user moves a shipment back to Sent, a later Highway update that still says "accepted" can move it to Dispatched again.
• Unbooking a Book It Now load doesn't cancel the secure rate con.

Get started

Highway - Secure Rate Confirmation

---

Report Previews

Brokers open big reports without stalling the browser, and still export every row.

Why we built it

Pull a year of shipments and the page tried to load every row at once. Pages stalled or failed, and your data was stuck behind it. We built Report Previews so big reports open fast enough to check your filters, while every export, shared link and scheduled delivery still carries the full result.

How it works

• 1,000-row preview. Custom Reports, in Back Office, Front Office and shared links, show at most the first 1,000 rows on screen. So do the Shipped, Inactive Customers, Tai Marketplace Activity, Customer Trends, Accounting Concerns and Baseline Overview reports, and every Profitability report.
• Preview notice. Over 1,000 rows, the page reads "Showing the first 1,000 of N rows. Use Export to download the full report."
• Export. In Custom Reports, Export to Excel opens Export Report, where you choose Preview Only or Full Report. Standard reports download the full report from Export. Every export is a CSV file that opens in Excel.
• Refresh window. Re-running a report shortly after shows the saved result: for up to 5 minutes when the date range is 60 days or less, and up to 24 hours when it's longer or has no date filter. Saving a change to a custom report's filters, columns or primary user/organization refreshes it right away.

Who can use it

• Used by: broker teams running reports, and customers viewing custom reports in Front Office or by shared link.
• Permissions: standard reports need Reports - Basic. Anyone who can view a custom report can download the Full Report. Building custom reports still needs Reports - Business Level.

Good to know

• Exports are CSV only.
• If an export fails, you stay on the report, the preview stays intact, and you can try again.
• Power BI and Excel connections keep receiving the full data.

Get started

Custom Report Builder: Overview & Setup · Introduction to Reports

---

CloneOps Tracking Updates

Your team sees where each new tracking update came from and automatically catches loads that have gone quiet.

Why we built it

A location pin tells you where a truck was, but not who reported it, so you can't tell a GPS ping from a guess before you call your customer. We built tracking source so you can judge every update before you trust it.

How it works

• Source column. Each new update in Shipment Location History shows its Source, such as MacroPoint, Trucker Tools, EDI, Public API or Manual Entry. Other connected integrations show under their own names.
• Source filter. Buttons for the sources on that shipment narrow both the table and the map. All clears the filter. Origin and destination rows are always shown.
• Catch loads that go quiet. The Last Location Update Filter flags loads with no location update in the hours you set. See Waterfall Tracking above.

Who can use it

• Used by: dispatchers and track-and-trace reps working loads every day.
• Permissions: no change.

Good to know

• Updates recorded before tracking source arrived, and archived locations, show a blank Source.
• Selecting a source hides rows with a blank Source.

Get started

Shipment Profile - Location History

---

Questions? Reach out to your Tai Customer Success Manager or our Support team.