EDI 850, 855, 856 and 810: the X12 order flow, and the purchase orders that never arrive as EDI
EDI 850, 855, 856 and 810 are the X12 transaction sets that carry a B2B order from purchase order to invoice: the buyer's 850 purchase order, the supplier's 855 acknowledgment, the 856 advance ship notice (ASN) that says what is on the truck, and the 810 invoice. A 997 confirms each one parsed. Not every customer sends them: some order by email, PDF or spreadsheet and will never set up EDI. Those orders need the same checks an 850 gets (item, unit, price, ship-to, duplicates), and they can get them without forcing the customer onto EDI, by reading the email and writing the order to the ERP. That is what Mirage's EDI alternative does for small and mid-size customers. Below, one invented order goes through all five documents.
- Published
- Updated
- Reading time
- 14 min
- Written by
- Jules Toussaint
Scope: X12 release 004010 between US suppliers and their customers, order to invoice. X12 standards are copyrighted by ASC X12; segment and code names follow the 004010 implementation references cited. Each trading partner's implementation guide governs what it requires.
In production, on orders that are not EDI
Biodéal, an organic dairy distributor, receives its customers' orders by email in their own formats: PDFs, Word tables, scanned forms, plain text. Mirage creates each order in SAP Business One. Since go-live on July 22, 2025: 2,943 orders and 12,993 lines entered automatically for 113 customers, a median of 48 seconds from email to order ready in SAP, and about 7% of orders flagged for a human check. None of those orders is EDI. Mirage is not an EDI translator: where a customer sends 850s, your translator keeps that job.
One order, two ways in: an 850 or an email
An 850 arrives structured: every value sits in a numbered element, with a code that says what it is. An email order carries the same content in the customer's own words. The checks are the same; what differs is how much the format has already done.
| Question | In an 850 | In an email or PDF order |
|---|---|---|
| New order, copy or change? | BEG01 purpose code (00 original, 01 cancellation, 05 replace, 07 duplicate) and the PO number | A "revised" PDF or "same as last week": compare customer, PO number and content |
| Which item? | Each PO1 ID has a qualifier: VP your part, BP the buyer's, UP a consumer UPC | The customer's own reference: a cross-reference per customer, a person when it fails |
| Which unit? | PO103 from a code list: EA each, CA case | "12 / 5 Kg", "PACK (X6P)" or no unit at all, as Biodéal's customers write them: convert with the pack size you hold |
| Ship to where? | N1*ST with a location code your cross-reference resolves | An address matched to the customer's records |
| Is it all there? | CTT01 counts the lines, SE01 the segments | Nothing counts the lines: check against the document |
| Does the buyer know your answer? | A 997 for syntax, an 855 line by line | A reply email or a confirmation PDF |
Source: Purpose codes, ID qualifiers, units, CTT01, SE01 (Stedi X12 004010 reference); quantity conventions: Biodéal case study.
The format carries the controls; the business checks below apply to both channels.
When EDI is not worth setting up, and when it is
EDI is built for volume. In IBM's words, it "is best suited for use cases involving business partners that exchange a high-volume of (often repetitive) documents in scheduled batches"; it "can have a significant up-front cost, generally requiring specialized software and expertise to set up", and each partner can have "its own individual requirements" (IBM). A buyer that prefers EDI still makes room: the GSA lets partners "with small order volume and less technical proficiency" use its vendor portal instead (GSA).
In practice, a new EDI connection rarely pays for itself with:
- A customer who orders a few times a month: mapping and testing against its guide is the same work as for one who orders daily.
- A customer who does not send EDI. Biodéal's 113 customers order by email in their own formats, and their orders still reach SAP Business One checked.
- Ad hoc orders: a one-off buyer, a spot order, a rush order confirmed by email after a call.
The mirror case: move a customer to EDI when it requires it (Shopbop's July 2026 manual requires the 850 and the 856, with SSCC labels, though not the 855, and charges back an ASN that arrives after the goods, sections 5.1 and 10), when its orders come often and in batches, or when it needs what an email cannot carry: an 856 its dock matches to the SSCC on each label (GS1 US). Between the two sit a customer portal and software that reads the email; the order entry automation guide compares them customer by customer.
The order between buyer, seller and warehouse
Source: X12 supply chain transaction flow; 997; 940, 945 (Stedi X12 004010 reference).
This guide follows one order through these sets. For every segment and element, see Stedi's free X12 004010 reference, one page per set: the 850, 855, 856, 810 and 997, and the 940 and 945 for the warehouse. Your partner's implementation guide says which segments it uses.
A change to a PO already sent travels as an 860, answered by an 865; the 857 combines ship notice and invoice; the 820 carries the payment, beyond this guide (X12).
The envelope: a complete ISA, then GS and ST
Every X12 file nests three envelopes: the interchange (ISA to IEA); functional groups (GS to GE) of one kind, named in GS01 (PO, PR, SH, IN, FA for the 850, 855, 856, 810, 997); and each document, ST to SE. Each trailer counts what it closes and repeats its header's control number: IEA02 equals ISA13, GE02 equals GS06, SE02 equals ST02.
Every ISA element has a fixed length, so a 004010 ISA is always 106 characters, terminator included. The sample order's ISA:
ISA*00* *00* *ZZ*EXAMPLEBUYER *ZZ*EXAMPLESUPPLY *261027*0930*U*00401*000000101*0*T*>~
| Elements | Value | Length | Meaning |
|---|---|---|---|
| ISA01 to ISA04 | 00, 10 spaces, 00, 10 spaces | 2, 10, 2, 10 | No authorization or security information |
| ISA05, ISA06 | ZZ, EXAMPLEBUYER + 3 spaces | 2, 15 | Sender qualifier (mutually defined) and ID |
| ISA07, ISA08 | ZZ, EXAMPLESUPPLY + 2 spaces | 2, 15 | Receiver qualifier and ID |
| ISA09, ISA10 | 261027, 0930 | 6, 4 | Date, YYMMDD only, and time |
| ISA11 | U | 1 | U.S. EDI Community of ASC X12, TDCC and UCS |
| ISA12 | 00401 | 5 | Envelope version; the release is in GS08 |
| ISA13 | 000000101 | 9 | Control number, repeated in IEA02 |
| ISA14 | 0 | 1 | No TA1 requested |
| ISA15 | T | 1 | Test data; P in production |
| ISA16 | > | 1 | Component separator |
Source: ISA elements and lengths, ISA15, GS, GS01, SE, ISA09 date format; EdiFabric on IEA02 and GE02.
Control numbers detect lost and repeated files, not orders: detect repeats on sender, receiver, ISA15 and ISA13 together, stored as text to keep the zeros. The release is agreed between partners and declared in GS08. X12 publishes one a year, usually in January: 004010 in January 1998, 005010 in January 2004, 008070 in March 2026 (X12 release schedule). A new release obliges no one to move.
One order through the 850, 997, 855, 856 and 810
Illustrative example, invented figures: a two-line order, from purchase order to invoice
Assumptions, all invented: parties, PO, address, parts and prices. Asterisk between elements, tilde after each segment, line breaks for reading. The buyer accepts no backorders: a quantity not confirmed is canceled. After the 850, each document shows ST to SE only.
The 850 purchase order
ISA*00* *00* *ZZ*EXAMPLEBUYER *ZZ*EXAMPLESUPPLY *261027*0930*U*00401*000000101*0*T*>~ GS*PO*EXAMPLEBUYER*EXAMPLESUPPLY*20261027*0930*101*X*004010~ ST*850*0001~ BEG*00*SA*PO-10457**20261027~ CUR*BY*USD~ REF*DP*042~ DTM*002*20261105~ N1*ST*EXAMPLE BUYER DC 3*92*DC03~ N3*100 SAMPLE ROAD~ N4*ANYTOWN*OH*44000~ PO1*1*24*CA*41.50*CT*VP*BRK-220*BP*778-0042~ PID*F****BRAKE PAD SET, 4 PER CASE~ PO1*2*6*EA*12.80*CT*VP*SEAL-14*BP*778-0187~ PID*F****SHAFT SEAL 14 MM~ CTT*2~ SE*14*0001~ GE*1*101~ IEA*1*000000101~
| Segment | What it says | In the sales order |
|---|---|---|
| BEG*00*SA*PO-10457**20261027 | Original, stand-alone order, PO-10457 of October 27 | Customer PO number and date |
| CUR*BY*USD | Buyer's prices in US dollars | Currency, checked against the price agreement |
| REF*DP*042 | Department 042 | Returned on the 856 or 810 if the guide asks |
| DTM*002*20261105 | Delivery requested November 5 | Requested date |
| N1*ST, N3, N4 | Ship to DC 3, code DC03 assigned by the buyer | Ship-to found through a cross-reference |
| PO1*1*24*CA*41.50*CT*VP*BRK-220*BP*778-0042 | 24 cases at 41.50, contract price, vendor part BRK-220 | Line 1, price checked against the contract |
| PO1*2*6*EA*12.80*CT*... | 6 each at 12.80, part SEAL-14 | Line 2 |
| CTT*2, SE*14 | 2 lines, 14 segments | Controls |
Only ST, BEG, the PO1 loop and SE are mandatory in a 004010 850; partners add terms (ITD), pack size (PO4), charges (SAC) or routing (TD5) as their guide says. Read each PO1 qualifier before its number. Line 1 is 24 x 41.50 = 996.00, line 2 is 6 x 12.80 = 76.80: 1,072.80 USD. Sold by the set (4 per case, says the PID), line 1 is 96 EA at 10.375; rounded to 10.38 it would total 996.48.
The 997 that goes back
ST*997*0001~ AK1*PO*101~ AK2*850*0001~ AK5*A~ AK9*A*1*1*1~ SE*6*0001~
AK1 names the group (PO, 101), AK2 the document, AK5 accepts it, AK9 the group: 1 included, 1 received, 1 accepted. It says nothing about delivery.
The 855 acknowledgment
ST*855*0001~ BAK*00*AC*PO-10457*20261027~ PO1*1*24*CA*41.50*CT*VP*BRK-220*BP*778-0042~ ACK*IA*24*CA*068*20261103~ PO1*2*6*EA*12.80*CT*VP*SEAL-14*BP*778-0187~ ACK*IQ*4*EA*068*20261103~ CTT*2~ SE*8*0001~
Only 4 of the 6 seals are available. BAK02 AC: lines follow, one differs. Line 1 is IA, line 2 IQ for 4 EA, both with a current schedule ship date (qualifier 068) of November 3.
The 856 ship notice
ST*856*0001~ BSN*00*SHP-5531*20261103*1400*0001~ HL*1**S~ DTM*011*20261103~ N1*ST*EXAMPLE BUYER DC 3*92*DC03~ HL*2*1*O~ PRF*PO-10457***20261027~ HL*3*2*P~ MAN*GM*00095212340000001027~ HL*4*3*I~ LIN**VP*BRK-220*BP*778-0042~ SN1**24*CA~ HL*5*3*I~ LIN**VP*SEAL-14*BP*778-0187~ SN1**4*EA~ CTT*5~ SE*17*0001~
BSN05 0001 announces shipment, order, pack, item. HL 1 is the shipment, shipped November 3 (DTM 011); HL 2 the order; HL 3 the pallet, by its SSCC in MAN; HL 4 and 5 the items, with what was packed in SN1. CTT01 counts the five HLs. A real 856 adds carrier, weight and bill of lading (TD5, TD1, REF) as the guide requires.
The 810 invoice
ST*810*0001~ BIG*20261103*INV-88120*20261027*PO-10457~ IT1*1*24*CA*41.50*CT*VP*BRK-220*BP*778-0042~ IT1*2*4*EA*12.80*CT*VP*SEAL-14*BP*778-0187~ TDS*104720~ CTT*2~ SE*7*0001~
BIG gives invoice date and number, then the PO date and number the buyer matches on. It bills what shipped: 24 x 41.50 + 4 x 12.80 = 1,047.20. TDS01 has two implied decimals, so it is sent as 104720; 1047 would mean 10.47. IT1 prices keep their decimal point.
| Line | Ordered (850) | Accepted (855) | Shipped (856) | Invoiced (810) |
|---|---|---|---|---|
| 1, BRK-220 | 24 CA | 24 CA (IA) | 24 CA | 24 CA, 996.00 |
| 2, SEAL-14 | 6 EA | 4 EA (IQ) | 4 EA | 4 EA, 51.20 |
With backorders, line 2 would add an ACK IB for 2 EA, covered by a later 856 and 810: the buyer's rule, not X12's.
Source: 850, 855, 856, 810, 997, date qualifiers, BSN05, TDS, data types (Stedi X12 004010 reference).
Sent as a PDF, the same order takes the same steps on the supplier's side, minus the 997: the confirmation, packing list and invoice go out the way that customer receives them.
The five documents above in one text file, as shown, to test a map or a parser. Everything in it is invented.
855 codes: the header type and the line status
The 855 reports back once the seller's system has processed the 850, affirming it or indicating changes (X12); it can also announce an order the vendor generated (855). BAK02 sets the kind of answer: AC when lines follow and one differs, AD when none does, AK for the header alone, RJ to reject. ACK01 gives each line's status: IA accepted, IQ quantity changed, IP price changed, DR date rescheduled, IB backordered, IR rejected. Both lists are longer: Stedi has them in full under element 587 and element 668.
Generate the 855 from the checked sales order, not from the 850: one sent the moment the order is translated says IA on lines the plant cannot ship.
The 856: hierarchy, SSCC, timing and the 945
X12 calls the 856 a critical transaction that ties the order to the delivery process (X12). Its body is a tree of HL segments: an ID (HL01), a parent (HL02) and a level, S shipment, O order, T tare, P pack, I item (element 735). BSN05 0001 orders them shipment, order, packaging, item; element 1005 lists the other structures. HL is the only mandatory segment of its loop, so a senseless tree still passes syntax (856). With carton detail, the pallet becomes T and each carton a P.
The SSCC
GS1's Serial Shipping Container Code identifies a logistic unit in 18 digits: extension digit, GS1 Company Prefix, serial reference, check digit. One scan at the dock links it to the ASN received in advance, which holds the product GTINs (GS1 US). A reprinted label keeps the number, a repacked unit gets a new one, and none is reallocated within a year of shipment (GS1 General Specifications 26.0, 2.2.1).
The sample uses GS1 prefix 952, reserved for examples: extension 0, prefix 9521234, serial 000000102, check digit 7 (1.2.3.1, 7.9.1). Under the barcode: (00) 095212340000001027, parentheses never encoded (4.14). In the 856: MAN*GM*00095212340000001027, 20 characters, since GM means SSCC-18 with its Application Identifier; AA is the 18 digits alone (element 88).
Timing, and the 945
The ASN must reach the receiver before the goods; the window is the partner's. Shopbop wants it within two hours of the shipment leaving the dock, one PO per ASN, MAN02 matching the GS1-128 label on every carton, and charges back an ASN not delivered before the shipment arrives (sections 5.3 and 10). Build the 856 from what was packed, never from the order.
Shipping from a third-party warehouse, the seller receives a 945 Warehouse Shipping Advice: the warehouse reports the shipment and reconciles ordered and shipped quantities (945). The 856 stays the seller's notice to its customer.
What each acknowledgment proves, and how files travel
A 997 reports syntax; AK3 and AK4 locate the errors. AK9 P means at least one document was rejected: resend those. The 997 does not cover meaning and is never itself acknowledged (997, element 715). A 999 also checks the partner's implemented subset (X12); a TA1 answers for the envelope (EdiFabric).
| Signal | What it shows | What it does not show |
|---|---|---|
| Signed AS2 receipt, verified | The message arrived intact | That it parsed |
| TA1 | The envelope was read or rejected | Anything inside it |
| 997 or 999, accepted | Syntax passed (and the partner's subset, for a 999) | That the order is accepted |
| 855 | Your answer, line by line | That the buyer agrees with a change |
Files move through a value-added network mailbox, over AS2 or over SFTP, which lacks AS2's proof of receipt (IBM). In AS2, signing, encryption and the receipt are each optional; a signed receipt, once verified, proves arrival, and HTTP success can coexist with an error disposition (RFC 4130, 2.4.2, 7.1, 7.6). An email order has none of these signals.
Checks before any order becomes a sales order
A translator that accepts an 850's syntax has not checked its content; an email order has had no check at all. These rules, recommended practice, apply to both.
| Check | What goes wrong | Rule |
|---|---|---|
| Currency | None stated, or not the agreement's | Hold; never assume one |
| Item | No cross-reference, or two | Hold until a person chooses |
| Identifier level | A consumer UPC (UP) where you sell the case (UK) | Map each qualifier to the right level |
| Unit | CA ordered, sold by EA; or CS for case, though 004010's CS is Cassette | Convert quantity and price together, or hold |
| Price | Off contract, or another price basis | Hold outside a stated tolerance |
| Dates | Past, or inside your lead time | Flag it; answer in the 855 if expected |
A PO number you already hold
It does not prove a duplicate: an order comes back five ways, and only the first two leave the ERP untouched. Email has the same five, without codes: a forwarded copy, a corrected PDF, "cancel line 2".
| What arrives | How to recognize it | What to do |
|---|---|---|
| Transport retry | Same sender, receiver, ISA15, ISA13 | Process nothing twice |
| Identical resend | New control numbers, same content; BEG01 may be 07 | No second order |
| Replacement | Same PO, new content; BEG01 05 | Hold and compare |
| Change | An 860, or an 850 used for changes (Shopbop's 850FR) | Change the existing order |
| Cancellation | An 860, or BEG01 01 | Cancel what has not shipped |
Source: Purpose codes, CA and CS, 860, Shopbop's 850FR, section 5.1.
The item, unit, price, ship-to, date and repeat PO checks as a spreadsheet: one row per order line, EDI or email, a hold when a check fails. Your items, prices and ship-to codes go in; no amount is filled in.
A failed order is exception handling: hold, show the reviewer the source, log the decision. See the sales order exception handling guide and the order entry error cost calculator.
Questions readers ask
The 850 is the buyer's purchase order. The 855 is the seller's answer once its system has processed it: BAK02 says whether the order is accepted, changed or rejected, and an ACK per line gives the status, quantity and date. A 997 only says the 850 parsed.
The trading partner decides: its guide asks for a 997, a 999 or neither, and sets the deadline. ISA14 requests something else, a TA1 on the envelope only. A 997 is never itself acknowledged, so no 997 ever answers a 997.
The 856 goes from the supplier to its customer and describes the shipment against the purchase order. The 945 goes from a warehouse to the seller, the depositor, to say a shipment was made and reconcile ordered and shipped quantities. A seller using a third-party warehouse may receive a 945, then send the 856.
An SSCC can identify any logistic unit, from a carton to a pallet; the partner's guide says which levels it wants labeled and described. With a pallet only, the pallet is the pack level; with carton detail, the pallet is the tare and each carton a pack with its own SSCC. Shopbop asks for one per carton.
Yes, without the customer setting up EDI. Software reads each order, runs the item, unit, price, ship-to and duplicate checks an 850 gets, writes the order to the ERP and holds for a person what it cannot confirm. The structure is what is lost: qualifiers, line counts and a 997 have to be rebuilt from the document.
Sources and scope
Checked on . X12 standards are copyrighted by ASC X12 and are not reproduced here; segment and code names come from X12's pages and Stedi's X12 004010 reference. GS1 rules from GS1 and GS1 US, AS2 from RFC 4130, one retailer's rules from its published manual, as an example. The order, its documents and the SSCC are invented.
- X12, Supply Chain Transaction Flow (x12.org): who sends the 850, 855, 860, 865, 856, 857, 810 and 820; the 855 reports back after the 850 has been processed; with an 857 no separate invoice is sent
- X12, Transaction Sets (x12.org): the 997 reports syntactical analysis, the 999 syntactical and relational analysis against a full or implemented subset; all X12 work products are copyrighted
- X12, Release Schedule (x12.org): published once per year, usually in January; 004010 available January 1998, 005010 January 2004, 008070 March 2026
- Stedi, X12 004010 reference: ISA Interchange Control Header: ISA01 to ISA16, names and fixed lengths; ISA14 requests a TA1
- Stedi, X12 004010 reference: element I14 Usage Indicator: I, P (Production Data), T (Test Data)
- Stedi, X12 004010 reference: GS Functional Group Header: GS01 to GS08; GS06 identical to GE02; GS08 version, release and industry identifier
- Stedi, X12 004010 reference: element 479 Functional Identifier Code: PO (850), PR (855), SH (856), IN (810), FA (997), SW (945)
- Stedi, X12 004010 reference: SE Transaction Set Trailer: SE01 counts the segments, ST and SE included
- EdiFabric, X12 Control Segments (vendor documentation): IEA02 must equal ISA13, GE02 GS06; ISA13 unique for the sender; TA1 errors on the envelope
- Stedi, X12 004010 reference: 850 Purchase Order: ST, BEG, the PO1 loop and SE mandatory, the rest optional; CTT01 is the number of PO1 segments
- Stedi, X12 004010 reference: element 353 Transaction Set Purpose Code: 00 Original, 01 Cancellation, 04 Change, 05 Replace, 07 Duplicate
- Stedi, X12 004010 reference: element 235 Product/Service ID Qualifier: UP, UK, EN, VN, VP, BP, IN
- Stedi, X12 004010 reference: element 355 Unit or Basis for Measurement Code: EA Each, CA Case, CS Cassette
- Stedi, X12 004010 reference: element 374 Date/Time Qualifier: 002 Delivery Requested, 011 Shipped, 068 Current Schedule Ship
- Stedi, X12 004010 reference: 855 Purchase Order Acknowledgment: BAK mandatory; ACK loop up to 104 per line; also a notice of a vendor generated order
- Stedi, X12 004010 reference: element 587 Acknowledgment Type: AC, AD, AE, AK, AT, RD, RJ
- Stedi, X12 004010 reference: element 668 Line Item Status Code: IA, IC, IP, IQ, DR, IB, BP, IR and the others
- Stedi, X12 004010 reference: 856 Ship Notice/Manifest: HL the only mandatory segment of its loop; CTT01 is the number of HL segments
- Stedi, X12 004010 reference: element 735 Hierarchical Level Code: S, O, T, P, I
- Stedi, X12 004010 reference: element 1005 Hierarchical Structure Code: 0001, 0002, 0004
- Stedi, X12 004010 reference: element 88 Marks and Numbers Qualifier: GM SSCC-18 and Application Identifier; AA SSCC-18
- Stedi, X12 004010 reference: 940 Warehouse Shipping Order: shipping requests from a seller to a warehouse, answered by a 945
- Stedi, X12 004010 reference: 945 Warehouse Shipping Advice: the warehouse advises the depositor that shipment was made, to reconcile order and shipment quantities
- Stedi, X12 004010 reference: 810 Invoice: BIG mandatory, IT1 loop, TDS the one mandatory total
- Stedi, X12 004010 reference: TDS Total Monetary Value Summary: TDS01, type N2: invoice total including charges, less allowances, before terms discount
- Stedi, Element data types in X12 EDI: N2 has two implied decimals: TDS*1000 means 10.00; ISA09 takes YYMMDD only
- Stedi, X12 004010 reference: 997 Functional Acknowledgment: AK1, AK2, AK5, AK9; does not cover semantic meaning; acknowledgments shall not be acknowledged
- Stedi, X12 004010 reference: element 715 Functional Group Acknowledge Code: A, E, P (at least one transaction set rejected), R
- GS1 US, An Introduction to the Serial Shipping Container Code (SSCC), release 3.0, February 2019: a logistic unit, 18 digits, one scan linked to the ASN, a new SSCC after repacking, GTIN in the ASN
- GS1, General Specifications Standard, release 26.0, January 2026: 1.2.3.1: prefix 952 for demonstrations and examples; 2.2.1: no reallocation within one year of shipment; 4.14: parentheses in human readable text only; 7.9.1: check digit
- Shopbop (Bop LLC), Vendor Operations Manual, July 2026: 5.1: required sets; 5.3: ASN within 2 hours of leaving the dock, one PO per ASN, MAN02 matching the GS1-128 label, one SSCC per carton; 10: chargeback for an ASN not received before the shipment
- IETF, RFC 4130, AS2, July 2005: 2.4.2: signing, encryption and receipts each optional; 7.1: what a signed receipt tells the sender; 7.6: HTTP success even when the disposition is an error
- IBM, What is EDI? (IBM Think): VAN mailboxes; AS2 with signatures and delivery notifications; SFTP without the same proof of receipt as AS2; best suited to high-volume, often repetitive documents in scheduled batches; a significant up-front cost; each partner's own requirements
- U.S. General Services Administration, GSA Global Supply vendor portal (updated June 2, 2026): EDI the preferred processing method; partners with small order volume and less technical proficiency may use the vendor portal
- Mirage Metrics, Biodéal case study: email orders into SAP Business One since July 22, 2025: 2,943 orders, 12,993 lines, 113 customers, median 48 seconds, about 7% flagged
This guide explains EDI practice for educational purposes. Your trading partner's implementation guide and agreements prevail over anything here.
Related on this site
- EDI alternative for small and mid-size customers: email and PDF orders written to the ERP like EDI orders
- How to automate order entry: EDI, a portal, OCR or an agent, by customer
- SAP sales order automation: the SAP Business One case
- Deduction and chargeback management: retailer deductions against your own records
- Glossary: EDI: the short definition
Send us the orders that never arrive as an 850
Send a batch of the email and PDF orders your team still keys. Each comes back as a sales order for your ERP, with the lines that need a decision flagged.
Prefer to talk it through? Book a call