Message ImplementationGuidelinePurchase Order MessageORDERS(Based on the EANCOM 2002 Guideline using UN/EDIFACT Directory D.01B)Version 1.5May 2020

Document Change ControlDocument VersionV1.0V1.1V 1.2Released02 February 201615 March 201623 May 2016BySPS CommerceSPS CommerceSPS CommerceV 1.308 March 2018SPS CommerceV 1.405 December 2019SPS CommerceV 1.508 May 2020SPS CommerceChangesDraft ReleaseAdded THE ICONIC GLNAdded Shipmentdate/time, requested inHeader DTMUpdate to TOD segmentChanged the maximumlength for fields, Ordernumber, supplier/ vendornumber and Vendor PartNumber.Added new currency codeCADAdded new order type,consignment order.Purpose of this Implementation GuideThe purpose of this guide is to provide suppliers with the necessary information to enable theimplementation of receipt of electronic Orders message (Purchase Order) from THE ICONIC.Who should use this GuideThis guide is intended for use by THE ICONIC suppliers to prepare for the implementation of ElectronicData Interchange (EDI) and to assist with applications integration, thereby ensuring successful electronictrading.Copyright 2016 SPS Commerce2THE ICONIC ORDERS

EDIFACT Specifications1 UN/EDIFACT Specifications1.1 Definition of UN/EDIFACTUN/EDIFACT: United Nations rules for Electronic Data Interchange for Administration, Commerce andTransport. They comprise a set of internationally agreed standards, directories and guidelines for theelectronic interchange of structured data, and in particular that related to trade in goods and services,between independent computerized information systems - EDI systems.1.2 UN/EDIFACT SyntaxThe UN/EDIFACT syntax rules set the standards for structuring data into segments, segments intomessages, and messages into an interchange.1.2.1 Structure of an InterchangeAn interchange may consist of the following segments:Segment IDSegment NameStatusUNAService String AdviceConditionalUNBInterchange HeaderMandatoryFunctional Group HeaderConditionalMessage HeaderMandatoryUNGUNHUser Data SegmentsUNTUNEUNZMessage TrailerMandatoryFunctional Group TrailerConditionalInterchange TrailerMandatorySegments starting with "UN" are called service segments. They constitute the envelope or the "packing"of the EDIFACT messages. User data segments contain the information itself, in a format specific to eachmessage type.Copyright 2016 SPS Commerce3THE ICONIC ORDERS

1.2.2 Structure of a MessageEach data segment has a specific place within the sequence of segments in the message. They may occurin any of the following three sections of the message: Heading section - A segment occurring in this section relates to the entire message.Detail section - A segment occurring in this section relates to the detail information only.Summary section - Only segments containing totals or control information may occur in the summarysection, e.g. invoice total amount, number of lines in a purchase order, etc.The same segment type may occur in more than one of the message sections, e.g. in the header and inthe detail section, and/or more than once in the same section.Some segments may be repeated a certain number of times at their specific location in the message. Thestatus, Mandatory or Conditional, and the maximum number of repetitions of segment types are indicatedin the message structure.Within a message, specific groups of functionally related segments may be repeated; these groups arereferred to as "segment groups". The maximum number of repetitions of a particular segment group at aspecific location is included in the message definition.A segment group may be nested within other segment groups, provided that the inner segment groupterminates before any outer segment group terminates.1.2.3 Segment StructureA segment consists of: A segment tag: identifies the segment typeData element separatorsSimple, composite, or component data elementsA segment terminatorData elements can be defined as having a fixed or variable length.A composite data element contains two or more component data elements.A component data element is a simple data element used in a composite data element.A data element can be qualified by another data element, the value of which is expressed as a code thatgives specific meaning to the data. The data value of a qualifier is a code taken from an agreed set of codevalues.Copyright 2016 SPS Commerce4THE ICONIC ORDERS

1.2.4 SeparatorsIn EANCOM four service characters (extracted from UNOA) have a special meaning and act as the defaultseparators for EANCOM;ASCIIHEXApostrophe‘27Segment terminatorDecimal Point.2EDecimal PointPlus sign 2BSegment tag and data element separatorColon:3AComponent data element separatorQuestion mark?3FRelease character; immediately preceding one ofthe service characters, it restores their normalmeaning. E.g. 10? 10 20 means 10 10 20.Question mark is represented by ?Copyright 2016 SPS Commerce5THE ICONIC ORDERS

