Read SDS -> Look Up Spec -> Compare -> Flag -> Confirm

Dangerous-Goods Packaging Checker

This agent reads a product's safety data sheet for its hazard class and packing group, then checks the packaging on the purchase order against your approved packaging spec master. It recommends the correct UN-coded packaging and flags any mismatch before the order is placed or the goods are packed. A person confirms the recommendation; the agent never changes a PO or approves a shipment.

The Problem

The drum was UN-rated. It was rated for the wrong packing group.

A buyer copies the packaging line from an old purchase order for a similar product. The new material is packing group I, but the drum ordered is only approved for packing group II. Nobody catches it because the code looks right at a glance and the SDS sits in a separate folder. The mismatch surfaces at dispatch, when the load is already staged and the paperwork is being checked.

What Changes

Read the SDS, read the spec, compare before the order goes out

The agent pulls the hazard class and packing group from the product's safety data sheet, looks up the approved packaging for that combination in your spec master, and compares it to what the purchase order specifies. When they match it says so; when they do not it flags the mismatch and names the correct approved code. Your buyer or dispatch lead reads the flag and decides.

Humans stay in control: the agent recommends the correct UN packaging code and flags mismatches, but your buyer or dispatch lead confirms the packaging before an order is placed or a load ships.

HOW THE AGENT WORKS

TRIGGERLLMAPIDECISIONACTIONWAIT
TRIGGERNew or changed PO lineFires when a purchase order line with a hazardous product is raised or edited.
APIFetch SDS hazard dataReads the product's hazard class and packing group from the safety data sheet source.
APIFetch packaging specReads the approved packaging codes for that hazard class and packing group.
LLMCompare PO to specChecks the PO packaging against the approved code and explains any gap.
DECISIONMatch or mismatch?
LLMDraft mismatch noteWrites a short note naming the wrong code and the correct approved one.
ACTIONSend recommendationDelivers the match confirmation or mismatch flag to procurement and dispatch.
The agent does not place orders or release shipments. Your buyer or dispatch lead does. The agent removes the manual cross-check between the SDS, the spec master, and the PO line.

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.

SDS and Spec MasterHazard class, packing group, approved codes
The AgentWorkflow engine + LLM
Buyer and DispatchPackaging recommendation and mismatch flags

WHAT YOUR TEAM PROVIDES ONCE

  • Safety data sheet access - a source for hazard class and packing group per product
  • Packaging spec master - the table of approved UN codes by hazard class and packing group
  • Purchase order feed - the PO lines carrying the packaging chosen for each buy
  • Notification channel - where recommendations and flags land for buyers and dispatch
  • Escalation contacts - who signs off when a mismatch needs a packaging change
What happens day-to-day: as hazardous purchase order lines are raised, the agent reads the SDS, checks the approved packaging, and either confirms the code or flags a mismatch with the correct one. Buyers see a green tick or a clear flag before the order is committed.

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

INQUIRY SOURCES

Safety data sheet or dangerous-goods data with hazard class and packing group
Packaging spec master listing approved UN codes per hazard class and packing group
Purchase order lines with the chosen packaging code

WORKFLOW ENGINE (N8N)

PO line raised or changed
Fetch SDS hazard data
Fetch approved packaging spec
Compare PO packaging to spec
Route match or mismatch
Draft mismatch explanation
Send recommendation to team

CONNECTS TO

Dangerous-goods data (SAP EHS / Sphera / 3E)Read: hazard class, packing group. Write: none
Packaging spec master (SAP / Oracle / custom master)Read: approved UN codes by class. Write: none
ERP purchasing (SAP / Oracle / Microsoft Dynamics)Read: PO packaging lines. Write: mismatch flag on PO note
Notification (Slack / Microsoft Teams / Email)Read: none. Write: match confirmation and mismatch flags
WITHOUT PMS API

Without API access, the buyer pastes the product and packaging into a form or shares an SDS export, and the agent replies with the approved code and any mismatch. It cannot annotate the PO, so the recommendation lives in the notification channel only.

WITH PMS API

With API access to the SDS source and packaging master, the agent reads hazard class, packing group, and approved codes directly and can attach a mismatch note to the PO line for the buyer to see in context. Checks run the moment a line is raised. 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
Webhook Trigger - catches new PO lines
Expose a webhook the ERP calls when a hazardous PO line is raised or edited.
Output: A JSON payload with the product code and chosen packaging.
APINode 2
HTTP Request - fetch SDS hazard data
GET the SDS endpoint by product code to return hazard class and packing group.
Output: Hazard class and packing group for the product.
APINode 3
HTTP Request - fetch packaging spec
GET the approved packaging codes for that hazard class and packing group.
Output: A list of approved UN codes.
LLMNode 4
LLM - compare and explain
Send the PO packaging, hazard class, packing group, and approved codes.
Output: A match or mismatch verdict with the correct code.
You check dangerous-goods packaging for chemical purchase orders. Given hazard class {hazard_class}, packing group {packing_group}, the packaging on the order {po_packaging}, and the approved codes {approved_codes}, decide whether the order packaging is approved for this product. Respond ONLY with valid JSON. No explanation.
INPUT
{"hazard_class":"3","packing_group":"I","po_packaging":"UN 1A2/Y","approved_codes":["UN 1A1/X","UN 1A2/X"]}
OUTPUT
{"verdict":"mismatch","reason":"Packing group I requires an X-rated drum; UN 1A2/Y is rated for packing group II only.","recommended_code":"UN 1A1/X"}
DECISIONNode 5
IF - only mismatches escalate
Route mismatch verdicts to the note draft; confirm matches quietly.
Output: Two paths, match and mismatch.
ACTIONNode 6
Send - post the verdict
Format the verdict and post to the procurement and dispatch channel.
Output: A delivered message with the recommendation.
MVP vs Advanced — Where To Start
MVP — START HERE
  • Start with one product family and its SDS entries.
  • Load the approved packaging codes for those products into a simple table.
  • Trigger the check manually with a product code and a packaging code.
  • Return a plain match or mismatch with the correct code.
  • Post results to one channel buyers already watch.
  • Test against a known bad pairing to confirm it flags correctly.
ADVANCED — ADD LATER
  • Trigger automatically on every hazardous PO line from the ERP.
  • Attach the mismatch note directly to the PO line.
  • Extend to the dispatch side so packing is re-checked before a load ships.
  • =+ Add packing group and inner-packaging rules for combination packagings.
  • Track mismatch rates by buyer to target training.
  • =+ Add a temperature and compatibility check that suggests a different packaging when the material needs it, for a person to confirm.

Full Video Walkthrough Coming Soon

Watch the agent match a hazard class to its approved UN packaging and catch a mismatch.

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.

OTHER AGENTS IN LEASING & MARKETING

Tracks vendor licenses, insurance, and certificates, flags what expires soon
Flags off-contract and duplicate buys the moment the order is raised
Scores supplier reliability and gives buyers a realistic lead time

Frequently asked questions

Dangerous-Goods Packaging Checker is an AI agent that matches UN packaging codes to hazard class before the wrong drum ships.
The drum was UN-rated. It was rated for the wrong packing group. The Dangerous-Goods Packaging Checker addresses this: matches UN packaging codes to hazard class before the wrong drum ships.
No. Your team stays in control. The agent does not place orders or release shipments. Your buyer or dispatch lead does. The agent removes the manual cross-check between the SDS, the spec master, and the PO line.