Sign in to Orderful's Mosaic platform and connect your ERP or order management system via a single API integration (REST or webhook) — Orderful handles all partner-specific EDI mapping on its end.
When Orderful delivers an inbound 850 PO as a JSON object to your webhook, extract the orderNumber, lineItems, and buyerParty from the payload.
For each inbound 850, construct a JSON 855 acknowledgment body following Orderful's schema, setting the acknowledgmentCode to 'AC' (accept), 'RJ' (reject), or 'PO' (partial) at line-item level as appropriate.
POST the 855 JSON to Orderful's outbound API endpoint using your API key; include the trading relationship ID (partnershipId) to route the document to the correct retail buyer.
Orderful translates the JSON to X12 EDI, wraps it in the correct ISA/GS envelope for that retailer, and delivers it via the agreed transport (AS2, SFTP, VAN).
Confirm successful delivery via Orderful's transaction status API or dashboard — look for a 997 Functional Acknowledgment from the retailer confirming receipt at the EDI layer.
Known gotchas
Orderful's platform normalizes partner-specific EDI variations into a consistent JSON schema — do not try to reverse-engineer retailer-specific X12 quirks in your application code; rely on Orderful's mapping layer.
Response SLAs for 855 acknowledgments vary by retailer compliance guides — some retailers impose a 24-hour window after 850 receipt; missing this SLA can trigger chargeback fees.
Orderful charges per transaction in most plans — test with sandbox transactions to avoid incurring costs for failed integration attempts.
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