DIRECT ANSWER
Match each unexpected PO to the closure's facility, lanes, dates and affected window. Check when the PO was created and whether it was manual or system-generated. A saved closure does not prove every order flow uses it or that existing POs changed. Confirm the applicable handling before changing orders.
Your warehouse calendar says closed, but another PO has arrived. The first question is whether the closure record and that PO describe the same facility, lane, dates and operating flow.
This guide focuses on Walmart U.S. first-party domestic warehouse suppliers using Ship Point Management. DSV operations and eCommerce FC lanes need separate scope checks below. Marketplace, Sam’s Club and non-U.S. procedures are outside this guide. It does not tell you to cancel an order or assume that Walmart changed its dates.
Identify what is actually closed
Write a precise operating statement: which physical facility cannot do what, during which dates and hours, in which timezone. “We are closed Monday” could mean no production, no carrier pickup or no receipt of inbound materials. Those restrictions are not interchangeable.
Next, retain the submitted event and the current record: supplier agreement, ship point, affected lanes, date range, selected windows and values, status, submission time and any response. A screenshot of an event name alone cannot establish the scope of the setting.
Walmart’s Ship Point Management FAQs distinguish Order, Ship and Delivery windows. They caution against mixing Open and Closed selections within a multi-day event. Compare your recorded choices with the actual restriction, without changing the event merely to try different combinations.
For one unexpected PO, add the issuing time, origin if shown, ship point, receiving location and relevant order dates. Compare its planned shipment and delivery dates with the particular window you closed. Receiving an order document is not itself a conflict with a shipping closure. If a relevant date is unavailable, record the uncertainty before calling the order affected. Keep different systems’ identifiers labeled rather than assuming two facility IDs must be identical.
Which order flow needs the check?
Start with this decision:
- Domestic Owned order serving the store network: compare the PO with the event’s exact agreement, lane, date and window. Establish the current event status and applicable process.
- Owned eCommerce FC lane: the indexed FAQ documents that FC ordering did not use calendar events. Confirm whether this exception still applies and which closure process your lane uses.
- Manual order: the same FAQ directs discrepancies to the Walmart associate who created the order. A calendar entry does not settle that person’s intended order handling.
- DSV customer order: use the current DSV outage and order-management instructions. A warehouse’s physical address appearing in both businesses does not establish that an Owned calendar event governs its DSV orders.
These are routing questions. They do not identify the cause of your particular order without the corresponding records.
A fictional closure timeline
All identifiers and events in this example are invented. The readable labels are placeholders, not valid Walmart identifiers. All times are America/Chicago.
The supplier’s physical warehouse cannot load outbound freight on September 14 or 15, 2026. The team expects its closure entry to take care of every affected order.
| Recorded event | What the team can establish |
|---|---|
| September 9, 09:00: PO-A is issued with planned shipment on September 14. | This order existed before the closure submission. |
| September 10, 14:00: an event is submitted for ship point SP-A and lane DC-A, covering September 14–15. Its saved values are Ship: Closed; Order: No Change; Delivery: No Change. | The saved record describes one lane and a specific window. Its current processing outcome still needs confirmation. |
| September 11, 11:00: PO-B arrives for the same lane with planned shipment on September 15. Its source record identifies it as manually created. | The shipment falls within the warehouse restriction. The issuing associate’s intended handling must be checked. |
| September 13, 09:00: the coordinator reviews both orders and finds no confirmed date change or cancellation in the evidence supplied. | Neither order has been shown to be resolved by the closure entry. |
The coordinator has two separate requests. For PO-A: confirm its current terms and the required handling of a shipment affected by the closure. For PO-B: ask the issuing associate to review the manual order against the documented warehouse restriction. Separately, the owner checks the event’s current status and whether its scope matches the intended closure.
This timeline does not prove that the event failed. It also does not prove that either PO can be ignored. The event submission time, affected calendar window and individual order history answer different questions.
What should you send for help?
Send the facility and agreement references, event record, actual closure restriction, affected PO list, relevant times and one explicit question about the unresolved handling. Preserve original records and later responses together.
The FAQ routes Supply Plan and event-setting issues to Supplier Optimization and calls for separate Transportation coordination for collect ship-point changes. Confirm the current handling for your actual request.
For each affected PO, ask the relevant owner to confirm any required revision, routing coordination or other action through the applicable process. An internal closure schedule is not evidence that an issued PO was canceled, its dates were extended or an appointment changed. This article sets no notice period or response deadline.
If the trouble is locating a particular order, use the missing-PO guide. If Supply Plan and demand numbers disagree, use the forecast-versus-orders guide.
Startup Success Lab’s buyer calendar and answer library connects upcoming events with prepared evidence and named owners. Its account-review process supports the follow-through. Agree on the next checkpoint with facility, account and logistics owners, recording what was confirmed, what remains unresolved and who owns each PO.
Source scope
Source review: September 13, 2026. The official Ship Point Management FAQ was reviewed through its public search-index text; direct access redirected to sign-in. Current account screens, FC rollout behavior and individual closure records were not verified. The scope checklist and fictional timeline are original aids, not a retailer approval or order-change instruction.