POST Item Maintenance by Product Type: Feed File Structure Overview
The POST Bulk Item Maintenance by Product Type request uses feed files to submit data. A feed consists of an API request with an attached file, called the feed file or load file. The feed file contains a list of records (for example, items) that suppliers submit for processing.
POST Item Maintenance by Product Type: Feed File Structure Overview
The POST Item Maintenance by Product Type request uses a single feed file to update item records. Suppliers can use the Item Maintenance feed file to either:
- Maintain the item content of any single item, regardless of the channel the item is sold
- Manage the supply chain information for an item
POST Item Maintenance by Product Type feed files have the following basic JSON schema structure:
{ "title": "SupplierItemFeed", "properties": { "SupplierItemFeedHeader": { "type": "object", "description": "Contains attributes applicable to the entire submission. Only required one time for the item(s) being updated." }, "SupplierItem": { "minItems": 1, "description": "This object is used to define each unique item update included in the submission.", "type": "array", "items": { "properties": { "Orderable": { "type": "object", "description": "The attributes related to Walmart ordering the item or for compliance purposes. Required for each product content update and must include the Primary Identify - GTIN-14." }, "Visible": { "type": "object", "description": "Contains all Product Types that can be selected for Item Maintenance and all of the possible attributes that can be maintained. This is not a required object for maintenance.", "properties": { "Product Type 1": "Animal Feed", "Product Type 2": "Tires" } }, "SupplyChain": { "type": "object", "description": "Object used to update Item Configurations and Supply Chain attributes. User must select the appropriate Supply Chain Object that the item configuration is sold to Walmart. This can be found in the GET Single Item v4 API in the attribute channelSold. Primary Identifier for each update is both the Product ID (GTIN) and Walmart Item Number (WIN).", "items": { "properties": { "DSVSupplyChain": { "type": "object", "description": "Used to update items sold via Drop Ship Vendor (DSV) channel." }, "OnlineSupplyChain": { "type": "object", "description": "Used to update item configurations sold to Walmart and only available for sale on walmart.com" }, "StoreSupplyChain": { "type": "object", "description": "Used to update item configurations sold to Walmart available for sale in Stores Only or Stores and on Walmart.com" } } } } } } } }
}
This schema maintains either of the following:
- An item's product content
- An item configuration's supply chain information
In both cases, users only need to provide the product identifier—either global trade item number (GTIN) only or GTIN and Walmart item number (WIN)—and the attributes they want to update. The feed file schema provided will define all attributes and include all definitions and examples.
If users update an item's product content (including images), then they must submit the Orderable
or Orderable
and Visible
objects in the SupplierItem
object. In the Visible
section, users must select the relevant product type for the item. Only attributes relevant to the selected product type will be accepted as identified in the schema file.
If users update an item configuration's supply chain information, then they must select the relevant SupplyChain
object. This selection is based on the channel the item is sold to Walmart.
Channel options are:
- Drop ship vending (
DSVSupplyChain
) - eCommerce only, shipped to a fulfillment center (FC) or distribution center (DC) (
OnlineSupplyChain
) - Sold in stores (
StoreSupplyChain
)
Users can find the item's Walmart item number (WIN) and the channel sold with the GET An Item request after the item has been set up.
Updated about 17 hours ago