ModernEDI

Docs

Start with the workflow, then use the references

Start with a partner and a mapping. Keep X12 at the partner boundary and work with the JSON, XML, HTML, or text your systems use. Scenarios and external Git are optional: add them when you need conversation-level checks or repository synchronization, without leaving the browser.

Get Your First Document Flowing Try Mapper Demo

Evaluating ModernEDI? Follow a sample order or plan implementation and support.

Getting Started

From blank workspace to visible EDI traffic

Want to see how the optional pieces connect? Follow one mapping change from sample output to conversation evidence and configuration history.

ModernEDI does not make X12 your system of record.

Inbound X12 is mapped into the ERP, WMS, accounting, XML, JSON, or custom document shape your operation actually uses. That mapped document should become the source of truth for review, changes, fulfillment, and billing.

Activity normally keeps transaction documents and associated acknowledgements available for 12 months after processing so your team can investigate and recover operational history. It is not a legal archive or records-management service. Export and independently retain any records your organization must keep for business, tax, regulatory, contractual, or legal purposes.

When you need to send a reply such as an ASN or invoice, your integration sends that XML, JSON, or text source document to the /reply API. ModernEDI applies the matching outgoing map to generate and validate the partner's expected X12, then handles the AS2 delivery, receipts, acknowledgments, and transaction linkage around it. The /send API is available for standalone outbound documents. The main ModernEDI workflow keeps X12 at the trading-partner boundary: receive and acknowledge partner traffic, map it into the business document you operate from, then map replies or standalone source documents back into partner-ready X12 when you need to send.

  1. Confirm your workspace endpoint. Wait for provisioning to finish and check the managed AS2 URL and public certificate. Keep private keys and API credentials private.
  2. Add your first real AS2 connection and partner profile. Enter partner identifiers, URLs, certificates, signing and encryption choices, then use the setup sheet to hand off your ModernEDI values.
  3. Test and deploy the mapping you need first. Use a representative sample in Mapper, inspect the result, then review and deploy the map. Saving a draft does not change live processing.
  4. Confirm a real document, then connect your system. Check the partner document, mapping result, and required acknowledgments in Activity. Use the Integration API from your backend when you are ready to collect mapped output or send replies.

Want a rehearsal before exchanging partner traffic? The managed test-partner 850→810 exercise is optional. See what it checks and what it does not.

Ready to verify your own supplier conversation? Adapt the complete 850, optional 855, 856, and 810 example, including maps, sample documents, and per-item checks. Extend it to partial shipments and backorders when fulfillment arrives in installments.

For freight, the complete motor-carrier example connects a 204 tender, 990 decision, 214 shipment events, and 210 invoice.