Seller guide
How do I verify a WFS peak storage surcharge by billing month?
Recompute seller-supplied WFS peak storage surcharges from stored volume and a supplied rate while preserving the base storage fee separately.
Confirm the source window before entering a row
Use one reporting currency and as-of date. For each seller-redacted SKU and billing month, retain a seller-owned reference, optional GTIN, average storage volume in cubic feet, recorded base monthly storage fee, supplied peak surcharge rate per cubic foot, and recorded peak surcharge. Explicitly confirm that the source row is current, the term source is current, and the billing month is inside the peak window shown to the seller. Remove order, buyer, address, payment, message, and instruction data.
Keep the base fee out of the surcharge recomputation
Multiply average storage volume by the seller-supplied peak surcharge rate and round once to cents. Compare that amount only with the recorded peak surcharge. Preserve the recorded base monthly storage fee unchanged, then add it to the recorded and recomputed surcharge only to show two total-storage-charge views. This prevents a base-fee difference from being disguised as a peak-surcharge difference and prevents the bounded tool from implying it verified both fees.
Apply a tolerance and preserve discrepancy direction
Subtract recomputed surcharge from recorded surcharge and compare the absolute difference with a seller-selected amount tolerance. Rank recorded-above-recomputed rows first, then recorded-below-recomputed rows, and retain reconciled rows as context. Total the two discrepancy directions separately. A net difference of zero can otherwise conceal one positive and one negative SKU that each needs source review. A mismatch does not prove Walmart charged the wrong surcharge.
Use month summaries to find scope and timing problems
Group row count, supplied average volume, recorded base fee, recorded surcharge, recomputed surcharge, both difference directions, and mismatch count by billing month. A whole-month cluster can indicate that the wrong rate effective date, peak-window assumption, export scope, or volume definition was supplied. It is not evidence that one SKU caused the issue. Compare only months built from the same statement definitions, currency, volume basis, and seller-supplied terms.
Verify the statement and current terms before escalating
For each queued reference, inspect the authorized statement row, volume calculation, rate effective date, peak-window definition, base fee, surcharge, credits, adjustments, and taxes. The arithmetic does not establish a credit, refund, or dispute right. Friday reads no Walmart account, embeds no WFS peak window or rate, files no case or dispute, changes no fee, inventory, listing, price, shipment, or seller account, and publishes no listing; a human decides any next step from current evidence.
Tools that help with this
Prices below are exact x402 per-call prices. Human card checkout uses fixed $3, $9, and $29 bundles; follow a tool page to see its applicable bundle.
- WFS Peak/Seasonal Storage Surcharge Verifier ($0.50) — Recompute supplied WFS peak surcharges and summarize differences by month
- WFS Monthly Storage Fee Charge Verifier ($0.50) — Verify the separate supplied WFS base monthly storage charge
- WFS Inventory Reconciliation Exception Finder ($1.00) — Reconcile supplied WFS inventory movements before trusting stored-unit context
Every paid output is a draft for your review before you publish, appeal, or activate anything. Friday does not access your seller account.
More seller guides
- Your Amazon listing was suppressed. What to check first.
- How do I verify WFS fulfillment fees by weight band?
- Why does my WFS inventory reconciliation report not balance?
- What should I check when a WFS hazmat item is on hold?
- How do I track FBA reimbursement deadlines and missing evidence?
- How do I reconcile a marketplace payout to orders and the bank deposit?