One wrong digit causes delays
A transposed digit in a container number or HS code leads to queries and delays. With the source location you check every value against the original before it moves on.
Reading freight documents – shipment data without retyping
Bills of lading, CMR consignment notes, packing lists and customs documents describe the same shipment from different angles – in the layouts of shipping lines, forwarders and suppliers. Excalitract extracts shipper, consignee, packages, weights, HS codes and container numbers according to your schema, every value with its source location. Your transport or customs software receives reviewed data instead of retyped data.
From freight documents to a shipment record
1 / 3Freight and customs documents
Bills of lading, CMR consignment notes, packing lists and customs documents – from shipping lines, forwarders and suppliers.
Packing lists with many rows
Packing lists itemize dozens of packages with contents, dimensions and weight. Excalitract maps them as a list in the schema – with a sheet of their own in the Excel® export.
Whole shipment files at once
Upload documents as a folder or ZIP – up to 200 documents per run. Documents submitted twice are detected before they are captured twice.
Explained briefly
Freight and customs documents in one minute
Shipment and line items
Freight documents become a reviewable shipment record
Transport planning and customs declarations depend on the shipment header and every single line item: goods description, packages, weight, HS code. Excalitract delivers both in one structure, evidences every value with its source location and leaves open what is not in the document. The customs classification stays with your team and your customs software.
- Shipment, package, line item Header data and line items as a nested list – one sheet per level in Excel®.
- Source location per number Container, seal and HS code numbers lead back to their place in the document.
- Open, not estimated If a weight is missing, the field stays open – it never silently becomes zero.
- Handover via REST API Approved shipment data straight into TMS or customs software.
Reviewed before data moves on
Your team confirms or corrects the values next to the original. Every correction is kept as a revision, and the export shows whether a value is preliminary or final.
Straight into TMS and customs software
Approved shipment data goes to your transport management or customs system as JSON or via the REST API – or as Excel® with one sheet per list level.
Typical fields
These are the values Excalitract extracts for you
Examples – you define exactly which fields are extracted in the schema.
- Shipper, consignee and carrier
- Bill of lading or consignment note number and date
- Container and seal numbers
- Line items with goods description, packages and weight
- HS codes and country of origin
- Place of loading and unloading, delivery terms
Your result
- Shipment data from freight documents without manual retyping
- Line items with weight and HS code as the basis for your customs software
- Every number and every weight traceable to the original document
More use cases
The same principle for other document types
Delivery notes and goods receipt Line items, quantities, order references and batches from delivery notes – structured for ERP and purchasing. 
Tenders and bills of quantities Deadlines, lots, requirements and bill items from tender documents – structured for estimating and bidding. 
Invoices and billing statements Line items, periods and amounts from invoices and billing statements – structured, detailed and evidenced. Demo
See Excalitract with your documents
No standard show: we prepare the demo for your documents and fields. Afterwards, you will know how Excalitract handles your document collection – and how you can measure it on a test set of your documents.