# Data Terms | Commitments, Liability and Corrections

> What each statement on this site actually means, what we commit to and what we do not, and what to do when a record turns out to be wrong.

Source: https://luressource.com/terms/commitments/

Direct answer. Terms are only useful when they distinguish a promise from a disclaimer. This page separates the two, and states what happens when a published record turns out to be wrong. Key facts. 1) Terms are only useful when they separate a promise from a disclaimer. 2) The pattern is that every claim is a statement about what we did, not about what will happen. 3) Four commitments, each of which can be checked rather than believed. 4) Four things we do not commit to, and each of these is a limit rather than a reservation. 5) The published data is provided as information for a buyer to act on, not as a contract. What we commit to, and what we do not Direct answer Terms are only useful when they distinguish a promise from a disclaimer. This page separates the two, and states what happens when a published record turns out to be wrong. Key facts Terms are only useful when they separate a promise from a disclaimer. The pattern is that every claim is a statement about what we did, not about what will happen. Four commitments, each of which can be checked rather than believed. Four things we do not commit to, and each of these is a limit rather than a reservation. The published data is provided as information for a buyer to act on, not as a contract. Terms are only useful when they separate a promise from a disclaimer. Most notices blur the two, which is why buyers stop reading them. This page states what each sentence means in practice, and what happens when a published record turns out to be wrong. What each statement means in practice What the site claims, and what each claim actually obliges us to do. Statement What it means What it does not mean A record is published only after the four gates pass The build refuses to publish a record that fails a gate, and the withheld count is visible on the directory page That the factory will perform well on your order Records carry a review date The date is when the record was last checked, and a record past 90 days is due for re-check That the figures are current to the day Reference bands are drawn from sampled listings The band reflects what sub-categories in that family normally trade at, with the unit stated That it is a quotation, or binding on any factory Capacity figures come from a structured interview The factory stated the number on a call, and it is published as its statement That we measured the capacity ourselves Data is published in machine-readable form The same values leave the site as files, at stable URLs That they are a separate, more authoritative dataset The pattern is that every claim is a statement about what we did, not about what will happen. That is the honest form for a directory: the four gates were run and can be re-run; the interview happened and its answers were recorded. What none of it establishes is the quality of a future production run, which is a property of the run rather than of the company. Our commitments, stated as obligations Four commitments, each of which can be checked rather than believed. We run the four gates before publishing, and a record that fails is absent rather than pending. We re-check published records on a 90-day cycle and date every record with its last check. We correct or withdraw a record when it is shown to be wrong, and a withdrawal changes the published count rather than happening quietly. And we do not sell placement — no sponsored listings and no ranking for sale, which is what makes the reading order on the site carry information. Four things we do not commit to, and each of these is a limit rather than a reservation. We do not warrant a factory's performance, because a verification is a check on a company and a shipment is a different object. We do not warrant that a reference band matches what any particular factory will quote, because a price depends on a specification and a quantity we cannot see in advance. We do not provide legal, customs or compliance advice; the compliance pages describe how rules work in practice and say where the rule text governs. And we do not warrant that a third-party document is genuine — we can tell you how to check a certificate with its issuing body, which is a stronger position than asking you to trust our copy of it. Where liability sits, and why The published data is provided as information for a buyer to act on, not as a contract. That is not a formality: a directory that indemnified a buyer against a supplier's behaviour would be selling insurance rather than information, and it would have to price the risk into access — which is the model this site deliberately does not use. What we can offer instead is checkability. Every figure carries its source, every verification carries a date, and any claim on the site can be re-run by a reader. Where a buyer's decision turns on one of those claims, the useful protection is not a liability clause; it is that the claim can be verified independently before the order exists. Changes to the data and to the standard Two different things change, and they are worth keeping apart. The data changes continuously: records are added, updated and withdrawn, and reference bands are restated on the 90-day cycle. That is why every record is dated and why a copy of a page is not evidence of the current state of the site. The standard changes rarely and is announced rather than silently applied. The four gates, the disqualifying conditions and the rule that a failed record is absent rather than pending are published as a standard, and a change to any of them would be visible because the pages that state them would change. Where a change to the standard would alter the status of a published record, the record is re-assessed rather than grandfathered. If a record turns out to be wrong Tell us, and the record is corrected or withdrawn. Corrections are published rather than applied quietly, because a record that was wrong and is now right is more useful than one whose history is invisible. Withdrawals are visible through the published count on the directory page, so a shrinking directory reads as a decision rather than as an outage. Where the error is ours — a stale field, a figure whose source has moved, a claim we cannot re-source — the fix is on us and there is no charge or condition attached. Where the error was supplied to us by a factory and we published it in good faith, the record is still ours to fix: publishing it made it our claim, and the standard we apply to a factory's numbers is the same one we accept for our own. What each statement actually means Four sentences carry most of the legal weight on this site. This is what each one commits us to. Statement What it commits us to Prices are reference bands An aggregated range from sampled listings with a stated unit —never an offer, never a substitute for a supplier quotation. Verification is dated Every record shows when the 4 verification gates were last run and is re-checked on a 90-day cycle; a stale record is visible as stale. Supplier identity is gated Factory contact details are released after a trade account is approved, which keeps them out of public scrape. The data feeds are quotable JSON and Markdown twins may be cited with attribution to Cheery Supply Chain; the underlying records stay dated. What we commit to, and what we do not The four commitments below are the ones a buyer can hold us to. The right column is what we deliberately do not promise. We commit to We do not promise Publishing only records that passed the 4 verification gates That a factory will hold a price, a capacity or a lead time Dating every record and re-checking it every 90 days That a record is current between re-checks Stating the unit and the basis on every published price band That a band is a quotation or an offer to sell Answering buyer enquiries and data requests within 1 business day That an incomplete specification can be priced at all What should you do if a record turns out to be wrong? Tell us which record and which field, with whatever evidence you have. We re-run the relevant gate rather than editing the field by hand. If it fails, the record is withdrawn from the build —it disappears from the directory rather than being marked as disputed. The withheld count on the directory page changes, so the correction is visible rather than silent. Where this sits in the process This page is one topic out of the verification standard. The overview is Terms of use . Where to next Product catalogue Sample listings with price per unit Verified directory Factories that passed 4 verification gates How sourcing works Six steps, timing, failure modes Price benchmark Reference bands and MOQ tiers Updated 2026-09-12 Scope Fishing tackle sourcing Sources 0 cited Was this page useful? Yes, useful Not really