Map shipment data to EDI 300 segments: BK1 (booking identification), Y4 (container information), W09 (equipment characteristics), and R4 (port/place information)
Build the ISA/GS envelope with the trading partner's interchange and group control numbers
Submit the 300 transaction set to the carrier's EDI VAN or AS2 endpoint and capture the 997 functional acknowledgment
Poll or receive the carrier's EDI 301 booking confirmation; parse the BK1 confirmation number and vessel/voyage details
Reconcile booking reference numbers across your TMS and the carrier's confirmation before issuing shipping instructions
Known gotchas
EDI 300 and 301 are ocean-specific ANSI X12 transaction sets; do not confuse them with 850/855 purchase order transactions used in retail
The 997 functional acknowledgment confirms envelope receipt only — a separate 301 is required to confirm the carrier has actually accepted the booking
Vessel, voyage, and port codes in the R4 segment must match the carrier's published schedule; mismatches cause silent rejections at some carriers
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp