Quick answer: Before repeating a product launch claim, identify the exact model, version, market, announcement date and promised feature. Find the original maker’s announcement or documentation, then check current availability and terms in that market. A press release can establish what a company said; it cannot by itself prove independent performance, user experience or an award.
Source check: 3 October 2026. This is an editorial verification method for global readers. The US Federal Trade Commission (FTC) sources below illustrate how to examine claims and reviews in the United States; they are not a statement of law in every country.
1. Turn the headline into checkable claims
Separate “announced,” “available to order,” “shipping,” and “tested.” Record the maker and exact model; a name shared by several versions is not enough. Note the region, currency, configuration, preorder conditions and date. If the headline promises a comparison winner, write down the comparison set and metric before evaluating it. A claim that cannot be traced to a named source should be marked Needs editor verification in the draft, not presented as established news.
2. Start with the original source
Use the dated company newsroom post, product documentation, regulatory filing or support page that actually contains the claim. Link the exact page, not a search-results page. Quote the company as the source of its own announcement, and distinguish a proposed feature from a released one. For US advertising, the FTC’s advertising FAQ explains that material express and implied claims need supporting evidence. That guidance does not turn a maker’s statement into an independent test.
3. Check price and availability separately
Reopen the current official product or seller page for the relevant market. Record the checked date, model, price currency, taxes or fees if displayed, shipping or preorder wording, and any exclusions. Do not copy a launch-day price into an undated “current price” claim. The FTC’s online-shopping advice recommends checking product and seller details and total cost before buying. Its advice is US consumer guidance; market-specific purchase rights should be checked with the relevant local authority.
4. Treat reviews and tests as different evidence
A specification sheet supports a stated specification, not a measured battery life or durability result. For a test claim, identify who tested which model, under what conditions and when. Do not describe a desk review as hands-on testing. Read reviews across sources and consider recency and incentives; the FTC’s review-evaluation advice warns that a plausible-looking review is not proof of authenticity. Do not invent ratings, testimonial quotations or an expert panel.
5. Keep a small claim-to-source record
| Claim | Minimum record | Hold when |
|---|---|---|
| Launch or feature | Original announcement, model/version, source date and market | The announcement does not name that feature or market |
| Current price or shipping | Current official offer, currency, region and checked date | Only an old launch post or reseller rumor is available |
| Performance or “best” | Named test, method, comparison set and result date | Only promotional copy or unattributed numbers exist |
| Customer reaction | Attributable review with platform, date and disclosure context | Identity or incentive is unclear |
When evidence conflicts, show the discrepancy and its dates; do not average incompatible figures. When an important claim remains unsupported, narrow the headline or hold the claim for an editor. The site’s Product News archive is for dated, sourceable updates, while Guides explains repeatable checks. Read About for the site’s scope or use Contact and corrections to flag a claim needing review.
Leave a Reply