Verification method · status definitions
Verification status categories: documented, rejected, unavailable, blocked, and review required
A status word is useful only when its meaning is stable. The archive uses separate categories so inventory, access, and code responses are not collapsed into one misleading label.
Documented cart result
Documented means a normal permitted guest-cart event recorded the code, time, item context, storefront response, and visible cart change. It does not mean an order was placed, payment was approved, tax was calculated, or every item and visitor is eligible.
The term is intentionally narrower than “guaranteed” or “works sitewide.” It tells a reader that a specific event was observed and recorded while keeping the merchant’s current checkout as the authority for the reader’s own cart.
Rejected, unavailable, and blocked are different
Rejected means the normal storefront response did not accept the code in the observed cart context. Unavailable means a test could not be run because no currently purchasable product or other required non-sensitive condition was available. Blocked means the normal path required a control the method will not bypass, such as a CAPTCHA or account gate.
These outcomes should remain visible. Calling an unavailable item a rejected code creates a false negative. Calling a blocked path documented success creates a false positive. The archive becomes trustworthy only when it preserves the actual reason a verification event could or could not be completed.
Manual review required
Manual review required means the system encountered a storefront change, ambiguous display, or condition outside the approved cart-only method. The correct response is to pause public status refreshes and inspect the change—not to keep writing a new “verified today” date.
This category is a safeguard against false certainty. It makes the system resilient when a merchant changes inventory, checkout behavior, product labels, payment presentation, or anti-automation controls. A visible review state is more credible than a silent guess.
Status words should prevent false equivalence
A documented acceptance, an unavailable product, an ordinary checkout block, and an ambiguous result are not variations of the same event. Each answers a different question. “Accepted” describes a visible code response in a complete evidence context. “Stock unavailable” describes the absence of a suitable test item. “Blocked” describes a normal-path limitation. “Manual review required” describes an outcome that should not be machine-classified as success or failure.
Readers should not rank these words emotionally. An unavailable or blocked record can be more informative than an unsupported accepted badge because it accurately states what the test did not establish. The archive uses distinct categories to keep dates, screenshots, and public language aligned with what was actually observed.