The Loblaw 850 Purchase Order, explained

What Loblaw expects in the 850

Loblaw trades on X12 4010 over AS2. Beyond the base standard, watch these:

How EDISQ maps it

The certified Loblaw 850 map loads when you enable the partner — fields auto-map from NetSuite, QuickBooks, Dynamics, and 33 other systems, validation runs against Loblaw's spec before transmission, and the sandbox replays Loblaw test scenarios until everything passes.

Common rejection reasons

Nearly all 850 rejections trace to reference data, not syntax: identifiers that don't match Loblaw's cross-references, echoed fields dropped from the original PO, or timing that misses the program window. EDISQ flags each before Loblaw ever sees the document.

Sample Loblaw 850

A representative 850 interchange addressed to Loblaw — envelope, body segments, and control totals:

1ISA*00*          *00*          *ZZ*ACMESUPPLY     *ZZ*LOBLAW         *260101*1200*U*00401*000000001*0*P*>~
2GS*PO*ACMESUPPLY*LOBLAW*20260101*1200*1*X*004010~
3ST*850*0001~
4BEG*00*SA*PO12345**20260101~
5REF*DP*056~
6DTM*002*20260110~
7N1*ST*LOBLAW DC 5093*92*5093~
8PO1*1*24*EA*9.75**UP*012345678905~
9PID*F****ACME WIDGET 24CT~
10PO1*2*12*EA*14.50**UP*012345678912~
11PID*F****ACME GADGET 12CT~
12CTT*2~
13SE*11*0001~
14GE*1*1~
15IEA*1*000000001~

FAQ