Blox Fruits stock should never be shown as current without an observed-at time, expected expiration, confidence label and stale-state rule. The official Roblox description says the dealer restocks random fruits every four hours, but this site still needs observer verification before publishing a live stock list.
Current stock rules
Blox Fruits stock is time-sensitive data. The official Roblox page states that the Blox Fruits Dealer restocks random fruits every four hours, while fruits can spawn on the map every hour and despawn after 20 minutes. That official cadence is useful, but it is not the same as a verified live Blox Fruits stock list.
The stock page should show two things at once: the latest observed stock and the reliability of that observation. A player who sees Blox Fruits stock needs to know whether the entry is verified, merely observed, already stale or temporarily unavailable. Without that label, a stock page can mislead players faster than a normal guide page.
Snapshot fields
| Field | Example use |
|---|---|
| Dealer type | Normal dealer or mirage dealer. |
| Fruit list | Stored as fruit IDs, not just display text. |
| Observed at | The time the stock was actually seen. |
| Expires at | The expected end of the four-hour window. |
| Verification count | Number of trusted observers who confirmed the same stock. |
| Confidence | Verified, observed, unconfirmed, stale or unavailable. |
| Source note | Screenshot, tester note or community report summary. |
Confidence states
Use these states for every Blox Fruits stock snapshot:
| State | Meaning |
|---|---|
| Verified | Two observers confirmed the same dealer stock before expiration. |
| Observed | One trusted observer submitted a timestamped stock snapshot. |
| Unconfirmed | A community report exists but needs review. |
| Stale | The expected refresh time passed, so it is no longer current. |
| Unavailable | Collection failed; do not keep a fake countdown active. |
Collection workflow
The recommended workflow is observer submission, second-observer confirmation, editorial publish, automatic expiration, stale archive and history chart. Blox Fruits stock should also distinguish normal dealer stock from mirage dealer stock because access and refresh behavior differ.
| Step | Action | Public result |
|---|---|---|
| Submit | A trusted observer records stock and time. | Hidden until reviewed. |
| Confirm | A second observer checks the same dealer type. | Can become verified. |
| Publish | Editor reviews timestamp and confidence. | Appears as current stock. |
| Expire | The refresh window passes. | Moves to stale history. |
| Archive | Snapshot is saved for frequency analysis. | Used on stock history pages. |
History and notifications
The stock history page should preserve every snapshot with dealer type, fruit IDs, observed time, expires time, submitter, verification count, confidence and source note. Notifications should wait until the stock workflow is reliable; otherwise alerts will spread stale information faster.
Notification signup should not ship before Blox Fruits stock has a stable history record. The first useful alert feature is not “ping every fruit.” It is a filtered alert that lets players choose fruit rarity, specific fruits, dealer type and confidence level.