REGISTER REGISTER TO LEARN

Read -> Cross-Check -> Flag -> Review -> Sign

Dangerous-Goods Dispatch Pre-Check Agent

Before a dangerous-goods shipment is documented and loaded, the agent checks that the hazard classification, UN number, packing group, packaging, quantity limits, marks, and required emergency documents all agree with each other. It reads your dangerous-goods master, the dispatch order, the packaging spec, and the document register, then returns a pass or fail checklist that names each inconsistency. It feeds your dangerous-goods document software, it does not replace it.

The Problem

The load was staged. The papers looked right. The packing group did not match the UN number.

It is 6 a.m. and a tanker is waiting at the gate. The dispatch clerk copies last week's declaration, changes the customer, and prints it. Nobody notices that the substance was reclassified in the master data two months ago, so the packing group on the paper is now wrong. The error is caught at the receiving terminal, the load is rejected, and the truck comes back full.

What Changes

Every field checked against the master before anything prints

The agent pulls the dispatch order the moment it is exported and lines up each dangerous-goods field against the master data and the packaging spec. Where the UN number, class, packing group, packaging code, quantity limit, marks, or emergency documents disagree, it writes a fail line naming the exact mismatch. The clerk sees one checklist and knows what to fix before the declaration is generated.

Humans stay in control: the agent produces a checklist, and your dangerous-goods adviser decides whether the load is cleared to document and dispatch.

HOW THE AGENT WORKS

TRIGGERLLMAPIDECISIONACTIONWAIT
TRIGGERNew dispatch order exportedFires when a dispatch order for a dangerous-goods line is exported from the dispatch system.
APIPull dangerous-goods master recordReads the matching dangerous-goods master record for each UN number on the order.
APIRead packaging and documentsReads the packaging spec and the document register for the substances on the order.
LLMCross-check every fieldCompares UN number, class, packing group, packaging, quantity limits, marks, and required documents across the sources.
DECISIONAll fields agree?
LLMDraft pass or fail checklistWrites a checklist that names each inconsistency and the source values that disagree.
ACTIONSend checklist to dispatcherDelivers the pass or fail checklist to the dispatcher and safety adviser for review.
The agent does not sign the dangerous-goods declaration or release the load. Your dangerous-goods safety adviser does. The agent removes the field-by-field cross-check that gets skipped when a truck is waiting.

HOW TO BUILD IT

Three levels of depth. Pick the one that matches where you are.

For the ops person who needs to understand what's involved and brief their team.

Your RecordsDG master, dispatch order, packaging spec, document register
The AgentWorkflow engine + LLM
Your Dispatch DeskClerk and safety adviser review the checklist

WHAT YOUR TEAM PROVIDES ONCE

  • Dangerous-goods master data - your table of substances with UN numbers, classes, and packing groups
  • Dispatch order export - the order lines with substance, quantity, and packaging for the shipment
  • Packaging spec - the approved packaging codes and quantity limits for each substance
  • Document register - the list of emergency and transport documents each substance needs
  • A notification channel - email, Teams, or Slack where the checklist lands
What happens day-to-day: a dispatch order is exported, the agent checks its dangerous-goods fields against your master data and packaging spec within a minute, and a pass or fail checklist arrives at the dispatch desk. On a pass, the clerk generates the declaration as usual. On a fail, the checklist names the mismatch so it is fixed before anything prints.

For the IT person or technical lead who needs to scope the integration.

INQUIRY SOURCES

Dangerous-goods master data export
Dispatch order export from the dispatch system
Packaging spec and document register

WORKFLOW ENGINE (N8N)

Dispatch order webhook or poll
Fetch DG master record
Fetch packaging and documents
Normalize and compare fields
Consistent set?
Generate checklist JSON
Post checklist to channel

CONNECTS TO

DG master data (SAP EHS / Kisters DG / manual table)Read: UN numbers, classes, packing groups, quantity limits. Write: none
Dispatch system (SAP / Oracle TMS / manual export)Read: order lines, substances, quantities, packaging. Write: none
DG document software (Labelmaster / DGOffice)Read: required document list. Write: pre-check result as a feed
Notification (Email / Microsoft Teams / Slack)Read: none. Write: pass or fail checklist
WITHOUT PMS API

Without API access, someone exports the dispatch order and master extract to a shared folder or spreadsheet, and the agent checks those files on a schedule. The checklist still names every mismatch, it just runs on the drop instead of in real time.

WITH PMS API

