Transaction set glossary
EDI 850: EDI 850 (Purchase Order), explained for SMB teams
The 850 is the inbound purchase order that starts most supplier EDI workflows.
What is SignalEDI?
Definition
- SignalEDI
- SignalEDI is an EDI and API integration platform that gets suppliers ready for trading-partner mandates. This document guide explains EDI 850 for SMB teams evaluating validation, mapping, partner readiness, pricing, and operational visibility.
What the 850 is
An 850 tells a supplier what was ordered, where it ships, and which item identifiers matter.
- PO number
- Buyer location
- Line items
- Delivery dates
Operations checks before fulfillment
For the synthetic PO1001 example, preserve the buyer's order reference and confirm 12 units of SKU-100 in the expected unit of measure. Compare the destination and requested dates with your accepted order. If the item identifier cannot be matched, hold that exception for operations rather than substituting a different SKU.
- Check repeated transmissions before creating another order; envelope control numbers and business PO references serve different purposes.
- Carry PO1001 into shipment and invoice reconciliation; do not reuse it as every document's control number.
- Confirm the partner's acknowledgment and change-order expectations from its current guide; validating an 850 is not permission to ship.
Example segments
ST*850*0003~ BEG*00*SA*PO1001**20260504~ N1*BY*RETAILER*92*STORE17~ PO1*1*12*EA*19.99**VN*SKU-100~
Common errors
- Missing BEG03 PO number
- Buyer/store location mismatch
- PO1 quantity or SKU mismatch
- Duplicate PO processing
Plain-English Integration Visualizer
Simple example: a purchase order becomes a QuickBooks order draft
A retailer sends a purchase order, or your team uploads the file. SignalEDI checks it against the saved partner setup and prepares a QuickBooks-friendly draft.
1. File arrives
A buyer sends an 850 purchase order, or your team uploads the file you already have.
2. Signal matches it
Signal checks the saved partner and message setup. You do not choose EDI versus API at upload time.
3. Fields are checked
Names, item codes, quantities, dates, and required partner fields are reviewed before the file moves.
4. QuickBooks gets a draft
A clean order draft is prepared, and Today shows whether it is checked, routed, or needs attention.
If something is wrong
Decisions explains the blocker in plain English, asks for approval, and only then retries or reprocesses.
Activation path for EDI 850
Use this page as the middle of the internal-link path: ICP page to document guide, document guide to partner requirements, partner requirements to comparison/pricing, then demo or trial.
- Understand the document and partner requirement
- Validate a representative X12 sample
- Preview the normalized JSON or QuickBooks-ready mapping
- Confirm partner onboarding, testing, and acknowledgement expectations
- Start trial and move the workflow into the onboarding wizard
Buyer-intent next steps
How SignalEDI handles EDI 850
- Maps BEG/N1/PO1 into structured order objects.
- Uses delivery/interchange identity checks for repeat receipts. Repeated POs with different interchange identifiers need business-order duplicate checks; envelope deduplication alone does not guarantee a unique order.
- Links PO data to ASN and invoice workflows.
Related links
FAQ
Common questions
The buyer or retailer usually sends the 850 to the supplier.
Yes. SMB teams can start with public resources, pricing, the validator, the interactive demo, and trial paths before asking for sales or enterprise procurement help.
No. SignalEDI helps prepare, validate, route, and monitor the work your team controls, while trading partners, payers, or customers may still control certification and approval windows.