DIRECT ANSWER
Compare what was actually approved with the exact item, location, cost unit, effective basis and PO version. A requested start date is not proof of the approved start date, and a current item cost does not prove an earlier PO changed. Identify the conflicting record before requesting a correction.
Your team agreed on a new cost with Walmart. Someone says the update is approved, but an issued purchase order still shows the old amount. Before invoicing at the new cost or submitting another change, establish which approval and which PO you are comparing.
This investigation is for Walmart U.S. first-party suppliers reviewing domestic store or shared-item cost records and POs. Confirm that the item’s department and program use the relevant Supplier One cost workflow. Marketplace retail pricing, import programs, DSV node costs and Sam’s Club require their own instructions.
Download the cost-to-PO comparison sheet. Use it to put the request, actual approval, recorded item cost and issued orders alongside one another.
What did Walmart actually approve?
Keep the commercial agreement and the system submission separately identifiable. For each, record the item configuration, supplier relationship, covered locations, cost amount, currency, unit and conditions. Preserve the approval wording and its date. “Buyer said yes” does not describe which records or orders the agreement covers.
Separate the date your team requested from the effective date or condition actually confirmed. If the approval does not explain whether it applies by PO issue date, shipment date or another event, ask. Do not select whichever date produces the preferred answer.
Temporary changes need an end condition. A submission or approval date is not automatically the date a cost applies to every order.
Walmart’s Vendor Managed Pricing report documentation separately names cost amount, effective date, received date, cancel date and pricing type, distinct from retail-price fields. Those attributes have different meanings. Report access is restricted to eligible suppliers and departments; this investigation does not require its API.
Check the item and location scope
Supplier One’s getting-started guidance places eligible cost maintenance at the Walmart Item Number level and identifies department exceptions. Its indexed official text was reviewed; full access requires sign-in. Confirm the current workflow for your item instead of treating a product-level content update as a cost change.
Retrieve the relevant cost submission and record its identifier, actual outcome and any item-level errors or unresolved review. Then inspect the cost record for the affected item and location, retaining the observation time and effective information available there. A completed batch does not establish that the particular configuration you need contains the intended value.
The Supplier One setup guide helps keep questions attached to the right submission. Continue through to the actual cost record and PO.
Compare the issued PO, not a remembered order
Obtain the PO version your team received, including its original issue date, revision date if any, line number, item, destination, quantity, unit cost and unit of measure. Preserve each relevant version. A revision date is not automatically a new-order date, and today’s record may differ from the one used to prepare an invoice.
Check that the costs use the same basis. A cost per shipping case and a cost per each cannot be compared by subtracting the displayed numbers. Reconcile pack conversion from supported item and order records. The PO quantity and pack comparison addresses that separate problem.
Identify allowances independently. A unit-cost change and a changed net amount after allowances are different questions.
A fictional example: three old-cost POs, one documented conflict
Assume all amounts are USD per each for ITEM-DEMO. The request sought a change from $2.00 to $2.40 for DC-A and DC-B starting September 5, 2026.
The actual fictional approval covers DC-A only, for new POs issued on or after September 10. That condition is supplied for this example; it is not a universal Walmart rule. A September 12 item-record check for DC-A shows $2.40 with the stated September 10 effective basis.
| PO evidence | What the supplied approval establishes |
|---|---|
| PO-A, issued September 8, DC-A, $2.00; revised September 12 only to change a delivery date | Outside the supplied approval’s new-order period. Neither the requested September 5 start nor this later revision establishes a new PO. |
| PO-B, issued September 11, DC-A, $2.00 | Conflicts with the supplied item, location and new-order conditions. Retrieve any revision or exception before deciding the correction. |
| PO-C, issued September 11, DC-B, $2.00 | Outside the approved location scope. The original request included DC-B; the approval did not. |
PO-B orders 500 eaches. The observed difference against the supplied approval is 500 × ($2.40 − $2.00) = $200. This calculation sizes the conflict. It does not authorize a $200 invoice increase or establish a recoverable deduction.
The account owner asks Walmart to confirm the applicable PO-B version and required correction. PO-A and PO-C remain separate questions if the team wants different commercial treatment. The completed comparison sheet preserves those distinctions.
Request a correction to the record that is wrong
State the discrepancy precisely: “This approval covers ITEM-DEMO at DC-A for new POs issued from September 10. PO-B version 1 is dated September 11 at $2.00. Please confirm the applicable cost and whether a PO or item-record correction is needed.” Include the approval, submission reference if available, relevant item observation and PO version.
Ask the responsible merchant, replenishment or support contact to confirm the current route for the item and order type. Do not use a new invoice, blanket cost upload or assumed retroactive change to resolve uncertainty. Retain any correction confirmation and compare the resulting record before closing the issue.
For the sheet, keep one supplier relationship and currency together. Use a row for each relevant request, approval, item observation or PO version and line. Retain line identifiers so different items on one PO do not collapse into one cost. Import identifiers as text and leave unknown fields empty. Costs across rows are comparisons, not amounts to total.
The sheet separates the requested start, confirmed effective basis, original PO issue date and PO revision date. Its record / observation date captures the request or approval date, or when the item record was checked. For PO rows, use the dedicated issue and revision fields. The example retains both versions of PO-A to show why a later revision alone does not meet the supplied new-order condition.
If deductions have already resulted, use the recurring-deductions guide to connect the invoice, PO and applicable terms. SSL’s cost-model guide helps keep the commercial basis and implementation decisions connected across the team.
Source scope
Source review: September 13, 2026. Walmart’s public pricing-report documentation was read directly; Supplier One workflow scope was reviewed through indexed official text. Detailed current cost-approval procedures and account screens were not checked. The method, worksheet and example are original. No approval deadline, automatic PO revision, retroactive price right or invoice instruction is established here.