Explore AIMS360's apparel business software
FREE DEMO
What is a EDI 850 Purchase Order software for managing retailer orders in apparel

The EDI 850 is the purchase order a retailer sends by EDI to start a wholesale order. AIMS360 turns each 850 into a sales order mapped to your styles, colors and sizes, and sends the 855 back from the live order.

EDI 850

EDI 850: the purchase order every EDI retail order starts with

The 850 is the purchase order a retailer sends you by EDI: what it wants, in which styles, colors and sizes, at what price, shipped where and by when. The 855, the 856 and the 810 that follow are all measured against it. AIMS360 turns each 850 into a sales order mapped to your styles, so nobody retypes a PO.

EDI 850 at a glance
Purchase Order
Retailer to you
Inbound, starts the order
X12 850
EDIFACT equivalent: ORDERS
997 + 855
How you answer it
860
How the retailer changes it
856 + 810
What follows it
BEG03
Where the PO number lives
The short answer

What is an EDI 850 purchase order?

An EDI 850 is the electronic purchase order in the ANSI ASC X12 standard. A retailer sends it to a supplier to place an order, and it carries the PO number and dates, the ship to and bill to locations, payment terms, and every line item by UPC or style with quantity, color, size and price.

For a brand selling wholesale, the 850 replaces the emailed PDF and the order keyed in by hand. It arrives as structured data inside ISA and GS envelopes, one 850 per purchase order, and the retailer holds you to it. The 855 says what you will ship against it, the 856 says what you did ship and the 810 bills for it. Retailers that run automated matching compare them line by line before they pay.

Outside North America the same job is usually done by the UN/EDIFACT ORDERS message: different syntax, same content.

Anatomy

What an EDI 850 file contains

The segments most apparel and footwear 850s carry, in file order, starting with the ISA and GS envelope.

