The sold item that is still for sale somewhere

01

The interval and its length

Applies to marketplace onlyown storefronthybrid

Between the moment an item sells and the moment the last surface stops offering it, there is an interval during which a second buyer can complete a purchase of an object that is no longer available. For stock held in quantity, that produces a backorder. For one-of-one stock, it produces a sale that cannot be fulfilled.

The interval has a length, and it is a property of a particular configuration — the channels in use, the integrations between them, and the caches in front of them. It can be observed directly in about half an hour, and until it is observed, its size is unrecorded.

02

Availability is an observation with a time on it

Applies to marketplace onlyown storefronthybrid

Commerce vocabularies carry the commercial half of this: offer availability is a property of the offer rather than of the object.¹ Product interfaces carry it as a transmitted field alongside price, condition, and media on identified products and variants.²

Neither supplies the observation time, which is the value a unique-inventory seller adds. An availability value with no timestamp does not indicate whether it is two seconds or two months old, and every downstream copy carries that same absence. The timestamp is what makes the value assessable by whoever reads it next.

03

Measuring the interval

Applies to marketplace onlyown storefronthybrid

The measurement takes one item that is live on more than one surface. Mark it sold in the system of record, then watch the public pages — the ones a buyer sees, rather than internal dashboards — until each stops offering it, recording the elapsed time per surface.

1. List every public surface where the object can currently be found, including any not directly controlled.
2. Trigger the removal the same way a real sale would.
3. Check each public surface against a clock until it stops being purchasable, recording the elapsed time for each.
4. Repeat once at a busy hour, since load is part of the configuration being measured.

Run against the camera, the exercise produces four lines, two of which have no elapsed time.

The two rows without an elapsed time record what has not been established, and each now has an owner and a next step. Before the measurement, all four rows were in that state.

Two findings recur when this is run for the first time. One surface is materially slower than the others, and it is not always the one expected. And a surface may not remove the item without a manual step that is not recorded anywhere, which is a finding about the process rather than about the interval.

04

Targets per fact type

Applies to marketplace onlyown storefronthybrid

A single target applied to everything moving through one pipeline sets the strictest case by the loosest one. A price that is an hour stale results in a correction. A sold one-of-one object that remains purchasable an hour later results in a sale that cannot be fulfilled. The two share a delivery path and not a cost.

Written as one figure for all four, the availability target is set by whatever governs the price file, which is the loosest input in the table.

05

A delivered update is not a changed page

Applies to marketplace onlyown storefronthybrid

A system can log a successful removal that did not take effect at the destination, and the internal record will read as correct. Caches, queues, approval steps, and eventual-consistency behavior sit between a delivered update and a changed public page, and none of them reports back into the sending system.

The check that covers that gap is looking at the public surface, which is what a buyer sees. The surface list is built once and kept beside the object record, and verification is a step in the removal procedure rather than a periodic audit, since a list reconstructed after a sale is a list assembled under time pressure.

06

What to leave at the old address

Applies to marketplace onlyown storefronthybrid

When an offer ends there are two options: delete the page, or leave one stating that the item is sold. A deleted page carries less information — every cached mention, saved link, and downstream copy of the old record has no route to resolving what happened, and that stays true indefinitely.

A page that remains and states the item is sold answers the question once, for a person or a system, at no recurring cost. It also covers the case this lesson measures: where a removal elsewhere ran late, the item is visibly sold at the address a reference is most likely to point at.

The notice states the sale plainly. A sold notice that leads with three similar items and places the sale below them restores the ambiguity the notice was there to resolve.

07

The measurement and what it covers

Applies to marketplace onlyown storefronthybrid

Availability is a property of the offer in the page vocabulary,¹ and a transmitted field in the product interface.² Neither defines an observation time, a removal interval, or a target, so those are recorded by the seller.

The measurement produces one elapsed time per surface for one configuration at one moment. It does not cover surfaces outside the seller’s control, which refresh on another party’s schedule, and it changes when a channel, an integration, or a platform release changes.