Skip to main content
Open https://edi.stateset.com, sign in with StateSet WorkOS, and select your workspace. A verified user without an organization can create one; existing company members should use an invitation from their administrator. Administrators manage connections and keys; viewers inspect operations.

​
Follow Get started

The console’s Get started page shows the next action and saved evidence for each relationship. Links retain the selected partner. A saved hold or unavailable readiness takes precedence over moving forward.
  1. Add a test partner. Enter agreed sender/receiver qualifiers and IDs, X12 version, supported inbound types, and intended transport. Use the current counterparty guide.
  2. Validate representative wire. The X12/EDIFACT dry run reports findings without processing an order. Correct the source, guide, or mapping before proceeding.
  3. Create a scoped integration key. Read-only supports observation; document processing adds validation, inbound processing, and outbound generation. Use a key per integration.
  4. Configure transport and downstream connections. Test the actual route; saving a credential does not establish exchange or ERP acceptance.
  5. Collect current evidence. Read the partner’s readiness report after changes.

​
Evidence and production

Readiness identifies configuration, eligible evidence, and production blockers. Guide and mapping review, transport tests, internal validation, counterparty acceptance, downstream acceptance, and production approval have separate roles. Changed identifiers, mappings, policy, transport, or fixture packs can invalidate earlier evidence. The standard runner includes positive and negative synthetic cases for configured supported inbound types. An unrestricted relationship selects 23 X12 and 10 EDIFACT types. This checks the parser baseline; add approved partner-specific fixtures for the actual guide. Fixture verdicts do not automatically advance onboarding.
Keep the relationship in test until its enforced onboarding stages and production setting are approved. Certified and live are different states. Internal packs and attributed operator attestations do not supply independent counterparty acceptance.

​
Connect StateSet Sync

Configure the ERP connector in Sync, then provide its tenant ID, API key, and webhook secret in Connections. Test and production need separate Sync tenants. The signed setup probe is a no-op and creates no order. A binding applies across the workspace’s partners in that environment. Inspect /v1/connections/sync/deliveries for receipts and /v1/connections/sync/deliveries/{event_id}/outcome for related observations. A StateSet order ID establishes Sync acceptance; qualify the actual ERP object and duplicate outcome separately. Retain the original connection’s evidence and stale-evidence warnings.

​
Complete an approved test exchange

Run the quickstart, then prepare order responses. Collect actual transport receipts, functional acknowledgments, physical-label acceptance where needed, and ERP object IDs. Include duplicates, delayed responses, rejection, change, and cancellation recovery. Agree on cutover and recovery ownership before production. For support retain workspace, partner, document/reference or correlation ID, timestamp, observed error, and expected result. Keep credentials in your secret store.
Last modified on October 20, 2026