Renewal & Expiry Configuration
Configure automatic alerts and expiry rules for brand contracts
How Expiry Alerts Work
- System automatically checks membership end dates daily
- Alerts are triggered based on configured windows (90, 60, 30, 15, 7, 3, 1 days before expiry)
- Brand lifecycle automatically changes to "expiring" when within alert window
- Brand lifecycle changes to "expired" when past membership end date
- Expired brands have restricted operations (no product updates, no sample issuance)
Alert Windows
Configure when alerts should be triggered before contract expiry
90 Days Before Expiry
Alert triggered 90 days before membership end date
60 Days Before Expiry
Alert triggered 60 days before membership end date
30 Days Before Expiry
Alert triggered 30 days before membership end date
15 Days Before Expiry
Alert triggered 15 days before membership end date
7 Days Before Expiry
Alert triggered 7 days before membership end date
3 Days Before Expiry
Alert triggered 3 days before membership end date
1 Days Before Expiry
Alert triggered 1 days before membership end date
Notification Recipients
Configure who receives expiry alerts
Super Admin (HQ)
Global administrators receive all expiry alerts
Admin / Onboarding Team
Knowledge Center admins receive alerts for their brands
Automatic System Behavior
Actions performed automatically by the system
Expiring State
When a brand enters any configured alert window, its lifecycle state automatically changes to "expiring". Dashboard and brand list will show expiring badge with days remaining.
Expired State
When membership end date is reached, brand lifecycle automatically changes to "expired". The following restrictions are enforced:
- Product updates and content changes disabled
- Sample issuance requests blocked
- Portal access restricted to read-only mode
Contract Renewal
To renew an expiring or expired contract, admin must upload new contract documents with updated dates. Upon validation and approval, brand will return to active state with full access restored.