Discuss onboarding

EDI for retail suppliers

Check your retail EDI before you send it.

Review supported purchase-order checks, find segment and element errors, and prepare your trading relationships for testing. Each customer's production connection requires its own guide review and partner acceptance.

Discuss onboarding
10 retailer guides built in X12 + EDIFACT AS2 · SFTP · VAN · API delivery 999-grade element-level errors
stateset-edi · compliance check

Free EDI compliance checker

Paste (or drop) an X12 purchase order to run the implemented checks for the selected profile. Results cover these checks, not complete retailer certification. No account required.

Your file is validated in memory and not stored. If you request the fix report below, we keep the excerpt you submit (first 4,000 characters) so we can annotate it — nothing else, nothing shared.

Want the annotated fix report + a mapping that passes?

Drop your email and we'll send a line-by-line fix for this file and a compliant version you can diff against.

This file passes. Shipping compliant EDI at volume is the next problem.

Configure your organization, trading partners, mappings, and transport. Validate test exchanges and collect acceptance before scheduling production.

Discuss onboarding

How it works

Three steps to clean EDI.

No mapping spreadsheets, no "best effort" translation. Your retailer's guide is executable rules in our engine.

01 / CONNECT

Point your feed at us

AS2, SFTP, VAN, or plain HTTPS API — we speak all four. Your retailer's connectivity requirements are part of their profile, not your problem.

02 / VALIDATE

Every document, against the real guide

Required segments, mandatory references like REF*DP, allowed element values, length bounds, conditional rules — checked before transmission, reported with 999-grade positions.

03 / TRANSMIT

Signed, acknowledged, auditable

Documents go out signed, acks (997/999) are matched automatically, and every interchange is queryable when the retailer's ops team comes asking.

Coverage

Retailer guides, built in.

Profiles implement selected guide checks. Confirm the program, document types, version, and current requirements with your trading partner before use.

Why suppliers switch

Errors you can act on, not decode.

Element-level violations

Not "document rejected" — the exact segment, element, and offending value, the way a 999 would report it.

850 is missing required
reference REF*DP
BEG-02 value 'ZZ' is not
allowed (expected BE, RL, SA)

Internal validation packs

Profiles include positive and negative fixtures for implemented checks. These are internal tests, separate from counterparty acceptance, and the sample pack is public.

Review before transmission

Use document validation alongside warehouse and shipping controls. Fulfillment accuracy and retailer acceptance require operational checks beyond EDI syntax.

Plan your next trading connection.

Start with your document requirements, transport, ERP or WMS, and expected volume. Go-live depends on completed testing and approval for your specific relationship.

Discuss onboarding