How to process (extremely) large EDI files with Stedi
Large EDI files are common across many industries, including healthcare (such as 834 Benefit Enrollments), logistics (210 Motor Carrier Freight Details and Invoices), and retail (846 Inventory Advice). Unlike most other EDI solutions, Stedi has virtually no file size limitations and can process EDI files that are gigabytes in size.
However, large files that have been translated into JSON still pose significant challenges for downstream applications. The translation ratio of an EDI file to JSON is typically 1:10, which means that a large EDI file can easily produce a multi-gigabyte payload that is difficult for downstream applications to receive and ingest.
Use fragments to split large transactions
INS
segment – or a brand may send an 846 Inventory Inquiry/Advice file containing millions of SKUs – each one in the LIN
segment.INS
loop in an 834, Stedi emits batches of INS
loops instead of a single giant JSON payload.fragment.processed.v2
event, which you can use to automatically send Destination webhooks to your API. Fragment processed events contain details about the original transaction as well as the actual fragment payload itself.Configure fragments
Set up the Stedi guide
First, you need to enable fragments in the Stedi guide for the transaction.
ON
, and click Publish changes.Create a transaction setting
ON
.Send fragments to your API
fragment.processed.v2
events to a Destination webhook. curl --request GET \
--url https://core.us.stedi.com/2023-08-01/transactions/{transactionId}/fragments/{fragmentIndex} \
--header 'Authorization: Key {STEDI_API_KEY}'
Get started on Stedi
Build an end-to-end integration in under 15 minutes. Automate exchanging EDI with any trading partner. Monitor transaction history and analyze your EDI data in real time.
Get blog posts delivered to your inbox.