Running CORVI? Keep it, or move on.
You can keep the system you run today and add FreighAI around it, or move on from it and let FreighAI be your main system. Start with pricing and operations either way, and add the rest when you are ready.
CORVI is the Freight Forwarding Management System sold by Kale Logistics Solutions. Kale describes it as booking, documentation, billing and operational coordination in one platform. Most teams keep it and put FreighAI around the email. Some decide the file itself should move. This page covers both.
Every email your company receives is read, understood and turned into a task for the right person, with the answer already drafted. Your team approves. Nobody lives in the inbox any more.
- 01There are two ways in, and this page covers both. Keep CORVI and add FreighAI around it, or move on from CORVI and let FreighAI be your main system.
- 02Most teams start with the first. CORVI holds the file: booking requests for ocean, air, rail and road, job orders, bills of lading and air waybills, milestone tracking, warehousing, invoicing, vendor payment, customs filing and reports.
- 03The same supplier runs the rails around you, which is rare. Kale publishes Airport Cargo Community Systems, Port Community Systems, Digital Trade Corridors, freezone management, CANOPUS and manifest filing for IGM and EGM. The regulated half of your operation already has an owner, and FreighAI touches none of it.
- 04Kale publishes AI, and this page says so first. The CORVI catalog names AI/ML and optical character recognition among its technologies, and Kale's AI programme is written about gate congestion, slot allocation, cargo movement, air routes and vessel calls. What that AI does inside a forwarder's CORVI file is not described in CORVI’s published material, checked September 2026.
- 05The mailbox is what is left. Watching your company mailboxes, drafting the customer reply for approval, chasing your own agents, and reading a carrier bill back to its job are each not described in CORVI’s published material, checked September 2026. What Kale describes is outbound: e-mail alerts, and alert sharing when a shipment arrives.
- 06FreighAI works those mailboxes so your people do not have to. What lands on a desk is a written task with a name on it. No CORVI connector exists and none is implied below. We scope the first workflow, integration requirements and implementation plan with your team.
CORVI already carries the file itself
For a team on CORVI, most of the operating record may already sit in one place. Kale's catalog describes a sales module, and central pricing holding vendor rates, selling rates, customer and enquiry contracts and quotations. Operations covers import and export booking requests for ocean, air, rail and road, job orders, bills of lading and air waybills, milestone tracking, warehousing and workflow approval. Finance covers invoicing, vendor payment and tax compliance, with ready integration to SAP, Microsoft Navision and Tally.
Its integration module reaches customs across the world and transmits shipment and manifest data to shipping lines, airlines and overseas agents. Its portal lets customers send enquiries, view quotations and bookings and approve documents.
Then there is a second half, and this is where a CORVI team differs from anyone else reading these pages. The company that sells you the system also runs the community rails your cargo passes through. Kale publishes Airport Cargo Community Systems, Port Community Systems, Digital Trade Corridors and freezone management, sells CANOPUS as a separate customs clearance product for ICEGATE filing, and publishes manifest filing for IGM and EGM. So the regulated, connected part of your operation is already somebody's job, and it is not ours.
Now look at the part of the day that reaches CORVI only when a person carries it there. An enquiry lands in pricing@ with a packing list and no gross weight, and somebody writes back to ask. Somebody emails three overseas agents for a lane you do not hold, and two never answer. Somebody builds the quote, follows it up, and replies when the price is called too high. An arrival notice lands in operations@, and a carrier bill in accounts@ to be matched before finance pays it.
CORVI is where the record ends up. The mailbox is where that work happens. Take your own week:
- Which enquiries and rate replies arrive before anything exists in CORVI?
- Which chasers depend on somebody remembering on a Friday?
- Which of your customers write to you instead of logging into the portal?
Enquiries, agent rate replies, arrival notices and carrier bills arrive here first.
Reads the thread, chases the agent, drafts the answer and hands a written task to the person who owns it.
Job orders, documents, milestones, warehousing, invoicing, customs filing, carrier and agent messaging, the portal, and the community systems.
What changes once FreighAI is in place?
FreighAI takes over those mailboxes. It watches every company mailbox, pricing, operations, tracking and accounts, and follows each conversation from start to finish. It works out what each email is and what it needs, then takes the action that message calls for. Follow-ups, chasers and reminders happen on their own, on the same conversation. Your people work in FreighAI, not in the inbox.
The email is only the start. The real time goes on what comes after it. Find the rate on the carrier’s site. Check the tracking in another tab. Open the TMS for the job. Look up what you charged this customer last time. Forward it to operations and wait. Chase the agent, or forget to. FreighAI does all of that itself. It pulls your rate cards, checks the carrier, looks up the customer’s history, reads the shipment status, and talks to your TMS or accounting system. It chases what has not come back. It passes the work from pricing to operations to accounts, with the email and everything it found attached. Nobody forwards it. Nobody re-keys it. Nobody asks for an update. Then it puts the finished piece in front of the right person, with the reply already written.
Your people work in FreighAI. Not in the inbox. Not in five browser tabs. CORVI keeps the file.
On a CORVI desk, that comes down to four things a person stops doing:
- Spots what is missing in an enquiry and drafts the email asking for it.
- Emails all your agents for a lane in one go, with the route and charge lines filled in, then chases the ones who do not reply.
- When the customer pushes back on price, a counter-offer is drafted and waits for approval.
- Reads a carrier bill and matches every airway bill back to its job, checking line by line before it is booked.
It happens on the thread, before the job order exists. Chasing, tracking checks, quote expiry and follow-ups run on their own. Nobody has to remember.
need DHL quote Gurugram → Ajman, 72kg, by Friday. express.
packing list attached. urgent pls 🙏
Pls quote for shipment as below. Confirmed pkg dims attached, IEC docs to follow…
The enquiry, before CORVI has heard of it.
An enquiry arrives in pricing@ with a packing list and a detail missing. Nothing exists in CORVI yet, and nothing will until a person types it in. This is that queue after FreighAI has read it, with the work behind each one already done.
- Read, not just sortedWorks out what each email is and what it needs, then takes the action that message calls for.
- Any attachmentReads PDF, Excel, Word, forwarded email, WhatsApp messages, photos and scans.
- Your team decidesYour team approves every reply before it sends.
Keep CORVI, or move on.
You can keep the system you run today and add FreighAI around it, or move on from it and let FreighAI be your main system. Start with pricing and operations either way, and add the rest when you are ready.
Keep CORVI. Add FreighAI around it.
This is the door most CORVI teams take, and the rest of this page argues it. CORVI keeps the file and Kale keeps the rails. FreighAI works the mail that reaches CORVI only when a person carries it there.
- CORVI keeps the job orders, the documents, the milestones, the invoicing and the reports.
- The customs filing and the Kale community rails are untouched. FreighAI never sits on one.
- FreighAI takes the mail that arrives first. The enquiry with no weight, the agent’s rate reply, the carrier bill.
- Your team approves every reply. The agreed hand-off carries the job order into CORVI.
Move on from CORVI. FreighAI becomes your main system.
The other door. You work in FreighAI and let CORVI go. Start with pricing and operations. The customs filing and the Kale community rails stay where they are either way.
- Enquiries and the quotes that follow them.
- Job orders, once a quote is won.
- Tracking replies to customers who email you.
- Carrier bills, matched line by line.
- Payment follow-ups and chasers.
- Your accounts. Finance runs inside FreighAI.
- Customs filing and the community rails. FreighAI files nothing and never sits on a community system.
- The warehouse. Binsy, the FreighAI warehouse product, runs together with FreighAI today.
- Carrier and agent messaging. Shipment and manifest data still has to reach the lines, the airlines and your overseas agents.
- A customer portal, if yours log in for quotations, bookings and invoices rather than emailing you.
- Statutory books and tax compliance, and the MIS and BI reports.
- How long have you had CORVI?
A file your team has built for years is worth keeping. One bought recently and still being set up is a different decision.
- Does your team work in CORVI, or around it?
Watch one ordinary morning. If the day happens in the mailbox and CORVI gets typed up afterwards, cost the second door.
- What would you lose?
List what only CORVI holds: the customs filing, the carrier and agent messaging, the warehouse, the portal. Each one needs a home first.
- What do your contract and your data say?
Ask Kale when the agreement renews and how you get your own history out. Ask. Do not assume.
On its own, FreighAI runs your enquiries, quotes, jobs, tracking replies, carrier bills, payment follow-ups and your accounts. FreighAI does not file customs declarations. It treats customs as a service provider or agent, and your team adds and updates the filing details by hand.
Which parts of FreighAI would a CORVI team use?
Quotation Agent
The enquiry arrives by email or WhatsApp, before a quotation exists anywhere. FreighAI spots what is missing in an enquiry and drafts the email asking for it. It emails all your agents for a lane in one go, with the route and charge lines filled in, then chases the ones who do not reply. When the customer pushes back on price, a counter-offer is drafted and waits for approval. Quotes expire on their own and can be revived if you want. CORVI's central pricing stays your rate and contract store.
Booking and Job Orders Agent
A won quote becomes a job on its own, fully filled in. A booking confirmation landing in operations@ becomes a task for whoever owns the thread, instead of being keyed in twice. What CORVI's job order needs from it is settled in the scope.
Tracking Agent
FreighAI answers “where is my cargo?” on the customer’s own thread, from carrier status, for approval. CORVI's portal already serves the customers who log in to check. This is for the ones who simply hit reply.
Invoice Reconciliation
FreighAI reads a carrier bill and matches every airway bill back to its job, checking line by line before it is booked. CORVI keeps invoicing, vendor payment, tax compliance and the accounting connection. Whether the matched result returns to CORVI is a technical scope decision.
Pick one. The enquiry that arrives by email is the usual starting point, because a CORVI team still does it entirely by hand.
What happens to one enquiry
Quotation is the first workflow here. The enquiry email reaches CORVI only after a person has read it and typed it in.
An enquiry arrives. FreighAI reads it, notices the weight is missing and asks for it. It pulls your rate cards, checks the carrier for a live rate, and emails your agents for the lanes you do not hold, then chases them until they reply. It drafts the quote with your margin rules and what that customer paid on that lane last time. Your pricer approves and it goes. It follows up. When the customer pushes back, the counter-offer is already drafted. When the quote is old, it expires. When it is won, the job is created.
Where the rate can be fetched without waiting on a person — a carrier API, a portal read in the background, or your own uploaded rate cards — a priced quote goes out in 10–15 minutes instead of 1–2 hours. That holds for ocean and air just as it does for express; the mode does not change it. Where a lane has to be priced by another agent or over the phone, the wait belongs to whoever is answering — not to the software. FreighAI still writes the RFQ, chases the reply, and turns whatever comes back into a priced, margin-checked quote the moment it lands.
What part of the approved result belongs in CORVI, and how it gets there, is decided in the scope. We scope the first workflow, integration requirements and implementation plan with your team.
need DHL quote Gurugram → Ajman, 72kg, by Friday. urgent pls 🙏
Hi Marco — DHL Express, AED 425 + AED 35 handling. ETA Thu·18:00, valid 24h. PDF attached.
- 01Enquiry emailInto pricing@, or by WhatsApp
- 02Reads itAsks for the gross weight nobody sent
- 03RatesYour rate cards, your agents emailed and chased
- 04Drafted quoteWritten against the thread it arrived on
- GATEYour pricer approves
- 06Follow-upAnd the counter-offer when the price is pushed back
- 07Central pricingVendor rates, selling rates and contracts
- 08Job orderCreated in CORVI on the agreed hand-off
At Infinity Logistics, average response time fell from more than 60 minutes to about 15 minutes, and the win rate rose from 35% to 73%. One customer’s attributed result, not an average and not a promise.
What stays in CORVI, what FreighAI adds and what must be scoped?
| Area | Stays in CORVI | FreighAI adds | Decision required |
|---|---|---|---|
| The forwarding file | Booking requests for ocean, air, rail and road, and job order generation and confirmation | A won quote becomes a job on its own, and the agreed hand-off carries it to CORVI | Which record and reference anchor the first workflow? |
| Rates, quotations and contracts | Central pricing: vendor rates, selling rates, customer and enquiry contracts, quotations | Pulls your rate cards, then emails all your agents for a lane in one go and chases the ones who do not reply | Which lanes are priced from a card, and which from an agent? |
| The enquiry thread and its follow-up | The quotation record, customer approval and workflow approval inside the file | Reads the enquiry, asks for what is missing, drafts the quote and the counter-offer, and follows up on the same thread. Reading an enquiry email into a quotation and drafting a counter-offer are not described in CORVI’s published material, checked September 2026 | What starts the workflow, and which chasers move? |
| Customs, community and regulatory rails | In-built customs filing and integration with customs worldwide, CANOPUS for ICEGATE clearance, the airport and port community systems, Digital Trade Corridors, freezone management and manifest filing | Nothing at all. Filing, duty lookup and the community rails stay where they are | Which of these must the first workflow respect? |
| Carrier and agent messaging | Integration with shipping lines, airlines and overseas agents to transmit shipment and manifest data, plus EDI | Emails your own agents for a price on a lane you do not hold, which is a different exchange from a manifest. That request and its chase are not described in CORVI’s published material, checked September 2026 | Which agents are on EDI, and which are still on email? |
| Documents, tracking and the portal | Bills of lading and air waybills, master and house documents, e-Docket sharing with approvals, milestone tracking, and a portal for quotations, bookings and invoices | Reads PDF, Excel, Word, forwarded email, WhatsApp messages, photos and scans. Tracking answers go out on the customer's own thread, for approval, for the customers who never log in | Which documents may FreighAI open, and who approves a reply? |
| Invoicing, warehousing and books | Customer invoicing, vendor payment, tax compliance, integration to SAP, Navision and Tally, warehouse operations, and the MIS and BI reports | Reads the carrier bill and matches every airway bill back to its job, checking line by line before it is booked. The warehouse and the reporting stay put | Does the matched result return to CORVI, and to which module? |
| AI in each system | AI/ML and optical character recognition are named among CORVI's technologies, and Kale runs an AI programme written about gate congestion, slot allocation, cargo movement and vessel calls for airports, ports, freight forwarders, carriers, terminal operators and regulatory authorities. What AI does inside a forwarder's CORVI file is not described in CORVI’s published material, checked September 2026 | Reads your mailboxes, does the work behind each thread, and hands a written task to a named person | Ask both suppliers to run their AI on one of your own email threads. |
| Hand-offs between departments | The CORVI screens pricing, operations and accounts each work in today | Work passes from pricing to operations to accounts with the email and everything it found attached. Nobody forwards it, re-keys it or asks for an update. | Which hand-off comes first? |
| What is published, and what gets scoped | The standard finance API and the integrations Kale publishes for accounting systems, airlines, agents, customs and carriers. A per-user model with flexible packages, and no price figure. A CORVI documentation or help centre is not described in CORVI’s published material, checked September 2026 | No CORVI connector is live and none is claimed. No price figure or fixed pilot length is published here either. We scope the first workflow, integration requirements and implementation plan with your team. | Which objects, which direction, whose credentials? |
- The forwarding file
- Stays in CORVI
- Booking requests for ocean, air, rail and road, and job order generation and confirmation
- FreighAI adds
- A won quote becomes a job on its own, and the agreed hand-off carries it to CORVI
- Decision required
- Which record and reference anchor the first workflow?
- Rates, quotations and contracts
- Stays in CORVI
- Central pricing: vendor rates, selling rates, customer and enquiry contracts, quotations
- FreighAI adds
- Pulls your rate cards, then emails all your agents for a lane in one go and chases the ones who do not reply
- Decision required
- Which lanes are priced from a card, and which from an agent?
- The enquiry thread and its follow-up
- Stays in CORVI
- The quotation record, customer approval and workflow approval inside the file
- FreighAI adds
- Reads the enquiry, asks for what is missing, drafts the quote and the counter-offer, and follows up on the same thread. Reading an enquiry email into a quotation and drafting a counter-offer are not described in CORVI’s published material, checked September 2026
- Decision required
- What starts the workflow, and which chasers move?
- Customs, community and regulatory rails
- Stays in CORVI
- In-built customs filing and integration with customs worldwide, CANOPUS for ICEGATE clearance, the airport and port community systems, Digital Trade Corridors, freezone management and manifest filing
- FreighAI adds
- Nothing at all. Filing, duty lookup and the community rails stay where they are
- Decision required
- Which of these must the first workflow respect?
- Carrier and agent messaging
- Stays in CORVI
- Integration with shipping lines, airlines and overseas agents to transmit shipment and manifest data, plus EDI
- FreighAI adds
- Emails your own agents for a price on a lane you do not hold, which is a different exchange from a manifest. That request and its chase are not described in CORVI’s published material, checked September 2026
- Decision required
- Which agents are on EDI, and which are still on email?
- Documents, tracking and the portal
- Stays in CORVI
- Bills of lading and air waybills, master and house documents, e-Docket sharing with approvals, milestone tracking, and a portal for quotations, bookings and invoices
- FreighAI adds
- Reads PDF, Excel, Word, forwarded email, WhatsApp messages, photos and scans. Tracking answers go out on the customer's own thread, for approval, for the customers who never log in
- Decision required
- Which documents may FreighAI open, and who approves a reply?
- Invoicing, warehousing and books
- Stays in CORVI
- Customer invoicing, vendor payment, tax compliance, integration to SAP, Navision and Tally, warehouse operations, and the MIS and BI reports
- FreighAI adds
- Reads the carrier bill and matches every airway bill back to its job, checking line by line before it is booked. The warehouse and the reporting stay put
- Decision required
- Does the matched result return to CORVI, and to which module?
- AI in each system
- Stays in CORVI
- AI/ML and optical character recognition are named among CORVI's technologies, and Kale runs an AI programme written about gate congestion, slot allocation, cargo movement and vessel calls for airports, ports, freight forwarders, carriers, terminal operators and regulatory authorities. What AI does inside a forwarder's CORVI file is not described in CORVI’s published material, checked September 2026
- FreighAI adds
- Reads your mailboxes, does the work behind each thread, and hands a written task to a named person
- Decision required
- Ask both suppliers to run their AI on one of your own email threads.
- Hand-offs between departments
- Stays in CORVI
- The CORVI screens pricing, operations and accounts each work in today
- FreighAI adds
- Work passes from pricing to operations to accounts with the email and everything it found attached. Nobody forwards it, re-keys it or asks for an update.
- Decision required
- Which hand-off comes first?
- What is published, and what gets scoped
- Stays in CORVI
- The standard finance API and the integrations Kale publishes for accounting systems, airlines, agents, customs and carriers. A per-user model with flexible packages, and no price figure. A CORVI documentation or help centre is not described in CORVI’s published material, checked September 2026
- FreighAI adds
- No CORVI connector is live and none is claimed. No price figure or fixed pilot length is published here either. We scope the first workflow, integration requirements and implementation plan with your team.
- Decision required
- Which objects, which direction, whose credentials?
Read this as the agenda for a scoping conversation, not a list of CORVI connections.
The objections we hear most
“Kale already does AI. Why would we need this?”
Kale does, and this page names it before answering. The CORVI catalog lists AI/ML and optical character recognition among its technologies, and Kale runs a separate AI programme it describes for gate congestion, slot allocation, cargo movement tracking, air routes and vessel calls. Those are real subjects, and none of them is a forwarder's mailbox. What AI does inside your CORVI file is not described in CORVI’s published material, checked September 2026. Ask Kale that question, and ask us the same one.
“Will this duplicate what we already pay for?”
It would, if the first workflow landed on something CORVI already handles well. So the scope has to start where a person still reads an email and types: the enquiry with the weight missing, the agent who has not come back, the answer nobody has written yet.
“Are you asking us to move off CORVI?”
Only if you want to. You can keep the system you run today and add FreighAI around it, or move on from it and let FreighAI be your main system. Start with pricing and operations either way, and add the rest when you are ready. On its own, FreighAI runs your enquiries, quotes, jobs, tracking replies, carrier bills, payment follow-ups and your accounts. The customs filing and the Kale community rails stay where they are on either door, and the two doors above set out how to decide.
“Is there a finished CORVI connector?”
No, and none is implied anywhere on this page. What FreighAI reads from or returns to CORVI is decided for the workflow you choose, with the objects, the direction and the limits written down. We scope the first workflow, integration requirements and implementation plan with your team.
“Our software vendor also runs the airport and port systems. Does that change anything?”
It changes what you should be careful not to buy twice. The community systems, CANOPUS and the manifest filing stay exactly where they are, on either door. FreighAI never sits on a community rail and files nothing with anybody. It works the other half: your email.
Common questions
Can FreighAI be my main system instead of CORVI?
Yes, if that is what you want. On its own, FreighAI runs your enquiries, quotes, jobs, tracking replies, carrier bills, payment follow-ups and your accounts. FreighAI does not file customs declarations. It treats customs as a service provider or agent, and your team adds and updates the filing details by hand. Binsy, the FreighAI warehouse product, runs together with FreighAI today. The community rails, the carrier and agent messaging and the portal are things CORVI holds today, so give each one a home before you move.
Do we have to move data out of CORVI?
Not automatically. A first workflow may need only the context it has to reason about, and it can run alongside CORVI without moving records. Anything that does have to move is named and justified during the scope.
Can FreighAI write into CORVI?
That comes from the confirmed scope for the workflow you choose. Kale publishes a standard finance API and integrations to accounting systems, airlines, agents and customs, and that is where the conversation starts. A published API is not a finished connection.
Which workflow should a CORVI team start with?
Start where work arrives by email or WhatsApp, passes between people, or waits for somebody to remember. The enquiry is the usual candidate.
What about CORVI's own email alerts?
They stay. Kale describes e-mail alerts among CORVI's utilities and alert sharing inside the organisation when a shipment arrives. That is CORVI telling your own people something. FreighAI runs the other direction: reading what your customers, agents and carriers send in. Watching your company mailboxes and reading what arrives is not described in CORVI’s published material, checked September 2026.
Does a person still check every reply before it goes?
Yes. Your team approves every reply before it sends. Your team approves. They do not compose, forward, file or chase. The reply goes out in their name. Chasing, tracking checks, quote expiry and follow-ups run on their own. Nobody has to remember. You set the supervision rules for each workflow.
Is CORVI the same thing as Kale Logistics?
CORVI is the product. Kale Logistics Solutions is the company that sells it. Kale's product menu lists it as the Freight Forwarding Management System, CORVI, under enterprise solutions. This page uses the name Kale uses today and treats Kale Logistics, Kale FFMS and CORVI LTE as aliases.
- Kale Logistics Solutions — Freight Forwarding Management System (CORVI): booking, documentation, billing and operational coordination in one platform, and the catalog linked from the pageverified 2026-09-03
- The CORVI catalog, linked from the product page — the sales and pricing, finance, operations, integration and reports modules, the utilities and technologies bands, the portal scope, and the per-user model. Undated by the publisherverified 2026-09-03
- Kale — Products: the community platforms, the enterprise solutions including CANOPUS and CORVI, and value added services including e-AWB, e-DO, e-CO and manifest filing for IGM and EGMverified 2026-09-03
- Kale — home: the one digital platform framing, the company's AI framing, and the CORVI one-line descriptionverified 2026-09-03
- Kale — Company: the community platforms and the development centres, including a dedicated AI centreverified 2026-09-03
- AI@Kale — the AI product site: turnaround, gate congestion and slot allocation, cargo movement tracking, air route and vessel call optimisation. A forwarder's mailbox is not among the described subjectsverified 2026-09-03
- CANOPUS — Customs Clearance Management System: single-window automation for ICEGATE filing, sold alongside CORVIverified 2026-09-03
- Kale — a CORVI case study for a freight forwarder: the customs and cargo community interface, rate management, the warehouse module, e-Docket sharing, ERP integration and email alerts on arrival. Undated by the publisherverified 2026-09-03
- Infinity Logistics customer reference, 15 May 2026 — response time and win rateverified 2026-08-31
Kale's client and country counts, the catalog's outcome percentages and Kale's superlatives for CORVI are not repeated. Four older web addresses carrying the CORVI name no longer resolve and are cited nowhere. Any gap noted here describes only what Kale had published about CORVI on 3 September 2026.
Bring one thread from your CORVI week
Pick the enquiry that arrived on WhatsApp before CORVI had a job for it, or the carrier bill that sat in accounts@ until somebody matched it. We will show the task your person would have approved, with the community rails where they are.