LOGISTICS INTELLIGENCE / CUSTOMS DECLARATIONS
Send us a commercial invoice, packing list, and certificate of origin for one shipment. Mirage extracts and cross-checks the data before it becomes a filed declaration, not after a hold at the border.
Built on the same document pipeline running at Transwin.
THE REALITY
A customs declaration is only as good as the commercial invoice, packing list, and certificate of origin it's built from — and those three documents rarely arrive already reconciled with each other. A mismatch that would take seconds to catch on purpose gets caught instead at the border, as a hold.
WHAT MIRAGE DOES
01
Commercial invoice, packing list, and certificate of origin are each read for cargo description, value, weight, HS codes where stated, and country of origin — in whatever language your trading partners use.
02
Cargo description, weight, and value are compared across all three documents. A mismatch — or a certificate of origin that doesn't match the invoice's supplier — is flagged before it reaches a declaration.
03
Your customs broker or in-house team receives a clean, cross-checked data set ready to file from, instead of three separate documents to reconcile by hand under time pressure.
THE OUTPUT
| Field | Commercial Invoice | Packing List | Status |
|---|---|---|---|
| Cargo description | Steel coils, cold-rolled | Steel coils, cold-rolled | Matches |
| Net weight↳ 450 kg difference between invoice and packing list — flagged for confirmation before it's declared at either figure. | 18,400 kg | 17,950 kg | Mismatch — flagged |
| Country of origin | Spain | Certificate of origin: Spain | Matches |
| HS code | 7209.16 | Not stated on packing list | Confirmed from invoice |
PROOF
Transwin
CargoScribe built against Transwin's actual freight and customs document mix
70% less manual data entry on freight documents
Agri-food, fertilizer, steel, and mining freight — high-scrutiny cargo categories, read the same consistent way
Send us the commercial invoice, packing list, and certificate of origin for one real shipment, and we'll show you exactly what gets flagged.
Book a 30-min call →or fill out the form below instead
FAQ
No. Mirage extracts and cross-checks the data a declaration is built from — commercial invoice, packing list, certificate of origin, HS codes where stated — and hands your team or your customs broker a clean, verified data set to file with. Filing itself stays with whoever files today.
Cargo description, weight, or value that differs between the commercial invoice and the packing list; a certificate of origin that doesn't match the declared country of origin; missing fields a declaration needs but the source documents don't clearly state.
No. It sits before the broker in the process, so the broker receives already-verified data instead of raw documents to reconcile themselves. Your existing broker relationship and filing process stay in place.
Yes. Commercial invoices and certificates of origin arrive in whatever language your trading partners use, and Mirage reads them without requiring a specific language or template per partner.
It's flagged as missing, not inferred. A commercial invoice without a stated HS code, or a certificate of origin that doesn't match the invoice's supplier, is surfaced to a person before it becomes a declaration error.
Yes. The underlying documents differ (import: commercial invoice, packing list, certificate of origin; export: largely the same set plus any export-specific licenses), but the extraction and cross-check approach is the same for both directions.
Under four weeks on average to a production deployment: indexing a sample of your actual customs document mix first, then a parallel pilot cross-checking real shipments before anything is fully automatic.
Pricing starts with a fixed-price pilot run on a real batch of customs documents, so you see what it catches before committing to anything larger. After that, it moves to an annual subscription priced by volume, quoted in your first conversation with us.