Bed Bath & Beyond
/
Purchase Order
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Bed Bath & Beyond. Contact Bed Bath & Beyond for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Bed Bath & Beyond logo

X12 850 Purchase Order

X12 Release 4010

This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business and industry practice relative to the placement of purchase orders for goods and services. This transaction set should not be used to convey purchase order changes or purchase order acknowledgment information.

---
  1. BBB may include multiple MSG segments at the header level and item level. Please refer to the 850 overlay at the end of this section as an example.
  2. BBB may send a revised purchase order. A revised PO will be a replacement PO and include a revision number in the BEG04.
  3. The company will be defined in the N1 “BY- Buying Party” segment. The company code sent in the N104 will need to be sent back in the invoice.
  4. The store will be defined in the N1 “ST – Ship To” segment. The store code in the N104 will need to be sent back in the invoice.
  5. The N1 “SF – Ship From” segment will be included if you have multiple shipping locations to define the specific location.
  6. Items will be identified by the Vendor Part number and/or description.
  7. BBB will issue POs and PO revisions with zero cost items and zero qty items. Zero qty and zero cost items will appear when a PO or item(s) on the PO are canceled. Zero cost items will appear when an item is no charge or vendor determined. Please contact your buyer if you have any questions.
Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • Typical Order
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/bed-bath-beyond/purchase-order/01GYW4E323ZND62GYVA2RRM7JR
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
BEG
020
Beginning Segment for Purchase Order
Max use 1
Required
REF
050
Reference Identification
Max use 1
Optional
FOB
080
F.O.B. Related Instructions
Max use 1
Optional
ITD
130
Terms of Sale/Deferred Terms of Sale
Max use 1
Optional
DTM
150
Date/Time Reference
Max use 10
Optional
Buying Party (Purchaser)
detail
PO1 Loop
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer

U
U.S. EDI Community of ASC X12, TDCC, and UCS
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

This version number covers the interchange control segments

00401
Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator

>
Component Element Separator

Functional Group Header

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

PO
Purchase Order (850)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

GS-04
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

GS-05
337
Time
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

Code used in conjunction with Data Element 480 to identify the issuer of the standard

T
Transportation Data Coordinating Committee (TDCC)
X
Accredited Standards Committee X12
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed

004010
Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Heading

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

Code uniquely identifying a Transaction Set

  • The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
850
Purchase Order
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BEG
020
Heading > BEG

Beginning Segment for Purchase Order

RequiredMax use 1

To indicate the beginning of the Purchase Order Transaction Set and transmit identifying numbers and dates

Usage notes

BBB will issue POs and PO revisions with zero cost items and zero qty items. Zero qty and zero cost items will appear when a PO or item(s) on the PO are canceled. Zero cost items will appear when an item is no charge or vendor determined. Please contact your buyer if you have any questions.

Example
BEG-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

00
Original
BEG-02
92
Purchase Order Type Code
Required
Identifier (ID)

Code specifying the type of Purchase Order

SA
Stand-alone Order
BEG-03
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

BEG-04
328
Release Number
Optional
String (AN)
Min 1Max 30

Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction

Usage notes

Revision Number (changes)

BBB may send a revised purchase order. A revised PO will be a replacement PO and include a revision number.

BEG-05
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BEG05 is the date assigned by the purchaser to purchase order.
REF
050
Heading > REF

Reference Identification

OptionalMax use >1

To specify identifying information

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

IA
Internal Vendor Number
REF-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

BBB assigned Vendor Number.

FOB
080
Heading > FOB

F.O.B. Related Instructions

OptionalMax use >1

To specify transportation instructions relating to shipment

Example
FOB-01
146
Shipment Method of Payment
Required
Identifier (ID)

Code identifying payment terms for transportation charges

  • FOB01 indicates which party will pay the carrier.
CC
Collect
PP
Prepaid (by Seller)
FOB-03
352
Description
Optional
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

ITD
130
Heading > ITD

Terms of Sale/Deferred Terms of Sale

OptionalMax use >1

To specify terms of sale

