Freight Analytics With an AI-Written Analysis on Every Report

Forwarders Are Rich in Data and Poor in Answers

Every forwarding company generates the raw material for great analytics: quotes won and lost, margins by lane, volumes by customer, transit performance by carrier, exceptions by trade. Very little of it ever becomes a decision. The data sits scattered across the TMS, spreadsheets, and inboxes — and pulling a management report means someone spends their Friday exporting, cleaning, and pasting.

The result is a business run on gut feel and lagging summaries. Which customers are quietly shrinking? Which lane is bleeding margin? Which agent's quotes never get answered? The answers exist in the data. Nobody has time to go find them.

Zavin's Reports & Analytics module is built to close that gap: reporting that runs itself, on data the platform captured itself — and analysis written for you, not left as homework.

Hundreds of Filter Combinations, One Report Builder

Freight reporting fails when the tool can only answer the questions its vendor predicted. Zavin's report builder supports hundreds of filter combinations across the platform's data — so the report you actually need is a configuration, not a feature request. Operations, sales, and management each get their own views of the same underlying records, built in minutes and refined as the questions evolve — without exporting anything to a spreadsheet.

Slice the business the way you think about it:

• •By lane and trade — Shanghai–Rotterdam ocean exports, transatlantic air imports, cross-trades.
• •By mode and product — FCL, LCL, air, road; HBL versus co-loaded; AWB volumes by carrier.
• •By commercial dimension — customer, salesperson, quote outcome, margin band, Incoterm.
• •By operations — carrier performance, milestone delays, documents outstanding, exceptions by branch.
• •By organization — branch, country, department, or the whole company in one view.
• •By time — this week against last, quarter against quarter, validity periods, ready dates.

Every Report Arrives With an AI-Written Analysis

A dashboard shows you numbers. It doesn't tell you which number matters. That last step — reading the chart, spotting the anomaly, connecting it to what's happening in the business — has always been left to whoever receives the report, which is exactly why most reports go unread.

Zavin does the reading for you. Every scheduled report is delivered with an AI-written analysis: a plain-language narrative of what moved, what stands out against the previous period, and what deserves a closer look. If quote volume on a lane jumped while the win rate slipped, the analysis says so — and points at where in the data to dig.

The difference in practice is who does the interpreting. Raw dashboards make every recipient an analyst. An AI-written analysis makes every recipient informed — and reserves human attention for the decision, not the deciphering.

Scheduled Reports That Run the Monday Meeting

Any report you can build, you can schedule. Weekly sales pipeline to the commercial team, daily exceptions to operations, monthly margin by branch to management — each delivered automatically, each with its AI-written analysis attached, so the Monday meeting starts from the same understanding instead of starting with a data pull.

Custom reports work the same way. Build a one-off view for a customer QBR or a carrier negotiation, save it, and rerun or schedule it whenever it's needed. Reports go where your team works — no logging into a separate BI tool to find out how the business is doing.

Scheduling turns reporting from an event into an operating rhythm. Instead of someone compiling figures once a problem is already visible, the numbers arrive on cadence — and the AI-written analysis flags the drift while it is still small. Exceptions surface on Tuesday, not at the quarter's post-mortem, and the conversation shifts from what happened to what the team is doing about it.

Better Reports Because the Data Is Captured at the Source

Most freight analytics fail before the report is ever built, because the underlying data was typed in by hand — late, abbreviated, or not at all. When a TMS depends on operators re-keying emails, the reporting layer inherits every shortcut: missing quote outcomes, blank reference fields, shipments created days after the booking.

Zavin's data is different because of how it's captured. The email core turns inbound mail into structured records the moment it arrives: RFQs become quotes with lanes and Incoterms, booking confirmations become shipments with zero manual data entry, rate sheets become database entries with validities. Nothing depends on someone remembering to re-type it.

That's the quiet advantage of reporting inside an AI operating system: the reports are only as good as the data, and the data was never touched by a tired human at the end of a long day.

Scoped by Role, Branch, and Country

Company-wide analytics can't mean company-wide exposure. Zavin applies field-level access control across every object, branch, and country — and reports inherit those rules automatically. A branch manager's report covers their branch. A salesperson sees their own pipeline, not their colleague's. Margin and buy-rate fields appear only for roles allowed to see them.

Scoping is enforced at the data layer, not the report template, so the same scheduled report can go to the whole management team and render differently for each recipient's permissions. Report access and delivery are logged, giving administrators a clear record of who receives which numbers.

Connected to Every Module in the Platform

Reports & Analytics has no data of its own — and that's the point. It reads directly from the records the other modules create: quotes and win rates from Pricing & Quote Automation, job files and milestones from Shipment Management, lane costs and validities from Rate Intelligence, customer activity from the CRM — all of it originating from the email core that feeds the entire platform.

Because every module writes to the same structured layer, a report can cross boundaries no point tool can: quote win rate by lane against the rates that priced those quotes, or customer email volume against shipment volume to spot accounts that ask a lot and ship a little. That cross-module view is where the interesting answers live — the ones neither a TMS export nor a standalone dashboard could produce.

Why Legacy TMS Reporting and BI Tools Fall Short

Legacy TMS reporting is a set of fixed exports over whatever operators managed to type in. The questions are predetermined, the data is patchy, and anything custom becomes a vendor ticket or a spreadsheet ritual. The email history — where most commercial signals live — isn't in the reports because it was never in the system.

Generic BI tools solve a different problem. They can chart anything, but only after someone builds pipelines, cleans the data, and maintains the dashboards — a standing analytics project most forwarders can't staff. And even then, the output is a dashboard that still needs a human to interpret it.

Zavin collapses that stack: the operating system captures clean data as a by-product of doing the work, the report builder queries it directly, and the AI writes the interpretation. No pipeline project, no dashboard graveyard.

Live in Under 14 Days

Reporting deploys with the platform — no data warehouse build, no migration, no IT project. As soon as your inboxes are connected and traffic flows, the data layer starts filling, and most teams are live in under 14 days. First reports typically cover quotes, shipments, and exceptions, with depth growing as history accumulates.

Because Zavin works alongside CargoWise, Magaya, and other systems, you don't have to replace your TMS to get modern analytics. Many teams start here precisely because reporting is the fastest place to feel the difference: the first scheduled Monday report, delivered with an AI-written analysis, tends to settle the argument.