EDI 850 BEG Segment: Beginning Segment for Purchase Order Guide
Inspect live BEG segments in our interactive X12 workbench below. Understand how BEG01, BEG02, BEG03, and BEG05 map to Shopify Order Names and QuickBooks PONUM fields.
Drop your file below, check the order, then download for QuickBooks Desktop (.IIF).
- 1Load your order file
- 2Check it and match your SKUs
Drop your EDI order file here
.edi, .x12 or .txt. The file is read on your computer and is not uploaded.
No chargeback risks found. This order passes every check.
Checked against the Walmart supplier guide for EDI 850.
- Detected Cross-Dock SDQ allocations (6 store-level splits verified against PO102).
- Walmart Dept #0018 & Vendor #123456789 verified.
Raw EDI Code Inspector
31 linesPrimary header of an EDI 850 Purchase Order. BEG03 is the legal PO # that must be echoed on your 856 ASN and 810 Invoice.
Purchase Order Summary & Line Items
| Order / Store # | Your SKU | Retailer Item # / UPC | Item Description | Qty | Unit Price | Line Total |
|---|---|---|---|---|---|---|
| PO-4500991288-STORE-0101 | Item: 554433221 UPC: 012345678905 | ORGANIC COTTON BATH TOWEL ROYAL BLUE | 25 EA | $12.50 | $312.50 | |
| PO-4500991288-STORE-0102 | Item: 554433221 UPC: 012345678905 | ORGANIC COTTON BATH TOWEL ROYAL BLUE | 35 EA | $12.50 | $437.50 | |
| PO-4500991288-STORE-0103 | Item: 554433221 UPC: 012345678905 | ORGANIC COTTON BATH TOWEL ROYAL BLUE | 40 EA | $12.50 | $500.00 | |
| PO-4500991288-STORE-0101 | Item: 554433299 UPC: 012345678912 | LUXURY WAFFLE ROBE WHITE XL | 20 EA | $18.00 | $360.00 | |
| PO-4500991288-STORE-0102 | Item: 554433299 UPC: 012345678912 | LUXURY WAFFLE ROBE WHITE XL | 20 EA | $18.00 | $360.00 | |
| PO-4500991288-STORE-0103 | Item: 554433299 UPC: 012345678912 | LUXURY WAFFLE ROBE WHITE XL | 20 EA | $18.00 | $360.00 |
Download for your software
Pick where the order is going, then download. Files are ready for Excel, QuickBooks, Shopify or a thermal printer.
Field mapping table: which EDI segment fills which column (for IT & bookkeepers)
BEG Segment Elements (BEG01 – BEG05) & ERP Mapping
Deterministic segment-to-column mapping rules enforced by our client-side X12 engine
| Source X12 Segment / Element | Sample Raw Value | Target ERP / CSV Column | Transformation & Validation Logic |
|---|---|---|---|
| BEG01 (Purpose Code) | 00 | Order Action | 00 = Original Order; 01 = Cancellation; 05 = Replace; 06 = Confirmation. |
| BEG02 (Purchase Order Type) | SA / DS / NE | Fulfillment Channel | SA = Stand-Alone Order; DS = Dropship to Consumer; NE = New Store Opening; BK = Blanket. |
| BEG03 (Purchase Order Number) | 4500991288 | PONUM / PRF01 / BIG04 | Primary legal PO # echoed onto 856 PRF01, 810 BIG04, and 4x6 GS1-128 labels. |
| BEG05 (Purchase Order Date) | 20261109 | Order Date (MM/DD/YYYY) | Converted from YYYYMMDD to 11/09/2026 for QuickBooks, Xero, and ShipStation. |
Critical Chargeback & Import Pitfalls We Prevent
Common EDI mistakes that trigger $250+ retailer fines or accounting balance errors
Truncating Long BEG03 PO Numbers in ERP Imports
Risk: 810 BIG04 Mismatch RejectionIf your ERP truncates BEG03 from 12 characters to 8 characters, the 810 Invoice you generate back will fail the buyer’s PO lookup.
Ignoring BEG01="01" (Cancellation) or "05" (Replace)
Risk: Duplicate ShipmentTreating a cancellation or replacement 850 as a brand-new order leads to double-shipping.
Not Echoing BEG05 PO Date on 856 PRF04 and 810 BIG03
Risk: Minor EDI Compliance WarningMany retailers expect the original PO date from BEG05 to be returned in PRF04 and BIG03.
How to Inspect & Map BEG Segments
Zero middleware setup — complete in under 60 seconds
View the live breakdown of BEG01, BEG02, BEG03, and BEG05.
Test different BEG02 order types or PO numbers in real time.
See how BEG03 populates PONUM and Order Name columns.
Frequently Asked Technical Questions
ANSI X12 specification details, retail companion rules, and ERP import answers
Why is BEG04 usually empty (two consecutive asterisks **)?
BEG04 is the Release Number, which is only used for Blanket Purchase Orders (BEG02=BK or RL). For standard standalone orders (BEG02=SA), BEG04 is omitted, resulting in BEG*00*SA*4500991288**20261109~.
Where does BEG03 go when generating an 856 ASN or 810 Invoice?
In an EDI 856 ASN, BEG03 maps to PRF01 under the Order (O) HL level. In an EDI 810 Invoice, BEG03 maps to BIG04.
Related EDI Converters, Retailer Guides & X12 Segment References
- X12 referenceEDI 850 SDQ Segment: Cross-Dock Store Allocation Guide & Excel Splitter
- X12 referenceEDI 856 BSN Segment: Beginning Segment for Ship Notice Guide
- X12 referenceEDI 856 HL Segment: S→O→T→P→I Hierarchy Validator & Excel Flattener
- X12 referenceEDI 856 MAN Segment: MAN*GM SSCC-18 & Marks and Numbers Guide
- X12 referenceEDI 810 BIG Segment: Beginning Segment for Invoice Guide
- ToolsConvert EDI X12 Files (850 / 856 / 810) to Excel (.XLSX) & CSV
- Transaction setsEDI 820 Payment Order / Remittance Advice Decoder & Excel Reconciler
- IntegrationsConvert EDI 850 Purchase Orders to QuickBooks Desktop (.IIF)
- RetailersTarget EDI 850 / 856 / 810 Converter, DPCI Mapper & ASN Validator