← Friday Seller Tools

Seller guide

How do I verify Amazon MCF order fees by size, weight, and speed?

Join redacted Multi-Channel Fulfillment orders to a seller-supplied rate table and isolate arithmetic differences without importing a live fee schedule.

Freeze one redacted order-fee snapshot

Choose one marketplace, currency, and as-of date, then keep only a seller-owned order alias, fulfillment date, size tier, shipping weight band, delivery speed, unit count, and recorded fulfillment fee. Remove buyer names, addresses, raw order IDs, contacts, messages, payment data, and delivery instructions. Preserve the size, weight, and speed labels exactly as they appeared in the source export. A renamed band can prevent an exact rate join, while silently normalizing it to a different tier can manufacture a reassuring but unsupported fee match.

Build the rate table you actually intend to test

Enter one seller-supplied fee for every unique size-tier, weight-band, and speed combination in scope. Give each combination exactly one rate and retain the source date or rate-card version outside the calculation. Do not fetch a current Amazon schedule midway through the audit or combine rates from different effective dates. Rows with no exact match belong in a missing-rate queue; they should never inherit a nearby weight band, a slower service, or a generic average merely so the batch can produce a total.

Recompute the fee with transparent unit arithmetic

For each matched row, multiply the supplied per-unit rate by the supplied fulfilled quantity and round the result to cents using one declared convention. Compare that amount with the recorded order fee inside a seller-chosen tolerance. Keep the expected fee, recorded fee, signed difference, absolute difference, matched rate key, and quantity together. A positive difference and a negative difference answer different questions, so report their exposure separately instead of netting them into an account total that can hide offsetting rows.

Rank review work without calling every difference an error

Put missing-rate and beyond-tolerance rows first, then sort by absolute supplied dollar difference. Summarize row count, units, expected fee, recorded fee, and both difference directions by size, weight, and speed. List unused rate rows as context: they can reveal a stale or overbroad input table, but they do not prove the export is incomplete. A fee difference can reflect an effective-date boundary, surcharge, bundle rule, source aggregation, or transcription issue that the bounded arithmetic does not model.

Verify the source record before accounting or support action

Open the authorized MCF order and current fee guidance for each queued alias. Confirm fulfilled quantity, product measurements, speed, fee effective date, adjustments, credits, and any charge type omitted from the supplied table. This method does not prove Amazon charged the wrong fee, establish that a credit is due, or replace an invoice or settlement reconciliation. Friday never changes fulfillment settings, orders inventory, contacts a recipient, files a case, or modifies an Amazon account; it only produces a reviewable arithmetic queue.

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.

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

Browse all guides →