Marketplace pulse board
Track new listings, bid spikes, timed drops, sold exits, and pickup-ready orders so buyers can pivot to the most realistic next action.
Bidding pressure rising
Graded sky-dragon card | reserve met | MintStack | 126 watching | open listing or create alert
Buy-now price trimmed
Creator graphics card | masked-serial checklist updated | insured shipping | 63 watching | open compare view
Pickup window opened
Restored pocket handheld bundle | accessory list visible | hub pickup window active | compare before bidding
Timed drop scheduled
Sealed strategy-card display | $143 opening bid | no bids yet | opens in 31 minutes
Sold listing closed
Slate canvas high-tops | sold at $118 | hub pickup completed | review and report windows visible
Saved-search hit
Compact graphics cards | 4 matches near pickup radius | 18 users watching | open compare view
Event Types
- The feed covers new listings, placed bids, ending auctions, price drops, sold items, pickup-ready orders, seller drops, report updates, and saved-search matches.
- Each event shows price context, watcher count cues, handoff path, seller context, and a realistic next action.
- Ended, sold, or unavailable items point buyers toward similar listings instead of dead ends.
Filters and Relevance
- Buyers can filter by followed sellers, saved searches, nearby pickup, watched auctions, price drops, category, and seller drops.
- Events tied to weak proof, restricted items, open review, or stale inventory stay out of prominent positions.
- Sorting supports newest, ending soon, nearby, most watched, price drops, and followed sellers.
Buyer Actions
- Save, compare, bid, buy now, ask a question, open seller, set price alert, and find similar appear only when the item state supports them.
- Review actions stay limited to completed purchases and won auctions.
- Report actions should open order-linked flows instead of public activity cards.
Privacy and Safety
- Public activity should never reveal private addresses, support notes, buyer identity, payment state, or sensitive account signals.
- Seller activity should respect mute controls, seller standing, restricted items, report pressure, and storefront limits.
- Location language should stay approximate unless the buyer opens a permissioned pickup or order view.
Service Health
- Operators should catch stale events, missing images, title-image mismatch, dead links, late auction closeout, empty groups, and noisy alert loops.
- Hub activity should reflect pickup windows, intake status, release readiness, and event staffing pressure.
- Activity can pause by category, seller, event type, or service area when a launch gate fails.
Hub Events
- Pickup-ready, intake-complete, release-window, packing-ready, local event, and no-show events should stay tied to the hub record.
- Hub events should show customer-safe timing, category, item proof, and pickup instructions without exposing staff notes.
- Operators can pause hub events when capacity, staffing, custody, or release rules need review.
Owner Review
- Owners should approve event labels, privacy rules, ranking logic, seller fairness, notification handoff, support links, and rollback controls.
- Launch review should verify that activity cards do not overstate checkout, payout, fulfillment, or support operations.
- Current activity is represented with static marketplace examples and no external notifications.
Suggested For You
Saved interests, nearby inventory, seller follows, auction timing, and privacy controls.
Price Alerts
Saved searches, watched targets, auction thresholds, local pickup matches, and quiet hours.
Bids Center
Active bids, top bid controls, won auctions, lost bids, reserve status, and closeout review.
Service Health
Route checks, listing quality, auction health, hub readiness, support pressure, and provider review.
Current demo state
Activity is represented with static marketplace events.
The demo shows new listing, bid, price drop, sold item, pickup-ready, seller drop, saved-search, buyer action, privacy, and service-health patterns using static examples.
Future platform state
Live activity needs account and inventory events.
Launch needs event storage, inventory freshness, bid state, saved-interest rules, notification handoff, privacy review, stale-event cleanup, support routing, and rollback tools.