Repository navigation
Stock Insights and Monitoring
GearBeacon records what it observes in the public regional catalog. It keeps fast restock detection while requiring repeated complete evidence for sellouts, price/status changes, and disappearance. It does not predict restocks or reserve inventory.
Every store check records its outcome and catalog evidence. A restock seen in a complete valid catalog is recorded immediately. Sellouts, ordinary status changes, price changes, and products disappearing from the catalog must match on two complete observations before GearBeacon commits the transition or queues an alert. While confirmation is pending, the dashboard keeps displaying the last-known-good value and Operations shows the candidate and observation count.
A product omitted from two consecutive complete catalogs becomes Unlisted rather than being silently removed. A later reappearance is detected immediately. Partial catalogs never advance missing-product evidence. HTTP rate limits honor Retry-After, and scheduled retries include jitter so multiple self-hosted installations do not retry in lockstep.
| Observation | Result |
|---|---|
| Complete valid restock | Recorded immediately |
| Sellout, ordinary status or price change | Requires two matching complete observations |
| First complete omission | Keep last-known-good state; show pending evidence |
| Second consecutive complete omission | Mark Unlisted |
| Partial catalog or failed fetch | Does not advance missing-product evidence |
| Reappearance | Detected immediately |
Operations shows each region's last/next check, errors, pending candidate, and observation count. Honor this evidence when interpreting a difference between the Store page and GearBeacon; a confirmation interval is intentional. Polling defaults to 60 seconds with a 30-second minimum, and upstream failures can extend the next attempt.
Open product details to see Stock insights. Choose a 7-, 30-, or 90-day window to view observed availability, recorded restocks, and observed available time. The timeline uses actual timestamps; Observation details provides dates and values as text. Unknown periods include time before monitoring began, restarts, failed or incomplete checks, overdue polling, and pending stock or price confirmation. Intervals cover consecutive observations with unchanged confirmed values; they do not establish what happened between polls. The most recent check is not extended forward to the present as known availability.
Price insights lists the lowest catalog price and the lowest catalog price observed while available for each window, plus the difference between the current confirmed price and your saved target. Comparisons use one SKU, Store region, and currency. Select an exact variant when a product has multiple variants. A missing price is not zero; an explicitly observed zero price remains zero. Catalog prices are not checkout totals and exclude shipping, additional taxes, and surcharges GearBeacon does not calculate.
For Any variant, readiness can be satisfied by one exact variant meeting both stock and price conditions. Price-history comparisons still need a consistent SKU; select a variant for meaningful minima rather than comparing different sizes or packs.
New insight history starts with complete checks after upgrading to 1.2.0. Earlier change records remain in Recent changes, but cannot reconstruct historical monitoring coverage or exact-variant prices. Windows with less retained history are marked Partial history; unknown periods are excluded from observed durations and minima. The application records no predictions of future restocks. History retention follows GEARBEACON_HISTORY_RETENTION_DAYS (365 days by default). Compact inventory intervals and regional monitoring intervals each have a 100,000-record limit per region; oldest intervals expire first. The chart shows at most 600 recent intervals and observation details at most 100, with a notice when limited; summary calculations use all retained observations in the requested window.
These are observed intervals, not continuous telemetry from the Store. A long monitoring gap, partial history notice, or limited chart is information about confidence, not proof that the product was sold out throughout that period. Retention affects insight history independently of Activity retention.
A ready purchase requires confirmed availability, any saved per-unit target, and remaining demand. Pending stock evidence, relevant pending price evidence, and stale monitoring coverage can make readiness unknown even while a card retains its last confirmed value. A collection needs every remaining member to qualify on that basis.
Quantities are a planning tool: public catalog availability does not confirm that the Store can fulfill the desired number of units. See Collections and Alert conditions.
Wiki home · Troubleshooting · Source repository · Releases · Report a security issue privately
Documentation covers GearBeacon 1.2.0 and the current source layout. GearBeacon is independent and is not affiliated with or endorsed by Ubiquiti Inc.
Start and install
Use GearBeacon
- Watchlist and Browse
- Collections and purchases
- Auto-buy setup and verification (dev)
- Alerts and notifications
- Email and webhooks
- Stock insights
- Activity and Operations
Configure and maintain
- Configuration reference
- Security and access
- Reverse proxy
- Backups and recovery
- Updates and rollback
- Troubleshooting
Develop