Quote-to-cash TMS for freight forwarders

From quote to cash, without typing it twice.

Tranvoro keeps the whole job on one record. The accepted quote becomes the shipment — with its cargo, routing, parties and charges. The shipment's charges become the invoice. The payment closes it out. One trail, from the first rate you send to the money in the bank.

The Tranvoro dashboard: active shipments, open receivables, a ready-to-invoice count, overdue tasks, and the shipments needing attention.
The operations dashboard, captured from a running Tranvoro instance. Demo data.

Tranvoro is pre-launch. The platform is built and running — we're now selecting a small number of forwarders as first pilots and working with them directly. No customer logos here, because we don't have any yet.

The problem

A shipment is one job. Your systems treat it as six.

Every handoff is a place where something gets retyped, a cost goes missing, or nobody can say what happened. Email and spreadsheets stop being the cheap option when the handoffs become the work.

  1. 01

    The quote gets retyped.

    You win the business, then someone rebuilds the whole thing as a shipment — cargo lines, containers, routing, parties, charges. Every retype is a chance to be wrong.

  2. 02

    Costs arrive after the fact.

    The agent's invoice lands three weeks later. By then "what did we make on that job?" is a research project.

  3. 03

    Documents live in an inbox.

    The B/L, the packing list, the commercial invoice — somewhere in a thread, in a version nobody can confirm is current.

  4. 04

    Billing is assembled by hand.

    Charges get copied into an invoice. Something gets billed twice, or not at all, and you find out at month end.

  5. 05

    The customer calls you for the status.

    Every update is a person stopping what they're doing to answer a question the system already knows the answer to.

None of these are missing features. They're seams — and the seams are where the margin goes.

How it works

One record, eight steps, no re-entry.

This is the whole workflow. Each step hands the last one's data forward — you don't rebuild it.

  1. Step 1 · Quote

    Build the rate offer, send it, get it approved.

    Build a quote with cargo, containers, routing legs and charge lines. Generate the PDF from your own template and send it. The customer opens a private approval link and accepts or rejects it — no account, no login. Every revision and status change is kept.

    A quote's Charges tab: charge lines with unit cost and sale price, quote status, and a profit summary showing revenue, cost, profit and margin.
    The approval page the customer opens: the quote reference, route, total, a charge breakdown, and Accept quote and Decline buttons.

    The quote you build, and the page your customer opens to accept it. Demo data.

  2. Step 2 · Convert to shipment

    Accepted becomes active. Nothing is retyped.

    Converting the quote creates the shipment and carries everything with it — cargo and packages, containers, routing legs, parties, milestones and charges. What you quoted is what you're now executing, and the two stay connected.

    An accepted quote, Detroit to Toronto, with the Convert action available in its header.
    The shipment created by that conversion, carrying the same route, customer, cargo, revenue, cost and margin across.

    One accepted quote, converted. The same numbers arrive on the shipment — nothing is retyped. Demo data.

  3. Step 3 · Run the shipment

    One workspace for the whole job.

    Overview, cargo, routing, schedule, milestones, parties, documents, customs, tracking, charges, communication, tasks and audit — all on the shipment, all in tabs. House and master shipments, containers and packages, multi-leg routing. Milestones show you what's late without you going looking.

    A shipment workspace: the full tab strip, milestone progress at seven of nine steps, open tasks with owners and due dates, and a validation panel listing what is still missing.
    One shipment, one workspace. Demo data.
  4. Step 4 · Documents

    Generated from your templates. Stored on the shipment.

    Build documents from templates that pull straight from shipment data — Tranvoro won't let you generate one that's missing required fields. Everything is stored privately against the shipment, and you choose exactly what the customer can see.

    The documents tab: stored documents listed with type, file, version, status, who uploaded them and when, above the required documents still missing.
    The generate-document dialog, its required-data panel marked two missing, with saving blocked until the shipper and consignee are set.

    Documents are stored on the shipment — and won't generate while required data is missing. Demo data.

  5. Step 5 · Charges and margin

    Revenue, cost and profit on the job itself.

    Receivables and payables sit side by side on the shipment, with tax and multi-currency handled where they happen. Prorate shared costs across shipments. Profit per job is a number you look up, not one you reconstruct at month end.

    A shipment's charges tab: revenue, cost and profit totals with margin, and cost lines billed in US dollars and euros, each converted to the shipment's base currency.
    Revenue, cost and margin on the job itself — in whichever currency the cost arrived in. Demo data.
  6. Step 6 · Invoice

    Bill from the charges. Not from a spreadsheet.

    Ready-to-invoice shows you which shipments have billable charges waiting. Generate the customer invoice from those charges, approve it, produce the PDF, send it. A charge can only be billed once — the system enforces it. Vendor invoices come in the same way: recorded, matched against the costs you expected, approved.

    The ready-to-invoice queue: a shipment with uninvoiced receivable charge lines and its uninvoiced amount, with an Invoice action on the row.
    The customer invoice generated from those charges, showing its lines, tax, totals, payment status and the draft, approved and posted trail.

    Billable charges become the invoice, and the approval trail comes with it. Demo data.

  7. Step 7 · Payment

    Allocate it, close it, watch the open amount fall.

    Record the payment and allocate it across the open invoices it settles. Open amounts come down, a fully settled invoice closes itself, and aging updates with it.

  8. Step 8 · Report

    Ask the obvious questions and get an answer.

    AR and AP aging. Uninvoiced shipments. Profit. Operational and sales reporting. All of it reads the same records your team has been working in all month — so the number on the report is the number in the shipment.

    The accounts-receivable aging report: current, 1 to 30, 31 to 60, 61 to 90 and 90-plus day buckets, with the open invoices behind them.
    The profit report: revenue, cost, profit and margin for each shipment, with shipments below the margin threshold flagged.

    Aging and per-shipment profit, read straight off the records the team worked in. Demo data.