1.3 UN/EDIFACT Documentation Conventions1.3.1 Format and Picture of Data ElementsThe following conventions apply in the present documentation:Aalphabetic charactersNnumeric charactersAnalpha-numeric charactersa33 alphabetic characters, fixed lengthn33 numeric characters, fixed lengthan33 alpha-numeric characters, fixed lengtha.3up to 3 alphabetic charactersn.3up to 3 numeric charactersan.3up to 3 alpha-numeric charactersThe format and picture of the data elements that will be used by THE ICONIC in the following EDIdocuments comply with the UN/EDIFACT Standards.1.3.2 Status indicatorsThere are five types of status used in the following pages, whether for simple, component or compositedata elements. They are listed below and can be identified when relevant by the abbreviations.MSpecified within the Standards as Mandatory, used as a trigger element.Must UseRequired by THE ICONIC for specific implementation or business rulesDDependent on a mutual agreement between the sender and receiver of themessage, governed by Business rules and / or a special arrangement, i.e.Primary Freight, etc.OData that can be omitted based on an agreement between the sender andreceiver.Not UsedSegment/data elements defined as optional by standard specification and arenot required for this Implementation. Data elements or composite elements notused preceding those indicated otherwise are shown for additional clarity.Unused trailing elements will not be shown in this document.Copyright 2016 SPS Commerce6THE ICONIC ORDERS

1.3.3 Interchange StructureThe interchange structure in an EDIFACT transmission is organized in several grouping levels. Theservice segments are the envelope of the groups.The first service segment possible in an interchange is the ‘UNA’ segment which is used to define theseparators being used in the interchange. The second service segment, ‘UNB’, indicates the beginning ofthe interchange. The next one, ‘UNG’, indicates the beginning of a group of messages of the same type,for example invoices. The last service segment, ‘UNH’, indicates the beginning of a given message. Toeach beginning service segment corresponds an ending service segment (note, UNA is not a beginningsegment).Service string advice:UNAInterchange envelope:UNB . UNZGroup envelope:UNG . UNEMessage envelope:UNH . UNTSegment UNA is dependent on the character set being used. THE ICONIC interchanges will include theUNA segment, as the UN/EDIFACT character set (C) will be used.Segments UNG.UNE are Conditional/Optional. These segments will not be sent as standard in this MIG.1.3.4 Interchange Control Structure (Envelope)Introduction:The Service String Advice, UNA, and the service segments UNB to UNZ shall appear in the below statedorder in an interchange. There may be several functional groups or messages within an interchange andseveral messages in a functional group. A message consists of s Max.Use0000 UNAService String AdviceOO10010 UNBInterchange HeaderMM10020 UNHMessage HeaderMM10030 UNTMessage TrailerMM10040 UNZInterchange TrailerMM1Copyright 2016 SPS Commerce7Notes andRepeat CommentsTHE ICONIC ORDERS

THE ICONIC use of the Purchase Order (ORDERS)messageBusiness RulesSuppliers will be required to support the receipt of Purchase Order from THE ICONIC as part of theprocess of automating THE ICONIC orders shipping to the Distribution Center.THE ICONIC will be sending Purchase Orders in the Ship To DC/Stand Alone order management modeland will expect that a Purchase Order Response (ORDRSP) message is returned within 48 hours foreach Purchase Order reporting any exceptions and advising the expected shipment/delivery dates.Suppliers will not be allowed to over supply or substitute the items in the Despatch Advice messages, asany items not included in the original Purchase Order / Purchase Order Change should be rejected.THE ICONIC will review the supplier’s requested changes based on the information sent in the ORDRSPmessage.THE ICONIC will send an updated Purchase Order as an electronic Purchase Order Change request tothe supplier for:requested changes they are in agreement or against in the Purchase Order Response message.any changes initiated by the buyer.THE ICONIC will transmit ORDERS message with Document Name Code 230 in BGM segment toindicate Purchase Order Change request.Suppliers are expected to update THE ICONIC order with the changes indicated in the Purchase OrderChange and are expected to confirm acceptance or rejection of the change through an electronicPurchase Order Response (ORDRSP).Suppliers are expected to pack and label as requested in the Purchase Order / Purchase Order Changeand transmit an Despatch Advice messages, representing the contents of the shipment, shortly after theshipment is in route (prior to the arrival at THE ICONIC location).THE ICONIC requires the transmission of Despatch Advice messages from suppliers prior to the deliveryof goods and the invoice after the delivery of goods as standard best practice.Suppliers must send one Despatch Advice messages per Purchase Order per delivery. A supplier canmake multiple deliveries for an order within the agreed delivery window. One Despatch Advice messagesshould only refer to one Purchase Order / Purchase Order Change.Suppliers must not send any Invoice for consignment order.Copyright 2016 SPS Commerce8THE ICONIC ORDERS

