Guide · Walmart Drop Ship Vendors on InfiPlex
Walmart DSV runs on hours, not days: acknowledge every PO within four hours, ship by the Expected Ship Date on Walmart's carrier and method, feed available quantity per facility every day, and hold rejections below 0.1%, on-time shipment above 99%, and the 15-day defect rate below 2%. InfiPlex, Walmart's first approved DSV channel partner solution, acknowledges on pull, posts tracking at label purchase, and keeps the inventory feed current through its Walmart DSV integration. An AI agent on the InfiPlex MCP server covers the questions around those clocks: what ships by ESD today, which acknowledgments or inventory feeds failed overnight, and why a rejection happened on a SKU the feed said was available.
Why DSV
InfiPlex pulls open Supplier Center orders automatically, acknowledges them on pull inside the four-hour window, prints Walmart's designated label or the Site-to-Store label, and posts tracking and inventory the moment a label is purchased. Those are the rules in the acknowledgment and ship rules guide, and they run without a person. What still took a person was the exception list: the order stuck in a warehouse that ran out, the tracking Walmart rejected, the inventory feed that failed at 2 AM. An agent asks the instance those questions in seconds, with order ids and timestamps, and on a warehouse key fixes what it finds.
| What your team asks the agent | Tools it calls | What it hands back |
|---|---|---|
| "Which DSV orders must ship today?" | order_search on the DSV channel with ship_by_end_date set to today, fully_shipped 0 |
Order ids, ship-by date, hours since the PO arrived, ship-to state, and the warehouse each routed to |
| "Did every DSV shipment from yesterday post tracking to Walmart?" | order_search with marketplace_fulfillment_error 1 on the DSV channel, then log_search on the Walmart Send Tracking types |
Orders whose tracking Walmart rejected, with the error text from the log |
| "Did the inventory feed to Walmart run overnight?" | log_search on the Walmart Send Inventory types for the last 24 hours |
Last successful send and any failure with its message |
| "Why did we reject the line for GL-410 on PO 1088223?" | order_search text_search, order_warehouse_routing_explanation_get, inventory_change_history_get |
What each warehouse had when routing ran, and the sales that drew it down beforehand |
| "Which SKUs are about to cause rejections?" | inventory_restock_list, then inventory_get per SKU |
SKUs at or below reorder point with stock by warehouse |
| "Is this a Site-to-Store order?" | order_get |
The ship-to (store address) and shipping method InfiPlex stored on the order |
Every tool above is documented on the tools reference. The DSV chargebacks guide explains what each missed clock costs.
Expected Ship Date
Walmart's published fulfillment chargeback is per order shipped after its Expected Ship Date, and the rates that decide routing are on-time shipment and rejections. The ESD on the PO is the order's ship-by date in InfiPlex, so ship_by_end_date is the ESD queue. DSV suppliers complete orders Monday to Friday by noon local. A shift lead on a warehouse key at 11 AM:
Status and notes are direct writes because they stay inside InfiPlex. Tracking is a previewed write: the first order_tracking_create call returns a plain-English preview and a token, the second executes, and InfiPlex posts the tracking to Walmart from there. The gates are in how AI agent writes are protected.
Acknowledgment, tracking, and inventory sends
The shop log is the record of the integration itself: each order pull, acknowledgment, tracking post, and inventory send, with Walmart's response. log_types_get gives the agent the type ids on your instance (the pattern is a channel, an action, and a status, for example a Walmart Send Tracking: Failed type); log_search on the failed types for the last 24 hours is the morning check. An account manager on a read-only key:
On a warehouse key the agent calls order_tracking_create with the carrier name and method split correctly, shows the preview, and executes on confirm. InfiPlex posts the corrected tracking to Walmart.
"Did every PO from the last 4 hours get acknowledged?" is a log_search on the acknowledgment types against the orders order_search returns for that window. A failed acknowledgment found at hour two is not a metric miss.
Walmart wants available quantity per distribution facility. inventory_get with a warehouse_id returns exactly what InfiPlex feeds for that facility, so "what does Walmart think Columbus has of MK-88" is one call.
S2S orders ship to a Walmart store, not the customer. order_get returns the store ship-to and the method InfiPlex stored, so the agent can list today's S2S orders separately for the pack station.
Rejections
A DSV rejection rate above 0.1% is one line in a thousand, and the usual cause is a feed that said available while the shelf did not. InfiPlex feeds per-facility quantities from the same multi-warehouse inventory every other channel draws on, which is how rejections stay rare. When one happens, the agent reconstructs it from the routing record and the change history.
The same three tools answer Walmart's buyer when they ask, and they produce the evidence a performance review needs. The multichannel inventory sync article covers buffers and send cadence; multi-warehouse order routing covers the routing rules the explanation record reflects.
Keys by role
The MCP server publishes a tool only when the key carries its scope, so the key is the whole permission model. Create each at Tools > Admin API on your instance with MCP Enabled, and send the URL and header from the set-up guide.
Read Orders, Read Inventory, Read Warehouse, Read Log. Both MCP flags No. Every question on this page works; nothing can change. This is the key for whoever talks to Walmart's buyer or reviews performance.
Add Write Orders and Write Inventory. Tracking and inventory changes stop at a preview the person approves; notes, status, and additional info write directly. The pack station's key.
Same scopes as the warehouse key, used by an unattended agent instructed to complete the preview-and-confirm flow itself. The morning unshipped orders agent writes the ESD queue before the shift starts; the failed sync watch agent reads the Walmart failed types every morning.
Prompts
shop_setting_search, read scope)The agent reads the stored channel name from your order data rather than guessing it, so "Walmart DSV" in a prompt resolves to whatever your instance calls that connection, and stays distinct from a Walmart Marketplace connection on the same instance. More prompts by role are on the prompts page.
Frequently asked
No, and it does not need to. InfiPlex acknowledges each PO on pull, inside Walmart's four-hour window. The agent reads the result and surfaces any acknowledgment that failed in the log so it can be handled before the window closes.
Yes. order_tracking_create records the shipment in InfiPlex and InfiPlex posts the tracking to Walmart through the integration, as it does for any shipment recorded in the admin or by a connected shipping tool. It is a previewed write on a key with Write Orders: preview and token first, execution second.
Indirectly, on a key with Write Inventory: inventory_set and inventory_set_bulk change the quantities InfiPlex holds per warehouse, behind a preview, and the next Walmart send carries them. Feed cadence and buffers are settings, which need Write Settings and MCP Allow Setting Writes; most suppliers leave those to a person in the admin.
Each connection stores its own channel name on the orders it pulls. The agent reads that value from earlier results and uses it exactly in order_search; it is instructed not to guess. A supplier running DSV and Marketplace on one instance can ask about either.
No; those live in Supplier Center. What the agent gives you is the InfiPlex record the metrics are computed from: arrival, acknowledgment, ship and tracking times, inventory at routing, and every send and failure. Watching those daily is how the rates stay inside the standard.
No. The MCP server is included with API access on every InfiPlex plan. Keys are unlimited and MCP calls are not metered. Your AI vendor bills model usage.
Resources
We will connect an agent to a DSV instance on a read-only key and reconstruct that rejection from the routing record and change history, tool by tool, while you watch.
Open Tools > Admin API, create a read-only key with MCP Enabled, and connect the assistant your team already uses. Questions: Contact us, email info@infiplex.com, or call 888‑770‑0857.
Order ids, PO numbers, SKUs, quantities, times, and warehouse names are examples. Walmart is a trademark of Walmart Apollo, LLC. Model Context Protocol is an open standard.
InfiPlex provides eCommerce companies, warehouses, and 3PLs with a robust platform to manage their sales channels.
©2026. All Rights Reserved. Privacy Policy | Terms & License