| Dangerous-goods declarations, shipping papers & manifests | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the dangerous-goods compliance workflow? | Mode modules create shipper declarations and handler workflows include manifests/NOTOC, with entitlement dependent on selected modules. |
| ERP, TMS, WMS, booking, API & EDI integration | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the dangerous-goods compliance workflow? | Web services and integrated solutions are available, but plan tables show web-service/integration entitlement varies by package. |
| Maintained regulatory content & amendment updates | Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the dangerous-goods compliance workflow? | DGOffice provides access to current regulatory information and maintained dangerous-goods datasets with amendments/updates. |
| Multimodal dangerous-goods shipment compliance | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the dangerous-goods compliance workflow? | DGOffice offers road, sea, air, rail and inland-waterway modules, but plans license a selected number of modes rather than universally including all modes. |
| Port, terminal, carrier & handler dangerous-goods workflows | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the dangerous-goods compliance workflow? | DGOffice documents ground/terminal handler workflows for pre-arrival data, acceptance, manifests, validated declarations and loading preparation; required modules may vary. |
| SDS & Section 14 transport information | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the dangerous-goods compliance workflow? | SDS Basic and SDS Editor are separate chemical-management modules/add-ons, not universal transport-software entitlement. |
| ADR / RID road and rail dangerous-goods compliance | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the dangerous-goods compliance workflow? | Road supports ADR and Rail supports RID, but the modules are licensed selectively rather than universally included. |
| IATA / ICAO air dangerous-goods compliance | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the dangerous-goods compliance workflow? | The Air module is based on ICAO/IATA, but transport modes are selected by license/module. |
| IMDG maritime dangerous-goods validation | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the dangerous-goods compliance workflow? | The Sea module is based on the IMDG Code, but DGOffice licenses are modular and do not universally include every transport mode. |
| Packaging, quantity, marks, labels & placards | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the dangerous-goods compliance workflow? | DGOffice offers shipping-label functionality, but packaging validation depth and label entitlement vary by module/license and are not assumed universally. |
| Segregation, compatibility & stowage validation | Partially Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the dangerous-goods compliance workflow? | Handler workflows include validated and segregated declarations; universal vessel/CTU stowage behavior across all licenses is not inferred. |
| UN number, proper shipping name & transport classification | Supported | What configuration, module, licensing, integration or operating assumption is required for this capability in the dangerous-goods compliance workflow? | DGOffice maintains dangerous-goods classification data and DGM identifiers linked to UN numbers and classification variants. |