Segment Name and what it carries in an apparel order
ISA / GS Interchange and group envelope. Sender and receiver IDs, delimiters and control numbers. GS01 is PO for purchase orders. GE and IEA close the envelope after SE.
ST Transaction set header. ST*850 and a control number that SE has to repeat.
BEG Beginning segment for purchase order. Purpose code (BEG01), PO type (BEG02), PO number (BEG03), release number (BEG04) and PO date (BEG05).
CUR Currency. The currency the prices are in, such as USD, where the guideline asks for it.
REF Reference identification. Department number (REF*DP), your vendor number at that retailer (REF*IA) and other references the guideline requires.
PER Administrative communications contact. The buyer or department to contact (PER*BD), with a phone number or email.
FOB F.O.B. related instructions. Who pays freight: PP is prepaid by the seller, CC is collect.
ITD Terms of sale. Payment terms: discount percent, discount days and net days, such as 2 percent 10, net 30.
DTM Date/time reference. The ship window and cancel date. Common qualifiers: 037 ship not before, 038 ship no later, 001 cancel after, 010 requested ship, 002 delivery requested.
TD5 Carrier details (routing). Carrier SCAC, transport method or routing text, when the retailer specifies how the goods move.
N1 / N3 / N4 Name, address and location loop. The parties: N1*ST ship to (a DC, a store or a consumer), N1*BT bill to, N1*BY buying party, N1*Z7 mark-for, the store the goods are ultimately for. N3 and N4 carry the address.
PO1 Baseline item data. One per line: line number, quantity, unit of measure, unit price and product ID pairs such as UP (UPC), VA (vendor style) and IN (buyer's item number).
PID Product/item description. Free form text (PID*F), commonly the style name, color and size.
PO4 Item physical details. Pack. PO401 is the number of units, or inner packs, per carton, so PO4*12 is a case pack of 12.
SDQ Destination quantity. The store breakdown for a line: store number and quantity pairs, up to ten stores per SDQ segment, repeated as needed.
CTT Transaction totals. CTT01 is the number of PO1 lines. CTT02, when sent, is a hash total of the quantities ordered.
SE Transaction set trailer. The segment count, including ST and SE, and the control number from ST.

Apparel detail: style, color, size, pack and store

UP PO1 qualifier for the 12 digit UPC, the most common item identifier in apparel and footwear 850s.
VA PO1 qualifier for the vendor's style number, your style.
IN PO1 qualifier for the buyer's item number, the retailer's own SKU.
BO / IZ PO1 qualifiers for buyer's color and buyer's size, on retailers that send them as codes.
Color and size travel as PID text or as their own PO1 qualifier pairs. Case pack sits in PO4 and the store split in SDQ. A UPC already identifies one style, color and size, so your UPC catalog has to be right before the first 850 arrives.
BEG codes

Purchase order type and purpose codes

BEG01, the purpose, and BEG02, the order type, tell you what kind of order this is before you read a single line.

BEG01 transaction set purpose code

00 Original. A new purchase order.
01 Cancellation. Cancels the purchase order with that number.
05 Replace. Replaces a purchase order sent earlier, in full.
06 Confirmation. Confirms an order already placed another way, so it should not be entered twice.
07 Duplicate. A resend of a purchase order already transmitted, not a new order.

BEG02 purchase order type code

SA Stand-alone order. A one time order, a common type for bulk wholesale.
DS Dropship. Ship direct to the retailer's customer.
RL Release or delivery order. Calls off quantities against a blanket order.
BK Blanket order, quantity firm. A committed total that is shipped in releases.
RE Reorder. Replenishment of an item the retailer already carries.
RO Rush order. Ship ahead of the normal window.
NE New order. Some retailers use it where others use SA.
Each retailer's guideline lists the codes it actually uses. The values above are standard ANSI ASC X12 codes, and a code one retailer sends routinely may never appear from another.
Sample file

Sample EDI 850 file, annotated

A short, fictional bulk order from Example Retailer: two styles, four lines, one store breakdown, dummy UPCs, envelopes left off. How a bulk 850 becomes cartons at the DC is on bulk EDI orders.

ST*850*0001~ BEG*00*SA*EX4500123**20261015~ CUR*BY*USD~ REF*DP*042~ REF*IA*V100234~ PER*BD*EXAMPLE BUYER~ FOB*PP~ ITD*01*3*2**10**30~ DTM*037*20261101~ DTM*001*20261120~ TD5*O*2*XMPL*M~ N1*ST*EXAMPLE RETAILER DC 0045*92*0045~ N3*100 EXAMPLE PARKWAY~ N4*ANYTOWN*CA*90000*US~ N1*BY*EXAMPLE RETAILER*92*0001~ PO1*1*24*EA*12.50**UP*000000000001*VA*TEE100~ PID*F****CREW TEE BLACK S~ PO4*12~ SDQ*EA*92*0101*12*0102*12~ PO1*2*24*EA*12.50**UP*000000000002*VA*TEE100~ PID*F****CREW TEE BLACK M~ PO4*12~ PO1*3*12*EA*21.00**UP*000000000003*VA*PNT200~ PID*F****CHINO NAVY 30~ PO1*4*12*EA*21.00**UP*000000000004*VA*PNT200~ PID*F****CHINO NAVY 32~ CTT*4*72~ SE*28*0001~
Segment What this order says
ST An 850, control number 0001.
BEG Original (00), stand-alone order (SA), PO number EX4500123, no release number, dated 15 October 2026.
CUR, REF, PER US dollars, department 042, your vendor number V100234 and the buyer to contact.
FOB, ITD Freight prepaid by you. Terms from the invoice date: 2 percent if paid in 10 days, net 30.
DTM, TD5 Ship not before 1 November, cancel after 20 November, by motor carrier XMPL (a fictional SCAC).
N1 / N3 / N4 Ship to the retailer's DC 0045. The second N1 is the buying party.
PO1 + PID TEE100 in black, sizes S and M, 24 each at 12.50. PNT200 in navy, waist 30 and 32, 12 each at 21.00. Each line carries the UPC (UP) and your style (VA), with color and size in PID.
PO4 The two tee lines ship in case packs of 12.
SDQ Line 1 splits 12 units to store 0101 and 12 to store 0102, both shipped to the DC.
CTT Four PO1 lines, 72 units in total.
SE 28 segments from ST to SE, control number 0001 to match ST.

Everything you send back keys off this file. The 855 answers these four lines by line number, the 856 keeps store 0101 and 0102 cartons apart, and the 810 bills against the same PO number, prices and terms.

Order types

Bulk, store-level and dropship 850s

One retailer can send all three. The segments look alike; what they mean for picking, labels and the 856 does not.

01

Bulk to a DC

N1*ST is the retailer's distribution center and each PO1 is a total for the whole order, often in case packs set by PO4. You pick by line, most retailers expect a GS1-128 SSCC label on every carton, and the 856 commonly follows a full shipment, order, pack, item hierarchy.

02

Store level

The ship to is usually still a DC, but SDQ splits each line by store, or an N1*Z7 mark-for names the store the cartons are for. You pick and pack by store, and the 856 commonly has to keep each store's cartons separate so the DC can cross dock them.

03

Dropship

BEG02 is often DS and N1*ST is the retailer's customer at a home address. Orders are usually one or a few units, shipped parcel, frequently with a branded packing slip rather than a GS1-128 carton label, and the 856 commonly uses a simpler shipment, order, item structure with tracking.

04

One workflow in AIMS360

Bulk and dropship 850s arrive in one workflow. AIMS360 applies the right map, label and ASN structure per program and routes each order to your warehouse or your 3PL.

In AIMS360

What AIMS360 does when an 850 arrives

The 850 becomes a sales order in the system that holds your inventory, warehouse and invoicing, so every document after it comes from one record.

Step 01

Received and validated

AIMS360 connects by VAN or AS2, or through the network the retailer mandates. The 850 is parsed against that retailer's map, on 4010 or 5010, and its header, lines and qualifiers are validated.

Step 02

Lands as a sales order

The BEG03 PO number becomes the reference the 855, 856 and 810 carry for that order.

Step 03

UPCs map to style, color and size

Each PO1 line is matched to your styles by UPC, vendor part number or retailer SKU across the full color and size matrix, so a 240 line PO lands as one order rather than 240 manual entries.

Step 04

Checked against inventory and pricing

Each line is validated against your product catalog, your pricing and your available to sell position across your DC, your 3PL and your stores.

Step 05

The 997 and 855 go back

The 997 confirms receipt. The 855 fires on import from the live order, with line statuses for what you can actually commit.

Step 06

Allocated and released to pick

Inventory allocates against the order. Backorders, partials and substitutions follow your retailer rules, and pick tickets, packing slips and GS1-128 carton labels print from AIMS360.

Step 07

The 856 from the packing scan

The ASN is built from the cartons your warehouse actually scanned, in the hierarchy that retailer requires, and transmits at scan and ship.

Step 08

The 810 from the shipment

The invoice generates from the same shipment record, so the 855, 856 and 810 reconcile by construction.

AIMS360 EDI is a managed service. The implementation team maps and tests each retailer's 850, trains your staff and writes a standard operating procedure for your business. The same platform has processed 1.2 million orders in a single day for one brand. EDI is an add-on, priced as a flat monthly fee per retailer with unlimited transactions. No VAN or per-document fees.

AIMS360 also runs its own MCP server, so ChatGPT, Claude, Grok and Gemini connect to live AIMS360 data. AI automation is an add-on.

Where it sits

How the 850 fits with the 855, 860, 856 and 810

Every other document in the order cycle answers the 850, changes it or follows from it.

Document Direction, timing and what it answers
850 Purchase order. Retailer to you. Starts the cycle, and everything else answers it.
997 Functional acknowledgment. You to retailer, commonly within 24 hours of each file. Answers: did the file arrive and parse?
855 PO acknowledgment. You to retailer, commonly within 24 to 48 hours of the 850. Answers: what will you actually ship?
860 PO change. Retailer to you, usually before the order ships. Answers: what has changed?
856 Advance ship notice. You to retailer, before the goods arrive. Answers: what is on the truck?
810 Invoice. You to retailer, after shipment. Answers: what is owed for what shipped?

Some retailers expect an 865 back to confirm an 860. AIMS360 processes the 860 in the same system as the original order and re-allocates inventory automatically when it arrives.

Who sends them

Retailers that send EDI 850s

Retailers that trade by X12 EDI send their purchase orders as 850s, each to its own guideline: required segments, date and type codes, store breakouts, dropship rules. AIMS360 connects to 350+ retailers on its EDI network and starts from pre built, retailer tested maps rather than a blank guideline.

See all 350+ EDI retailers on the AIMS360 network.

EDI 850 FAQ

Common questions

An EDI 850 is the electronic purchase order in the ANSI ASC X12 standard. A retailer sends it to a supplier to place an order, and it carries the PO number and dates, the ship to and bill to locations, payment terms, and every line item by UPC or style with quantity, color, size and price. Outside North America the equivalent UN/EDIFACT message is ORDERS.

The buyer sends it and the seller receives it. In wholesale that means the retailer sends the 850 and the brand or manufacturer receives it, usually over a VAN or an AS2 connection. The 997, 855, 856 and 810 you send back all answer it or follow from it.

The PO number is in BEG03, the third element of the BEG segment, and the PO date is in BEG05. The vendor number the retailer assigned you usually appears in a REF segment with the IA qualifier or in an N1 loop with the VN qualifier, depending on the retailer's guideline. AIMS360 uses the BEG03 PO number as the reference across the 855, 856 and 810 for that order.

The 850 is the retailer's purchase order, inbound to you. The 855 is your purchase order acknowledgment, outbound to the retailer, saying line by line what you will actually ship: accepted, changed, backordered or rejected. Many retailers measure fill rate against what you acknowledged, so the 855 should come from your real inventory position rather than an automatic accept. AIMS360 generates the 855 from the live order.

The 850 creates the order. The 860 is the retailer's purchase order change, sent later to change quantities, dates or prices, add or cancel lines, or cancel the order. Some retailers expect an 865 back to confirm the change, and some skip the 860 and retransmit the 850 instead, sometimes with BEG01 set to 05 for replace. AIMS360 processes the 860 in the same system as the original order and re-allocates inventory automatically when it arrives.

Two clocks start when the 850 arrives. The 997 functional acknowledgment, which only confirms the file was received and readable, is commonly expected within 24 hours, and some retailers expect it much sooner. The 855 acknowledgment, where a retailer requires one, is commonly due within 24 to 48 hours, and some retailers set a shorter window for some categories. Windows vary by retailer, so confirm them in the guideline issued to your account.

PO1 is the line item. Each PO1 carries a line number, the quantity ordered, the unit of measure, the unit price and one or more product ID pairs, each a qualifier and a value. In apparel the common qualifiers are UP for the 12 digit UPC, VA for your style number and IN for the buyer's item number. Color and size arrive either as PID text or as further PO1 pairs such as BO for buyer's color and IZ for buyer's size.

A bulk 850 ships to the retailer's distribution center in case quantities, usually with GS1-128 carton labels and a full carton level ASN. A dropship 850 is often marked with BEG02 set to DS and has the retailer's customer as the ship to, typically one or a few units shipped parcel with a packing slip. Same retailer, different map, different 856. AIMS360 runs both in one workflow.

Not always. The 850 usually travels over a value added network (VAN) or a direct AS2 connection, and some retailers mandate a specific network. With AIMS360 you do not license a VAN or a translator of your own. AIMS360 EDI connects by VAN or AS2, or through whichever network the retailer mandates, and charges no VAN or per-document fees.

EDI is an add-on, priced as a flat monthly fee per retailer with unlimited transactions. No VAN or per-document fees. Volume is not metered, so a peak season that multiplies your 850s does not multiply your EDI bill.

No. The 850 arrives in AIMS360 as a sales order showing the PO number, ship to, dates, styles, colors, sizes and quantities, not as raw segments. The implementation team builds and tests each retailer's map, trains your staff and writes a standard operating procedure for your business, so a team with no EDI background can run retailer orders.

Most retail 850s are on X12 version 4010, written 004010 in the GS segment, and a growing number use 5010. Each retailer's guideline pins the version. AIMS360 runs both side by side, so 4010 and 5010 retailers feed the same order flow.

Related documents

The rest of the order cycle

Last reviewed 15 October 2026 by the AIMS360 EDI team. Segment and code detail reflects the ANSI ASC X12 850 transaction set. Which segments, qualifiers and codes a retailer uses, and its acknowledgment windows, are set in its own EDI guideline, are stated here as commonly used rather than universal, and can change. Confirm against the guideline issued to your vendor account. The sample file is fictional.

Ready when you are

Turn each 850 into an order nobody retypes

See AIMS360 bring in a retailer 850, map it to your styles and send back the 855 in a 30 minute demo.