Manual Hazard Compliance Replaced with Integrated Rules Engine for Consistent Dangerous Goods Management

Overview

A chemical warehouse struggled to meet dangerous goods requirements because rules lived in binders and varied by operator and shift. Loads were reworked at the dock, carriers rejected shipments, and audits required manual reconstruction. Intelligex implemented a governed rules engine integrated with the Warehouse Management System (WMS) and Transportation Management System (TMS) that validated packing, segregation, labeling, placarding, documentation, and routing at pick and ship. When exceptions were necessary, the Quality Management System (QMS) captured approvals with e-signatures. Hazard handling became consistent and auditable, with fewer last-minute fixes and clearer decisions for warehouse and transportation teams.

Client Profile

• Industry: Chemical distribution and third-party warehousing
• Company size (range): Mid-market, multi-site DC network serving varied modes
• Stage: Established WMS and TMS; compliance driven by SOP binders and operator knowledge
• Department owner: Operations & Manufacturing
• Other stakeholders: Environmental, Health, and Safety (EHS), Quality Assurance, Transportation, Regulatory Affairs, Customer Service, IT/Security

The Challenge

Hazardous materials moved daily across ground, air, and ocean. Operators relied on printed SOPs, laminated charts, and experience to decide how to pick, pack, mark, and ship. Interpretations differed by person and site. Pallets sometimes combined incompatible classes, limited quantity rules were misapplied, and printed marks or shipping papers did not always match the product and mode. Carriers flagged issues at pickup, and loads returned from the dock for rework.

Systems were not helping. The WMS managed inventory and wave release, but it did not enforce segregation or packaging standards during pick and pack. The TMS set appointments and printed paperwork, yet it did not validate that a load’s labels, placards, and descriptions matched mode-specific regulations. When deviations happened, the QMS opened incidents, but the evidence was scattered. Teams needed a consistent, system-level way to apply dangerous goods rules in the workflow rather than relying on binders and memory.

Regulatory complexity added pressure. Requirements differ across jurisdictions and modes, with exceptions and special provisions that can be hard to apply at speed. The company wanted a solution that respected established regulations and guidance—such as the U.S. Department of Transportation’s Hazardous Materials Regulations (PHMSA HMR), the International Maritime Dangerous Goods Code (IMDG Code), and the European Agreement concerning the International Carriage of Dangerous Goods by Road (ADR)—without replacing core WMS and TMS.

Why It Was Happening

Fragmented data and manual handoffs were the root cause. Product hazard details, such as United Nations (UN) numbers, proper shipping names, hazard classes, packing groups, special provisions, and quantity limits, lived in safety data sheets and spreadsheets, not in a system that could drive decisions. The WMS had item and lot data but not a structured hazard profile. The TMS printed paperwork but did not reconcile content against live order lines and mode restrictions. Operators filled the gap with best efforts and quick references, which led to inconsistent outcomes.

Ownership was diffuse. EHS maintained classification and documentation, Operations ran pick and pack, Transportation booked modes and tenders, and Quality managed deviations. Without a shared rules engine and common identifiers, each team optimized locally. The last mile lacked enforcement: a pallet could be built and wrapped before anyone confirmed that labels, marks, and documents matched the shipment’s hazard profile and route.

The Solution

Intelligex implemented a dangerous goods rules engine that sat between product data, WMS execution, and TMS shipping. The service maintained a governed catalog of hazard attributes and mode-specific rules, validated orders during pick and pack, and verified documentation and placards at ship confirm. When a rule blocked a step, operators received clear prompts to correct the issue. If an exception was justified, a QMS workflow captured approval with reason codes and evidence. The approach integrated with existing tools and added guardrails where decisions happen.

• Integrations: Connected to WMS platforms such as SAP Extended Warehouse Management (EWM), Manhattan, Blue Yonder, or Oracle WMS Cloud for pick, pack, and load tasks; linked to TMS such as Oracle Transportation Management, SAP TM, or MercuryGate for mode, routing, and paperwork; synchronized exceptions and approvals with QMS tools like ETQ Reliance, MasterControl, or TrackWise. Label printing integrated with platforms like BarTender or Loftware/NiceLabel for regulated marks and labels.
• Hazard catalog: Centralized product classifications (UN number, proper shipping name, class/division, packing group), subsidiary risks, limited and excepted quantity eligibility, special provisions, tunnel and temperature controls, and segregation groups. Tied catalog entries to items and customer-specific variants.
• Pick and pack validation: Enforced segregation at the tote, pallet, and trailer level; checked inner and outer packaging types, quantities, and net contents; validated limited quantity rules; and blocked confirmation until violations were corrected or approved.
• Labeling, placarding, and documents: Generated or validated required marks, hazard labels, and placards based on content and mode. Verified shipping papers and declarations against order lines and thresholds, preventing ship confirm when documentation was incomplete.
• Routing checks: Applied mode and carrier restrictions (e.g., no air for certain divisions, tunnel codes for road, stowage/segregation for ocean) and suggested compliant alternatives when a plan conflicted with rules.
• Exception handling: Routed time-bound overrides through the QMS with e-signatures, reason codes, and attachments (SDS excerpts, customer instructions). Linked results back to the shipment for auditability.
• Dashboards and alerts: Provided live views of blocked tasks, common violations, and shipments at risk. Notifications to supervisors and transportation coordinators surfaced issues early.
• Security and permissions: Enforced role-based access to catalog edits and exception approval. All changes to rules and classifications were versioned with full audit trails.
• Standards alignment: Catalog and logic aligned with key references, including PHMSA HMR, IMDG Code, and ADR. Worker-facing content followed Hazard Communication expectations outlined by OSHA HazCom.

