Not yet bound

Can I actually buy this right now?

ALS-COFFEE-1.3-STOCK-001

The engine can run this kind of check and a public product page can settle it — but THIS standard has not yet written the binding or put the entry through its adversarial pass. The obstacle is unwritten work in this document, not the evidence and not the engine. Each one names the engine capability that fits.

Why this is not yet bound

`in_stock` is a live engine ReqKind and public product data adjudicates it, so this is neither `advisory` (the evidence exists) nor `blocked` (the engine exists). No binding and no adversarial pass have been authored for this entry in this standard, so it is not `executable`; the obstacle is unwritten work in this document, not the evidence and not the engine.

Assertion

purchasable_now is_purchasable true

Applicability

applies when
any coffee product page a buyer can reach
signal
availability data in structured data or the variant list

Accepted evidence

  • variant_availability — at least one variant listed as available
  • structured_data — a JSON-LD offer availability value indicating stock

Explicitly insufficient evidence

What does not count, and why. Published because the omission is where a check quietly becomes a claim.

  • "in stock" in prose
    Marketing copy is not the availability field a machine consumer reads, and it is frequently left behind when stock changes.
  • a pre-order or back-order availability value
    The coffee is not immediately purchasable, which for a seasonal lot is a meaningful difference the buyer needs rather than a technicality.
  • "restocked" or "new arrival" badges
    These are recency signals rather than availability, and inferring stock from them is how a stale page reads as current.

Conflict rules

  • When structured data and the variant list disagree — then the engine reads structured data first and then the variant list, which is the precedence it already documents

Discrimination

Authored expectation: no prediction, confidence low. The numeric band this standard used to carry is not published at this grammar version.

Sellers routinely hide or unpublish sold-out products, so a page a buyer can reach is usually purchasable. Seasonal micro-lots and pre-order harvest releases give this a real non-zero rate in coffee, but not enough to reach the fifteen per cent floor with confidence, so it is published rather than run. If a later measurement puts it inside the band it should be promoted, and that promotion would be a strengthening change needing no attestation.

The numeric fail-rate band this reasoning was authored with is NOT carried at grammar 1.2 and is not reproduced here. Authored bands held 1 of 10 against this category's own sample and every miss was HIGH, so a direction derived from the band would inherit the error that condemned it (SCHEMA.md §9.3 step 3). The band survives in ALS-COFFEE v1.1 (standard_hash f8ec2780f60c38931913e5b6cd37506500c8462709209de7180ba6691d6137e7), which is byte-frozen and still served.

For a shopper

A coffee page you can reach is usually one you can buy from, so this rarely surprises anyone. The exception worth knowing is a pre-order for a new harvest, which is a real wait rather than a stock quirk.

For a merchant

Expose availability in structured data with a purchasable offer, and mark harvest pre-orders as pre-order rather than as in stock so a machine consumer does not promise immediate dispatch.

Grounding

  • Google Merchant Center product data specification (retailer_help_centre)
    that availability is a required feed attribute with a defined enumeration including preorder and backorder, which is why the distinction between in stock and pre-order is treated as material by machine consumers