Freight Rate Database Software That Builds Itself

Your Best Rates Are Trapped in Personal Inboxes

Ask a forwarding operation where its rates live and the honest answer is: everywhere and nowhere. Carrier rate sheets land in the pricing manager's inbox. A partner's spot quote for Shanghai to Jebel Ali sits in a sales rep's thread. An air rate to Frankfurt lives in an Excel attachment someone forwarded in March. The company paid for all of this knowledge — and doesn't own any of it.

The cost shows up every time an RFQ arrives. Someone searches their inbox, asks around on chat, re-requests a rate the company already has, or quotes from memory. When the person who "knows the lane" is on leave or resigns, the rates leave with them.

Zavin closes that leak at the source. Because the platform reads company email as its core function, every rate that arrives — in anyone's inbox — is parsed and stored in one company-wide rate database. Your rate database builds itself as a side effect of reading the mail.

How AI Turns a Week of Rate Emails Into a Live Database

Rate emails pour into a forwarding company all week, in every format carriers and agents can invent: PDF rate sheets, Excel attachments, tables pasted into email bodies, one-line spot offers buried in a reply. No pricing team can keep up with manually re-keying all of it — which is exactly why most rate databases go stale.

Zavin parses each of these formats as it arrives:

• •Structured rate sheets — carrier PDFs and Excel files are read table by table, including surcharges, free time, and routing notes.
• •Partner quotes — an agent's emailed offer for a lane becomes a stored buy rate with its validity window attached.
• •Spot offers — a one-line rate in a reply thread is recognized, extracted, and filed like any formal sheet.
• •Amendments — GRIs, surcharge updates, and revised sheets update the existing lane records instead of piling up as duplicates.

From Personal Inbox to Company Asset

The shift is bigger than convenience — it is a change in who owns the knowledge. When rates are parsed automatically from every connected mailbox, a rate received by one salesperson in one branch becomes instantly searchable by the whole company: by lane, carrier, mode, equipment, validity, and source.

That means the pricing desk in Rotterdam can quote using the buy rate an agent sent to a colleague in Singapore overnight. It means new hires inherit the company's full rate history on day one instead of building a private stash for a year. And it means resignations stop being rate-database extinction events.

Access is still governed, not open-ended: field-level access control across every object, branch, and country decides who can see which rates, margins, and sources — so company-wide does not mean uncontrolled.

Validity, Expiry, and Rate Hygiene

A rate database is only trustworthy if it knows what is still true. Every parsed rate in Zavin carries its validity window, and the database treats that window as law: expiring rates are flagged before they lapse, expired rates fall out of quoting automatically, and superseded sheets replace their predecessors instead of sitting beside them.

That hygiene is what separates a live database from a folder of PDFs. When the quote engine pulls a buy rate, it pulls a rate that is valid today, for that equipment, on that lane — not the newest attachment someone could find. And when no valid rate exists, the system says so and triggers a fresh rate request rather than quoting on a dead number.

Ocean, Air, and Everything on the Lane

Ocean and air rates fail differently, so they are parsed differently. Ocean rates are modeled around equipment and routing: FCL by container type, LCL by weight-or-measure, port pairs like Shanghai to Jebel Ali or Nhava Sheva to Rotterdam, with THC, BAF, and free time captured as line items rather than mashed into one number.

Air rates are modeled around chargeable weight: per-kilo breaks, minimums, fuel and security surcharges, and airport pairs on the AWB. A rate that looks cheap at one weight break and terrible at another is stored so the quote engine can see both.

Incoterms context is preserved too — a CIF-basis partner quote and an FOB-basis carrier rate are not interchangeable, and the database keeps them distinct so nobody quotes apples against oranges.

The Database That Feeds Your Quotes

Rate Intelligence is not a filing cabinet — it is the fuel line of the platform. AI Email Automation, the core module, is what feeds it: every inbound message is read, and the rates inside are routed here. Pricing & Quote Automation is what drinks from it: when an RFQ arrives, the quote engine prices it from this database, which is how an RFQ email becomes a sent quote in under 30 seconds when rates are on file.

The loop closes on its own. Rate requests sent out during quoting come back as emails; those replies are parsed into the database; the next RFQ on that lane is priced instantly. The more your company quotes, the better its rate coverage gets — without anyone maintaining anything.

Why a TMS Rate Module Stays Empty

Nearly every legacy TMS has a rate management module. Nearly every one of them is empty, stale, or half-maintained — and the reason is structural, not lazy staff. A TMS rate module depends on humans re-keying or uploading rates that arrive by email, which means it decays the moment the team gets busy. The database is always one hiring gap away from being fiction.

Point rate-management tools improve the storage but not the feeding: someone still has to put the rates in. Zavin inverts the model. Because the platform already reads every company inbox — 80% of freight forwarding runs on email — the rates are captured where they arrive, automatically, whether or not anyone remembers to file them. The database stays alive because filling it requires no behavior change at all.

Control, Approval, and a Full Audit Trail

Automation never means the pricing team loses the pen. You decide which parsed rates go straight into the quoting pool and which need a pricing manager's review first — for instance, auto-accepting rates from contracted carriers while holding new-partner quotes for approval.

Every rate in the database carries its provenance: the source email, the sender, the parse date, what was extracted, and every edit or approval since. If a quote ever raises a question, you can walk from the sell rate back to the original carrier email in seconds. That audit trail, combined with field-level access control by role, branch, and country, keeps a self-building database defensible in front of any customer, auditor, or carrier.

Live in Under 14 Days — No Rate Migration Project

Because the database fills itself from live email, there is no migration project and no historical clean-up to fund. Connect your mailboxes, set your approval and visibility rules, and the database starts accumulating from the first day — every incoming sheet, quote, and spot offer parsed as it lands. Most teams are live in under 14 days.

Zavin works alongside CargoWise, Magaya, and your existing TMS, so your system of record stays exactly where it is. The difference is that the next time someone asks "do we have a rate for this lane?", the answer comes from a database instead of a colleague's memory.