Implementation

• Discovery: Cataloged SKUs and current classifications, reviewed SDS sources and ownership, and mapped pick/pack/ship steps by mode. Collected carrier and customer-specific requirements and documented the most frequent violations and rework scenarios.
• Design: Defined the canonical hazard catalog, rule taxonomy, and event points in WMS/TMS where validation occurs. Established segregation logic, limited quantity interpretation, label/placard generation, and document verification rules. Set exception paths, roles, and required evidence for approvals.
• Build: Implemented integrations to WMS and TMS events, built the rules engine and catalog service, and configured label and document templates. Stood up dashboards, alerts, and QMS workflows for exceptions. Implemented role-based permissions and versioning for catalog maintenance.
• Testing/QA: Ran validations in shadow mode against live orders, comparing engine outcomes to operator decisions and carrier feedback. Tuned rules for edge cases and clarified prompts. A human-in-the-loop review board approved early exceptions and catalog updates before enabling hard blocks.
• Rollout: Enabled by site and mode, starting with outbound ground where most volume flowed. Switched pick/pack checks to hard stops after operators were comfortable with prompts. Extended to air and ocean flows, coordinating with Transportation on routing checks and paperwork timing.
• Training/hand-off: Delivered role-based sessions for pickers, packers, shipping clerks, supervisors, and EHS/Quality. Updated SOPs and quick-reference guides inside the WMS station UI. Transferred catalog ownership to EHS/Regulatory with change control and periodic review.

Results

Hazard decisions moved from binders to a governed workflow. Pickers and packers received clear prompts when a pallet violated segregation or quantity rules, and they corrected issues before wrap and load. Shipping clerks printed the right marks, labels, and documents from controlled templates, and the TMS flagged routes that conflicted with the load’s profile. Dock rework decreased, and carrier handoffs became steadier.

Audit readiness improved. Each shipment carried a traceable record of validations, labels, placards, and paperwork matched to the order lines and hazard catalog in force at the time. Exceptions were documented with approvals and evidence. Supervisors and EHS leaders saw patterns in violations and addressed training or catalog gaps proactively. The warehouse kept its WMS and TMS; the difference was the consistent application of rules at the point of work.

What Changed for the Team

• Before: Operators referenced binders and charts. After: The WMS prompted compliance checks with clear pass/fail messages and fixes.
• Before: Segregation and quantity rules varied by person. After: A rules engine enforced standardized logic across sites and shifts.
• Before: Labels and documents were assembled manually. After: Controlled templates generated required marks, labels, and shipping papers.
• Before: Carriers rejected noncompliant loads at pickup. After: Routing and mode checks occurred before tender and ship confirm.
• Before: Exceptions were informal. After: QMS approvals captured reason codes, e-signatures, and supporting evidence.
• Before: Audits required reconstruction. After: Each shipment’s validations and documents were traceable and consistent.

Key Takeaways

• Put dangerous goods logic in the workflow; validate at pick, pack, and ship inside WMS and TMS rather than relying on binders and memory.
• Maintain a governed hazard catalog tied to items; UN numbers, classes, packing groups, and special provisions must live in a system, not a spreadsheet.
• Generate labels, placards, and documents from controlled templates; remove station-level edits that create drift.
• Check routing against mode restrictions before tender; prevent rework by catching conflicts early.
• Keep a clear exception path in QMS with e-signatures and evidence; governance turns edge cases into learning, not risk.
• Align with established regulations and guidance and integrate, don’t replace; the gains come from orchestration and enforcement.

FAQ

What tools did this integrate with? The rules engine connected to the existing WMS (for example, SAP EWM, Manhattan, Blue Yonder, Oracle WMS Cloud) to validate pick and pack steps, and to TMS (such as Oracle Transportation Management, SAP TM, or MercuryGate) to verify routing and ship confirm. It generated labels and marks through platforms like BarTender or Loftware/NiceLabel, and it logged exceptions and approvals in the QMS (for example, ETQ Reliance, MasterControl, or TrackWise). Dashboards and alerts surfaced in Microsoft Teams or existing supervisor portals.

How did you handle quality control and governance? Product classifications and rules lived in a versioned catalog with role-based edits. Validations fired at defined WMS/TMS events, and hard blocks prevented confirmation when rules failed. Changes to the catalog followed change control, and shipments carried an audit trail of the rules in force, validations performed, and documents produced. The approach aligned with references such as PHMSA HMR, IMDG Code, and ADR.

How did you roll this out without disruption? Validations ran in shadow mode first, showing operators and shipping clerks what would have been blocked while the legacy process continued. After tuning prompts and rules, hard stops were enabled by site and mode. Existing WMS, TMS, printers, and forms were reused; the new layer orchestrated decisions and documents rather than replacing systems.

How were the rules kept current as regulations changed? EHS/Regulatory owned the catalog and reviewed changes on a defined cadence. Updates flowed through change control with impact assessment and training notes. The rules engine supported effective dating, so shipments were validated against the version in force at the time of work.

How did you manage classification and SDS data? Item hazard attributes were sourced from the authoritative classification maintained by EHS, informed by Safety Data Sheets and customer requirements. The classification was normalized into the catalog with UN number, proper shipping name, class/division, packing group, subsidiary risks, special provisions, and quantity limits. The WMS and TMS consumed only the fields required for validation and documentation, keeping sensitive content within EHS’s governed repository.