Zero-touch PDF ingestion. Payloads pushed straight into CargoWise.
Multimodal parsing reads the scan, the fax and the PDF alike. Every field is cross-checked and validated before anything is pushed to CargoWise. 45 minutes back per file.
Send us 100 files you have already cleared. We return the parsed output and every mismatch we found, with no integration to stand up first.
Three hidden costs of manual entry
Manual entry on a customs file costs three times over: the operator hours it takes, the demurrage an undetected mismatch triggers, and the cleanup generic OCR does not avoid.
The 45-Minute Re-Keying Tax
An operator retypes HS tariff codes, piece counts and gross weights out of a low-DPI scan or a fax. Those are paid hours spent before the file ever reaches CargoWise.
The Demurrage Blindspot
The packing list states one net weight, the bill of lading a different gross weight. Nobody intercepts the gap until the container is already at the terminal, accruing demurrage against it at the terminal’s daily rate.
The Fragile OCR Trap
Generic OCR returns a flat file, not a shipment. Somebody still has to clean the fields by hand before CargoWise will accept the payload: the re-keying moved desks, it did not go away.
The durations and amounts quoted here are order-of-magnitude estimates meant to frame the problem, not measurements taken in your operation.
From messy PDF to CargoWise in 3 seconds
A file passes three stages before it reaches CargoWise: the document is ingested as it arrives, reconciled field by field, then pushed across as a validated payload.
- 01
Multimodal document ingestion
We ingest the file as it arrives: any language, any layout, any format. Scans, faxes, native PDFs and photographs of paper documents all enter the same pipeline.
- 02
Field-level reconciliation
Container numbers, gross weights, HS tariff codes and IncoTerms are reconciled field by field against your purchase-order data. Any discrepancy is flagged the moment it appears, not once the entry has been filed.
- 03
Direct UniversalShipment payload push
The validated record maps to native eAdaptor XML and is pushed straight into CargoWise. Nobody re-keys anything: your team reviews only what was flagged.
Will this break our CargoWise?
No. The software connects upstream, through the native eAdaptor and Universal eXchange APIs. CargoWise remains your system of record: nothing is replaced, no schema is modified and no database override is required.
The 100-shipment live benchmark
Send us 100 shipments you have already cleared. We run them through the same pipeline and return a side-by-side benchmark: the hours your team spent against the processing time, and every discrepancy it caught that had gone out unnoticed.
Historical files only, so no live shipment is at stake. No integration, no credentials to hand over, no change to your CargoWise. You keep the benchmark either way.
Frequently asked questions
- Does this replace CargoWise?
- No. CargoWise stays your system of record. The software sits upstream, prepares the data and sends it; it replaces no CargoWise function and modifies no CargoWise data.
- What happens when a document is unreadable?
- The file is flagged as an exception rather than pushed through with doubtful data. Your operators then handle only those cases, which is exactly the work the pipeline exists to reduce.
- How long does it take to set up?
- The 100-shipment benchmark needs no integration at all: you send the files, we return the results. Going live depends on your CargoWise environment and is scoped separately.
The logical next step
Fixing one broken process usually reveals another, right next to it.
Last reviewed :