ORDERS Purchase Order MessageIntroduction:The ORDERS message specifies details for goods or services ordered under conditions agreed betweenthe vendors and THE ICONIC.Notes:This Message Implementation Guide (MIG) is based on the EANCOM 2002 Australian Retail IndustryImplementation Guidelines for the Purchase Order Message derived from the international UN/EDIFACTdirectory D.01B.This MIG is designed to support the transmission of THE ICONIC’s order flow for the supply chainprocesses for DC’sDependency notes:An original purchase order message will convey the following functional usage indicators:- Standard delivery request: Applicable to all purchase orders.An original purchase order message will convey the following functional usage indicators:- Standard delivery request: Applicable to all purchase orders.A change/ replace purchase order message will convey the following functional usage indicators:- Standard delivery request: Applicable to all purchase orders.Business rules:1) THE ICONIC will be the generator / sender of the purchase order message.2) There will be single delivery locations within each purchase order transmitted with a unique THEICONIC' order number.3) All messages received from THE ICONIC must be acknowledged promptly with a ControlAcknowledgment message specified by THE ICONIC.4) Purchase order responses (ORDRSP) are required for all purchase orders according to business rulesspecified in the MIG for that message.5) All required data in this MIG must be provided to be compliant with the requirements of the AustralianTaxation for THE ICONIC Suppliers.6) All messages received from THE ICONIC must be checked for duplicate Interchange ControlReference numbers and Purchase Order numbers.Usage notes:M: Specified within the Standards as Mandatory, used as a trigger element.R: Required by THE ICONIC for specific implementation or business rulesD: Dependent on a mutual agreement between the sender and receiver of the message, governed bybusiness rules and / or a special arrangement.O: Data that can be omitted based on an agreement between the sender and receiver.X: Segment/data element defined as optional by standard specification and are not required for thisImplementation. Data elements or composite elements that are not used preceding those indicatedotherwise are shown for additional clarity. Trailing elements that are not used will not be shown in thisdocument.THE ICONIC is THE ICONIC Electronics"Attribute" is the EDI standards definitionCopyright 2016 SPS Commerce9THE ICONIC ORDERS

"User Attribute" is "THE ICONIC Definition"Heading Section:Pos.No.Seg.IDUNANameService String AdviceReq.Des.MM0005UNBInterchange HeaderM1M0010UNHMessage HeaderM1M0020BGMBeginning of MessageM1M0030DTMDate/Time/PeriodM2D0070FTXFree TextC10M0120Segment Group 2: NAD-SG5MM0130Name and AddressMO0220Segment Group 5: CTA-COMOM0230CTAContact InformationM1D0240COMCommunication ContactC3O0290M0300O0460M0470MNADCUXTODSegment Group 7: CUXOCurrenciesMSegment Group 12: TODOTerms of Delivery or TransportMMax.Use1GroupRepeatNotes andComments3111111Detail Section:Seg.IDMust UsePos.No.1030M1040LINNameSegment Group 28: LIN-PIA-IMD-MEAQTY-MOA-SG32-SG38-SG43Line ItemM1O1050PIAAdditional Product IdC2O1060IMDItem yM1M1120MOAMonetary AmountM2M1320Segment Group 32: PRIMM1330Price Req.Des.CSegment Group 38: TAXODuty/Tax/Fee DetailsMSegment Group 43: ALC-SG46OAllowance or ChargeMMax.UseGroupRepeat9999Notes andComments1111101Segment Group 46: MOAOMonetary AmountM1NameSection ControlReq.Des.MMax.Use1Max.Use31Section Control:MPos.No.2330Seg.IDUNSGroupRepeatNotes andCommentsGroupRepeatNotes andCommentsSummary Section:MPos.No.2340Seg.IDMOANameMonetary AmountReq.Des.MM2350CNTControl TotalC2M2400UNTMessage TrailerM1M2420UNZInterchange TrailerM1Copyright 2016 SPS Commerce10THE ICONIC ORDERS

