Log
Corrections
A site that publishes dated figures will get some of them wrong. What separates a reference from a blog is what happens next, and whether you can see it happen.
The log
| Date | Page | What changed |
|---|---|---|
| 2026-09-05 | HTS codes: reasonable care and penalties | Was: Negligent misclassification penalty given as the lesser of domestic value or four times the duties. Now: Negligence: two times the duties; gross negligence: four times; fraud: full domestic value, per 19 U.S.C. § 1592(c). The negligence and gross-negligence tiers had been conflated. Verified against the statute. |
| 2026-09-05 | Entry Type 11 vs Type 01 | Was: Postal shipments described as subject to a flat $80 / $160 / $200 per-package duty. Now: The flat option expired February 28, 2026; postal shipments are assessed ad valorem and, since July 24, 2026, require a bonded postal informal entry. The flat-duty transition period ended before the article was published. Verified against the CBP interim final rule of June 24, 2026. |
| 2026-09-05 | FBA shipment discrepancy claims | Was: Claim window presented as contested between 60 days and nine months. Now: Fifteen to sixty days from the shipment delivery date, under Amazon’s policy of September 5, 2024. The nine-month figure was the pre-2024 rule. Verified against Amazon’s announcement. |
| 2026-09-05 | FBA New Selection Program | Was: Described as a referral-fee discount on the first $25,000 in sales per new ASIN. Now: A referral-fee cap of 10% on the first 100 units and 5% on the next 100 units per new-to-FBA branded parent ASIN, from July 30, 2026. The dollar tiers belong to the separate New Seller Incentives program. Two Amazon programs had been conflated from a secondhand news summary. |
| 2026-09-04 | Amazon deal and coupon fees | Was: The $70-per-day-plus-1% structure described as a superseded arrangement. Now: That is the current structure for deals outside peak events (since June 2, 2025); peak events use $100 plus 1.5%, capped at $5,000. Two concurrent fee structures had been read as one replacing the other. Verified against Amazon’s March 2025 and July 2026 announcements. |
| 2026-09-04 | Amazon listing optimization | Was: Title limit presented as unresolved between 200 characters and 75 characters. Now: 75 characters in all categories except media since July 27, 2026, with a 125-character Item Highlights field; 200 was the January 2025 rule. Both figures were correct on different dates. The July 2026 change had not been incorporated. |
| 2026-09-04 | FBA storage fees | Was: A change effective July 1, 2026 raising the standard-size rate to $0.87 per cubic foot and moving the aged-inventory trigger to 180 days. Now: No such change occurred. Standard-size storage is $0.78 per cubic foot off-peak in 2026, and the aged-inventory surcharge has started at day 181 since 2023. The figure traced to a single vendor blog and to nothing Amazon published. Verified against Amazon’s 2026 fee pages. The same error was removed from the Walmart WFS and removal-decision guides. |
| 2026-09-04 | Low-inventory-level fee | Was: Threshold presented as uncertain between 28 and 35 days of supply. Now: 28 days, on both the 30-day and 90-day windows, per Amazon. The 35-day figure came from one vendor blog and does not appear in Amazon’s documentation. |
What counts as a correction
Anything that would change a reader's decision. A wrong fee rate, a wrong effective date, a misattributed source, an arithmetic error in a worked example, a claim that turns out not to be supported by the source cited for it. All of these get a dated note on the article and an entry here.
Fixing a typo, a broken link or a clumsy sentence is not a correction and does not get logged. Nothing about the substance changed, and a log that fills up with punctuation edits stops being useful for the thing it exists to record.
Updates are not corrections either
When a marketplace changes a fee, the figure that was published was not wrong — it was true on the date it carried. Those pages get a revised modified date and, where the change is material, a note explaining what moved and when. That is a normal part of maintaining a dated reference, and it is recorded differently from an error on our part. Platform-side changes are tracked on the fee and policy log.
What a correction looks like on the page
The wrong figure is replaced in the body text, so nobody reads the error by accident. A dated note is added at the foot of the article stating what the figure previously said, what it says now, and why it changed. The article's modified date is updated. Then it is logged here.
What does not happen: quietly editing the number and leaving the page looking as though it always said that. If a figure here moves, you should be able to find out that it moved.
How to report one
Email contact@fbatactics.com. The report is far more useful with three things in it:
- The page, and ideally the section or the sentence.
- What you believe the correct figure or claim is.
- Where it comes from — a link to the marketplace's own documentation is ideal.
Reports are read by the author. Where a correction is warranted, the aim is to publish it within 48 hours. Where it is not, you will get a reply explaining why, with the source the original figure rests on. Disagreement about which of several published figures is current is common in this subject and is usually worth the exchange — several pages on this site now carry a table of contested figures because two sources could not be reconciled.