StateSet EDI

Exchange X12 and EDIFACT documents, review fulfillment, and follow transport, acknowledgment, and downstream evidence.

StateSet EDI validates and records trading-partner documents, generates outbound EDI, and tracks delivery and acknowledgments. The console adds company workspaces, partner setup, order fulfillment, mappings, exceptions, and evidence review. Agents use a JSON CLI or MCP server over the same API.

Reviewed October 20, 2026 against source 3f6b5c0 in stateset-edi. API and CLI: 0.10.2; JavaScript client: 0.1.3; MCP package: 0.2.1. The retained October 20 deployment identifies tagged source b1f7aa9. Later release-assurance commits and console recovery fixes have separate evidence; that record does not establish their deployment.

Choose your task

Task	Guide
Set up a workspace and qualify a relationship	Onboarding and readiness
Validate and process a test PO	Quickstart
Review partial fulfillment, carton labels, ASNs, and invoices	Orders and recovery
Configure transformations and customer callbacks	Mappings and callbacks
Operate through a terminal or JavaScript integration	CLI and SDK
Connect an MCP host	EDI MCP server
Review rollout, capacity, and recovery evidence	Deployment and qualification

Follow separate outcomes

Generated bytes, queued delivery, transport receipt, functional acknowledgment, and an ERP object establish different facts. A 997 does not establish fulfillment or payment. Retain partner, document, PO, event, delivery, request-key, and control-number identities. References can repeat across partners.

Platform coverage

• Documents: X12 purchase orders, acknowledgments, shipping, invoicing, inventory, routing, freight, and remittance; EDIFACT order and logistics messages.
• Transport: API/download, directory/VAN, tenant SFTP and FTPS connections, hosted SFTP, AS2 with MDN evidence, and durable email submission through StateSet Mail.
• Operations: connected order evidence, exceptions with revisions and history, reconciliation, deductions, audit, and explicit recovery actions.
• Integration: configuration-bound readiness, guide/mapping versions, cross-references, customer callbacks, and StateSet Sync receipts tied to the original connection.

The API reference covers 202 documented source operations. It is not an exhaustive inventory of internal handlers. The source MCP server exposes 167 tools; REST, SDK, and MCP coverage differ. REST adds X12 753 and EDIFACT INVRPT outbound generation beyond the SDK’s twelve outbound kinds.

Keep new relationships in test until their current guide, mapping, transport, counterparty acceptance, downstream acceptance, and production approval are recorded. An internal pack, deployed image, or synthetic test cannot supply a counterparty’s approval. Start with onboarding and the transaction inventory.