Dangerous Goods / Hazmat Compliance Software buyer guide
Review the wider capability model, products, evaluation criteria and procurement questions for this category.
Validate dangerous-goods data, shipment rules or transport requirements against the International Maritime Dangerous Goods Code where explicitly supported.
Recorded product facts are shown separately from buyer-specific recommendation scores. “Not yet verified” means evidence is incomplete; it does not mean the product lacks the capability.
| Product | Status | Confidence | Implementation | Evidence | Limitations / notes | Last verified |
|---|---|---|---|---|---|---|
HV Hazcheck Validate NCB Hazcheck | Supported | 99% | Not recorded | 1 source | Hazcheck Validate explicitly validates dangerous-goods shipments against IMDG Code provisions. | Sep 19, 2026 |
LD Labelmaster DGIS Labelmaster | Supported | 98% | Not recorded | 1 source | Labelmaster states DGIS validates shipments against the latest IMDG Code requirements. | Sep 19, 2026 |
S ShipHazmat Bureau of Dangerous Goods | Supported | 98% | Not recorded | 1 source | ShipHazmat applies current IMDG requirements to ocean/vessel dangerous-goods shipping documents and compliance logic. | Sep 19, 2026 |
D DGOffice.net DGM-SDG | Partially Supported | 99% | Not recorded | 1 source | The Sea module is based on the IMDG Code, but DGOffice licenses are modular and do not universally include every transport mode. | Sep 19, 2026 |
LE Lisam ExESS Lisam | Partially Supported | 97% | Not recorded | 1 source | ExESS supports IMDG transport classification labels and Section 14 transport data, but full IMDG shipment validation is not inferred. | Sep 19, 2026 |
Use this capability as one requirement inside the wider category evidence model. The links below are research and comparison paths, not a product recommendation.
Review the wider capability model, products, evaluation criteria and procurement questions for this category.
Understand TechSelectAI coverage, source verification and research gaps before interpreting individual capability records.
See how support status, confidence, freshness and Unknown ≠ Unsupported are handled.
Supported, conditional, unknown and not-supported states are kept distinct so missing evidence is not treated as a negative fact.
Confidence reflects the strength of the recorded evidence for this capability, not overall product quality.
A product can strongly support this capability and still be a poor overall fit due to deployment, integrations, security, region, budget or other must-haves.
TechSelectAI can evaluate this capability together with your other must-haves, integrations, deployment constraints, security requirements, region and budget.
Evaluate software for my company