Advisory

Will this be roasted after I order, and how soon after roasting does it ship?

ALS-COFFEE-1.2-ROASTORDER-001

This question is worth asking but is not reducible to a check a page can settle. It is published as guidance, not as a test.

Assertion

roast_to_dispatch_bound is_stated true

Applicability

applies when
the seller makes a roast-to-order or freshness-at-dispatch claim
signal
product or policy text claims roasting on demand

Accepted evidence

  • product_description — a stated maximum interval between roasting and dispatch with units, plus a roast schedule and an order cut-off making it auditable

Explicitly insufficient evidence

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

  • "ships within 24 hours"
    The cleanest and most common trap in the freshness class: it is dispatch latency, not roast age. A bag roasted three weeks ago also ships within twenty-four hours, so any check matching a short interval near freshness language accepts a statement that constrains nothing.
  • "roasted to order" unqualified
    It describes the workflow rather than the latency and is compatible with the next scheduled batch being days away.
  • "we roast Mondays" with no dispatch commitment
    A Monday roast dispatched Friday loses four days, and the schedule alone conceals that.
  • a subscription cadence read as a roast-to-delivery bound
    Delivery every two weeks says nothing about the age of the coffee in any one delivery.
  • express or free two-day shipping
    Courier speed is substituted for roast recency, which is the substitution this entry exists to refuse.
  • a roast-to-order claim on a page where no roast date reaches the buyer
    The promise is then structurally unfalsifiable, because the buyer has no way to check the thing they were sold on.

Conflict rules

  • When the only quantified interval on the page is a shipping interval — then refuse the freshness reading; the tractable check here is negative rather than positive

Discrimination

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

Very few sellers commit to a roast-to-dispatch maximum with a cut-off, while many make an unqualified roast-to-order claim, so the assertion as specified would fail for nearly all of them. Its value is in distinguishing the two rather than in the pass rate.

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

Ships within twenty-four hours tells you when the parcel leaves, not how old the coffee is. The claim worth looking for names a maximum time between roasting and dispatch, and it is only checkable if the bag that arrives carries its roast date.

For a merchant

State a maximum roast-to-dispatch interval with units alongside your roast schedule and order cut-off, and print the roast date on the bag so the commitment can be checked.

Grounding

  • Shopify App Store listing for a coffee roasting-schedule application (retailer_help_centre)
    that roast-to-order fulfilment is a real tooled operational pattern on the platform this standard targets, with software existing to turn incoming orders into roasting schedules — so the claim describes a genuine workflow rather than only a marketing posture