Segment:Position:Group:Level:Usage:Max Use:Purpose:UNA Service String Advice0Mandatory1To define the characters selected for use as delimiters and indicators in the restof the interchange that follows. The specifications in the Service string advicetake precedence over the specifications for delimiter etc. in UNB segment. Whentransmitted, the Service string advice must appear immediately before theInterchange Header (UNB) segment and begin with the upper case charactersUNA immediately followed by the six characters selected by the sender toindicate, in the following sequence: UNA: .? ‘Notes:Example:UNA: .? ‘Data Element SummaryData ComponentElement Element NameAttributesM0010COMPONENT DATA ELEMENT SEPARATORComposite element delimiter: ColonMan.1M0020DATA ELEMENT SEPARATORData element delimiter Plus signMan.1M0030DECIMAL NOTATIONMan.1The character transferred in this position shall be ignored by the recipient.Retained to maintain upward compatibility with earlier versions of thesyntax. Full stop / PeriodM0040RELEASE INDICATORMan.1Release indicator is used to signify that the following texts contain one ofthe characters used as composite, data or segment delimiter, hencerelease its usage convention for that instance.? Question markM0050RESERVED FOR FUTURE USENot used.White space (blank)M0060SEGMENT TERMINATORMUsed to delimit the end of the current segment and start a newsegment.‘ ApostropheCopyright 2016 SPS Commerce11Man.1an.1THE ICONIC ORDERS

Segment:Position:Group:Level:Usage:Max Use:Purpose:Dependency Notes:Semantic Notes:Comments:Notes:UNB Interchange Header00050Must Use1To start, identify and specify an interchangeAll messages implemented based on EANCOM 2002 will use syntax level C, version 3as indicated in DE 0001 and DE 0002 as UNOC:3.This supports all characters defined in ISO 8859-1 : Information processing - Part 1:Latin alphabet No. 1Example:UNB UNOC:3 9377779346556:14 SUPPLIER GLN:14 160202:0730 1679730 1'UNB UNOC:3 TST1THEICONIC:ZZZ SUPPLIER GLN:14 160202:0730 1679730 1'MMMMMMust UseData Element SummaryData ComponentElement Element NameAttributesS001SYNTAX IDENTIFIERM1Identification of the agency controlling the syntax and indication ofsyntax level.0001Syntax identifierMa4Coded identification of the agency controlling a syntax and syntax levelused in an interchange.UNOCUN/ECE level CAs defined in ISO 8859-1 : Information processing Part 1: Latin alphabet No. 1.0002Syntax version numberMn1Version number of the syntax identified in the syntax identifier (0001).3Version 3ISO 9735 Amendment 1:1992.S002INTERCHANGE SENDERM1Identification of the sender of the interchange.0004Sender identificationMan.35Name or coded representation of the sender of a data interchange.THE ICONIC will use the following addresses:0007Copyright 2016 SPS CommerceProduction EDI Identifier9377779346556Testing & Certification EDI IdentifierTST1THEICONICPartner identification code qualifierCan.4Qualifier referring to the source of codes for the identifiers ofinterchanging partners.14EAN (European Article Numbering Association)Partner identification code assigned by theEuropean Article Numbering Association.THE ICONIC code qualifier used for ProductionZZZMutually definedTHE ICONIC code qualifier used for Testing &Certification12THE ICONIC ORDERS