Example
ITD-01
336
Terms Type Code
Optional
Identifier (ID)

Code identifying type of payment terms

  • If the code in ITD01 is "04", then ITD07 or ITD09 is required and either ITD10 or ITD11 is required; if the code in ITD01 is "05", then ITD06 or ITD07 is required.
01
Basic
ITD-12
352
Description
Optional
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

DTM
150
Heading > DTM

Date/Time Reference

OptionalMax use 10

To specify pertinent dates and times

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

002
Delivery Requested
DTM-02
373
Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

N1 Buying Party (Purchaser)
OptionalMax 1
Variants (all may be used)
Ship FromShip To
N1
310
Heading > Buying Party (Purchaser) > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Usage notes

The company will be defined in this segment. The company code sent in the N104 will need to be sent back in the invoice.

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

BY
Buying Party (Purchaser)
N1-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

Usage notes

Bed Bath & Beyond (BBB)
Christmas Tree Shops (CTS)
Harmon Stores
Buybuy BABY
BBB Canada

N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

Usage notes

Assigned by BBB.

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
String (AN)

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
0010
Bed Bath & Beyond (BBB)
0020
Christmas Tree Shops (CTS)
0030
Harmon Stores
0040
Buybuy BABY
0060
Cost Plus
5050
BBB Canada
N1 Buying Party (Purchaser) end
N1 Ship From
OptionalMax 1
Variants (all may be used)
Buying Party (Purchaser)Ship To
N1
310
Heading > Ship From > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Usage notes

This segment will be included if you have multiple shipping locations to define the specific location.

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

SF
Ship From
N1-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

Usage notes

Vendor Name

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

Usage notes

Assigned by BBB.

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Usage notes

Shipper Location

N1 Ship From end
N1 Ship To
OptionalMax 1
Variants (all may be used)
Buying Party (Purchaser)Ship From
N1
310
Heading > Ship To > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Usage notes

The store will be defined in this segment. The store code in the N104 will need to be sent back in the invoice.

Example
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

ST
Ship To
N1-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

Usage notes

Store Name

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

Usage notes

Assigned by BBB.

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

Code identifying a party or other code

  • This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
Usage notes

Store Number

N3
330
Heading > Ship To > N3

Address Information

OptionalMax use 2

To specify the location of the named party

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

Usage notes

Store Address Line 1

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 55

Address information

Usage notes

Store Address Line 2

N4
340
Heading > Ship To > N4

Geographic Location

OptionalMax use >1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Optional
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Optional
Identifier (ID)
Min 2Max 2

Code (Standard State/Province) as defined by appropriate government agency

  • N402 is required only if city name (N401) is in the U.S. or Canada.
N4-03
116
Postal Code
Optional
Identifier (ID)
Min 3Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

N1 Ship To end
SPI Loop
OptionalMax >1
SPI
450
Heading > SPI Loop > SPI

Specification Identifier

RequiredMax use 1

To provide a description of the included specification or technical data items

Example
SPI-01
786
Security Level Code
Required
Identifier (ID)

Code indicating the level of confidentiality assigned by the sender to the information following

ZZ
Mutually Defined
MSG
480
Heading > SPI Loop > MSG

Message Text

OptionalMax use 50

To provide a free-form format that allows the transmission of text information

Usage notes

BBB may include multiple MSG segments at the header level and item level.

Example
MSG-01
933
Free-Form Message Text
Required
String (AN)
Min 1Max 264

Free-form message text

SPI Loop end
Heading end

Detail

PO1 Loop
RequiredMax >1
PO1
010
Detail > PO1 Loop > PO1

Baseline Item Data

RequiredMax use 1

To specify basic and most frequently used line item data

  • PO102 is required.
Example
If Unit or Basis for Measurement Code (PO1-03) is present, then Quantity Ordered (PO1-02) is required
If either Product/Service ID Qualifier (PO1-06) or Product/Service ID (PO1-07) is present, then the other is required
PO1-01
350
Assigned Identification
Optional
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • PO101 is the line item identification.
Usage notes

Line Number

