Bring shipment details together
Put review fields in one table while retaining original document citations.
Lumi / Freight & logistics
The agent compares package counts, weights and consignee details across the commercial invoice, packing list and booking confirmation, collecting mismatches and gaps. Your operations team resolves them and decides what is sent.

The agent for this industry is a proposal: product access is not open, and feasibility is confirmed before a pilot. BI is already deployed with customers.
Watch the agent work · 26 seconds
Friday, 10:40. Cut-off is in 3 hours. Do the documents agree?
Three parts of document review the agent could take on.
Put review fields in one table while retaining original document citations.
Compare package counts, weights, and party details using the stated units.
Check supplied files against the document list agreed for this shipment.
Every pilot measures preparation, review, correction and support time. There are no savings figures to publish in advance.
Three authored scenarios with synthetic IDs and figures, showing where the agent stops and what it hands to your reviewer. Not customer data.
Say what needs to be done; the agent works through the four steps below and stops where your decision is needed. Sample files, matching rules and the reviewer are agreed before a pilot.
Authorized commercial invoices, packing lists, bookings, bills of lading, and customer instructions.
Organizes information into agreed templates, keeps identifiers intact and cites a source for every line.
Compare parties, container IDs, package counts, weights, units, and document versions.
The agent lays out every mismatch with its source; you decide before anything happens downstream.
Proposed workflow
The packet the agent is planned to hand back after each run. File formats are agreed before work begins.
Proposed deliverables
Key shipment fields with a document reference for each detail.
Show both conflicting values for the operator to confirm.
Documents still missing from the supplied shipment packet.
Cite authorized files, locations and versions.
Record failures, unverified items and decisions needed.
Matching fields across files do not establish a correct declaration. Commodity classification, customs requirements, and shipping instructions remain with the responsible team.
No customs filing, HS-code decisions, shipping instruction sending, or booking changes.
Pick a recent set of documents. Together we see which part is worth handing to the agent and which should stay with your specialists.

Measure preparation and review effort, identify bottlenecks, and document the recurring cycle.
Confirm data permissions, reviewers, output formats, acceptance criteria, and clear costs.
Check workflow handling on realistic synthetic cases before requesting access to actual records.
Account for all support effort, compare against the current baseline, and decide together on next steps.
Not yet. It is a proposed scope to discuss your needs; feasibility is confirmed before any real records are used. BI is already deployed with customers and can start on its own.
No customs filing, HS-code decisions, shipping instruction sending, or booking changes.
Authorized commercial invoices, packing lists, bookings, bills of lading, and customer instructions. Please do not send confidential documents through the contact form.
No. The form simply registers your interest so we can connect. Scope, pricing, and deployment criteria are agreed transparently before any work starts.
Describe the result you need, not the steps: your last run, how often it recurs, where it takes the most effort. No real files needed yet.
Discuss your workflowLeave your details and a brief description; no files needed yet.
Your request was received. No account was created and no payment was taken.