Eight steps. One record. The only thing you enter twice is nothing.

Capabilities

What's in the box.

Everything listed here is shipped and running today. What isn't here is in the next section.

Operations

  • ShipmentsLifecycle, workspace, saved views, configurable columns and filters.
  • Cargo & containersPackages, dimensions, containers, house and master shipments.
  • Routing & milestonesMulti-leg routing, schedules, milestone templates, overdue flags, tracking.
  • QuotesBuild, PDF, send, customer approval, convert to shipment.
  • PartiesCustomers, vendors, carriers and agents with contacts, addresses and roles.
  • Tasks & notesWork and conversation attached to the shipment, not to someone's inbox.

Money

  • ChargesReceivables and payables, tax, multi-currency, prorating, per-shipment profit.
  • AR invoicingGenerate from charges, approve, PDF, send.
  • AP invoicesRecord vendor invoices, match them against expected costs, approve.
  • PaymentsAllocation across open invoices, updating open amounts, invoice status and aging.
  • ReportsAR/AP aging, uninvoiced, profit, operational and sales.

Customer-facing

  • Customer portalYour customer sees their shipments, progress, ETA and the documents you shared.
  • Document sharingDeliberate, per-document, private by default.
  • Quote approval linksThe customer approves without an account.
  • Notifications & email templatesIn-app notifications and configurable email templates; outbound email dispatch is not connected yet.

Control

  • Roles & branch accessPeople see the branches they work in.
  • Financial approvalApproving money is a separate grant from doing the work.
  • Audit logKey actions are recorded with who did what and when in an append-only audit log.
  • ImportsBring parties and shipments in from files rather than typing them.
  • AI-assisted intakeEmails and documents are classified and fields are extracted for human review before selected data is applied to an existing shipment.
The shipment list: saved views, filters, a search field, configurable columns, and per-row flags such as missing documents or ready to invoice.
Operations · the shipment list, with saved views and configurable columns. Demo data.
The customer portal: shipment reference and route, departure and estimated arrival dates, the carrier, a progress timeline, and the documents shared with the customer.
Customer-facing · what your customer sees, and only what you shared. Demo data.
The audit log filtered to financial events, each row showing when it happened, the entity, the action, the user and a summary of what changed.
Control · the append-only audit log, filtered to financial events. Demo data.
Roles and permissions: the role list with internal and external roles, and a permission matrix in which approving and posting money is a separate grant from doing the work.
Control · roles, branch access, and money approval as its own grant. Demo data.

Why this is different

All of the quote-to-cash workflow. None of the implementation project.

If you're on spreadsheets and email

How work changes if you are running on spreadsheets and email today
TodayWith Tranvoro
The quote gets rebuilt as a shipmentIt converts, with cargo, routing, parties and charges
Margin is reconstructed at month endMargin is on the shipment, in the currency it happened in
Documents live in a threadDocuments live on the job, generated from your templates
The customer emails you for statusThe customer opens the portal
Only the person who did it knows what happenedThe audit log knows

If you're on a large legacy suite

How work changes if you are running on a large legacy suite today
TodayWith Tranvoro
An implementation project measured in monthsSet up your tenant, import your parties, run a real shipment
Paying for modules built for global networksBuilt for the small-and-mid forwarder's actual workflow
Operations here, accounting somewhere elseCharges, invoices and payments on the same record
Change requests go through a queueFounder-led pilot; you talk to the people building it

If you need deep customs filing, EDI networks, warehouse management or country-by-country compliance, a large suite is the right answer and we'll tell you so.

Straight answers

What Tranvoro doesn't do yet.

