LOGISTICS INTELLIGENCE / DANGEROUS GOODS
Automate Dangerous Goods Declaration Checks
Send us a dangerous goods declaration. Mirage extracts UN number, class, packing group, and quantity, and checks them against each other and the shipment record before it ships.
Built on the same document pipeline running at Transwin and Ofret.
THE REALITY
A dangerous goods declaration has to be internally consistent: UN number, hazard class, and shipping name all have to agree, and all of it has to match what's actually being shipped. Checking that by hand, under time pressure, is exactly where a mismatch slips through.
WHAT MIRAGE DOES
Every declaration, checked for internal consistency
Extracts the fields that have to agree
UN number, proper shipping name, hazard class, packing group, and quantity are read from the declaration, whatever format it arrives in.
Cross-checks them against each other and the shipment
A hazard class that doesn't match the declared shipping name, or a quantity that doesn't match the shipment record, is flagged before the declaration moves forward.
Routes flagged declarations to your compliance team
Anything inconsistent or incomplete goes to a person with the specific mismatch already identified, instead of a full manual re-check of every declaration.
THE OUTPUT
Every declaration, checked field against field
| Field | Declared Value | Consistency Check | Status |
|---|---|---|---|
| UN Number | UN1993 | Matches Class 3, flammable liquid | Consistent |
| Proper Shipping Name | Flammable liquid, n.o.s. | Matches UN1993 and Class 3 | Consistent |
| Packing Group↳ UN1993 requires a stated packing group (I, II, or III), flagged as incomplete rather than shipped without it. | Not stated | Required for UN1993 | Missing: flagged |
| Quantity | 4 x 200L drums | Shipment record: 4 x 200L drums | Consistent |
PROOF
The document pipeline behind this, in production elsewhere
Transwin
The logistics agent deployed against Transwin's actual freight and customs document mix
70% less manual data entry on freight documents
Agri-food, fertilizer, steel, and mining freight, cargo categories where declaration accuracy matters
Ofret
2 tailored logistics environments deployed, one per entity
90%+ of standard RFQs matched and processed without manual entry
Same field-extraction and cross-check logic used here to check declarations
Ready to see your own declarations checked?
Send us a real dangerous goods declaration, and we'll show you exactly what gets checked and what would have been flagged.
How a deployment runs: Observe, Map, Build, Run, Expand. See the method
Prefer to talk it through first? Book a call
FAQ
Frequently asked questions
UN number, proper shipping name, hazard class, packing group, and quantity are extracted and checked against each other and against the shipment record, catching a mismatched class or a UN number that doesn't match the declared shipping name before it ships.
Not yet with a published case study naming dangerous goods specifically, our two current logistics clients' proven results are on RFQ handling and general freight/customs document processing. The extraction and cross-checking mechanism is the same one running in production there, applied to a document type it hasn't been named against publicly yet.
No. It checks the declaration's internal consistency and flags what's missing or mismatched before your compliance officer reviews it, removing the manual line-by-line check that comes first, not the sign-off itself.
It checks the declaration against itself (do the stated UN number, class, and shipping name agree) and against your shipment record. Checking against the full regulatory text of a specific mode's rules (IMDG for sea, IATA for air, ADR for road) is scoped per deployment, tell us which mode you need during your first call.
Scanned forms, PDFs, and emailed declarations are all read the same way, whether they're generated by your own system or received from a shipper or forwarder.
It's flagged as incomplete, not filled in with an assumed value. A missing packing group or an illegible UN number routes to a person before the shipment moves.
4 to 6 weeks to a production deployment: indexing a sample of your actual dangerous goods paperwork and shipment records first, then a parallel pilot on real declarations before anything is fully automatic.
Pricing starts with a fixed-price pilot run on a real batch of dangerous goods declarations, 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.