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:
refunded, or part of a return that was requested, opened or closed: returned, with Shopify's return reason mapped to ours (for example "size too small" becomes size, "defective" becomes quality, "wrong item" becomes not_as_described);
otherwise, once the category's window has passed (14 days): kept_silent.
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:
Shopify order: the shop's domain, the order number and the order's confirmation number (the random code shown to the buyer after checkout and in the confirmation email). Order numbers follow each other and can be guessed; confirmation numbers cannot, so only the buyer, or an agent acting for them, can vouch for an order.
If the shop is connected to BuyRecord, the order is looked up in the shop's records right away. If the confirmation number matches, the product is in the order and the order is neither cancelled nor a test, the outcome counts. Otherwise it is refused and nothing is stored.
If the shop is not connected yet, the submission waits as pending. When the shop installs BuyRecord, its first sync checks it against the shop's orders; matching submissions then count, others are rejected. Pending submissions expire after 180 days.
Confirmation email (any store or service, including outside Shopify): the agent sends the merchant's original order confirmation email, the order number and the product name. Merchants sign their emails cryptographically (DKIM). We check that the signature is valid, that it comes from the sender's own domain and covers the whole message and its date, and that the order number and the product name appear in it. The purchase date is the email's signed date. Nobody can change a signed email without breaking its signature.
The email is read in memory to check it, then discarded. It is never stored or logged. We keep the merchant's domain, the product name, the date, the outcome and a salted hash of the merchant, order number and product, so each purchase can be reported once.
Anyone who controls a domain could sign "receipts" for it. Merchants known only from confirmation emails are therefore published once their domain has been reviewed as a real, independent business. Their verified outcomes are recorded from the start and appear once the domain is approved.
Payment receipt (a reference or a PDF or screenshot, which anyone could produce): stored as quarantined and never counted.
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:
Outcome
Weight
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.
No score below 5 counted outcomes. The outcome count is always published with the score, with a confidence level: low under 10 outcomes, medium under 30, high from 30.
Top reasons: the three most frequent reasons among returns and complaints.
Store profile: return rate, complaint rate, and the share of outcomes citing late delivery or damage, also from 5 outcomes.
Scores and product pages are recomputed after every sync.
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.
Data comes only from each retailer's official API. BuyRecord does not scrape retailer sites.
Matching uses the exact barcode only, never product names.
Retailer data is shown as "published by the retailer". It is never counted in verified scores and never used to rank results.
It is kept only as long as each retailer's terms allow (72 hours for Best Buy, 24 hours for Walmart), then deleted.
Affiliate links: some retailer links may be affiliate links, and BuyRecord may earn a commission if a purchase follows. Each such link is marked (affiliate_link: true in the API, "affiliate link" on product pages). Commissions never affect which products are shown or their order.
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.
Source: the CPSC's official public database export, downloaded once a day. The whole copy is replaced each day, so a report the CPSC removes disappears here within a day. Reports appear on SaferProducts.gov about three weeks after they are submitted.
Matching: only by the exact barcode (UPC), or by the exact manufacturer model number (at least 8 characters with at least 3 digits) together with the brand. Family names such as a phone series are never used.
What is shown: the number of reports since 2024, how many state an injury or a death, and the most frequent problem types (for example overheating or breakage). Problem types come from a keyword classification of each report and are approximate.
What is never kept or shown: the consumer's own words, locations, ages, retailers and company comments. Only counts.
Brands are never ranked by number of reports: brands that sell more units receive more reports.
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.
Proof: the booking platform's original confirmation email (Booking.com, Airbnb, Accor), sent by the guest's agent. Its DKIM signature must be valid, cover the sender and date and the whole body, and come from the platform's own domains. The reservation number, property name, city and both dates must appear in the signed content. The email is read in memory once and discarded.
Timing: a stay is accepted only after its check-out date, and within 12 months of it. One report per reservation.
Properties are matched by the platform's own property identifier when the email has one (Booking.com page, Airbnb listing, Accor hotel code), otherwise by name and city; when unsure, a separate property is kept rather than merging.
Scoring: as for products: no score below 5 verified stays, confidence by number of stays, quarantined reports never count.
Available through the REST API (/v1/stays/...); not yet through MCP.
Known limits of v0
Only the last 60 days of orders are visible until Shopify grants access to full order history.
If any unit of an order line is returned, the whole line counts as returned.
kept_positive and complained come only from verified agent submissions.
Products known only from confirmation emails have no price band or category yet.
Scores are per product, not per variant (size or colour).