Most of a forwarding desk's day starts in the inbox. The value of a forwarder's software is decided by how much of that inbox it handles before a human touches it, and by what it puts in front of the manager afterwards.
This guide is short on the problem and long on the payoff: what automation-first freight forwarding software does on the desk, what it delivers to the manager, how to evaluate it, and where Zavin — our product — fits.
Key takeaways
- Freight forwarding software has six jobs — record, quote, CRM, rates, documents, tracking. The value is in how many of them run without re-typing.
- Automation-first software reads the RFQ, prices from a company-owned rate repository, and stages the shipment for approval. Teams doing this have cut RFQ processing time by up to 85%.
- Every automated stage writes to the same records, so win rate by lane, partner turnaround and margin by charge arrive as a by-product — not a separate BI project.
- The manager's payoff is decisions: reprice a losing lane, replace a slow partner, chase a quiet account, close a leaking charge — from a dashboard, not an export.
- It runs alongside CargoWise or whichever system of record you already have. Nothing migrates; go-live is under 14 days.
What freight forwarding software should do in 2026
Six jobs: the system of record (job file, bills, parties, milestones), quoting, CRM, rate management, documents (HBL, MBL, pre-alerts, arrival notices, VGM), and tracking and customer service.
Every vendor lists all six. The question that separates them is how many happen before an operator types. Record-first software — CargoWise, Magaya and their peers — stores the job once the work is done. Automation-first software starts at the email: it reads, prices, drafts and stages, then the operator approves. The two coexist; most forwarders adopting automation keep their system of record and add the layer in front of it.
What automation delivers on the desk
Six situations every forwarder recognises, and what changes.
The RFQ that lands at 11pm
It is read on arrival: ports, equipment, Incoterm, weight, ready date lifted from the email and its attachments. If rates are on file, a margin-aware, branded quote is ready for approval in under 30 seconds. The operator's first act in the morning is to approve it, not to re-type it.
The rate sheet stuck in one inbox
A carrier tariff emailed to one desk is parsed into a central rate repository with validity and carrier, and tariff templates are built from it. The Dubai desk prices tomorrow's RFQ from the rate that reached Karachi today.
The partner that goes quiet
Structured rate requests go to the right pricing contact at each partner office — the partner directory builds itself from every inbound email — and the system records how long each partner took to reply. Replies land on one cost sheet: buy, sell, transit, FX, inclusions, margin.
The booking that becomes a shipment file
Booking confirmation, shipping instructions and packing list are read into a master/house shipment draft. Where documents disagree, the contradiction is flagged, not overwritten. HBL, MBL, pre-alert, arrival notice, delivery order and VGM are generated from the record and packed into one outbound email.
"Where is my container?" and "please amend the consignee"
Routine inbound requests — tracking queries, document change requests, status questions — are handled from the inbox under the same approval control. Around 50% of routine email is handled end to end once the system is tuned.
The email in another language
Inbound mail is translated, long threads summarised, and a reply drafted and refined in the company's voice. The operator edits and sends.
What automation delivers to the manager
The records that ran the desk are the records the dashboards read. That is the part most software gets wrong — the numbers exist, but only after someone exports them. Here they are the by-product. Seven questions, answered without a spreadsheet.
Which lanes are we winning, and which are we losing?
Win rate by lane, account, branch and mode on a custom dashboard — built by the manager from hundreds of filter combinations, not requested from IT. Action: reprice the lane you keep losing on transit time, or stop chasing it.
Which partners are costing us deals?
Quote turnaround per partner, measured on every tender. Action: route the next RFQ to the office that answers in an hour, and take the numbers into the next commission negotiation.
Where is margin leaking?
Margin by lane, account and charge — cost against sell at the charge level, not a lump called freight. Action: tighten the pricing rule for the branch that keeps quoting under the floor; the override approval trail shows who did.
Which accounts are going quiet?
Quote volume and win rate per account over time, on a CRM built on freight objects — lanes, Incoterms, equipment, shipment history — rather than a contact list. Action: assign the follow-up before the account has finished moving to a competitor.
How did the month go — before Monday?
Reports built by the manager — tables, KPIs, charts, period comparisons — scheduled for delivery with an AI-written analysis: what moved, what stalled, where margin leaked, which data is missing. Action: the Monday meeting starts at the decision, not at the spreadsheet.
The question you would ask an analyst
Ask the copilot across every record and file — "what free time did we quote Globex on SHA–LAX?", "which Q3 quotes over $20k are still open?" — and get the answer with the record behind it. It can also make the change: adjust the quote, update the shipment, when asked and when permitted.
Who is allowed to see what?
Roles, hierarchy, multi-branch and multi-country partitions, down to field level. Dubai sees Dubai; head office sees the group; a trainee never sees group margin. Action: grow the team without growing the exposure.
Why the data compounds
Each stage writes to one set of records: the rate repository, the partner directory, the freight CRM, the shipment file. So every quote makes the next quote faster, every partner reply makes the next tender smarter, every shipment makes the month-end truer. The intelligence is not a module bolted on afterwards. It is what the automation leaves behind.
What still needs a human
The operator approves the quote, confirms the booking, handles the exception and owns the customer. Expensive actions pass through an approval queue that shows what was extracted, what was drafted, and why the system is confident. That is what makes automation acceptable to the person whose name is on the house bill.
How to evaluate freight forwarding software
Six tests to run in any demo. Bring your own ugliest RFQ.
- Does it read the email, or does someone re-type it? Send a real RFQ with a messy attachment and watch.
- Does it price, or does it template? Ask where the buy rate came from and whether margin was applied by rule.
- Where does a partner's emailed rate go after the deal? "It stays in the thread" means rates are not an asset in that system.
- Does the booking become a shipment, or a second data-entry job?
- Can a manager see win rate by lane without an export? If the answer involves Excel, the intelligence is not built in.
- Does it keep your system of record? If adoption means migrating off CargoWise or Magaya, you are buying a six-month project.
The landscape, honestly
The record-first platforms answer "where is the job and is it compliant." The automation layers answer "who is doing the reading, the pricing and the analysis."
- CargoWise (WiseTech) — the enterprise system of record. Deep, global, priced per transaction since the December 2025 Value Pack repricing. Automation arrives after the record exists.
- Magaya — mid-market TMS with integrated accounting. Strong record and finance; quoting and inbox automation are lighter.
- GoFreight — mid-market forwarding TMS, particularly strong with US forwarders; a full system of record with a modern interface.
- Descartes — enterprise logistics suite spanning customs, routing and forwarding; broad rather than desk-specific.
- Wisor — quoting and rate procurement, focused on pricing speed rather than the full shipment loop.
- Raft — automation of customs, accounts payable and back-office documents for larger forwarders.
- Zavin — an automation layer for the commercial desk — inbox, quoting, CRM, rates, shipments, documents, dashboards — run alongside the system of record.
Where Zavin fits
Disclosure: Zavin is our product; read this as a vendor's own scoping.
Zavin reads every inbound email, parses arriving tariffs into a company-wide rate repository, prices quotes from tariff templates and partner replies, and stages shipments and documents for approval. CRM, partner directory, dashboards, scheduled AI-analysed reports and a copilot that can read — and edit — every record sit on the same data, under field-level access control by branch and country.
It runs alongside CargoWise as the system of record, goes live in under 14 days because nothing migrates, and is priced publicly at $125 per seat per month plus usage-based AI processing, every module included. Pilot teams have seen quote win rates improve by six percentage points.
What it is not: a customs-filing engine, an accounting ledger, or a replacement for the TMS you already run.
See the platform, the quoting module, reports and dashboards, or pricing — or book a walkthrough on your own RFQs.