Create Inbound Shipment label

The purpose of this service is to generate WFS Receiving Labels in various formats for receiving purposes. Please note this is not a carrier label; these labels are required for the FC to identify the Inbound Order and Shipment ID they are receiving against.Receiving labels are customizable:

  1. 3 size and format options are available to choose from through the LabelSize and LabelFormat fields:
    • 4 in. x 6 in. (PDF).
    • 4 in. x 3 1/3 in. (PDF).
    • 4 in. x 6 in. (ZPL).
  2. Provide the type of the label (box or pallet) in the LoadType field and the number of the labels needed in the Count field.
  3. Print the WFS receiving label.
  4. Affix the WFS receiving labels to the boxes/ pallets.

If none of the above optional inputs are provided, a blank 4 in. x 6 in. PDF format label will be generated. Sellers must work with the warehouse/supplier to provide the required details before sending any Shipments to WFS FCs:

  1. Print the WFS receiving label.
  2. Fill out the FILL OUT section based on the seller’s packing situation. For example, if a seller plans to ship 3 boxes to the WFS fulfillment center, print out 3 labels and fill out BOX 1 of 3, 2 of 3, and 3 of 3 in the FILL OUT section.
  3. Circle one shipment type in the CIRCLE ONE section. For example, if there are different SKUs in the box, circle MIXED SKUS in the CIRCLE ONE section.
  4. Affix the WFS receiving labels to the boxes/ pallets.
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Request fields

payload
object
required

Request Payload

Headers
string

A unique ID to track the consumer request by channel. Use the Consumer Channel Type received during onboarding

string
required

A unique ID which identifies each API call and used to track and debug issues; use a random generated GUID for this ID

string
required

Walmart Service Name

string
required

The Epoch timestamp

string
required

The vendor's digital signature, generated by running the JAR file or custom generation code

string
required

A unique ID required to access the API

string
required

Accept Header

Response

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/pdf