Not UsedM0008S003M0010Must Use0007Not Used0014MS004M0017M0019M0020Not UsedS005Not Used0022Not Used0025Not Used0026Not Used0029Must Use0031Copyright 2016 SPS CommerceAddress for reverse routingCan.14Address specified by the sender of an interchange to be included by therecipient in the response interchanges to facilitate internal routing.INTERCHANGE RECIPIENTM1Identification of the recipient of the interchange.Recipient identificationMan.35Name or coded representation of the recipient of a data interchange.Partner identification code qualifierCan.4Qualifier referring to the source of codes for the identifiers ofinterchanging partners.14EAN (European Article Numbering Association)Partner identification code assigned by theEuropean Article Numbering Association.ZZZMutually DefinedRouting addressCan.14Address specified by the recipient of an interchange to be included bythe sender and used by the recipient for routing of receivedinterchanges inside his organization.DATE AND TIME OF PREPARATIONM1Date and time of preparation of the interchange.Date of preparationMn6Local date when an interchange or a functional group was prepared.Date in YYMMDD format, i.e. March 7th, 2016 is presented as 160307Time of preparationMn4Local time of day when an interchange or a functional group wasprepared.Time in 24 hour-clock format, i.e. 3:30 PM is presented as 1530INTERCHANGE CONTROL REFERENCEM1 an.14Unique reference assigned by the sender to an interchange.This data element is specified as alphanumeric and, for all THE ICONICimplementations, only numbers are accepted as interchange control.The value presented here must match with the value presented in DE0020 in segment UNZ.RECIPIENTS REFERENCE PASSWORDC1Reference or password as agreed between the communicatingpartners.Recipient reference/passwordMan.14Unique reference assigned by the recipient to the data interchange or apassword to the recipient's system or to a third party network asspecified in the partners interchange agreement.Recipient reference/password qualifierCan2Qualifier for the recipient's reference or password.APPLICATION REFERENCEC1 an.14Identification of the application area assigned by the sender, to whichthe messages in the interchange relate e.g. the message identifier if allthe messages in the interchange are of the same type.PROCESSING PRIORITY CODEC1 a1Code determined by the sender requesting processing priority for theinterchange.ACKNOWLEDGEMENT REQUESTC1 n1Code determined by the sender for acknowledgement of theinterchange.13THE ICONIC ORDERS

Not Used0032Not Used0035Copyright 2016 SPS CommerceFor all outbound messages from THE ICONIC, this indicator will alwaysbe used as a request for a CONTRL message to be returned to THEICONIC.Refer to D.01B Data Element Dictionary for acceptable code values.COMMUNICATIONS AGREEMENT IDC1 an.35Identification by name or code of the type of agreement under which theinterchange takes place.TEST INDICATORC1 n1Indication that the interchange is a test.14THE ICONIC ORDERS

Segment:Position:Group:Level:Usage:Max Use:Purpose:Dependency Notes:Semantic Notes:Comments:Notes:UNH Message Header00100Must Use1A service segment starting and uniquely identifying a message. The messagetype code for the Purchase order message is ORDERS.Example:UNH 1679730 ORDERS:D:01B:UN:EAN010'MMData Element SummaryData ComponentElement Element NameAttributes0062MESSAGE REFERENCE NUMBERM1 an.14Unique message reference assigned by the sender.THE ICONIC will only send one message per interchange. The uniquemessage number is always the same as the Interchange ControlReference (DE0020) in the UNB segment. DE0062 in UNH segment willbe exactly the same as DE0062 in the UNT segment.S009M0065M0052M0054M0051Copyright 2016 SPS CommerceMESSAGE IDENTIFIERM1Identification of the type, version etc. of the message beinginterchanged.Message type identifierMan.6Code identifying a type of message and assigned by its controllingagency.ORDERSPurchase order messageA code to identify the purchase order message.Message type version numberMan.3Version number of a message type.DDraft version/UN/EDIFACT DirectoryMessage approved and issued as a draft message(Valid for directories published after March 1993 andprior to March 1997). Message approved as astandard message (Valid for directories publishedafter March 1997).Message type release numberMan.3Release number within the current message type version number(0052).01BRelease 2001 - BMessage approved and issued in the second 2001release of the UNTDID (United Nations Trade DataInterchange Directory).Controlling agencyMan.2Code identifying the agency controlling the specification, maintenanceand publication of the message type.UNUN/CEFACTUnited Nations Centre for Trade Facilitation andElectronic Business (UN/CEFACT).15THE ICONIC ORDERS

