What is EDI, and what does a small supplier need to get started?
Short answer: EDI, short for electronic data interchange, is a standard way for two companies' computer systems to swap business documents such as purchase orders, ship notices and invoices without anyone retyping them. Your customer sends an order (an 850), you send back a ship notice (an 856) and an invoice (an 810). A small supplier can usually start with a hosted web EDI service and connect it to its accounting or ERP system later.
A big customer just told you to get on EDI by a certain date, and you want to know what it is, what it touches and what you actually have to do first.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
What is EDI?
The letters stand for electronic data interchange. Cleverence, a warehouse software company, defines it as the computer-to-computer exchange of business documents between companies, replacing paper, email and fax with standard electronic formats.
Think of a purchase order. Today it may arrive as a PDF, and someone on your team types it into your system. With EDI the order arrives as a data file in an agreed layout. Your system reads it with no typing. The same thing happens in reverse when you confirm the order, ship it and bill for it.
Large buyers and retailers use EDI because they handle thousands of orders. They cannot read thousands of emails. So if you want to sell to them, you often have to accept orders and send documents in the form they set. That is why the request usually arrives as a rule in a supplier agreement, not as a suggestion.
Which documents does EDI use?
Every document type has a number. These are the ones a supplier meets first, as described by Cleverence and Orderful (an EDI platform that publishes plain guides and prices).
| Number | Document | What it does |
|---|---|---|
| 850 | Purchase order | The customer's order to you |
| 855 | Purchase order acknowledgment | You confirm the order, and note any changes to quantity, price or date |
| 856 | Advance ship notice (ASN) | You tell the customer what is in the shipment before it arrives |
| 810 | Invoice | You bill for what shipped |
| 846 | Inventory advice | You report stock levels |
| 997 | Functional acknowledgment | A receipt that says the file arrived and could be read |
A basic customer may ask for only three: the 850 in, then the 856 and 810 out. Ask yours for the exact list before you pay for anything.
One trap: a 997 shows the file was delivered and readable. It does not show the contents were right. That gap is why customers also check the data inside each document, and why bad data leads to fines (often called chargebacks) even when every file went through.
What are the EDI formats?
The format is the rulebook that sets the layout of each document. Two matter. X12 is the main standard in North America. The X12 organization says it has been chartered by the American National Standards Institute for more than 40 years and lists more than 320 transaction standards. EDIFACT is the global standard, maintained by the United Nations and common in Europe and international trade.
If you sell to US buyers, expect X12. If you sell to European buyers, ask whether they use EDIFACT. Your provider handles the format. You will never write it by hand. Many customers also add their own rules inside the standard, which they publish as an implementation guide. That guide is the document you will read most.
How do EDI documents travel?
The file has to get from their computer to yours. TrueCommerce, an EDI provider, describes the common routes. A value-added network is added below as a common older option.
- SFTP: a secure file transfer over an encrypted connection with a login. It is commonly used for batches of files.
- AS2: a widely used standard for sending files securely over the internet, with encryption, digital signatures and delivery receipts. TrueCommerce calls it a preferred choice for retail and supplier networks.
- HTTPS: web-based, often used for real-time exchange.
- API exchange: sending structured data through an API (a way for one program to talk to another) instead of batch files.
- VAN: a value-added network, a third-party mailbox service that passes messages between partners. IBM describes VANs as one of the two common ways to exchange EDI documents.
So EDI versus SFTP is a question of layers. EDI is the document layout. SFTP is one of several roads the file can travel on. Your customer may require one road, so ask which.
What is the difference between EDI and an API?
IBM compares them this way. EDI uses strict standards such as X12 and EDIFACT, traditionally in scheduled batches, though modern setups can run near real time. An API uses flexible formats such as JSON and XML and lets one system ask another for specific data on demand. EDI setup needs mapping and specialist knowledge. APIs are usually quicker to build but need developers. IBM also says the two are not rivals, and many companies use EDI for stable, routine documents and APIs for speed and visibility.
For a small supplier the choice is rarely yours. The customer picks the method and you follow it. You only get a say on how your side connects.
What is the difference between EDI and an ERP?
An ERP, short for enterprise resource planning, is the software inside your company that holds items, orders, stock and invoices. QuickBooks, an accounting program, plays that role in many small firms. EDI is how that system talks to your customer's system. You need both.
If nothing connects them, someone reads each EDI order on a screen and types it in. That works for a few orders a week. It fails at scale. When you are ready for that step, see how EDI orders get into QuickBooks, Shopify or an ERP.
What are the alternatives to EDI?
- Email and PDF orders. Easy for the buyer. Your team types each one, though software can now read these and match them to your items. See email order processing.
- A customer portal. The buyer keys the order into your site. You still need it to land in your system. See a B2B portal that works with QuickBooks.
- An API link. The buyer's system calls yours. Both sides need developers.
- Web EDI. A hosted service where you work in forms in a browser instead of connecting systems.
If a customer requires EDI, none of these replaces it for that customer. They can still help with every other customer you have.
A worked example (made-up figures)
Say I run a small hardware supplier with 6 people. A regional chain says: send 856 and 810 for every order, starting in 8 weeks. They send about 25 orders a month, about 3 lines each.
That is 25 orders in (850), plus 25 ship notices and 25 invoices out, roughly 75 documents a month, for one trading partner (a customer you exchange EDI with). Retyping 25 orders at about 6 minutes each is 2.5 hours a month. Not painful. A web EDI service fits. Now say the chain grows to 250 orders a month, and two more chains ask for EDI. Retyping becomes 25 hours a month, mistakes cost fines, and a link to the accounting system starts to pay for itself.
The lesson: the volume and the number of customers decide the setup, not the word EDI.
What do I need to start as a small supplier?
- Get the customer's EDI guide. Ask for the document list, format, transport method and the date they want you live.
- List what you must send. Most customers want the 850 in, and the 856 and 810 out. Some want 855 and 846 too.
- Ask if they require a provider. Some buyers recommend one, but TrueCommerce says you can use any provider no matter who your trading partners use. Ask your customer if they need a certification test.
- Count partners and documents. This decides which price model fits. See what EDI software costs a small supplier.
- Pick web EDI or a connected setup. Web EDI is cheapest to start. A connected setup removes retyping.
- Test before you go live. Send sample documents and fix errors before real orders flow.
If you are comparing two of the big names, read SPS Commerce vs TrueCommerce.
When is a layer on top worth building?
An EDI provider moves documents. It does not run your business rules. Things like checking stock before you confirm, flagging a price that does not match your price list, or splitting one order into two shipments still depend on your own systems. That glue is where custom work earns its keep. If you want an overview of what that kind of work involves, my page on AI integration services explains it. I would build only after the EDI link is live and the retyping is a real cost.
How I'd approach this
I would not start by shopping for software. I would start with the customer's EDI guide and one question: how many orders a month will this customer send? If it is under about 50, I would take the cheapest web EDI option, meet the date, and keep retyping for now. If it is more, or more customers are coming, I would plan the link to the order system from the start, because retyping at volume is where errors and fines come from. Whichever way, ask for a written quote that lists every fee, and keep a note of the date your customer wants you live. That date is the real deadline.
Questions people ask
What is EDI in simple terms?
It is a standard way for two companies' systems to swap business documents like orders, ship notices and invoices, with no one retyping them.
What does EDI 850 mean?
The 850 is the EDI purchase order, the document a customer sends when it wants to buy from you. The 856 is the advance ship notice and the 810 is the invoice.
What is the difference between EDI and API?
EDI uses strict document standards, often sent in scheduled batches. An API uses flexible formats and works on demand. Many companies use both. For custom links between your own systems, see AI integration services.
What is the difference between EDI and SFTP?
EDI is the document layout. SFTP is an encrypted way of moving the file. An EDI file can travel by SFTP, AS2 or another method, and your customer may choose which.
What are the main EDI formats?
X12 is the main standard in North America and EDIFACT is the global standard maintained by the United Nations. Your provider handles the format, and each customer may add its own rules in a guide.
Do I have to use the EDI provider my customer recommends?
Often not. TrueCommerce says you can work with any provider regardless of who your trading partners use. Ask your customer in writing whether they require a specific provider or a certification test before you buy.
More in this topic: B2B: EDI for distributors (4 guides) →