Capability
The Check That Does Not Get Tired at Product Four Hundred
Statements in draft content are checked against available evidence and configured rules, and release is blocked when a claim cannot be supported.
The Question This Answers
What stops an unsupported claim reaching my website?
A checklist item asking reviewers to catch unsupported claims is honored for the first fifty products and skimmed for the next several hundred. That is not a failure of care. It is what happens to any control that depends on sustained attention at volume.
Why It Is a Gate, Not a Warning
The Claim Firewall blocks release rather than flagging for consideration. The argument is not that software judges better than a person; it is that software applies the same judgment to product four hundred as to product one.
What It Checks
- Whether a factual statement is tied to a passage in an attached source document.
- Whether a statement conflicts with another source covering the same attribute.
- Whether condition or commercial language is consistent with the product's recorded condition data.
- Whether statements fall into categories your organization has configured as restricted.
When It Blocks
A blocked statement is reported with the reason and the evidence it was checked against. The usual resolutions are to attach a source that supports it, revise the statement to what the evidence does support, or remove it.
Not a Regulatory or Legal Review
Boundaries
What This Does Not Do
Stated plainly, because knowing the edges of a capability is more useful than another list of benefits.
- It does not provide regulatory, legal, or clinical approval of any kind.
- It cannot detect that a manufacturer document is itself wrong.
- It checks statements against evidence. It does not judge whether a statement is commercially wise.
- It is not a substitute for human review; it is what makes human review tractable.
In Sequence
What Comes Before and After
Each capability hands something specific to the next. Following the chain is usually more useful than reading them in isolation.
Questions
Common Questions
Can it be turned off?
The gate on release is structural. What your organization configures is which additional claim categories are restricted, not whether unsupported statements can bypass the check.
Does it slow the workflow down?
It moves work earlier. Statements that would have failed review are caught before a reviewer spends time on them, which usually reduces total time rather than adding to it.
Private Beta
See This Working on Your Catalog
Capability pages describe the mechanism. A working session on your own products shows you how it behaves with your data, which is a more useful basis for a decision.