Surface: EDI console or
https://api.edi.stateset.com. Prerequisites: a test partner,
scoped document-processing key, approved 850 sample, and configured effects you intend to
exercise. Success: linked document/response evidence for that partner and PO. Actual
partner and ERP acceptance need independent observations.1. Set up the relationship
Use onboarding to save test identifiers, required types, guide, transport, and current evidence. Review/v1/partners/{id}/readiness. An empty guide or
passing internal pack does not establish partner certification. Keep production held until
independent acceptance and production approval are current.
2. Validate and process the 850
The quickstart provides the actual requests. First callPOST /v1/edi/validate/{partner_id} and inspect the report. Then deliberately call
POST /v1/edi/inbound/{partner_id} with the unchanged approved wire.
Retain the interchange and document controls, partner/PO identity, response headers, and
full result. Inspect interchange and every document’s status. Return or deliver the
acknowledgment through the agreed transport; possession of a returned 997 is not evidence
that the retailer received it. A duplicate interchange is commonly 409; inspect the
original. Lost/truncated responses require ledger investigation before another attempt.
3. Acknowledge the commercial order
Open Orders for the partner and PO. An 855 commercial response is distinct from the 997 functional acknowledgment. Review per-line accept, reject, and backorder commitments. Preview the response, inspect policy findings, and retain its exact overrides, order revision, and idempotency key before dispatch.4. Ship and invoice the intended quantities
Prepare an 856 for the real shipment: remaining quantities, carrier/date, cartons, and SSCCs that match the actual printed labels. Support partial fulfillment deliberately; accepted or queued outbound quantities affect remaining order state. Prepare the 810 from current evidence. Review invoice identity/date, qualified product identity, decimal prices, allowances, and the intended total. A generated ASN or invoice does not establish shipment or payment. See reviewed sends and recovery.5. Recover uncertainty without duplicating a document
Persist the original reviewed operation. If a response is lost, inspect current evidence and explicitly retry with the same key, revision, and overrides. Restore access to the same workspace if necessary; an authentication failure does not prove a prior rollback. A new key can create a second intended document. Client/tab storage has its own durability limits, so integrations need durable original-request storage.6. Verify each outcome
Use operations and partner-scoped lifecycle/evidence to investigate.
The MCP demo creates synthetic test traffic and acknowledgment
fixtures; its completed loop does not establish actual retailer acceptance.