We recently received notice that effective this month, all vendors trading with Target.com will be required to implement an EDI solution. The details of the change including concerns for specific EDI document numbers can be found below:

As we move away from the VCommerce (Channel Intelligence) solution, we require that all vendors implement an EDI solution to connect with Target.com.  This is the only way that you will be able to receive purchase orders, send inventory feeds, and send advance ship notifications.  Attached are new specifications.

Specific EDI Document Changes:

846

• Not accepting the QTY segment any longer (must use SDQ segment)

850

• REF, DTM, N9 segments are now defined as “Must Use”
• REF segment we will be sending a “WS” warehouse storage location number
• DTM02 is a now a “Must Use”
• TD503 (Identification Code) element we will NOT be sending a SCAC code value
• TD505 (Routing) we will be sending a custom code as listed in the guideline
• TD512 (Service Level Code) we will be sending a EDI standard code instead of “ZZ” – Mutually Defined
• MSG segment – we will not be sending this segment.  This segment has been previously used for return method for packing slip. In the past this data printed on the packing slip at the line item level.  Going forward no return method text will be printed on the packing slip.
• PO110 (Product/Service ID Qualifier) element we will sending either UP, UA, UK or IB instead of always UP

855

• ACK029 element will be used to identify a rejection reason from a list of possible reasons.

856

• LIN, SN1, PRF, TD5 (at shipment level), MAN, DTM (at order level) segments are now defined as “Must Use”
• BSN05 (Hierarchical Structure Code) is now a “Must Use” element.  Only allow a value of 0004 or ZZZZ (blank is no longer allowed).
• TD503 (Identification Code)  element we are expecting a valid 4-digit SCAC code (USPN, BNAF, CEVA, FDEX,….)
• TD505 element (Routing) we are expecting a custom code
• TD512 element (Service Level Code) we are expecting an EDI standard code.  We are not expecting a “ZZ” – Mutually Defined
• N1 segment we are only expecting the Ship From Information

860

• REF segment is now defined as “Must Use”
• In the REF segment we will send two occurrences; one containing the vendor id and one containing the guest order number

865

• POC and ACK segments are now defined as “Must Use”
• Removed DTM segment from guideline at header and detail

If you have any questions about the changes, feel free to post them in the comments below or contact us. For more information on our EDI solutions, visit our website.

Article by Kevin Martin

Kevin is the Marketing Coordinator at eBridge and manages the company website, blog, and social media outlets.

EDI - Our Customers Trading Partner Series, EDI Integration, EDI Tips and Tricks, Integration edi, target, update