Transaction set glossary
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 EDI resource explains EDI 850 (Purchase Order), explained for SMB teams for SMB teams evaluating validation, 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.
Continue the supplier workflow
- EDI for suppliers and distributors
- EDI 856 (Advance Ship Notice), explained for SMB teams
- EDI 810 (Invoice), explained for SMB teams
- Retailer onboarding requirements
- Prepare your partner letter and onboarding inputs
Sources and review status
Maintained by SignalEDI content operations. Automated editorial review by Codex automated editorial reviewer.
- X12 transaction set descriptions
Defines 850 purchase orders, 856 ship notices and 810 invoices. Does not establish retailer deadlines, penalties or SignalEDI capabilities.
Source consulted ; this is not an editorial review date.
Confirm document versions, deadlines, labels and test approvals against your partner's current implementation guide. Illustrative examples are not certified partner files. Lab validation does not authorize Production delivery.
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
How SignalEDI handles it
- 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 paths
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.