Walmart Marketplace API: the order lifecycle on the wire

The three-stage flow

Retrieve, acknowledge, then ship, cancel, or refund

Walmart groups its own Orders API documentation into exactly this shape: retrieve orders to see what exists and what needs action, acknowledge to confirm you will fulfill, then shipping, cancellations, and refunds to close each order line out. Every seller-fulfilled order has to be acknowledged before it can be shipped; skipping straight to shipping without acknowledgment is not a supported path.

Order line statuses

What each one means

Status lives at the order-line level, not just the order level, so a single purchase order with three line items can show one line Shipped and another Cancelled at the same time. Partial and multi-box shipments are supported: ship the lines that are ready and leave the rest in Acknowledged until they move.

The WFS exception

One endpoint, not the general-purpose one

The single most common integration mistake on this API is calling the standard cancel endpoint (/v3/orders/{purchaseOrderId}/cancel) against an order fulfilled by Walmart Fulfillment Services. Walmart's own documentation states plainly that WFS orders cannot be cancelled that way; the correct call is the fulfillment API's cancel endpoint (/v3/fulfillment/orders-fulfillments/cancel), and it only works before the shipment reaches a non-reversible state such as Receiving in Progress, Closed, or already Cancelled. An integration that only implements the standard cancel path will silently fail, or error, on every WFS order it tries to cancel.

Cancellation reason codes

Why the reason you choose matters

Every cancellation requires a reason code: CUSTOMER_REQUESTED_SELLER_TO_CANCEL, SELLER_CANCEL_OUT_OF_STOCK, and others in Walmart's published list. The code is not paperwork. Walmart uses it to decide whether the cancellation counts against your Cancellation Rate (seller-accountable reasons like out-of-stock do; customer-requested and fraud do not) and can affect future item visibility if a pattern of out-of-stock cancellations emerges. Choosing the accurate reason, not the convenient one, is what keeps the performance standards reading correctly.

Automation

How InfiPlex runs the Marketplace order flow

InfiPlex retrieves and acknowledges Walmart Marketplace orders automatically, ships with carrier and tracking data the moment the carrier scan confirms dispatch, and routes cancellations to the correct endpoint, the standard order-cancel path for self-fulfilled lines and the fulfillment API for WFS-fulfilled ones, with the accurate reason code attached. Program page: Walmart Marketplace integration; performance implications are in the seller performance standards guide.

Frequently asked

Questions, answered

Questions developers hit while wiring up the Walmart Marketplace Orders API.

Resources

Related pages and references

Building or debugging a Walmart Marketplace integration?

Tell us where the connection is failing, we have wired up every endpoint on this page, including the WFS cancellation exception. Contact us, email info@infiplex.com, or call 888‑770‑0857.