Notification delivery
Review the customer notices a marketplace needs when bids change, orders move, pickup windows open, support cases need documents, and sellers have action items.
Bid Notices
- Outbid, top bid accepted, reserve met, ending soon, won auction, and lost auction notices link back to the exact item.
- Urgent bid notices show the current price, next bid step, time remaining, and whether a checkout review is ready.
- Quiet-hour overrides require a clear user choice before any external bid notice can be sent.
Offer Notices
- Buyer offers, seller counters, proof requests, bundle replies, trade replies, and offer expirations stay grouped by item.
- Accepted offers move into cart review with item, seller, price, handoff choice, and expiration timing preserved.
- Seller-side notices separate new offers, counter deadlines, buyer questions, and support holds.
Order Updates
- Order notices cover checkout review, paid state for future launch, packing proof, shipment handoff, delivery updates, and review eligibility.
- Receipt and refund notices keep order number, seller, item title, credits, fees, and support contact close together.
- Every order notice links to the order timeline so buyers can see the current step before contacting support.
Pickup Reminders
- Hub pickup reminders show location, release window, QR state, required identification, item proof, and pickup desk instructions.
- Local pickup reminders protect private address details until both sides have an approved handoff route.
- Missed pickup notices route to reschedule, support, or seller hold review based on the order state.
Support Notices
- Missing item, condition issue, delivery damage, refund review, seller response, appeal, and claim notices show the next required action.
- Document requests name the evidence needed: item photos, packaging photos, hub receipt, tracking event, or message history.
- Support fallback keeps case updates available in the account even when external delivery is delayed or blocked.
Template Review
- Each template needs subject text, body text, item context, destination route, urgency, privacy review, and owner approval.
- Templates must not ask buyers or sellers to send payment details, passwords, private documents, or off-platform contact details.
- Launch review should test templates on mobile so long item titles, hub names, and deadlines still fit.
Delivery Status
- The delivery log separates queued, sent, opened, delayed, muted, failed, blocked, and action-needed states.
- Failures create visible support work for urgent orders, pickup release, account safety, and refund deadlines.
- Owner review needs retry rules, rate limits, abuse controls, provider status, and rollback steps before launch.
Customer Fallbacks
- Critical notices always have an in-account fallback: inbox alert, order timeline, case timeline, or seller action list.
- Muted notices stay visible in notification history so customers can understand why an alert did not interrupt them.
- Staff can review delivery status without seeing private message content unless the case requires it.
Inbox & Alerts
Customer-facing bid, offer, pickup, seller, and support notices.
Notification Preferences
Quiet hours, urgent overrides, channel choices, consent, and alert controls.
Communications
Buyer alerts, seller messages, support notices, templates, and delivery review.
Service Health
Delivery states, provider checks, support pressure, and owner review.
Support Operations
Notice ownership, response targets, evidence handoff, and customer updates.
Receipts & Invoices
Receipt, refund, credit, and seller statement notices.
Current demo state
Delivery behavior is represented with guided records.
The page shows notice types, templates, delivery states, fallbacks, support ownership, and owner review without sending external email, SMS, or push notifications.
Future platform state
Live delivery needs approved services and support coverage.
Launch needs verified contact methods, consent records, approved templates, provider credentials, bounce handling, unsubscribe controls, retry rules, abuse limits, audit logs, and staffed escalation paths.