How do I verify WFS fulfillment fees by weight band?

Freeze one statement window and one dated rate card

Choose one reporting currency and a bounded charge window. Keep a seller-owned charge reference, charge date, SKU alias, supplied size tier, billed unit weight, fulfilled units, and recorded fulfillment charge. Remove buyer, order, address, payment, message, and instruction data. Separately copy the WFS rates you intend to test and preserve their effective date. Do not combine statement rows from one period with rates remembered from another period; a precise recomputation against the wrong rate card is not useful evidence.

Validate weight-band boundaries before joining charges

Give each supplied rate a unique code, size tier, exclusive lower weight bound, inclusive upper bound, and per-unit fee. Within a size tier, bands must not overlap. Treat an exact upper-bound weight as part of that band and an exact lower-bound weight as outside it unless the adjacent band contains it. A charge should match exactly one supplied band. Missing or multiple matches belong in source review; never select the nearest rate simply to make every row calculable.

Recompute fulfilled units times the matched unit fee

Multiply the supplied fulfilled-unit count by the matched per-unit rate and round once to cents using a declared half-up convention. Subtract the recomputed fee from the recorded charge and compare the absolute difference with a seller-chosen tolerance. Preserve the rate code, quantity, expected fee, recorded fee, signed difference, and absolute difference together. Sum positive and negative differences separately; netting them can hide two unrelated rows that need review.

Rank mismatches first and keep clean high charges as context

Put unmatched and beyond-tolerance rows first, ordered by absolute dollar difference. If the seller supplies a high-charge threshold, keep clean charges above it in a separate review band rather than calling them errors. Summarize rows, units, recorded fees, recomputed fees, and both discrepancy directions by supplied rate band. List unused rate rows too: they may show an overbroad rate card, but they do not prove the statement or rate table is incomplete.

Verify measurements and fee context before any support action

For each queued alias, inspect the authorized source record, packed measurement, size classification, weight rounding, rate effective date, units, adjustments, surcharges, credits, and any fee component omitted from the bounded model. A difference does not prove Walmart charged the wrong fee or that a credit is due. Friday reads no Walmart account, files no dispute, changes no shipment, listing, inventory, fee, or account, and publishes no listing; it produces an arithmetic review queue for a human.

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 Fulfillment Pick & Pack Fee Charge Verifier ($0.50) — Recompute redacted WFS charges against exact seller-supplied weight bands
• Dimensional-Weight and Shipping Size-Tier Classifier ($0.25) — Check supplied package measurements against a separate seller-supplied tier table
• Marketplace Payout Reconciliation Analyzer ($1.00) — Trace a verified recorded fee through seller-supplied settlement evidence

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

• How do I reconcile Etsy transaction and payment processing fees?
• Why does my WFS inventory reconciliation report not balance?
• How can I tell if a package is close to the next shipping size tier?
• How do I verify Amazon MCF order fees by size, weight, and speed?
• How do I track FBA reimbursement deadlines and missing evidence?
• How do I reconcile a marketplace payout to orders and the bank deposit?

Browse all guides →