EDI for small business: what one retailer asks of a small supplier

What EDI means for a small business

For a small supplier EDI is rarely a choice of technology. A retailer or distributor states it as a condition, and from then on purchase orders arrive as X12 files and the replies are expected in the same form. Walmart's supplier page lists "Electronic Data Interchange (EDI)" in the same list as a Dun & Bradstreet number and a GS1 membership number.

The requirement does not scale down. A supplier with 20 orders a month exchanges the same four documents, in the same version, against the same implementation guide as a supplier with 2,000. What scales is the handling: at 20 orders the documents can be typed, and the rest of this page shows how far that goes.

What you need before the first document

GS1 US describes the company prefix as the way to get multiple barcodes at once and to identify "higher levels of packaging like a case or pallet". That second use matters at the first carton label: a UPC licensed on its own identifies a product, and the SSCC on a carton is built on a company prefix.

A purchase order from the retailer uses those numbers from the first line:

BEG*00*SA*4500018236**20260928~
PO1*1*24*EA*12.50**UP*614141104826*VP*10482~
PO1*2*16*EA*8.75**UP*614141104994*VP*10499~
CTT*2*40~

Two lines, 24 and 16 units, 40 in total, which is what CTT02 carries. UP introduces the UPC and VP your own item number. The order value is 24 times 12.50 plus 16 times 8.75: 300.00 plus 140.00 is 440.00. The segments are explained on the EDI 850 page.

The documents for one retailer, counted

One order is four business documents: the 850 in, and the 855, the 856 and the 810 out. Each is answered by a 997: you send one for the 850 and receive one for each of your three.

Take 20 orders a month, two of which ship in two parts.

• 850: 20 received
• 855: 20 sent
• 856: 20 plus 2 is 22 sent
• 810: 22 sent, one per shipment in this example
• 997: 20 sent, and 20 plus 22 plus 22 is 64 received

That is 84 business documents and 84 acknowledgments, 168 in the month.

A portal as a rule generates and files the 997s itself, so the typing load is the 64 outbound documents plus keying 20 orders into your own system. At 8 lines per order that is 160 order lines a month. If the program includes the 846 inventory advice, as Walmart's drop-ship set does, a stock file per item is added on the schedule the retailer sets.

Where the portal stops being enough

Twenty orders a month is about one per working day, with three documents typed for each. Three changes move a supplier past that point.

Volume. At 200 orders a month the same sum gives 640 outbound documents and 1,600 order lines. The documents also have deadlines: Kroger, for example, requires the ship notice at least 90 minutes before the truck arrives. A notice typed at the end of the day misses that for every morning shipment.

A second retailer. It brings its own guide, version and codes. Kroger's portal specifies X12 version 5010; Walmart's drop-ship sample is 4010 with fixed delimiters. In a portal that is a second set of forms.

Small orders in a drop-ship program. Each consumer order is its own 850, 855, 856 and 810. Where a network or portal meters per document, the charge falls on every order however small it is. The metering units are explained under EDI software.

The portal remains a valid way to be EDI capable. The retailer sees the same files either way.

What practitioners report

The supplier forums r/edi and r/Netsuite hold years of first-hand accounts from small businesses. Paraphrased, the recurring ones are:

• A retailer requires EDI from a supplier that receives one order a month.
• The retailer's onboarding contractor charges a testing fee whichever provider the supplier ends up using.
• A provider changes a mapping without notice, a document starts failing, and the retailer's deduction stays with the supplier.
• A contract runs for a year and renews automatically.
• A per-document fee outweighs the margin on small drop-ship orders.

These are reports, not statistics. They do point at four things to read in any offer before signing: the setup fee per trading partner, the monthly minimum, the contract length with its renewal clause, and the unit that is metered. The categories of provider and what each one covers are set out under EDI provider; how deductions arise is under EDI compliance.

What this means for your integration

A small supplier does not need an ERP to stop typing. It needs the 850 to land as an order in whatever holds its orders, and the 855, 856 and 810 to be built from the records that already exist there: a store platform, an accounting package, a shipping tool.

We build that as an EDI integration to your systems and your retailer's guides, for a fixed build price and a monthly fee, and we host and run it. Outbound documents are validated before they are sent, and every 997 is matched to its document. A document that fails is held and shown in the dashboard with the reason. Tell us which retailer and how many orders a month.