EDI Inspector Lite · Free · Beta
Read an EDI 214, 204, 856, 211, 210, 820, 830 or 862 file as plain data
Paste a raw X12 file or load a sample, and EDI Inspector Lite, the free version of the Crucible EDI Inspector, shows you the shipments, stops, parts and charges inside it. It lists anything that looks wrong and gives you the JSON. There is no sign-up and no API key.
The contents of your file are never stored. See exactly what we log.
8
Document types read
Free
Lite: no account, no key
Not stored
File contents
What it does
From a raw 214 to a shipment you can read
On the left is what arrives from a carrier. On the right is what the inspector shows: the status, the last location, the delivery appointment and the reason for the delay.
B10*7741093*BOL558210*DEMO~ LX*3~ AT7*SD*BE***20260925*0640*ET~ MS1*TAYLOR*MI~ K1*I-75 NB CLOSED AT EUREKA RD~ AT7***AB*NA*20260925*1100*ET~
Toledo, OH → Sterling Heights, MI
- Last location
- Taylor, MI
- Delivery appt.
- Sep 25, 11:00 AM ET
Shipment delayed: road conditions
“I-75 NB closed at Eureka Rd”
Sample data shown. The parties and numbers are made up.
Try it now
Open the inspector with a sample file already loaded
Each button opens the inspector with a made-up file loaded and read for you. Every party and number in the samples is fictional, and each is marked as a test file.
214
Shipment status
A shipment picked up, in transit and booked for a delivery appointment.
Open this sample →204
Load tender
A truckload tender: pickup and delivery stops with dates, weights and PO.
Open this sample →856
Ship notice (ASN)
An advance ship notice with part, quantity and pack labels.
Open this sample →210
Freight invoice
Line-haul plus a fuel surcharge, adding up to the invoice total.
Open this sample →211
Bill of lading
A bill of lading with parties, commodity, weight and pallet count.
Open this sample →820
Remittance advice
A payment advice showing which invoice it covers.
Open this sample →830
Planning schedule
A weekly forecast with a past-due quantity, firm daily lines and cumulative received quantities.
Open this sample →862
Shipping schedule
A shipment-based schedule with past-due and firm requirements, a JIT time and container detail.
Open this sample →With problems
A file with problems
A 214 with a wrong segment count and an unknown status code, to show how problems are reported.
Open this sample →The eight documents
What each document is, and what you see
These are X12 transaction sets that carriers, shippers, suppliers and payers exchange. For each one, this is who normally sends it and what the inspector pulls out.
214Shipment Status
Sent by a carrier to report where a shipment is. You see the current status, every event with its time and location, the delivery appointment and the reason behind a delay or exception.
204Load Tender
Sent by a shipper or broker to offer a load to a carrier. You see the lane, every stop in order with its date window, weight and pieces, any hazmat, and the respond-by deadline.
856Ship Notice (ASN)
Sent by a shipper or supplier before freight arrives. You see the carrier, the PRO and bill of lading numbers, ship and delivery dates, and every part line with its quantity and cumulative quantity.
211Bill of Lading
Sent by a shipper to hand freight to a carrier. You see the shipper, consignee and bill-to, the references and requested dates, and every line of freight with its description, quantity, weight and class.
210Freight Invoice
Sent by a carrier to bill a shipment. You see the PRO and bill of lading it covers, who pays, the amount due and every charge in dollars, with a warning when the lines don’t add up to the total.
820Remittance Advice
Sent by a payer to say what a payment covers. You see the amount, whether it came by EFT or check, the payer and each PRO the money applies to. Bank account numbers are cut down to the last four digits.
830Planning Schedule
Sent by a manufacturer to its suppliers to forecast what it will need. You see the release and its horizon, each part’s requirements by week or day, any past-due quantity, and the cumulative quantities authorized and received.
862Shipping Schedule
Sent by a manufacturer to a supplier with the short-term requirements that sit on top of the 830. You see each part’s quantities and dates, whether those are ship dates or delivery dates, JIT times and container detail.
Real files are messy
It still reads the file, and it tells you what looked wrong
A file with a bad segment count or an unfamiliar code is still a file somebody sent you. The inspector reads what it can and returns it, then lists each problem it found: counts that don’t match, codes it doesn’t recognise, dates that look wrong and invoice lines that don’t add up to the total. When it isn’t sure of a value, it keeps what it was sent and warns you. It does not guess. Test files are labelled as tests.
Privacy
What we log, and what we don’t
Your file is read in memory and the result goes back to you. This is the whole record the tool keeps about each use.
We keep
- A fingerprint of the file (a hash), so we can see when the same file is sent twice
- The file’s size
- The document types it contained
- How many records and how many warnings it produced
- Whether it was marked as a test file, and whether the request worked
We don’t keep
- The contents of your file
- The translated result
- Your IP address, in this usage log
We keep the counts because the document types people bring, and the problems found in them, tell us what to build next. Separately, this website and the inspector page count visits with an analytics tool we host ourselves, which does not set cookies.
Beta, plainly
What it does today, and where it stops
The readers were built from published carrier and shipper implementation guides and checked against the example files those guides print. They have not yet been checked against production files from every trading partner, which is why this is a Beta.
X12 only
EDIFACT, EANCOM and other X12 document types are not supported yet.
Reads and flags, doesn’t validate
It does not check a file against one trading partner’s own specification.
256 KB a file, 10 files a day
These are Lite’s limits, per visitor, and the sample files don’t count toward them. The full EDI Inspector takes files up to 5 MB through the API.
Nothing is sent into Crucible
Files you inspect here are read and returned. Feeding shipments into monitoring needs an API key.
Send us your messiest file
If a file reads wrong, we want to see it
If the inspector misreads a file, or warns about something you know is fine, send it to [email protected]. Take out names and addresses first if you like, because we mostly need the structure. We will tell you what we found, and if the reader got it wrong, we will work on fixing it.
Email a fileQuestions
Common questions
Is EDI Inspector Lite really free?
Yes. There is no account, no card and no API key. Lite reads files up to 256 KB, and each visitor can read 10 of their own files a day, so the capacity stays available to everyone. The sample files are not counted. The full EDI Inspector, with larger files, API access and 214 status files feeding Crucible monitoring, is also free for Crucible clients and for carriers and logistics providers on the Crucible network.
Do you keep my EDI file?
No. The file is read in memory and the result is sent back to you. The usage log keeps only a fingerprint of the file, its size, the document types it contained, counts of records and warnings, and whether it was marked as a test file.
Which EDI formats does it read?
X12 documents of eight types: 214 shipment status, 204 load tender, 856 ship notice, 211 bill of lading, 210 freight invoice, 820 remittance advice, 830 planning schedule and 862 shipping schedule. EDIFACT, EANCOM and other X12 document types are not supported yet. If you use one, email [email protected] with a sample file.
How accurate is the EDI inspector?
It is in Beta. The readers were built from published carrier and shipper implementation guides and checked against the example files those guides print. They have not yet been checked against production files from every trading partner. When the inspector is unsure of a code or a value, it keeps what it was sent and adds a warning instead of guessing, so read the warnings.
Does it validate my file against my trading partner’s specification?
No. It reads the file, shows what it contains and flags what looks wrong. Checking a file against one partner’s own implementation guide is a different job.
What is a test interchange?
The interchange header carries a usage indicator in field 15 (ISA15): T for test, P for production. The inspector labels test files so nobody mistakes sample data for live freight. The sample files here are all marked as test.
Need more than Lite?
The full EDI Inspector is free for Crucible clients and for carriers and logistics providers on the Crucible network. With an API key you can post files up to 5 MB straight from your own systems and receive JSON back, and carriers can have their 214s feed Crucible monitoring. Not on the network yet? Ask us how to join.
The inspector is built by Agentic Alchemy, founded by a supply chain operator, as part of Crucible, a road freight and parcel visibility platform.