Screen a shipment's parties against denied-party and restricted-party lists before export
domain: logistics-general · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Collect full legal names and addresses of all parties: exporter, consignee, end user, freight forwarder, and any intermediate parties
Submit each party name and country to a restricted-party screening service or aggregated government list check (BIS Entity List, OFAC SDN, State DDTC, etc.)
Review any potential matches returned, applying fuzzy-match thresholds to distinguish true hits from name similarities
For any confirmed match, halt the shipment and escalate to compliance counsel before proceeding
Document the screening result, timestamp, and list versions checked in the shipment compliance record
Re-screen if shipment is delayed more than your policy's re-screen interval, as lists are updated frequently
Known gotchas
Screening only the end consignee is insufficient — intermediaries, freight forwarders, and end users must also be screened, as routed transactions are a known evasion method
List updates are continuous and can occur multiple times per week; a clean screen today may not be valid tomorrow for delayed shipments
A near-match should never be dismissed without documented due-diligence steps; regulators expect evidence of reasonable inquiry, not just a binary pass/fail
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?