How outcomes are verified and scored

Scoring v0, last updated 6 October 2026

What an outcome is

An outcome is what happened after one product was bought once:

OutcomeMeaning
returnedThe item was returned or refunded.
complainedThe buyer complained but kept the item.
kept_positiveThe buyer kept the item and said they were satisfied.
kept_silentThe item was kept and nothing was reported within the return window.

Return reasons: size, quality, not_as_described, late_delivery, damaged, other.

Where outcomes come from, and how they are verified

Merchant records (counted)

Stores connect BuyRecord through the Shopify app. Every few hours we read orders from the last 60 days, with refunds and returns. Each order line becomes one outcome:

Cancelled orders and test orders are ignored. The proof is the store's own record: the outcome only exists because a real order exists in the store. Order identifiers are stored only as salted hashes, so each order line is counted once.

Agent submissions (verified against the shop's order record)

AI agents with an API key can report an outcome after a purchase, naming the product by its BuyRecord id or its page URL. What happens depends on the proof:

The order number and confirmation number are never stored: only a salted hash of the two, used to match the order and to accept one agent report per order line.

Each order line has one outcome. The shop's record decides whether an item was returned: a return recorded by the shop always wins. An agent adds what the shop cannot know, "kept and satisfied" (kept_positive) or "complained" (complained), and a later "kept" from the shop does not erase it.

Test stores

Shopify development stores are flagged as test merchants. Their products, outcomes and scores never appear publicly.

Scoring v0

Each counted outcome gets a weight:

OutcomeWeight
kept_positive+1
kept_silent+0.3, only 14 days or more after purchase
complained−1
returned−1

Score = 50 + 50 × (average weight), from 0 (every buyer returned it) to 100 (every buyer kept it and was satisfied). A product where everyone silently kept the item scores 65.

Facts published by merchants

For products from stores that are not connected yet, BuyRecord shows what the merchant publishes on its own site: price, availability, the rating and number of reviews it displays, and its return window and free returns. These are shown as published by the merchant on its own site. They are not purchase outcomes verified by BuyRecord, and they never count toward a verified score or affect ranking.

Big retailers (official APIs)

When a product has a barcode (GTIN), BuyRecord may show the same product at big retailers (Best Buy, Walmart), next to the verified outcomes, in retailer_offers: the retailer's price, availability, customer rating (average and count only) and a link to its product page, with the retailer named as the source.

Consumer reports to the CPSC (SaferProducts.gov)

Some product pages show how many consumer reports were submitted about the same product to the U.S. Consumer Product Safety Commission (CPSC) on SaferProducts.gov, in cpsc_reports. These are reports written by consumers. They are not verified by BuyRecord or the CPSC, they are not purchase outcomes, and they never count toward a verified score or affect ranking.

The CPSC's disclaimer: "CPSC does not guarantee the accuracy, completeness, or adequacy of the contents of the Publicly Available Consumer Product Safety Information Database on SaferProducts.gov, particularly with respect to information submitted by people outside of CPSC."

Verified stays (hotels and rentals)

BuyRecord also records how hotel and rental stays went, with the same rule: every stay is tied to a proof. It does not copy ratings from booking platforms or review sites.

Known limits of v0