Set up items for WFS

All items must be Walmart Fulfillment Services (WFS) eligible before you can create an inbound order (IO) to the WFS fulfillment network.

Step 1: Make item WFS eligible

If you have not yet created your items, you can use the WFS Item spec to both set up and convert items for WFS items in one setup process.

  • The WFS Item JSON specification is available in the Marketplace Items guide under Item spec versions.
  • To create new WFS eligible items in one process, use the latest full spec for both Walmart and WFS. To learn more about Item Spec and how to set up items, refer to Get item setup requirements.
  • To learn more about how to create an item, refer to Create a new item (Full item setup) in the Items guide.

Step 2: Restrict item sale by geographic location

When setting up or converting items for WFS, you must specify sales restrictions by geographic location (state or ZIP code).

Step 3: Ensure required attributes are complete

The first 148 lines of the JSON spec are all required. Most required attributes are explicitly marked required in the spec file.

Within the Trade Item object with four optional attributes. At least one of them is required.

Trade item required attributes

In the TradeItem object, at least one of these attributes is required: each, inner pack, case, or pallet.

This example excerpt identifies the four TradeItem attribute groups, showing only the names of the attributes. The entire section of the attribute is required, so nested details are omitted for brevity.

"TradeItem": {   "$schema": "http://json-schema.org/draft-04/schema#",      "type": "object",      "properties": { . . . "each": { . . . "innerPack": { . . .   "case": { . . .    "pallet": { 

Step 4: Create an inbound purchase order

Once all items are WFS eligible, you can create an inbound purchase order.

Download and extract the Inbound Purchase Order JSON Schema: InboundPurchaseOrderSchema.zip.

The InboundPurchaseOrderSchema.zip contains the JSON Schema definitions for creating WFS inbound purchase orders. It specifies the payload structure, required fields, data types, and validation rules for purchase order metadata, ship-to facility details, shipments, and shipment item lines (SKU and quantities), including enumerations and date/time formats used for validation.