EDI to JSON Converter – Documentation

Overview

EDI to JSON is a browser-based tool that converts Electronic Data Interchange (EDI) documents into structured JSON data. It allows developers, analysts, and integration engineers to inspect and transform EDI messages quickly without installing specialized software.

The converter parses common EDI standards such as X12, EDIFACT, HIPAA transactions, and TRADACOMS. Once parsed, the EDI segments and elements are transformed into a JSON representation that can be easily consumed by modern applications, APIs, and data processing pipelines.

All processing happens locally inside the browser. Files are never uploaded to a server, ensuring full privacy and security for sensitive business documents.

The tool is built using Toflio, a Markdown-to-PDF rendering platform, which powers the structured document pipeline used by this application.


Key Features

Client-Side Processing

All EDI parsing happens directly inside the browser. No file uploads or server processing occur. This ensures that sensitive business data remains on the user's machine.

Multi-Standard Support

The parser supports multiple EDI standards used across different industries including logistics, healthcare, retail, and manufacturing.

Large File Support

The converter can process files up to 100 MB in size depending on browser memory limits.

Developer Friendly Output

The output JSON structure is designed to be easy to inspect and integrate into modern applications.


Supported EDI Standards

The parser supports the following EDI formats:

ANSI X12

Commonly used in North America for business transactions such as purchase orders, invoices, and shipping notices.

Examples include:

  • 850 Purchase Order
  • 810 Invoice
  • 856 Advance Ship Notice
  • 837 Healthcare Claim

EDIFACT

A global EDI standard used widely in Europe and international trade.

HIPAA Transactions

Healthcare transactions built on top of the X12 standard.

TRADACOMS

An older standard used mainly in UK retail systems.


Supported File Types

The converter accepts the following file formats:

  • .edi
  • .x12
  • .dat
  • .txt

Maximum supported file size: 100 MB

Files larger than this limit may exceed browser memory constraints.


How the Converter Works

The tool processes EDI files using a multi-stage parsing pipeline.

1

Step 1 – File Loading

The EDI file is loaded into the browser using the FileReader API. No data is transmitted externally.

2

Step 2 – Format Detection

The parser automatically detects the EDI format by inspecting control segments such as:

  • ISA (X12)
  • UNB (EDIFACT)
  • UNA (EDIFACT service string advice)
3

Step 3 – Segment Parsing

EDI messages consist of segments separated by delimiters. The parser splits the message into segments and extracts the segment identifier.

Example segment:

ISA*00* *00* *ZZ*SENDERID*ZZ*RECEIVERID*210101*1253*U*00401*000000905*0*T*~
4

Step 4 – Element Extraction

Each segment contains multiple elements separated by element delimiters (typically * in X12).

Example:

ISA*00* *00* *ZZ*SENDERID

becomes:

  • ISA01 = 00
  • ISA02 = (blank)
  • ISA03 = 00
  • ISA04 = (blank)
  • ISA05 = ZZ
  • ISA06 = SENDERID
5

Step 5 – JSON Conversion

Segments and elements are structured into a JSON document.

This JSON structure allows developers to easily inspect or transform EDI messages.


Example Conversion

Example EDI Input

ISA*00*          *00*          *ZZ*SENDERID      *ZZ*RECEIVERID    *210101*1253*U*00401*000000905*0*T*~
GS*PO*SENDER*RECEIVER*20210101*1253*1*X*004010~
ST*850*0001~
BEG*00*SA*123456**20210101~

JSON Output

{
  "meta": {
    "format": "X12",
    "transactionType": "850"
  },
  "segments": [
    {
      "segment": "ISA",
      "ISA01": "00",
      "ISA02": "",
      "ISA03": "00",
      "ISA05": "ZZ",
      "ISA06": "SENDERID"
    },
    {
      "segment": "GS",
      "GS01": "PO",
      "GS02": "SENDER",
      "GS03": "RECEIVER"
    },
    {
      "segment": "ST",
      "ST01": "850",
      "ST02": "0001"
    }
  ]
}

This structured output allows the data to be used in:

  • APIs
  • databases
  • ETL pipelines
  • analytics systems
  • integration platforms

How to Use the Tool

Upload an EDI File

  1. Open the converter page.
  2. Drag and drop an EDI file into the upload area.
  3. Alternatively click Select File and choose a file from your computer.
  4. The file will be parsed instantly.
  5. View the structured JSON output in the viewer.

Paste EDI Text

You can also convert EDI messages without uploading a file.

Steps:

  1. Switch to Paste Text mode.
  2. Paste the raw EDI message.
  3. Click Process Text.
  4. The parser will convert the message to JSON.

Quick Clipboard Parsing

The tool also supports direct clipboard parsing.

If you copy an EDI message and press Ctrl + V anywhere on the page, the tool will automatically detect and parse the content.


Privacy and Security

EDI documents often contain sensitive business information including:

  • purchase orders
  • invoices
  • shipment details
  • healthcare claims
  • financial data

For this reason the converter follows a strict privacy model.

No File Uploads

Files are processed locally and never transmitted to external servers.

No Data Storage

The application does not store files, logs, or document content.

No External APIs

The parsing engine runs entirely inside the browser.

This architecture ensures that confidential business documents remain private.


Performance

Modern browsers can handle large EDI documents efficiently.

Typical performance characteristics:

File SizeApproximate Parse Time
1 MB< 100 ms
10 MB< 500 ms
50 MB1–2 seconds
100 MB2–4 seconds

Performance may vary depending on browser and system memory.

Limitations

While the parser supports common EDI standards, certain limitations exist.

Non-Standard Custom Segments

Some trading partners use custom segments that may not be fully interpreted.

Malformed EDI Files

If the file does not follow correct delimiter or segment structure, parsing may fail.

Extremely Large Documents

Files exceeding 100 MB may exceed browser memory limits.

Use Cases

The EDI to JSON converter is useful in several scenarios.

Debugging EDI Transactions

Developers can quickly inspect EDI messages during integration testing.

API Integration

JSON output can be used directly in REST APIs and microservices.

Data Transformation

The JSON structure allows easier transformation into databases or analytics pipelines.

Documentation

Integration teams can convert EDI messages into readable formats for internal documentation.


About Toflio

This tool is built using Toflio, a Markdown-to-PDF platform designed for generating structured documents.

Toflio provides reliable document rendering pipelines used for technical documentation, reports, and data exports.

Learn more about Toflio at:

https://www.toflio.com

Future Improvements

Planned improvements include:

  • downloadable JSON files
  • EDI validation against standards
  • segment documentation
  • schema visualization
  • CSV and XML export formats

Conclusion

EDI remains a critical standard in many industries, but its raw format can be difficult to inspect and integrate with modern systems.

This EDI to JSON converter simplifies the process by transforming structured EDI messages into developer-friendly JSON while preserving privacy through client-side processing.

It provides a fast, secure, and accessible way to inspect and work with EDI data directly in the browser.