Establish an AS2 or SFTP trading partner agreement with the carrier's EDI hub to receive inbound 310 transactions
Parse the B3 segment to extract the bill of lading number, vessel, voyage, and port of loading/discharge
Extract cargo detail from the L5 and L0/L1 loops including commodity description, package count, weight, and volume
Map the N1 loops to shipper, consignee, and notify party entities in your system using the N1 qualifier codes
Validate the 310 data against the 304 shipping instructions to confirm all cargo details are correctly captured before releasing documents
Known gotchas
The 310 is the carrier's authoritative ocean bill of lading; discrepancies between the 304 instructions and the 310 must be corrected via amendment before the vessel sails
Some carriers issue the 310 only after departure; systems that trigger downstream processes on 310 receipt must account for this timing
Negotiable versus non-negotiable (straight) bill of lading status is carried in the B3 segment and affects how the document can be used for title transfer
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