Guides
My Account

Update lag time for an item

Use the Lag time feed to update fulfillment lag time for many SKUs in one request. Lag time is the number of days between order date and ship date. Most items must ship the same day or the next day. If you need 2 days or more, request approval at the category level first. Use this endpoint to:

  • Set or change lag time for multiple SKUs.
  • Target a specific ship node when your catalog uses multiple nodes.
  • Align item handling times with your operational reality.

Prerequisites

  • Walmart Marketplace API access and OAuth 2.0 token.
  • Approval for any values that are 2 days or more.
  • Knowledge of your SKUs, optional GTINs, and any ship node IDs.

Best practices

  • Keep lag time at 0 or 1 day whenever possible.
  • Request approval before you set 2 days or more.
  • Start with a small pilot feed. Expand after you confirm processing results.
  • Use a unique WM_QOS.CORRELATION_ID per request to simplify support.
  • Match the payload to the official schema files. Do not add extra fields.
  • Align values with your operations. Do not set a value you cannot meet.

Endpoint

POST `https://marketplace.walmartapis.com/v3/feeds?feedType=lagtime`

This endpoint submits a bulk feed to update lag time.

Query parameters

  • feedType = lagtime (required)

Required headers

  • WM_SEC.ACCESS_TOKEN
  • WM_QOS.CORRELATION_ID
  • WM_SVC.NAME
  • WM_CONSUMER.CHANNEL.TYPE (optional)
  • Accept: application/json
  • Content-Type: application/json or application/xml

Request body

Supply one or more items. Each item should include an identifier and a fulfillmentLagTime value in days.

JSON (example)
Assumption, based on common feed patterns and your attachment. Confirm wrapper names in the schema package before production.

{ "lagTime": [ { "sku": "ABC-123", "fulfillmentLagTime": 1 }, { "sku": "DEF-456", "fulfillmentLagTime": 2, "shipNode": "1234567890" }, { "gtin": "00012345678905", "fulfillmentLagTime": 0 } ]
}

XML (example)
Assumption. Wrapper and element names may differ. Use the Lag Time schema from the portal’s ZIP package when you prepare XML.

<LagTimeFeed> <lagTime> <sku>ABC-123</sku> <fulfillmentLagTime>1</fulfillmentLagTime> </lagTime> <lagTime> <sku>DEF-456</sku> <shipNode>1234567890</shipNode> <fulfillmentLagTime>2</fulfillmentLagTime> </lagTime> <lagTime> <gtin>00012345678905</gtin> <fulfillmentLagTime>0</fulfillmentLagTime> </lagTime>
</LagTimeFeed>

Request and response

Sample request

curl -L 'https://marketplace.walmartapis.com/v3/feeds?feedType=lagtime' -H 'WM_QOS.CORRELATION_ID: 1c9a6f4e-9f74-4b2b-bd7f-2a7e9a9d1a01' -H 'WM_SVC.NAME: Walmart Marketplace' -H 'WM_SEC.ACCESS_TOKEN: <access_token>' -H 'Accept: application/json' -H 'Content-Type: application/json' -d '{ "lagTime": [ { "sku": "ABC-123", "fulfillmentLagTime": 1 }, { "sku": "DEF-456", "fulfillmentLagTime": 2, "shipNode": "1234567890" } ] }'

Modify your code

  1. Keep feedType=lagtime in the query string.
  2. Replace the example SKUs with your identifiers. You can send sku or gtin for each line.
  3. If your catalog uses multiple ship nodes, include shipNode for the items that require it.
  4. Set fulfillmentLagTime to the number of days you can meet in operations. Use 0 or 1 unless you have approval for 2 or more.
  5. Replace <access_token> with a valid OAuth 2.0 token in the WM_SEC.ACCESS_TOKEN header.
  6. Generate a new unique WM_QOS.CORRELATION_ID for every request. Keep WM_SVC.NAME and the Accept and Content-Type headers as shown.
  7. Send the request body as JSON or XML that matches the Lag Time schema. Do not add extra fields.
  8. Read the 202 response and capture feedId.
  9. Poll GET /v3/feeds/{feedId} until processing completes. Review any line level errors.
  10. Spot check a few items with GET /v3/lagtime to confirm the new values.

Result

{ "feedId": "3AF227D8C8E649E1B0A4D2B1F8E4C7A6", "feedType": "lagtime", "ingestionStatus": "INPROGRESS", "itemsReceived": 2
}

Check processing status

After you submit the feed, poll feed status to confirm success and review any errors.

GET `https://marketplace.walmartapis.com/v3/feeds/{feedId}`

Typical terminal values:

  • PROCESSED
  • PROCESSED_WITH_ERRORS
  • ERROR

When the status is processed, validate a few items with GET /v3/lagtime using the same identifiers.

How it works

  1. Build a JSON or XML feed with your SKUs and the new fulfillmentLagTime values.
  2. Submit the feed with feedType=lagtime.
  3. Capture the feedId from the 202 response.
  4. Poll feed status until processed.
  5. Validate a sample of SKUs with the GET Lag time endpoint.
  6. If any lines failed, fix the items and resubmit only the failed ones.

Troubleshooting

  • 400 Bad Request
    The feed body does not match the schema or feedType is missing. Validate against the Lag Time schema.

  • 401 Unauthorized
    The access token is missing or expired. Get a new token and retry.

  • 403 Forbidden
    Your role or account lacks permission for the action. Confirm account status and scopes.

  • 429 Too Many Requests
    You are sending feeds too quickly. Slow down and retry with backoff.

  • Item level errors
    Check the feed result details for each failed line. Common causes include unknown SKU, invalid shipNode, or fulfillmentLagTime outside allowed range.

Related

  • GET lag time for an item. Retrieve the current fulfillmentLagTime for a single item.
  • Shipping configuration. Review account level settings and any approved exceptions.

Updated about 20 hours ago