We start with primary sources
Technical claims start with the exact manufacturer record. Regional price and warranty may use an authorized seller.
How we choose
Editorial policy
How we check facts, keep money out of rankings, show what we do not know, and fix mistakes.
Our promise
We show the facts that can change an answer, such as budget, space, routine, sources, and estimates. The answer must stand without a paid relationship. A commission or sponsor cannot make a poor fit rank well.
How we publish
Evidence states stay separate
A specification is a product detail from the maker or an authorized seller. Estimated means we calculated a value from stated inputs.
An observed physical test means we used the exact product under a published test plan, with the test date and limits attached. Measured means a number has a stated tool, method, unit, and repeated runs.
We could not confirm this means sources conflict or a needed fact is missing. We keep these evidence states separate.
Money does not set the score
Commission rate, merchant availability, and sponsorship are not inputs to the recommendation score.
We show conflicts
We show product-version conflicts and missing measurements. We do not fill them with guesses.
Our rule for test claims
We call a product tested only when we physically tested that exact product and recorded the test. We do not turn a product detail, owner story, review roundup, or estimate into a hands-on claim.
Dates have a clear meaning
Checked dates show when we looked at a source. Updated dates show when we reviewed the page. Neither guarantees a current retail offer.
Our review steps
- Define the reader's question and the facts needed to answer it.
- Identify the exact U.S. product version and collect direct sources.
- Use common units without changing the source meaning.
- Separate required limits from preferences and estimates.
- Check every claim against its source and add important limits.
- Publish source and update dates. Revise the page under the corrections policy.
Software and human responsibility
Software may help organize product records, run formulas, find inconsistencies, and format drafts. It cannot create a product fact or firsthand observation. Espresso Receipt remains responsible for each published claim. Each claim must trace to a listed source, a disclosed model, or a documented test.
Who publishes this?
Espresso Receipt publishes the recommendations, articles, and catalog and handles corrections as an organization. No individual author or reviewer credential is currently published. Before an individual byline or reviewer credit can appear, a real person must confirm their name, relevant experience, review role, and conflicts.
Reviews and corrections
Brands may submit objective corrections with a public source. They do not receive editorial approval or a promise that requested language will be used.
Readers can report an error through the corrections page. We log material changes when they could have changed a recommendation, cost, fit decision, or safety-relevant understanding.