Some of your trading partners will not fax a purchase order or email a PDF invoice; they expect the data to flow straight between systems. That is EDI, and in fuel it is often the price of admission to work with big suppliers and customers.
What EDI is
EDI, electronic data interchange, is a standardized way for two businesses to exchange documents computer to computer, with no one re-keying them. Orders, invoices, and shipment confirmations move in an agreed format. Most of it runs on the ANSI X12 standard, where each document type has a number: an 850 is a purchase order, an 810 is an invoice, a 214 is a shipment status update. When a supplier says they require "an 810," that is what they mean.
Where it shows up in fuel
Usually between a jobber and its larger partners: suppliers, big commercial accounts, and chains that require it. Common documents are purchase orders, invoices, and delivery confirmations. Where a partner mandates EDI, you have to send and receive in their format to trade smoothly, which makes it a practical requirement rather than a preference.
EDI and NAXML
EDI and NAXML aim at the same thing, system-to-system data exchange, in different styles. Traditional X12 EDI is the cross-industry workhorse. NAXML is XML-based and built specifically for the convenience and petroleum world to be lower-cost and simpler. The industry also has its own XML standards body, PIDX (the Petroleum Industry Data Exchange), which is more common upstream and midstream than in fuel distribution. A modern back office may speak more than one of these, depending on the partner. It is one branch of the broader jobber software picture.
Why it matters
Re-keying orders and invoices between systems is slow and a magnet for errors, and some partners require EDI to do business at all. Losing a supplier contract over an 810 you cannot send is the expensive version of this problem, which is why FastDragon Fuel Jobber is built to exchange data with trading partners rather than bolting it on later. It is the same single-entry idea behind BOL-to-invoice: let the data flow rather than typing it twice.
Frequently asked
Which X12 transaction sets matter most in fuel distribution?
Three do most of the work: the 850 purchase order, the 810 invoice, and the 214 shipment status. A partner may also ask for an 856 advance ship notice or an 820 payment advice. Their EDI implementation guide lists the exact sets, versions, and fields they expect, so request that document before quoting any integration work.
What is PIDX?
PIDX, the Petroleum Industry Data Exchange, is the standards body that publishes XML document standards for oil and gas commerce, covering things like invoices and field tickets. It shows up most in upstream and midstream supply chains. Downstream fuel distribution leans more on X12 and NAXML.
What is a VAN in EDI?
A VAN, or value-added network, is a third-party mailbox service that routes EDI documents between trading partners and confirms delivery. It was the traditional way to connect, and many partners still use one. The newer alternative is AS2, a direct, encrypted connection over the internet that skips the per-document VAN charges.
How does a small jobber meet an EDI mandate without an IT department?
Two common routes: a web-EDI portal, where you key documents into the partner's site by hand, or a managed EDI provider that translates between your back office and the partner's format for a monthly fee. The portal costs less but reintroduces typing. The provider route scales once the document volume justifies it.
Do I need EDI to run a fuel business?
Plenty of small jobbers run fine on email and PDFs. The pattern to expect: EDI arrives as a condition of a specific contract, when a major supplier, a national chain, or a government account writes it into the agreement. Plan for it when you start chasing those accounts, not after you win one.