Must Use0057Not Used0068Not UsedS010Not Used0070Not Used0073Copyright 2016 SPS CommerceAssociation assigned codeCan.6Code, assigned by the association responsible for the design andmaintenance of the message type concerned, which further identifiesthe message.EAN010EAN Version Control NumberCOMMON ACCESS REFERENCEC1 an.35Reference serving as a key to relate all subsequent transfers of data tothe same business case or file.STATUS OF THE TRANSFERC1Statement that the message is one in a sequence of transfers relatingto the same topic.Sequence message transfer numberMn.2Number assigned by the sender indicating that the message is anaddition or change of a previously sent message relating to the sametopic.First/last sequence message transfer indicationCa1Indication used for the first and last message in a sequence of the sametype of message relating to the same topic.16THE ICONIC ORDERS

Segment:Position:Group:Level:Usage:Max Use:Purpose:Dependency Notes:Semantic Notes:Comments:Notes:BGM Beginning of Message00200Must Use1A segment by which the sender must uniquely identify the order by means of itsname and number and when necessary its function.The following notes are applicable to the BGM segment only:NoteWhen C002 DE 1001 230 then suppliers are required to replace the previousversion of Purchase order with the current version in its entirety.Example:Original purchase orderBGM 220 RE-WAPM000265 9'An updated transmission (Replacement order and/or cancellation order) can besent by THE ICONIC. Purchase Order Response is expected according to anagreed set of business rules.Replacement purchase order will supersede the purchase order sent previously.BGM 230 RE-WAPM000265 5'Cancellation purchase order will supersede the purchase order sent previously.BGM 230 RE-WAPM000265 1'Original consignment orderBGM 227 CO-CAPM000123 9'Data Element SummaryData ComponentElement Element NameAttributesMust UseC002DOCUMENT/MESSAGE NAMEC1Identification of a type of document/message by code or name. Codepreferred.Must Use1001Document name codeCan.3Code specifying the document name.Conditional: Standard Purchase Order. Required if all other conditionsdo not match.220Order227Consignment orderOrder to deliver goods into stock with agreement onpayment when goods are sold out of this stockInvoice must not be sent by suppliers for thistype of order.230Purchase order change requestChange to a purchase order already sent.Not Used1131Code list identification codeCan.17Not Used3055Code list responsible agency codeCan.3Not Used1000Document nameCan.35Copyright 2016 SPS Commerce17THE ICONIC ORDERS

Must UseC106DOCUMENT/MESSAGE IDENTIFICATIONC1Identification of a document/message by its number and eventually itsversion or revision.Must Use1004Not UsedNot UsedMust Use105610601225Not Used4343Copyright 2016 SPS CommerceDocument identifierCan.35To identify a document.THE ICONIC's purchase order numberFormat: AlphanumericMinimum length: 1Maximum length: 20Version identifierCan.9Revision identifierCan.6MESSAGE FUNCTION CODEC1 an.3Code indicating the function of the message.Code value 9 will only be sent when C002 DE 1001 220Value 5 and 1 will be sent when C002 DE 1001 2301CancellationMessage cancelling a previous transmission for agiven transaction.5ReplaceMessage replacing a previous message.9OriginalInitial transmission related to a given transaction.RESPONSE TYPE CODEC1 an.318THE ICONIC ORDERS

