Inventory Interfaces

You can use the Inventory Interfaces as your data format specification to transfer inventory-related information between Walmart.com and Direct Ship Vendors. This article outlines guidelines for their usage.

Note: You can also view this article in Word format: Walmart.com Drop Ship Vendor_Inventory Interfaces_XML.docx

Functionality
Data files supported by these interfaces conform to the v4.0.0 XML specification. The files are as follows:

• Item Inventory File – Contains elements that reflect the current count of all items. (Sent from DSV to Walmart.com only).

Response files supported by these interfaces are as follows:

• Confirmation File – Contains a file confirmation (Sent from Walmart.com to DSV only).
• Error File – Contains a file error message (Sent from Walmart.com to DSV only).

Design Description
Each file transfer is divided into three basic steps:

1. The sender generates a data file and pushes it to the recipient's server.
2. The recipient parses the received file and validates the file format and data consistency.
3. If the file parses, the recipient replies with a Confirmation File to the sender. Otherwise, reply with an Error File.

Interface Design and Implementation

System Requirements

• Messages are sent between Walmart.com and the DSV as ASCII text files in XML format. After creating a file, its creator pushes it to the recipient.

Error Handling/Resend Process
Will use Error Files for messaging. There are two types of error response:

1. The received file is incomplete or invalid against the v4.0 DTD. In this case, the entire file is bad, and it’s assumed that no data was processed. The sender will receive only the Error File (no Confirmation File) and resend a valid file as soon as possible.
2. The file contains a message with bad data. In this case, only the error message is rejected, and all other messages in the file are processed. For example, if Walmart.com processes an Item Inventory file with 10 II_ITEM messages and finds 2 messages that contain bad data, then the following will occur:
   • Walmart.com sends a Confirmation File because the Item Inventory File is complete and valid against the v4.0 DTD.
   • Walmart.com sends an Error File with 2 FE_ERROR elements detailing the bad II_ITEM messages.
   • Walmart.com processes the other 8 II_ITEM messages.
   • Supplier resends the II_ITEM messages in a subsequent file.

Scheduling & Volume Analysis
Variations on the standard schedule (as described in the following) can be negotiated between each DSV and the Walmart.com Logistics Team. Outbound Walmart.com messages are generated as follows:

• Confirmation and Error Files – One or both of these messages are generated as each inbound file is processed (if applicable). The messages are placed in an outbound queue and transmitted every ten minutes.

Inbound Walmart.com messages are processed as they are uploaded to the gateway server. Each DSV is expected to send files as follows:

• Inventory Update – The DSV sends Item Inventory Files every 20 minutes. Vendors with many items can reduce the volume of inventory data by sending a full refresh once per day and update every 20 minutes containing items that have been changed since the last update.

Sample Inventory File

---

<?xml version="1.0" encoding="UTF-8"?>
<WMI>
<WMIFILEHEADER FILEID="225474.20091104.150503.841770" FILETYPE="FII" VERSION="4.0.0">
<FH_TO ID="2677" NAME="Walmart.com"/> <FH_FROM ID="123456" NAME="ABC brands">
<FH_CONTACT NAME=" ABC brands - Tom Clever" EMAIL="[email protected]" PHONE="2607235171" PHONEEXT="1067"/> </FH_FROM>
</WMIFILEHEADER>
<WMIITEMINVENTORY>
<II_ITEM ITEMNUMBER="10669104" UPC="0088333406931" SKU="BEACHR12 GOL">
<II_AVAILABILITY CODE="AC">
<II_ONHANDQTY>22</II_ONHANDQTY>
<II_DAYS MIN="1" MAX="2"/>
</II_AVAILABILITY>
</II_ITEM>
<II_ITEM ITEMNUMBER="10669105" UPC="0088333406932" SKU="BEACHR12 SIL">
<II_AVAILABILITY CODE="AC">
<II_ONHANDQTY>37</II_ONHANDQTY> <II_DAYS MIN="1" MAX="2"/>
</II_AVAILABILITY>
</II_ITEM>
<II_ITEM ITEMNUMBER="10669106" UPC="0088333406576" SKU="CDPCB">
<II_AVAILABILITY CODE="AC">
<II_DAYS MIN="1" MAX="2"/>
</II_AVAILABILITY>
</II_ITEM>
<II_ITEM ITEMNUMBER="10669107" UPC="0088333406921" SKU="CDRET">
<II_AVAILABILITY CODE="AC">
<II_DAYS MIN="1" MAX="2"/>
</II_AVAILABILITY>
</II_ITEM>
</WMIITEMINVENTORY>
</WMI>

General XML File Structure

Initial XML Declaration
The first line of the file defines the XML Standard version and the character encoding used in the file. The format for this is as follows:

XML Data Definition
Each data element (and its component attributes and sub-elements) is described in this document with the following information:

• XPath Location: The location of each element or attribute within the data element is defined based on Xpath notation.

  • If the Xpath begins with a “/” character, then it’s absolute within the XML message (e.g. “/WMI/WMIHEADER/FH_TO@ID”).
  • If the Xpath begins with any other character, then it’s relative to the specified reference node (e.g. “FH_TO@ID”, with a reference node of “/WMI/WMIHEADER”).

  For further information, see http://www.w3.org/TR/xpath.

• Optional/Required: Specifies whether each element or attribute is required to populate its parent element.

  • If optional, then the element or attribute can be populated with no data or omitted entirely. Note that most optional data must be populated based on certain conditional business rules, so this must be considered when validating the file.
  • If required, the element or attribute must exist and can not be empty.

