Why Spreadsheets End Up as EDI
Plenty of buyers still plan orders in Excel, and plenty of suppliers still receive them that way, then retype them into an EDI portal or ERP. When a trading partner asks for an EDI 850 instead, the spreadsheet already holds everything the 850 needs: a PO number, the items, quantities, prices and where to ship. The converter maps those columns to X12 segments and builds the envelope, so the file passes the same structural checks a partner's translator runs.
Getting the Spreadsheet Right
- One row per line item; repeat the PO number on every line of the same order.
- Put UPCs in their own column as numbers or text with all 12 digits. Excel drops leading zeros from numbers, which breaks the check digit; format the column as text.
- Use two-letter X12 units: EA each, CA case, PK pack, BX box.
- Keep prices as plain numbers. Currency symbols and thousands separators are removed.
Then check the result in the EDI viewer and validator, with a retailer selected under Validate for. For the meaning of each segment, see the 850 purchase order guide. Working with CSV exports instead? Use CSV to EDI; it is the same converter. If your system exports orders as XML, see how the fields line up in XML to EDI. To answer a PO you received, reply to a PO with an 855, 856 or 810.
From One File to Every Order
If spreadsheets are how orders reach you every week, OrderSync can read them as they arrive by email, check them against your catalog and pricing, and create clean orders for your team to approve, alongside your EDI, PDF and portal orders. See multi-format order processing or the free order form template for buyers who still send spreadsheets.