Get Customer Return Orders status

Log in to see full request history
timestatususer agent
Retrieving recent requests…
LoadingLoading…

Provides the list of customer return orders with the corresponding details. The purpose of this service is to generate WFS Receiving Labels in various formats for receiving purposes. This is not a carrier label; these labels are required for the FC to identify the Inbound Order and Shipment ID they are receiving. Receiving labels are customizable:

Three size and format options are available to choose from through the LabelSize and LabelFormat fields:

  1. 4 in. x 6 in. (PDF).
  2. 4 in. x 3 1/3 in. (PDF).
  3. 4 in. x 6 in. (ZPL).

Provide the type of the label (box or pallet) in the LoadType field and the number of the labels needed in the Count field. Print the WFS receiving label. Affix the WFS receiving labels to the boxes/ pallets.
If none of the previous 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:

Print the WFS receiving label. Fill out the FILL OUT section based on the seller’s packing situation. For example, if a seller plans to ship three boxes to the WFS fulfillment center, print out three labels and fill out BOX 1 of 3, 2 of 3, and 3 of 3 in the FILL OUT section.

Circle one shipment type in the CIRCLE ONE section. For example, if there are different SKUs in the box, circle the MIXED SKUS in the CIRCLE ONE section. Affix the WFS receiving labels to the boxes/ pallets.

Query Params
string

Limiting the number of records fetched. Valid range is from 1 to 50 inclusive.

string

Setting an offset to skip records. Valid range is from 0 to 50000 inclusive.

string

Search the order based on an order number.

string

Search the order based on a return order number.

string

Search the order based on a start date (Date in YYYY-MM-DD format).

string

Search the order based on an endDate date (Date in YYYY-MM-DD format).

Headers
string
required

Basic authorization header. Base 64 encodes the Client ID and Client Secret retrieved in step two of the integration steps.

string
required

The access token retrieved in the Token API call

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

Response

Language
URL
Click Try It! to start a request and see the response here! Or choose an example:
application/json