• Data Type: Specifies the type of data that’s contained in an element or attribute.

  • “STR” – A string value that can contain alphanumeric characters and punctuation. This is parsed data, so any XML markup delimiters must be escaped with a character string as follows:

    • Replace greater than (>) with “>”
    • Replace less than (<) with “<”
    • Replace ampersand (&) with “&”
    • Replace double-quote (“) with “"”
    • Replace apostrophe (‘) with “'”
    • For more information, see http://www.w3.org/TR/REC-xml

  • “DEC” – A decimal value that contains only numeric data and a decimal point. If the decimal is not present, it’s implied at the end.

  • “NUM” – Numeric data that can’t contain any alphabetic characters or punctuation.

  • “DTM” – A formatted date/time value that contains only numeric and punctuation characters. It is formatted as “MM/DD/CCYY.hh24.mi”, where “MM/DD/CCYY” is the date and “hh24.mi” is the 24-hour time (e.g. “12/11/2001.17.01”).

  • “FID” – A formatted File ID that contains only numeric and punctuation characters. It is built from the file generation date and time, the WMFC vendor number, and a six-digit random number (to guarantee uniqueness). The format is:
    VVVVVVVVV.YYYYMMDD.HHMMSS.NNNNNN
    Using the following notation:

    • VVVVVVVVV is the Vendor ID assigned by Walmart.com (1 to 9 digits)
    • YYYYMMDD is an eight-digit file creation date (GMT date)
    • HHMMSS is a six-digit file creation time (24-hour GMT time)
    • NNNNNN is a six-digit random number.

    Note that these are the same fields used to generate an XML filename. The filename and the File ID will use the same date, time, and random number values.

• Data Length: Specifies the maximum length of the data as follows:

  • “STR” – Number of character digits. Note: When a character is escaped, the length of the data string expands. The length of the data string may be up to 6 times the number of string characters (for a case with all double-quote characters).
  • “DEC” – Expressed as “N.D” notation, where “N” is the number of characters allowed to the left of the decimal and “D” is the number of digits to the right. Note: Leading zeros are not required.
  • “NUM” – Number of numeric digits.
  • “DTM” – Number of characters in the formatted string.
  • “FID” – Number of characters in the formatted string.

WMIHEADER Element
The WMIHEADER element is the first element in any file. It contains a unique file ID, the sender's name, the sender's vendor number, and information for contacting the sender.

Note: for the FILETYPE value, use FII: File contains WMIITEMINVENTORY data element

Item Inventory XML File

Vendors use the Item Inventory File to periodically update the Walmart.com website's item information. This information tells customers whether an item is available through the website and how long it'll take to fulfill.

File Naming Convention
The file name contains the file type, creation date and time, the Supplier ID, and a six-digit random number. All filenames are case-sensitive.

The naming convention is:
WMI_Inventory_VVVVVVVVV_YYYYMMDD_HHMMSS_NNNNNN.xml

• Use the following notation:

• VVVVVVVVV is the Supplier ID assigned by Walmart.com (up to 9 digits)

• YYYYMMDD is a formatted file creation date (GMT date)

• HHMMSS is a formatted file creation time (24-hour GMT)

• NNNNNN is a six-digit random number to guarantee uniqueness.

Example: WMI_Inventory_999999_20010418_163108_097981.xml

WMIITEMINVENTORY Element
The WMIITEMINVENTORY element contains a group of inventory update messages. Each message from the supplier contains an update for a specific UPC. If data is missing or invalid, then II_ITEM elements can be individually rejected via a WMIFILEERROR file (see error handling section above).

• Availability Code Values:

• AC: Active – Item can be ordered only if the number of items on hand is sufficient to fulfill the amount ordered. An II_ONHANDQTY element is required, and an II_DAYS element is optional. If II_DAYS is not specified, a default range of 1 to 2 business days is assumed.

• AA: Always Available – This is for high-demand items that might drop to zero on hand but are restocked constantly. The supplier will accept orders, even if there is zero stock, and ship items as they become available. An II_DAYS element is required to indicate how long it will take to fulfill an order.

• PO: Pre-Order – Supplier is accepting pre-orders for the item. An II_START element is required to indicate when orders are expected to ship. In addition, an II_ONHANDQTY element is required to determine how many items may be pre-ordered. After the start date, it behaves like an active item (II_ONHANDQTY required and II_DAYS optional).

• JT: Just in Time – Item is stocked on demand. II_DAYS must indicate how long it will take to fulfill an order.

• BO: Build to Order – Item is pre-configured and manufactured on demand. II_DAYS must indicate how long it will take to fulfill an order. Since the supplier configures these items before the order is placed, it’s assumed that the item will always ship, and backorders aren't allowed.

• SE: Seasonal – Item is available but seasonal, and orders are only accepted during a specified date range. Both II_START and II_END elements are required to indicate the date range. Within the date range, it behaves like an active item (II_ONHANDQTY required and II_DAYS optional).

• RO: Run Out – Item is discontinued and will not be restocked. For II_INVENTORY, II_END indicates the last date on which orders will be accepted. Before the end date, it behaves like an active item (II_ONHANDQTY required and II_DAYS optional).

• NA: Not Active – Item isn't available for purchase at this time.

• DT: Deleted – Item isn't available for purchase and might be deleted from the catalog.

NOTE: Two availability code values will automatically remove an item from the Walmart.com site catalog. The “NA” code is used if it's possible that the item UPC may return at some time in the future and “DT” is used if the item UPC won't return (such as UPC is discontinued). Send at least two consecutive update messages before the UPC is removed from the inventory feed.**