With API access to the master data and dispatch export, the agent runs the check automatically the moment an order is exported and returns a checklist in under a minute. No rekeying, no waiting for a batch job. Best experience.

For the person who wants to build this agent step by step. Each node below maps to an n8n workflow node.

TRIGGERNode 1
Trigger - dispatch order arrives
n8n Webhook or Schedule node watching the dispatch export folder or endpoint.
Output: A dispatch order payload with substance, UN number, quantity, and packaging fields.
APINode 2
HTTP Request - fetch master record
GET the dangerous-goods master record for each UN number on the order.
Output: Master fields: class, packing group, quantity limit, required documents.
LLMNode 3
LLM - compare declared vs master
Send the order fields and the master fields, ask for a structured comparison.
You are a dangerous-goods checker. Compare the declared shipment fields against the master data.

Declared: {declared_fields}
Master: {master_fields}

For each field (un_number, class, packing_group, packaging_code, quantity_limit, marks, documents), say whether declared and master agree. List every mismatch with expected and found values. Respond ONLY with valid JSON. No explanation.
INPUT
declared: UN1203, class 3, PG III, packaging 3H1, 200 L; master: UN1203, class 3, PG II, packaging 3H1, 60 L limit
OUTPUT
{"result": "fail", "mismatches": [{"field": "packing_group", "expected": "II", "found": "III"}, {"field": "quantity_limit", "expected": "60", "found": "200"}]}
DECISIONNode 4
IF - any mismatch
n8n IF node on result equals fail.
Output: Routes fails to the checklist builder, passes to a clear-to-document note.
LLMNode 5
LLM - write the checklist
Turn the comparison result into a short pass or fail checklist a clerk can act on.
Turn this comparison result into a short pass or fail checklist a dispatch clerk can act on.

Comparison: {comparison_json}
Order: {order_id}

List each line as fixed or action needed, name the field and the correct value. Respond ONLY with valid JSON. No explanation.
INPUT
comparison with two mismatches on packing_group and quantity_limit, order DO-4471
OUTPUT
{"order_id": "DO-4471", "status": "fail", "lines": [{"field": "packing_group", "action": "set to II per master"}, {"field": "quantity_limit", "action": "reduce to 60 L or split load"}]}
ACTIONNode 6
Send - notify dispatch desk
n8n Email or Slack node posting the checklist to the dispatcher and safety adviser.
Output: A message with the pass or fail checklist and the order id.
MVP vs Advanced — Where To Start
MVP — START HERE
  • Start with one substance family and one dispatch route so the master data is small and clean.
  • Pull the master extract and one real dispatch order into a spreadsheet the agent can read.
  • Check the six fields that fail most often: UN number, class, packing group, packaging, quantity limit, documents.
  • Send the checklist to one dispatcher by email and have them confirm each flag by hand for two weeks.
  • Log every flag and whether it was a real mismatch to measure the false-flag rate.
  • Only after the flags are trusted, connect the notification channel the whole desk uses.
ADVANCED — ADD LATER
  • =+ Add a webhook from the dispatch system so the check runs the moment an order is exported.
  • =+ Feed the result into your dangerous-goods document software as a pre-check status.
  • =+ Cover multi-substance loads and segregation rules between substances on the same truck.
  • =+ Track the false-flag rate per substance and tune the comparison thresholds.
  • =+ Add a monthly report of the most common mismatches to fix the source data.
  • =+ Version the master data snapshot with each check so a cleared load can be reconstructed later.

Full Video Walkthrough Coming Soon

Watch the agent catch a packing-group mismatch before the declaration prints.

Register to be notified

Everything on this page is free to learn.

When you're ready to build — do it yourself or bring us in.

Register FOR WALKTHROUGHS
Book a call to scope this

OTHER AGENTS IN LEASING & MARKETING

Dangerous-Goods Mixed-Load Segregation Checker

Checks if a mixed dangerous-goods load is legal to travel together

Frequently asked questions

Dangerous-Goods Dispatch Pre-Check Agent is an AI agent that checks hazard class, UN number, packaging, and papers agree before the truck loads.
The load was staged. The papers looked right. The packing group did not match the UN number. The Dangerous-Goods Dispatch Pre-Check Agent addresses this: checks hazard class, UN number, packaging, and papers agree before the truck loads.
No. Your team stays in control. The agent does not sign the dangerous-goods declaration or release the load. Your dangerous-goods safety adviser does. The agent removes the field-by-field cross-check that gets skipped when a truck is waiting.

This is 1 of 2 agents in Logistics & Dispatch. → · Explore all 15 departments →