
Three freight quotes arrive. One includes destination handling. Another says “subject to local charges”. The third quotes only the main carriage. A spreadsheet can rank their totals, but the lowest visible number may describe a smaller service.
In a December 2025 r/logistics discussion, a poster describes comparing PDF, Excel and WhatsApp quotations. This is an unverified public account. We use the scenario to explain a workflow, not as a Kaliits customer story or evidence of market size.
Establish one shipment baseline
Before extracting prices, record the route, origin and destination service points, shipment date, cargo description, weight and volume, transport mode and equipment where relevant. Give the request a stable reference. Every candidate quote must point to that same request.
Record what your team wants included: pickup, main carriage, destination handling, delivery and any other applicable service. A quote covering port-to-port transport should not quietly compete with a door-to-door offer. If the scope differs, mark the difference before calculating a rank.
Build a comparison that preserves unknowns
For each charge, retain the provider’s original label, amount, currency, charging basis and evidence location. A per-container charge and a per-shipment charge need different calculations. Preserve the original quote beside the extracted proposal.
Use separate states for included, excluded, conditional and not stated. “Not stated” must remain unknown. It must not become zero because the model failed to find a price. Keep quote validity, booking conditions and assumptions visible.
If you convert currencies, retain the original amounts, chosen comparison rate, rate date and calculation. The comparison rate is a planning assumption. It does not amend the provider’s quotation or guarantee the final invoice.
A fictional comparison
Suppose quote A shows 1,800 in one currency for the main movement and excludes destination handling. Quote B shows 2,000 in the same currency and explicitly includes that handling. These fictional values do not establish that A is cheaper: its missing component still needs confirmation.
The comparison can show “known total: 1,800; destination handling unresolved” for A. It can show “known total: 2,000; stated scope complete” for B. The operations buyer then requests the missing detail and assesses service, capacity and timing alongside price.
Automate preparation, retain the booking decision
A document workflow can collect quotations, extract proposed charges, flag scope mismatches and prepare a clarification email for review. A manager approves the normalized comparison and the booking decision. An unfamiliar surcharge, ambiguous unit or conflicting revision should enter the exception queue.
Start with a common quotation template if providers will use it. A structured form or the comparison feature already available in your transport system may be enough. Add custom document processing where inconsistent incoming formats still create measurable manual work.
Test the decision, not only extraction
Try an expired quote, two currencies, a revised attachment, a conditional surcharge and a quote that omits a required leg. The test passes when a reviewer can trace each amount, explain the differences and identify unresolved costs before booking.
Measure correction rate, clarification time and comparisons requiring review. Do not claim savings from a faster draft alone. For a scoped review of document intake, extraction and approval, see Kaliits document workflow services.


