Corrections
When a published figure or claim turns out to be wrong, we fix it and log the fix here with the date it shipped. Rows that change because a vendor changed its price are not corrections — those are updates, noted in the row itself. This page is for our mistakes.
Our guide said ShipCalm's pricing page shows its Pro plan at $895/week 'in the comparison table', and SKU management and storage at $1.25 and $0.18 as well as $1.45 and $0.19. The page does disagree with itself, but not the way we described. It shows different prices at different screen widths. At 768px and wider (typically desktop and tablet) it shows $2.65 per DTC order, $1.45 per SKU and $0.19 per cubic foot; below 768px (typically a phone held upright) the same page shows $2.45, $1.25 and $0.18, with lower pallet, oversize and receiving fees, and it leaves some lines out. The $895 Pro figure is the comparison table below 1025px; at 1025px and wider the same table says $995, beside a $999 plan card. A reader on a desktop checking our guide would have found $995 and reasonably concluded we were wrong. We traced it by reading the page's own breakpoint rules. Our dataset now records the figure shown at 768px and wider and notes the other in the row, and that is the figure every other ShipCalm mention on this site quotes. The first version of this entry, live for about an hour, said the page 'serves' different prices to phone and desktop 'visitors'. The evidence is screen width, not device, so it now says that. Along the way, a quick automated read of the page labelled the narrow-screen prices as a second 'Pro plan' price list. That was wrong, and it was caught before it reached the site.
Fulfyld's $7.74 is a published average, not a quoted rate. We published it as a rate: 'Fulfyld bills $7.74 per order all-in', 'the $7.74 rate', a flat $7.74 in comparison tables. Fulfyld's own page labels the figure 'Average Cost $7.74 +' and says, of all its per-order figures, 'These are real averages, not your quote.' The $7.51–$10.27 range row is the same kind of number, two averages with a trailing plus. Every place on this site we state either is now restated as a published average, and the worked examples that divide by $7.74 say that they use an average. We could not establish whether the page said "average" when we first read it on 2026-08-04, so this is logged as our error rather than as a vendor update: the same rule as the 2026-08-10 entry below, where a claim that could go either way goes in the log. The same pass found that our 2026-09-09 entry was incomplete. It fixed the data row that wrongly said the range varied by package weight, but the claim survived as prose in two guides (3PL hidden fees, Flexport monthly minimum) and in hand-typed table rows. Those are corrected in this change. An entry that says a thing is fixed has to mean everywhere it was published, not only the row we started from. The paid Kit workbook is the exception so far: its preloaded Fulfyld card still treats $7.74 as a flat rate, and this entry will say so when the next Kit release fixes it. One more error, in our own 2026-09-09 entry below: it said we had understated the spread roughly nine times. No reading of the figures gives that. The top of Fulfyld's published range ($124.64) is about twelve times the top of the range we published ($10.27), and that entry now says so.
Our Fulfyld "all-inclusive per-order fee range" row published $7.51–$10.27 and described it as varying by package weight and shipping speed. The weight half of that was wrong, and wrong in the direction that flatters the vendor. Both endpoints sit in the SAME 4–12oz band: $7.51 is 4–12oz standard at the 10,000+/month tier, $10.27 is 4–12oz international at the 501–1,000/month tier. The range measured volume tier and destination, never weight. Across the weight bands Fulfyld actually publishes, the range runs $7.51 to $124.64 (20–25lb international at the 0–250/month tier), and standard shipping alone reaches $16.13. So the top of the range we published ($10.27) was about a twelfth of the top of Fulfyld's published range ($124.64), and a reader sizing a heavier parcel against it would have been badly misled. (Corrected 2026-09-11: this sentence first said we understated the spread "roughly nine times", which no reading of the figures gives.) Caught by a scheduled re-verification pass against the live pricing page, not by a reader. This is our error and not a vendor change: Fulfyld did not move a price, we misread what the two endpoints had in common. The row now states the band, the two tiers and the true full-range figures, and it is the same class of mistake as the 2026-08-10 entry below — a claim about how a fee works, rather than a wrong number.
The paid workbook shipped the Amazon MCF error corrected on this page a day earlier, and not only on its reference tab. Its Amazon MCF card was hard-coded, so rebuilding from the corrected dataset would not have touched it: the card priced a four-unit order at $3.64 rather than at four times $3.64, which put MCF at $6.22 per order instead of $9.32, third cheapest of four instead of dearest. Its notes still claimed Amazon does not publish the two-unit and three-unit cells and that the October–December storage table is login-gated. Both claims were retracted here on 2026-08-17 while the file kept repeating them. Fixed, along with the peak storage rate the card had never carried at all: at $2.40 per cubic foot the fourth quarter is $2,997 higher than the workbook had projected. Two defects found while fixing it were older than the error above and are also fixed. The Benchmarks print area was pinned to the row count of an earlier build, so 18 sourced rows never appeared in a printout or PDF — among them the $3.45 per-unit rate the workbook's own Walmart WFS example is built on. And six explanatory paragraphs were destroyed by the generator at build time, including the only instruction for the Red-Flag Checklist's status column and the note carrying our correction address. Both had shipped in every prior version. Anyone who bought v1.0.8 should re-download.
Two figures in the benchmark table were wrong, both found by re-reading the dataset rather than the page. First, receiving labour was given as $38–$40 per hour. The $38 is Simple Global's KITTING labour rate, not a receiving rate, and the two Flexport receiving rows at $48 per hour added on 2026-08-12 were missing entirely — so the figure imported a number from another service line and understated the ceiling by $8. Filtering the dataset to rows whose unit is "per hour" AND whose service line is receiving returns exactly three: Flexport at $48 twice, Fulfyld at $40. The range is $40–$48. Second, ShipCalm's returns fee was published as "$4.95 per item" where the row's unit column reads "per return". Those are different bills the moment a return contains two items, and the unit column is what this site treats as authoritative everywhere else. Noted while fixing it, and still open: that row contradicts itself — its fee_item reads "per-item returned fee" while its unit reads "per return". The published figure now follows the unit column; which of the two matches ShipCalm's own page needs a fresh read.
Three claims in the guides, all downstream of the Amazon MCF unit error logged below, and all wrong in the direction that flattered us. First: the pick-fee guide said "the rate card's unit column reads per order". The rate card has no unit column. That column was ours, it said per order, and it was wrong — so the sentence attributed our own data-entry defect to Amazon. Second: the comparison guide said 700 orders in its worked profile "cannot be priced from public data" and that "the gap is itself the finding". Amazon publishes all four unit-count columns on the same rate card the guide already cites — for small standard 4 oz or less at standard speed they are $7.34, $4.98, $4.10 and $3.64 per unit — so the gap was in our extract, not in what Amazon discloses. Third: the same guide said Amazon's current and October–December peak storage tables were "only available inside Amazon's login-gated or JS-rendered pricing tool" and that the column "cannot be projected through Q4 from public data at all". Both tables are printed on the public card: January–September $0.78 and October–December $2.40 per cubic foot for standard size. A peak rate that triples storage cost is the most consequential figure in any Q4 model, and we told readers it was unobtainable. Two derived figures were also overstated because the formula behind them dropped the 2 lb threshold Amazon prints: a 25 lb small bulky unit read $36.83 bare and $38.12 with the 3.5% surcharge, against $35.33 and $36.57. The methodology page's Amazon MCF chip read /order and now reads /unit. The largest consequence was arithmetic, and it reached the front page. The comparison guide priced Amazon MCF at $6.22 per order by multiplying a per-unit fee as though it were charged per order: its four-item line read 100 orders at $3.64 = $364.00, when a four-unit order at $3.64 per unit is $14.56 and the line is $1,456.00. Priced correctly against the same 2,000-order profile — 1,200 single-item, 500 two-item, 200 three-item, 100 four-item, at the published $7.34, $4.98, $4.10 and $3.64 per unit — MCF costs $17,704.00 in fulfillment, $619.64 in the 3.5% surcharge and $312.00 in storage: $18,635.64, or $9.32 per order. The published $6.22 understated it by 50%. Because the guide also bracketed 700 of those orders as unpriceable, the figure had been carried as a range, $6.22 to $7.56; there is no range, because Amazon publishes a rate for every order size. Two conclusions changed with it. MCF is not the mid-priced option of the four cards compared, it is the most expensive, while still publishing the lowest headline multi-unit rate of any of them. And the guide said normalizing left the naive ranking unchanged; it does not — MCF and Fulfyld swap. $6.22 was one of the four worked-example figures printed on the home page and inside the $4.33–8.32 span on the Kit page, so both now read $4.33–9.32, and the home chart derives its colours from the amounts rather than pinning the neutral bar to a fixed position, which is why it had gone on showing the wrong bar as the most expensive. Still open, named here rather than quietly carried: the 2-unit and 3-unit cells are cited from the rate card but are not yet rows in the dataset; the October–December peak storage rate of $2.40 per cubic foot is published and our Q4 projection has not been recomputed with it; and /guides/3pl-hidden-fees/ attributes a 40-foot container size to MyFBAPrep that MyFBAPrep does not publish.
Every Amazon MCF row taken from the rate card's fulfillment fee tables stated the wrong unit of charge. They were published as per order, the multi-unit tiers included, so small standard 4 oz or less read $7.34 per order at one unit and $3.64 per order at four or more — as recorded, a four-unit order cost about half a one-unit order. Re-reading the rate card those rows cite, its fee tables are laid out in columns headed 1-unit order, 2-unit order, 3-unit order and 4+ unit order; its surcharge footnote refers to the item's base fulfillment fee; and Amazon's MCF pricing page advertises a saving of up to 50% on per-unit fulfillment fees for multi-unit orders, which is what $3.64 against $7.34 is. The fee is charged per unit, banded by how many units the order contains, so four units of that item cost 4 × $3.64 = $14.56 — 98% more than one unit, not half. In all but two of those rows the amount was already right and only the unit was wrong, and the unit is what makes a row comparable to anything else. The two exceptions had also dropped a weight threshold the card prints: small bulky up to 30 lb is $18.08 + $0.75/lb above 2 lb, and large bulky up to 30 lb is $18.43 + $0.77/lb above 2 lb. Read without that threshold, the small bulky row overstates a 25 lb unit by $1.50, $36.83 against $35.33. The bulky tiers above 30 lb and the extra large tiers are printed as one rate spanning all four unit-count columns, and those rows now record that no multi-unit discount applies to them. Every row sourced to the rate card was re-read on 2026-08-17. No rate changed.
Three Flexport rows stated the wrong unit of charge. Reserve Storage month 1 was published as $15 per pallet per month; it is $15 per pallet, a one-time charge covering the first month — recording it as monthly implied it recurs at $15 when months 2–12 are $27.50. The EDI connection fee was published as $200 per month; it is $200 per month per active connection, so a merchant with three connections pays $600, and our row understated that by a multiple. The daily storage minimum was published as $0.10 per unit per day; the source says per DSKU per day. Separately, Reserve Storage months 13+ was labelled LAX-specific when $60 applies at every facility. Amounts were correct throughout; the units were not. In all four cases we held a second, correct copy of the same fee under our other Flexport label — the disagreement between our own two records is what surfaced them.
Walmart WFS return processing was published at $4.70–17.55 per unit with the note that it "mirrors standard fulfillment fee tiers". The amount was right; the note was not. Reading Walmart's returns table directly, returns are a separate schedule: $4.70 at ≤1 lb against $3.45 for fulfillment, and $1.25 per unit higher on every tier up to 20 lb. The two schedules become identical only from 21 lb up. Anyone using our note to estimate a light-item return from the fulfillment fee would have been low by $1.25 a unit. The conditions field now states the relationship, and this row carries a 2026-08-12 read date.
Two Flexport rows recorded a price range where the source announces a single change. The monthly minimum fulfillment spend was published as $500–5,000 with the note that it varied by account; the source states an increase from $500 to $5,000 effective 1 January 2026. The row now reads $5,000, keeping $500 as the amount it replaced and the date the change took effect. The daily minimum storage charge per DSKU changed the same way, from $0.01–0.10 to $0.10. Both figures were reachable on the page throughout; what changed is which reading we record. We hold two separately sourced sets of Flexport rows and they disagreed on this point — the disagreement is what surfaced it.
What counts as a correction
A rate we reported that was never accurate, a source we misread, a figure attributed to the wrong vendor, or a claim that outran its evidence. Routine updates, where a vendor changed a published rate and we refreshed the row, are recorded in the dataset's verification dates rather than here.
The 2026-08-10 entry sits on the line between those two, which is why it is here rather than left to the verification dates. Flexport did change the number, and it announced the change — so on one reading it is routine. But our row had described the minimum as varying by account, which is a claim about how the fee works, not just a number, and the source does not support it. Where an entry could go either way, it goes in the log. A corrections page that only admits the unambiguous cases is not measuring anything.
Spotted an error? Email data@ratecardlab.com. Verified fixes ship within a week and get logged here no matter how small they are.
Get these as they ship
Rather than checking this page, have it come to you. One email when a correction is logged, a vendor moves a published rate, or a company is added — nothing else, and nothing on a schedule. To come off, email data@ratecardlab.com and we delete the record.