Item setup schema key points

MPItemFeedHeader contains attributes that are applicable for all items in the submission. These headers are required and only need to be completed once per submission.

The MPItem object is completed for each item submitted. Sellers can include multiple items per submission. The MPItem object contains the Orderable and Visible schemas. If you are setting up a WFS item, the MPItem object will also contain the TradeItem object for you to provide all your logistic and critical attributes.

The Orderable object includes all the relevant attributes that Walmart requires to create an Offer for your item so that it may be sold on Walmart.com. The attributes included in this section may vary between Fulfillment channels (SFF vs WFS), for example, shipping dimensions are required for Seller Fulfilled Items, but Walmart Fulfilled items require TradeItem hierarchies. The Orderable object also includes the item’s primary identifier, such as its global trade item number (GTIN).

The Orderable object can include key attributes for specific Walmart Programs. For example, to create a pre-order item, you must complete theisPreOrder attribute as well as the conditionally required releaseDate attribute.

You can either add inventory during item setup or after the item setup is completed. To add inventory for pre-order items, find the Inventory attribute in the schema and update the three associated child attributes: Inventory Quantity, fulfillmentCenterID, and preOrderAvailableOn. Specify the pre-order availability date for inventory using the inventoryAvailabilityDate attribute in the yyyy-mm-dd format. This field is required for pre-order items setup but can be left blank for non-pre-order items. All these attributes are available in the Orderable schema and are conditionally required. Refer to the schema sample.

To add inventory for non-pre-order items, provide values for the Inventory Quantity, and fulfillmentCenterID attributes in the Orderable schema.

It’s very important to remember to check your submission to make sure all the Conditionally Required attributes have been filled out completely before submitting your entry.

NOTE: Enrollment is required for Pre-Order, Pre-Owned, and Restored programs.

In the Visible object, the seller must define the product type being set up. Based on the product type selected, the seller will complete the relevant attributes as identified in the feed file schema provided. Based on the chosen Product Type, attribute requirements, values, and recommendations will vary.

Additionally, if you’re using API specification version MP_ITEM-5.0.20240517-04_08_27, to create a Restored item, you must add the refurbished product identifier (GTIN, UPC, EAN) into the productID field. restoredProductIdentifier attribute is not available in the old specifications.

If you’re using the latest API specifications, to create a Restored item, you must add the refurbished product identifier (GTIN, UPC, EAN) into the productId and the restoredProductIdentifier fields. The value in these two fields must match. Failure to submit both fields will result in an error.

The Visible object may also contain key attributes for certain Walmart Programs. For Example, to create a Pre-Owned product, you must be enrolled in the pre-owned program and select the correct pre-owned Condition for your items. Refer to the WFS schema example in this article.

Attributes for the TradeItem object are only used for WFS. The item configurations defined in this section allow your items to have orders placed and be received by the Walmart Fulfillment centers.

The Product ID GTIN and dimension attributes for each are the only required attributes to successfully submit a WFS item. Make sure to provide each package dimensions and quantity for the item. The Orderable and Visible objects will contain the same item data, but each sellable TradeItem configuration will be independent of the trade item objects.