Most software sites make you find this out on the call. Here it is up front.

  • No public API or webhooks.They're planned. They're not built. If your evaluation depends on them, we're not ready for you yet.
  • No customs filing.There's a customs tab on the shipment for status and data. It is not a filing engine and it doesn't connect to a customs authority.
  • No EDI.No carrier or partner EDI messaging.
  • No carrier rate feeds or rate marketplace.You bring your rates; Tranvoro isn't a rate shopping engine.
  • No automatic exchange-difference posting.Charges and invoices are multi-currency. But a payment is allocated at the amount you enter, so if the rate moved between invoicing and receipt, Tranvoro will not work the gain or loss out for you.
  • No accounting-system sync.Invoices, payments and reports live in Tranvoro. There's no automatic push to an external accounting package today.
  • No warehouse management.Cargo and containers on the shipment, not inventory and bin locations.
  • English only.The system is built for more languages and none of the others are switched on yet.
  • No mobile app.It's a web application. It works on a tablet; it isn't a phone-first product.
  • No customers yet.We're pre-first-pilot. That's the honest reason there are no logos on this page.

If any of these are dealbreakers, tell us on the call and we'll say so plainly rather than sell you a roadmap.

Where we are

Built, deployed, and looking for the first forwarders.

Tranvoro was built as a complete quote-to-cash system rather than a booking tool with billing bolted on later — because the seams between those two halves are where forwarders actually lose money.

The baseline product is built and deployed. What it hasn't had yet is your business running through it. That's what the pilot is for, and it's why the first group is small: we can only work properly with a handful of forwarders at once.

Being early is a real trade. You'll find rough edges before we do. In exchange you get direct access to the people building it, and the product bends toward the way you actually work rather than the way a roadmap committee imagined it.

  • Running in productionDeployed, monitored, backed up, with a tested restore procedure.
  • Built for the whole jobQuote through payment, not a fragment of it.
  • Founder-ledYou'll talk to the person building it, not a ticket queue.

Pilot programme

Run one lane through it and see.

A pilot starts with a conversation, not a contract. Tell us how you're running things now and we'll tell you honestly whether Tranvoro fits — including when it doesn't.

  1. A call.Thirty minutes on how your operation actually runs — quotes, branches, currencies, who touches the money.
  2. A real walkthrough.Your workflow in the product, using your kind of shipment. Not a slide deck.
  3. A scoped pilot.We set up your tenant, import your parties, and run a real lane end to end — quote to payment. Terms in writing before anything starts.
  4. Your call.Your data is yours and exportable, whether you continue or not.

Request a pilot conversation

We'll reply personally. No sequence, no newsletter.

Questions

Straight answers.

Do you have customers?

Not yet. Tranvoro is pre-launch and we're selecting the first pilots now. Everything you see on this page is the real product — the screenshots come from the running system, not a mockup.

What does it cost?

We haven't published pricing yet. Pilot terms are agreed directly and in writing before anything starts, and we'll publish standard pricing before general availability. If a number now is what you need to take this seriously, ask us on the call and we'll give you one.

How long does it take to get going?

There's nothing to install. Setting up a tenant, configuring your master data and importing your parties is the work, and party and shipment imports are built in. During the pilot we do that with you rather than handing you a manual.

What happens to our data if we stop?

It's yours. You can export it and we'll help you get it out. No hostage-taking.

Can I stop my staff from seeing everything?

Yes. Roles are scoped to branches, so people see the branches they work in. Approving money is a separate permission from doing the work — an operator can raise charges without being able to approve the invoice.

Is our data separated from other companies'?

Yes. Tranvoro is multi-tenant with isolation enforced at the operation layer, not just in the interface. Files are stored privately. Key actions are recorded in an append-only audit log. The system is backed up daily and the restore procedure has been tested.

Do you handle multiple currencies?

Charges carry their own currency and convert to the shipment currency for the profit figure, and invoices are issued in the currency you bill in. Payments are the limit: a payment is recorded in its own currency and allocated at the amount you enter, so Tranvoro does not calculate an exchange gain or loss for you when the rate has moved. That one is listed under what we don't do yet.

Do you support house and master shipments?

Yes — consolidation with house and master shipments, containers, packages and multi-leg routing.

What's the AI part?

Incoming emails and documents are classified and their fields extracted into a review step. A person chooses which fields to apply to an existing shipment; nothing is applied without confirmation. It's one reviewed step in the workflow, not the product.

Can you connect to our accounting system?

Not today. There's no automatic sync to an external accounting package, and no public API or webhooks yet. If that's a requirement, we're not the right fit right now and we'd rather say so.

We're small. Will we outgrow it?

The scope is the full quote-to-cash workflow with multiple branches, multiple currencies and role-based control already in it — it isn't a starter tool that stops at bookings. Where the real ceiling is, we've listed above: customs filing, EDI, WMS and deep country compliance aren't ours.

Who are you?

A small team building Tranvoro for forwarders who are stuck between spreadsheets and a system that costs more than the problem. On a pilot you talk to the people building it.

See it against a real shipment of yours.

Thirty minutes, your workflow, an honest answer about fit.