Zappos EDI Guideline
Zappos EDI GuidelineANSI X12 - 004010 855 Purchase Order AcknowledgmentVersion: 1.0Author:Created:Zappos07/08/2011
Electronic Data Interchange855 – Purchase Order Acknowledgment(Inbound to Zappos, X12 4010)July 2011Last updated: Date: 2012-08-31PurposeThis document provides detailed guidelines and conventions for implementing purchase orderacknowledgments with Zappos. Our 855 Purchase Order Acknowledgment, as detailed in thisdocument, will provide you with all of the information necessary to fill our requirements.These guidelines comply with published ASC X12 standards for EDI version 4010 for all dataelements and segments.Mandatory segments and elements are always required on every document. Optional segmentsand elements that are required by Zappos are marked as “Must Use”. Segment usage is marked atthe top of each page under Usage. Element usage is marked in the far-left column beside eachelement. If the column is blank, the element is optional. Information in the Attributes column isfrom the ASC X12 standards and is provided for reference only. Trading Partners must adhere toour requirements as indicated by “Must Use”.Business RulesZappos requires the UPC/EAN, the QTY, and the Price to be returned as acknowledged on the lineitem level. An 855 is required back within 2 business days or 48 hrs. Start Ship date isacknowledged on a header level not on item level* (see technical notes below). A second 855 isexpected to be sent if something changes on the vendors end. This second 855 is expected to besent at least 7 days before the start ship date of the PO. An 855 is not expected to be sent by avendor in response to an 860 if an 855 has already been received by Zappos. The exception wouldbe if there is a change request to the 860 on our vendors end.Technical Notes: If an item is not available for shipment within the requested shipping window, theseller may request a change to the entire order with a BAK02 type of AC (Acknowledge - WithDetail and Change) and updating the date information in the DTM segment or the seller may cancelthe item from the current order and contact Zappos to request a separate PO for that item with alater shipping window. Only the start ship date should be requested to be changed.ContactsEDI Teamedi@zappos.comCommunication IDs
TestingS/R ID: ZZ/ZAPPOSKYAccount/User ID: VANS/HAMAILProductionS/R ID: ZZ/ZAPPOSKYAccount/User ID: VANS/HAMAILDelimitersElement Separator - “*”(HEX “2A” in ASCII)(HEX “5C” in EBCDIC)Component (Sub Element) Separator - “ ”(HEX “3E” in ASCII)(HEX “6E” in EBCDIC)Segment Terminator - “\n”(HEX “0A” in ASCII)(HEX “15” in EBCDIC)
08/31/12Purchase Order Acknowledgment - 855Table of Contents855. .Purchase Order Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 1ISA. .Interchange Control Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 3GS. .Functional Group Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 5. .Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 7. .BAK Beginning Segment for Purchase Order Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 8ST. .REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 9. . 10SAC Loop SAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH . 11SAC Service, Promotion, Allowance, or Charge Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH ITD. . 13Terms of Sale/Deferred Terms of Sale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH . . 14DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH .LoopN1 PH N115N1. .Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 16N2. . 17Additional Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH N3. . 18Address Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH N4.Geographic Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 19. . 20PO1 Loop PO1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH . . 21PO1 Baseline Item Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH PID. . 23Loop PID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH . .PID Product/Item Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 24. . 25ACK Loop ACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH . . 26ACK Line Item Acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH SE. . 28Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH GE. . 29Functional Group Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH IEA.Interchange Control Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PH 30855 Zappos 4010.ecsi
08/31/12Purchase Order Acknowledgment - 855855Purchase Order AcknowledgmentFunctional Group PRThis Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase OrderAcknowledgment Transaction Set (855) 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 industrypractice relative to a seller's acknowledgment of a buyer's purchase order. This transaction set can also be used asnotification of a vendor generated order. This usage advises a buyer that a vendor has or will ship merchandise asprearranged in their partnership.Not Defined:PosIdSegment NameReqMax UseISAGSPosIdSegment Name010020STBAK050REFTransaction Set HeaderBeginning Segment forPurchase OrderAcknowledgmentReference IdentificationService, Promotion,Allowance, or ChargeInformationTerms of Sale/DeferredTerms of SaleDate/Time ReferenceRepeatNotesUsageInterchange Control HeaderM1Must useFunctional Group HeaderM1Must useReqMax UseMM11Must useMust useO 1Must useO1UsedO5UsedO10Must useHeading:LOOP ID - OOP ID - N1300310Repeat200NameAdditional NameInformationAddress InformationGeographic LocationOO12UsedUsedOO21UsedUsedReqMax UseDetail:PosSegment NameLOOPLOOPIDID--PO1PO1010PO1Baseline Item DataOPIDACKProduct/Item DescriptionO1Line Item AcknowledgmentO1DependentUsed104104Summary:855 Zappos 000001000001Dependent
08/31/12Purchase Order Acknowledgment - 855PosIdSegment Name030SETransaction Set TrailerReqMax UseM1ReqMax UseMM11RepeatNotesUsageMust useNot Defined:PosIdSegment NameGEIEAFunctional Group TrailerInterchange Control TrailerRepeatNotesUsageMust useMust useNotes:2/010L2/010PO102 is required.PO102 is required.User Note 1:Zappos requires the 855 (Purchase Order Acknowledgement) document in response to all 850 (Purchase Order)twoBusiness(2) BusinessDaysof receiving850.documents within 48Hoursof receivingthe the850.Change History:8/31/20122/17/2011Updated N2DatafromZAPPOSFULFILLMENT CENTERS, INC. TO C/O rsfromtheC/OACK01element:ICItemLLC.Accepted - Changes MadeKYDCDR Item Accepted - Date Rescheduled2/17/2011AddedUserto ACKsegmentRemovedtheNotefollowingqualifiersfrom the ACK01 element:IfitemAcceptedis not availablefor shipmentICanItem- ChangesMade within the requested shipping window, the seller may request a change tothe entireorder with- aDateBAK02type of AC (Acknowledge - With Detail and Change) and updating the dateDRItem AcceptedRescheduledinformation in the DTM segment or the seller may cancel the item from the current order and contact Zappos torequestUsera separateforsegmentthat item with a later shipping window.AddedNote toPOACKIf an item is not available for shipment within the requested shipping window, the seller may request a change tothe entire order with a BAK02 type of AC (Acknowledge - With Detail and Change) and updating the dateinformation in the DTM segment or the seller may cancel the item from the current order and contact Zappos torequest a separate PO for that item with a later shipping window.855 Zappos 4010.ecs2
08/31/12Purchase Order Acknowledgment - 855ISA Interchange Control HeaderPos:Max: 1Not Defined - MandatoryLoop: N/AElements: 16User Option (Usage): Must useTo start and identify an interchange of zero or more functional groups and interchange-related control segmentsElement Summary:RefIdElement NameISA01I01Authorization Information QualifierReqTypeMin/MaxUsageMID2/2Must useDescription: Code to identify the type of information in the Authorization InformationAll valid standard codes are used.ISA02I02Authorization InformationMAN10/10Must useDescription: Information used for additional identification or authorization of the interchangesender or the data in the interchange; the type of information is set by the AuthorizationInformation Qualifier (I01)ISA03I03Security Information QualifierMID2/2Must useDescription: Code to identify the type of information in the Security InformationAll valid standard codes are used.ISA04I04Security InformationMAN10/10Must useDescription: This is used for identifying the security information about the interchangesender or the data in the interchange; the type of information is set by the SecurityInformation Qualifier (I03)ISA05I05Interchange ID QualifierMID2/2Must useDescription: Qualifier to designate the system/method of code structure used to designatethe sender or receiver ID element being qualifiedAll valid standard codes are used.ISA06I06Interchange Sender IDMAN15/15Must useDescription: Identification code published by the sender for other parties to use as thereceiver ID to route data to them; the sender always codes this value in the sender IDelementExternal Information: This field will be the sender’s EDI IDISA07I05Interchange ID QualifierMID2/2Must useDescription: Qualifier to designate the system/method of code structure used to designatethe sender or receiver ID element being qualifiedAll valid standard codes are used.CodeNameZZMutually DefinedISA08I07Interchange Receiver IDMAN15/15Must useDescription: Identification code published by the receiver of the data; When sending, it isused by the sender as their sending ID, thus other parties sending to them will use this as areceiving ID to route data to themExternal Information: This field will be the Zappos EDI receiver IDFormatting Notes: ZAPPOSKY855 Zappos 4010.ecs3
08/31/12Purchase Order Acknowledgment - 855RefIdElement NameISA09I08Interchange DateReqTypeMin/MaxUsageMDT6/6Must useDescription: Date of the interchangeExternal Information: This field will be the date the EDI message was createdFormatting Notes: YYMMDDISA10I09Interchange TimeMTM4/4Must useDescription: Time of the interchangeFormatting Notes: HHMMISA11I10Must useMID1/1Interchange Control Standards IdentifierDescription: Code to identify the agency responsible for the control standard used by themessage that is enclosed by the interchange header and trailerAll valid standard codes are used.ISA12I11Interchange Control Version NumberMID5/5Must useDescription: Code specifying the version number of the interchange control segmentsAll valid standard codes are used.ISA13I12Interchange Control NumberMN09/9Must useDescription: A control number assigned by the interchange senderExternal Information: This field will be a unique control number representingthe ISA - IEA transactionISA14I13Acknowledgment RequestedMID1/1Must useDescription: Code sent by the sender to request an interchange acknowledgment (TA1)All valid standard codes are used.ISA15I14Usage IndicatorMID1/1Must useDescription: Code to indicate whether data enclosed by this interchange envelope is test,production or informationAll valid standard codes are used.CodePTISA16I15Data TypeProductionTestComponent Element SeparatorM1/1Must useDescription: Type is not applicable; the component element separator is a delimiter and nota data element; this field provides the delimiter used to separate component data elementswithin a composite data structure; this value must be different than the data elementseparator and the segment terminatorSample Data::ISA*00* *00* *ZZ*VENDOR *ZZ*ZAPPOSKY *120731*0832*U*00400*000000112*0*P* 855 Zappos 4010.ecs4
08/31/12Purchase Order Acknowledgment - 855Pos:GS Functional Group HeaderMax: 1Not Defined - MandatoryLoop: N/AElements: 8User Option (Usage): Must useTo indicate the beginning of a functional group and to provide control informationElement Summary:RefIdElement NameGS01479Functional Identifier CodeReqTypeMin/MaxUsageMID2/2Must useDescription: Code identifying a group of application related transaction setsCode NamePRGS02142Purchase Order Acknowledgement (855)Application Sender's CodeMAN2/15Must useDescription: Code identifying party sending transmission; codes agreed to by tradingpartnersGS03124Application Receiver's CodeMAN2/15Must useDescription: Code identifying party receiving transmission; codes agreed to by tradingpartnersGS04373DateMDT8/8Must useFormatting Notes: Date expressed as CCYYMMDDExternal Information: This field will be the date that the EDI was createdGS05337TimeMTM4/8Must useDescription: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, orHHMMSSD, or HHMMSSDD, where H hours (00-23), M minutes (00-59), S integerseconds (00-59) and DD decimal seconds; decimal seconds are expressed as follows: D tenths (0-9) and DD hundredths (00-99)GS0628Group Control NumberMN01/9Must useDescription: Assigned number originated and maintained by the senderExternal Information: This field will be a unique control number representingthe GS - GE transactionGS07455Responsible Agency CodeMID1/2Must useDescription: Code identifying the issuer of the standard; this code is used in conjunction withData Element 480All valid standard codes are used.GS08480Version / Release / Industry IdentifierCodeMAN1/12Must useDescription: Code indicating the version, release, subrelease, and industry identifier of theEDI standard being used, including the GS and GE segments; if code in DE455 in GSsegment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are therelease and subrelease, level of the version; and positions 7-12 are the industry or tradeassociation identifiers (optionally assigned by user); if code in DE455 in GS segment is T,then other formats are allowed855 Zappos 4010.ecs5
08/31/12Purchase Order Acknowledgment - 855CodeName004010 Draft Standards Approved for Publication by ASC X12 Procedures Review Boardthrough October 1997Semantics:1. GS04 is the group date.2. GS05 is the group time.3. The data interchange control number GS06 in this header must be identical to the same data element in theassociated functional group trailer, GE02.Comments:1.1. A functional group of related transaction sets, within the scope of X12 standards, consists of acollection of similar transaction sets enclosed by a functional group header and a functional group trailer.Sample 4010855 Zappos 4010.ecs6
08/31/12Purchase Order Acknowledgment - 855Pos: 010ST Transaction Set HeaderMax: 1Heading - MandatoryLoop: N/AElements: 2User Option (Usage): Must useTo indicate the start of a transaction set and to assign a control numberElement Summary:RefIdElement NameST01143Transaction Set Identifier CodeReqTypeMin/MaxUsageMID3/3Must use4/9Must useDescription: Code uniquely identifying a Transaction SetCode Name855ST02329Purchase Order AcknowledgmentTransaction Set Control NumberMANDescription: Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction setExternal Information: This field will be a unique control number representingthe ST - SE transactionSemantics:1.1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to selectthe appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).Sample Data::ST*855*0001855 Zappos 4010.ecs7
08/31/12Purchase Order Acknowledgment - 855Pos: 020BAK Beginning Segment forMax: 1Heading - MandatoryPurchase OrderAcknowledgmentLoop: N/AElements: 4User Option (Usage): Must useTo indicate the beginning of the Purchase Order Acknowledgment Transaction Set and transmit identifying numbersand datesNote: PO Acknowledgments with missing BAK segments will fail and cannot be processed by Zappos.Element Summary:RefIdElement NameBAK01353Transaction Set Purpose CodeReqTypeMin/MaxUsageMID2/2Must useID2/2Must use1/22Must useDescription: Code identifying purpose of transaction setCode Name00BAK02587OriginalAcknowledgment TypeMDescription: Code specifying the type of acknowledgmentCode NameACADRJAcknowledge - With Detail and ChangeAcknowledge - With Detail, No ChangeRejected - No DetailUser Note 1:When BAK02 “AC” or “AD”, PO1 is required.When BAK02 “RJ”, PO1 is not used.BAK03324Purchase Order NumberMANDescription: Identifying number for Purchase Order assigned by the orderer/purchaserExternal Information: This field needs to contain the Zappos PO numberUser Note 1:
(Inbound to Zappos, X12 4010) July 2011 . Last updated: Date: 2012-08-31. . These guidelines comply with published ASC X12 standards for EDI version 4010 for all data . Zappos requires the 855 (Purchase Order Acknowledgement) document in response to all 850 (Purchase Order) documents within 48 Business Hours of receiving the 850.
4010 EDI documents (note EDIFACT transaction sets will be required by Amazon EU divisions): EDI 753 - Request for Routing Instructions EDI 855 - PO Acknowledgement EDI 754 - Routing Instructions EDI 856 –Advance Ship Notice EDI 810 - Invoice EDI 860 –PO Change Request EDI 846 - Inventory Advice/Update EDI 865 –PO Change Seller
collection of EDI data is received in a batch. The batch of EDI data includes a plurality of EDI documents and each of the plurality of EDI documents has at least one EDI transaction corresponding to a transaction type. The EDI transactions included in the EDI documents are identified by decoding the received EDI data according to EDI standards.
Zappos, an online retailer, is proving that it can. The company’s revenue grew from 1.6 million in 2000 to 1.64 billion in 2010. Tony Hsieh, Zappos’ CEO says, “It’s a brand about happiness, whether to customers or employees or even vendors.” Zappos’ zany corporate culture and focus on customer satisfaction has made it bothFile Size: 229KB
Larry Hernandez of Zappos d Inspired opening: Self summary or employer brand ad for Zappos? Larry’s summary is written to inspire candidates. Listing Zappos’ core values helps candidates self-select, saving him and them time! Show vs. tell: The Zappos Family Music Video demonstrates the company’s
King Fish Media Case Study ZAPPOS.COM Online retailer uses storytelling through custom "magalogs" to bring the Zappos culture and lifestyle to print. 1. BULOVA "MARINE STAR" Decadent stainless steel timepiece with 24 gorgeous diamonds. Available in Stainless Steel (shown). SKU# 7482271. 285.00 12 PUT A LITTLE ZAPPOS IN YOUR DAY!
4010 EDI documents (note EDIFACT transaction sets will be required by Amazon EU divisions): EDI 753 - Request for Routing Instructions EDI 855 - PO Acknowledgement EDI 754 - Routing Instructions EDI 856 – Advance Ship Notice EDI 810 - Invoice EDI 860 – PO Change Request
1. What is EDI? 2. What is the 'Omni-hannel' 3. Omni-Channel EDI solutions 4. Where does EDI fit into the marketplace? 5. Third Party Logistics (3PL) EDI 6. Online Retailers and CommerceHub EDI 7. eCommerce Platform EDI 8. B2BGateway EDI and QuickBooks Online 9. Pricing 10. Customer Service 11. B2BGateway Fact Sheet & Trading Partners 12 .
Some digital banking features may not be available depending on your computer, mobile device or operating system. You may not be able to access all the products and services we offer through digital banking. We can restrict access to digital banking for any of the reasons set out in your Product terms. We may add products and services you receive (individually or jointly with someone else .