PO1-02
330
Quantity Ordered
Optional
Decimal number (R)
Min 1Max 15

Quantity ordered

Usage notes

Total quantity ordered.

PO1-03
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

CA
Case
DZ
Dozen
EA
Each
GS
Gross
PR
Pair
ST
Set
YD
Yard
PO1-04
212
Unit Price
Optional
Decimal number (R)
Min 1Max 15

Price per unit of product, service, commodity, etc.

Usage notes

Item Cost

PO1-06
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

  • PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
VA
Vendor's Style Number
PO1-07
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Vendor's Style Number

PID Loop
OptionalMax >1
PID
050
Detail > PO1 Loop > PID Loop > PID

Product/Item Description

RequiredMax use 1

To describe a product or process in coded or free-form format

Example
PID-01
349
Item Description Type
Required
Identifier (ID)

Code indicating the format of a description

  • If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
F
Free-form
PID-05
352
Description
Optional
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

Usage notes

Description for BBB UPC.

PID Loop end
PO4
090
Detail > PO1 Loop > PO4

Item Physical Details

OptionalMax use >1

To specify the physical qualities, packaging, weights, and dimensions relating to the item

Example
PO4-01
356
Pack
Optional
Numeric (N0)
Min 1Max 6

The number of inner containers, or number of eaches if there are no inner containers, per outer container

Usage notes

Case Pack Quantity

TD5
250
Detail > PO1 Loop > TD5

Carrier Details (Routing Sequence/Transit Time)

OptionalMax use 12

To specify the carrier and sequence of routing and provide transit time information

Example
TD5-05
387
Routing
Optional
String (AN)
Min 1Max 35

Free-form description of the routing or requested routing for shipment, or the originating carrier's identity

Usage notes

Load Sequence

MSG
289
Detail > PO1 Loop > MSG

Message Text

OptionalMax use >1

To provide a free-form format that allows the transmission of text information

Usage notes

BBB may include multiple MSG segments at the header level and item level.

Example
MSG-01
933
Free-Form Message Text
Required
String (AN)
Min 1Max 264

Free-form message text

PO1 Loop end
Detail end

Summary

CTT Loop
OptionalMax >1
CTT
010
Summary > CTT Loop > CTT

Transaction Totals

RequiredMax use 1

To transmit a hash total for a specific element in the transaction set

  • The number of line items (CTT01) is the accumulation of the number of PO1 segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.
Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

Usage notes

Total Number of PO1 Segments

CTT Loop end
SE
030
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

Typical Order

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231030*0221*U*00401*000000001*0*T*>
GS*PO*SENDERGS*RECEIVERGS*20231030*022118*000000001*X*004010
ST*850*10001
BEG*00*SA*2445913-00*0*20071014
REF*IA*000101185
FOB*CC**FOB ORIGIN
DTM*002*20071121
N1*SF*MEG*92*ABCD
N1*BY*Bed Bath & Beyond*92*0010
N1*ST*EDGEWATER*92*115
N3* 489 RIVER ROAD
N4* EDGEWATER*NJ*07020~
SPI*ZZ
MSG*RT GDE COLLECT
MSG*HEADER COMMENT
MSG*PO TYPE CP NEW STORE
MSG*SUPPORT TICKET
MSG*DEPT/ROOM/STORE
MSG*APPROVER
PO1*1*120*EA*15.2**VA*WMSWB
PID*F****24”X48” SHELF WHITE
PO4*10
TD5*****TRUCK 1
PO1*2*72*EA*5.05**VA*WMSWC
PID*F****12”X36” SHELF WHITE
PO4*6
TD5*****TRUCK 1
PO1*3*60*EA*8.4**VA*WMSWQ
PID*F****12”X48” SHELF WHITE
PO4*6
TD5*****TRUCK 2
MSG*SUPPLEMENTAL REASON CODE A
MSG*SUPPLEMENTAL LINE #
MSG*ITEM COMMENT
MSG*CHANGE COMMENT
CTT*3
SE*35*10001
GE*1*000000001
IEA*1*000000001

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.