Segment:Position:Group:Level:Usage:Max Use:Purpose:Comments:Notes:DTM Date/Time/Period00301Must Use2A segment specifying general dates and, when relevant, times related to thewhole message. The segment must be specified at least once to identify theorder date.This segment is used to specify dates/times relating to the Purchase Orderand/or dates relating to the delivery of the goods.DE 2005: Identification of the 'Document/message date/time' (code value 137) ismandatory in an EANCOM message.Example:Purchase Order creation dateDTM 137:20160601:102'Delivery Requested window dateDTM 64:20160705:102'DTM 63:20160805:102'Shipment Requested (Ex-Factory Ship Date ) dateDTM 10:20160701:102'MMMust UseData Element SummaryData ComponentElement Element NameAttributesC507DATE/TIME/PERIODM1Date and/or time, or period relevant to the specified date/time/period type.2005Date or time or period function code qualifierMan.3Code qualifying the function of a date, time or period.10Shipment date/time, requestedDate on which goods should be shipped or dispatchedby the supplier.Conditional: Ex-Factory Ship Date, transmitted forvendors if outlined in their contractual paymentterms.63Delivery date/time, latestDate identifying a point of time after which goods shallnot or will not be delivered.64Delivery date/time, earliestDate identifying a point in time before which the goodsshall not be delivered.137Document/message date/time(2006) Date/time when a document/message is issued.This may include authentication.Required: System generated date when thepurchase order is created.2380Copyright 2016 SPS CommerceDate or time or period valueCan.35The value of a date, a date and time, a time or of a period in a specifiedrepresentation.19THE ICONIC ORDERS

Must Use2379Copyright 2016 SPS CommerceDate or time or period format codeCan.3Code specifying the representation of a date, time or period.102CCYYMMDDCalendar date: C Century ; Y Year ; M Month ; D Day.20THE ICONIC ORDERS

Segment:Position:Group:Level:Usage:Max Use:Purpose:Dependency Notes:Semantic Notes:Comments:Notes:MNot UsedNot UsedMust UseMNot UsedNot UsedNot UsedNot UsedNot UsedNot UsedFTX Free Text00701Optional99A segment with free text information, in coded or clear form, used whenadditional information is needed but cannot be accommodated within othersegments. In computer to computer exchanges such text will normally requirethe receiver to process this segment manually.This segment is used to provide any free text information related to the completepurchase order response message.Dependency Note:DE C108: This composite is only used if coded text cannot be used.Example:FTX AAB TERMS OF PAYMENT: Direct Entry Credit to a Vnd 30 days FromStatement’Data Element SummaryData ComponentElement Element NameAttributes4451TEXT SUBJECT CODE QUALIFIERM1 an.3Code qualifying the subject of the text.AABTerms of payments[4276] Conditions of payment between the parties toa transaction (generic term).4453FREE TEXT FUNCTION CODEC1 an.3C107TEXT REFERENCEC1C108TEXT LITERALC1Free text; one to five lines.4440Free text valueMan.512Free form text.Required: Used by THE ICONIC for free for terms of payment text4440Free text valueCan.5124440Free text valueCan.5124440Free text valueCan.5124440Free text valueCan.5123453LANGUAGE NAME CODEC1 an.34447FREE TEXT FORMAT CODEC1 an.3Copyright 2016 SPS Commerce21THE ICONIC ORDERS

Group:Position:Group:Level:Usage:Max Use:Purpose:Notes:NAD Segment Group 2: Name and Address01201Must Use3A group of segments identifying the parties with associated information.Example:THE ICONIC's buyer is a storeNAD BY 9377779346556::9 THE ICONIC CNR COMWAY & CARRINGTONSTREETS LISMORE NSW 2480'CTA PD :Buyer Name'COM (02) 8885 2326:TE'COM [email protected]:EM'Supplier:NAD SU 8353296::92 SUPPLIER PTY LTD PO BOX 999 CAROLEPARK QLD 4300'CTA PD :Supplier contact'COM (02) 8885 2326:TE'COM [email protected]:EM'Segment SummaryMPos.No.01300220Seg.IDNADNameName and AddressSegment Group 5: Contact InformationCopyright 2016 SPS Commerce22Req.Des.MCMax.Use1Group:Repeat1THE ICONI

V1.0 02 February 2016 SPS Commerce Draft Release V1.1 15 March 2016 SPS Commerce Added THE ICONIC GLN V 1.2 23 May 2016 SPS Commerce Added Shipment date/time, requested in Header DTM Update to TOD segment V 1.3 08 March 2018 SPS Commerce Changed the maximum length for fields, Order number, supplier/ vendor number and Vendor Part