In the Stedi dashboard, create a new Trading Partner profile with the partner's ISA/GS identifiers (qualifier + ID) that will appear in the interchange envelope headers.
Configure the partnership: select the transaction sets you will exchange (850, 855, 856, 810), and set the direction (inbound PO from retailer, outbound ASN/invoice to retailer).
Build or import a Guide for the 850 transaction set — Stedi's Guide editor lets you define which segments and elements are required for this specific partner, overriding the base X12 standard where the retailer deviates.
When a PO arrives (via SFTP, AS2, or Stedi's API endpoint), Stedi translates it to JSON (JEDI format) and delivers it to your webhook or S3 bucket; parse the JSON to extract orderNumber, lineItems, shipToAddress, and requestedDeliveryDate.
Acknowledge the PO by constructing an 855 JSON payload following the JEDI schema and calling POST /2024-01-01/x12/translate to convert it to X12, then POST /2024-01-01/partnerships/{partnershipId}/outbound to send it to the retailer.
Monitor transaction status in the Stedi UI or via GET /2024-01-01/executions/{executionId}/transactions to confirm delivery and detect any interchange-level acknowledgment (997/999) failures.
Known gotchas
Each retailer has a unique EDI implementation guide that deviates from the base X12 standard — always obtain the retailer's vendor compliance guide before finalizing your Stedi Guide configuration; mismatched segment qualifiers cause 997 rejection.
ISA control numbers must increment sequentially and be unique per interchange; Stedi manages this automatically when using outbound API endpoints, but if you inject raw X12 you must manage control numbers yourself.
Stedi's JEDI JSON format uses the X12 segment names as keys — familiarize yourself with the mapping between JEDI property names and the corresponding X12 loop/segment/element positions in the 850 spec.
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