How to Automate Labelmaster

Dangerous goods paperwork is a shipment's permission to travel

Labelmaster sells the physical parts of hazmat compliance, and it sells the software that decides what those parts should say. The labels, placards, packaging and publications are the visible half. DGIS, its Dangerous Goods Information System, is the half that runs in a browser and produces the declaration.

Dangerous goods shipping is unusual in that the paperwork is not administration, it is the permission. A drum of flammable adhesive can be perfectly packed and still be turned away at the counter because the proper shipping name is wrong, the packing group is wrong, or a mark is in the wrong place. The shipment does not travel, and depending on what went wrong, the consequences run past a delay.

The people who live in it are shipping clerks, hazmat coordinators and compliance managers at chemical manufacturers, laboratories, firms sending lithium batteries, and the warehouses that pack for them.

The declaration gets signed, and then the chasing starts

Getting the declaration right is the part the trade takes seriously. What surrounds it is where the week disappears.

A hazmat load delivers and the signed proof of delivery does not come back, so billing stalls and somebody starts working through the carrier's own document portal to find it. A shipment sits somewhere it should not, and finding out means opening a tracking page one shipment at a time. A carrier invoice arrives carrying a dangerous goods fee, a limited access charge and a reweigh, and setting those against the contracted rate takes longer than anybody has.

Then the dates. Training records with renewal deadlines on them. Carrier approvals and insurance certificates. A supplier revising a safety data sheet without telling anyone downstream. All of it lives in a spreadsheet only as current as the last person who opened it.

Labelmaster

Proof of delivery for DG loads collected Signed receipts pulled from whichever carrier document portal holds them and filed against the shipment, so billing is not waiting on a phone call.

Hazmat fees checked against the contract Carrier invoices compared line by line with the agreed rate, so a dangerous goods charge billed at the wrong band becomes a dispute rather than a rounding error.

Renewal dates surfaced weeks early Training records, carrier approvals and insurance certificates carried with their real expiry dates, so a lapse is caught before a shipment depends on it.

DGIS validates the shipment in front of it

DGIS handles the hardest and most consequential piece of this, far better than a shelf of binders did.

It validates shipment data against the current rules and updates itself as they change, drawing on U.S. DOT, IATA, ICAO, IMO and IMDG requirements plus carrier variations, so a shipment is checked against the 49 CFR, the IATA Dangerous Goods Regulations and the IMDG Code rather than somebody's memory. It stores the detail of every item shipped, pre-populates the fields on a dangerous goods declaration, and produces labels and marks diagrams showing where each one belongs on the package. It covers inner packaging validation, electronic signatures and training schedule management, and runs in the cloud with nothing installed. DGIS Web Services lets an ERP or WMS call the same content and validation and get shipping papers back.

All of that acts on a shipment being created, using data the system already holds. That is what it is for, and it is the shape of the ceiling.

Nothing in it walks over to the carrier's document portal for the delivery receipt, or to the invoice, or to the roster of who is due to be retrained, or to the supplier's site where a safety data sheet just changed revision. Those answers exist, on other companies' websites, behind other logins.

Renewal dates and carrier approvals that count themselves down

Every piece of evidence around a hazmat shipment already exists, filed on a portal belonging to a carrier, a supplier or a training provider. Nobody is reading those portals on a schedule.

Proof of delivery for dangerous goods loads collected from whichever carrier portal holds it and filed against the shipment, so the invoice goes out. Carrier invoices compared line by line with the contracted rate, so a dangerous goods fee charged at the wrong band becomes a list of disputes rather than a rounding error. In-transit shipments read each morning, so a hold is known the day it appears.

The dated obligations are the clearest win. Employee training records, carrier approvals and insurance certificates carried with their real renewal dates, counted down rather than remembered, so the reminder lands weeks ahead rather than the morning after. Supplier safety data sheets watched for a new revision, so the person who owns classification hears about it and can decide what it changes.

The boundary here is not a preference, it is the job. Gathering evidence, comparing numbers and flagging a date is safe to run unattended. Classifying a material, completing a declaration and signing it are the work of a trained hazmat employee, and they stay there.

Gathering evidence is not the same as certifying a shipment

Chasing a delivery receipt takes no hazmat qualification. Deciding what goes on a declaration takes one, and the two jobs should not be done by the same thing.

WebRun is an AI agent that works a real Chrome browser, signed in as you. It opens the carrier's document portal, the tracking page, the invoice or your own DGIS records, reads what is there, and produces the chase list, the dispute list or the expiry list.

It runs on your schedule in a private environment, and any run can be watched and stopped. Nothing is filed, submitted or sent on your behalf. Anything that leaves the building is drafted and read by a person first.

The workflows below are already built, and each one names the systems it opens.