Skip to main content

StateSet EDI

StateSet EDI is a multi-tenant X12 and EDIFACT gateway. It receives trading-partner documents over any common transport, strictly validates and translates them into StateSet VES events, acknowledges every functional group with a 997 (and every malformed interchange with a TA1), generates outbound order-lifecycle documents from StateSet-shaped JSON, and confirms delivery back to the partner — tracked, retried, and reconciled. It is built on the same stack as the Sync Server: Rust, axum, tokio, serde, reqwest (rustls), tracing, and Prometheus.

Highlights

Five transports

HTTP API, file/VAN directory drop, native SFTP client, AS2 (signed and encrypted, with MDN receipts), and AS1 (EDI over email).

Confirmed delivery

Outbound AS2 is tracked, MDN-confirmed, retried with exponential backoff, and dead-lettered with an alert on failure.

Strict, certifiable

One inbound endpoint auto-detects the syntax — X12 answers with a 997, EDIFACT with a CONTRL. Envelope validation, per-partner implementation guides, exact-decimal money, and replay-proof event IDs.

Retail-ready

40+ packaged retailer connectors and UCC-128 / SSCC-18 label generation.
Additionally:
  • Multi-tenant, with a WorkOS-SSO operator dashboard.
  • HA-ready — every coordination store shares through Postgres.
  • Operational alerting to Slack-compatible webhooks and email.
  • MCP server exposing 117 agent-callable tools.

Document flow

The same pipeline — dedup, validate, translate, queue, acknowledge — runs behind every transport, so a partner can move between transports without any code changes.

Beyond the wire

The gateway does more than move documents. It also covers the operational surface that EDI programs actually run on:

Next steps

Quickstart

Run the gateway and process your first 850.

Transaction sets

Every supported X12 set and its direction.

Transports

HTTP, file/VAN, SFTP, AS2, and AS1.

MCP server

Drive EDI flows from Claude with 117 tools.