Hazmat Segregation Compatibility Checker
Build an internal tool that checks every hazmat putaway against your own segregation matrix, flags incompatible storage before it happens, and routes risky placements to a safety lead for sign-off.
A login-protected tool where you propose a location for a hazmat item, it checks the segregation matrix against the neighbors and the zone, flags any conflict, and a safety lead approves or overrides with a written justification before the putaway is allowed to commit - with a full audit trail and a CSV compliance record.
Before you start
- A list of your items with their hazard classes (a spreadsheet is fine)
- Your segregation / incompatibility matrix (which classes can't be stored near which)
- A location / zone map that marks which zones are hazmat-approved
- Free Supabase, Vercel, and Resend accounts (the plan walks you through them)
The problem this kills
A receiver finds an open slot, drops a pallet of an oxidizer next to a stack of flammables, and walks away. Nobody meant to break a rule - the segregation matrix lives in a binder, the approved-zone map lives in someone's head, and the pressure is to get the dock cleared. Weeks later an auditor or, far worse, an incident makes the mistake very expensive.
The knowledge to prevent this already exists in your building. It's just not in the moment, in front of the person making the call. This tool puts your own segregation rules into the putaway decision itself: propose a location, get an instant compatibility check against the neighbors and the zone, and never let a flagged placement commit without a safety lead's eyes on it.
What you'll build
A small, login-protected web app for your team:
- Propose a putaway. Pick a hazmat item and a candidate location.
- Automatic segregation check. The tool reads your matrix and compares the item's hazard class against whatever is already stored in and around that location - and confirms the zone is even approved for that class.
- Clear conflict flags. Green to go, or a plain-language list of exactly which neighbor and which rule is the problem.
- A human gate. Flagged placements can't just proceed. A safety lead reviews and either approves, or records an override with a written justification.
- An audit trail and CSV compliance record. Who proposed what, who approved or overrode it, when, and why - exportable for audits.
What's inside the Implementation Plan
- It starts by interviewing you about your business. Before writing a single line, the plan has the AI agent ask about your hazard-class scheme, the exact shape of your item and location data, how your matrix is laid out, which zones are approved, your volumes, and your real approval rules. It reflects a short tailored spec back to you for a thumbs-up - so you get a tool built around your warehouse, not a generic template.
- A step-by-step build, each step ending in a ready-to-paste prompt for your AI coding agent.
- Your own segregation matrix and approved-zone map as the source of truth - you supply them, the tool enforces them.
- Override justifications captured and stored for audits.
- A duplicate guard so the same item + location + check can't be logged twice.
- A "No API yet?" fallback: load items, matrix, and zones from spreadsheets and export the compliance log as CSV - so it's fully buildable today, with no integration to your WMS required.
The governance it includes (this is the point)
This isn't a toy. The plan builds in the controls a safety-critical process demands:
- Login so only your team can use it.
- Row-level security so each organization only ever sees its own items, matrix, and decisions.
- A complete audit trail - every proposal, check, approval, and override, with timestamps and the person responsible.
- A hard human-in-the-loop gate - the tool flags and drafts, but a safety lead must approve (or justify an override) before any putaway is allowed to commit.
- Duplicate guards so the same check can't be recorded twice.
Who it's for
EHS coordinators, hazmat receivers, and warehouse safety leads who own dangerous-goods storage compliance and want the segregation rules enforced at the moment of putaway - not discovered after the fact. No coding background needed.
You've got this - paste the first prompt and let the agent interview you.